Article 11: Technical documentation
Article 11 and Annex IV address technical documentation for high-risk AI systems. Your legal and product teams determine the required content and maintenance process.
VeriProof contribution
VeriProof evidence may support sections covering:
- application purpose, environment, and ownership;
- captured runtime activity and model references;
- governance policies and recorded results;
- human-review requirements and decisions;
- monitoring, exceptions, and remediation; and
- evidence scope and integrity verification.
These records are one part of the technical file. Add the system design, data methods, test results, and performance evidence.
Include human-factors analysis and change-management records where required. Assign an owner to keep the complete file current.
Prepare an update
- Define the system version and period.
- Export the relevant VeriProof records.
- Verify the export manifest and configured provider proofs.
- Reconcile the records with the customer-owned technical file.
- Record changes, approvals, limitations, and open actions.
Related guidance
Last updated on