Linking Evidence to Controls
Uploading evidence is necessary but not sufficient. The critical step for audit readiness is linking evidence to the specific controls it supports. This is what proves a control is actually implemented — not just claimed.
Why Linking Matters
An auditor doesn't just want to see that you have documents. They want to see:
When evidence is linked to a control:
How to Link Evidence
From the Control
From the Evidence Item
From the AI System Detail Page
Control-Evidence Mapping Examples
| Control | What Evidence to Link |
| GOV-01 AI Governance Ownership | System record showing named owners (screenshot) |
| DEP-01 Instructions for Use Stored | Vendor's instructions for use document (PDF) |
| DEP-02 Human Oversight Assigned | Oversight owner assignment + training completion record |
| DEP-08 Logs Retained ≥ 6 Months | Log retention configuration screenshot + retention policy |
| TRN-01 AI Interaction Disclosure | Screenshot of disclosure notice as shown to users |
| VEN-01 Vendor Identified & Contract | Contract PDF or link |
| VEN-03 Vendor Security Evidence | SOC 2 report, ISO 27001 certificate |
| LIT-02 Training Completion Tracked | Training completion report |
Evidence Quality Indicators
Not all evidence is equal. Strong evidence:
Gap Analysis
Controls without linked evidence show as gaps in:
Best Practices
🔗 Link immediately: When uploading evidence, link it to the relevant control(s) right away
📋 One control, multiple evidence: A control may need several pieces of evidence (e.g., oversight assignment + training record + SOP)
🔍 Check the gap checklist: It tells you exactly which controls need evidence
✅ Approved and current: Only approved, non-expired evidence truly satisfies a control
📄 Export to verify: Generate an Evidence Pack to see how your evidence looks in audit format