Risk management
System context, identified risks, limitations and evidence gaps give reviewers a record to work from.
Resource / EU AI Act
Requirements need
an evidence trail.
Regulatory work is one reason to keep a good technical record. Epok helps connect system context, evidence and review decisions to the requirements your team is assessing.
Read Regulation (EU) 2024/1689Start with scope, not a checklist.
Applicable obligations depend on the system, intended use and your organisation’s role. Epok supports recording that rationale. The mapping below illustrates evidence preparation, primarily for high-risk systems; it is not a determination that an obligation applies or has been fulfilled.
ReferenceRequirement areaSupporting record in Epok
Data & data governance
Dataset Cards and linked evidence record data provenance, collection context and quality considerations.
Technical documentation
System Records and deterministic Evidence Pack drafts connect documented statements to stored sources.
Record-keeping
Linked training, evaluation and runtime evidence can contribute to the technical record. Coverage depends on what your team captures.
Oversight & performance
Reviewer states, evaluation evidence and recorded limitations support examination of oversight, accuracy and robustness.
Transparency
Role- and use-specific transparency actions and a draft Transparency Pack support review for customer-facing assistants.
Keep the source. Keep the open questions.
Gap Workbench controls show missing and accepted evidence. Evidence Pack drafts retain source mappings and reviewer state. These materials support internal review and conformity-assessment preparation; they do not establish compliance or replace counsel, a notified body or a regulator.
See the product behind the recordReference basis: Regulation (EU) 2024/1689. Check the official text, amendments and current Commission guidance for applicability and transition dates.
European Commission guidanceStart with one AI system
Build the record before you need it.
Discuss beta accessPrivate beta. A focused scope, agreed with your team.