Skip to main content
A Control evidence (by framework) pack organizes Zespan’s recorded facts under a framework’s named controls, instead of under the agent-centric sections a Compliance Card uses. Three framework mappings are available: SOC 2, the EU AI Act, and ISO/IEC 42001.
A control evidence document describes evidence about your AI systems, as observed by Zespan, and which obligation or control it supports. It is not a conformity assessment, an audit, or a certification, and it never states that an obligation is met.

SOC 2

Choosing Control evidence (by framework) and the SOC 2 framework maps evidence to three Trust Services Criteria controls: Each control’s narrative is explicit about scope. CC6.1, for example, states plainly that the section “reports what Zespan recorded; it does not assess whether those assignments were appropriate.” A control document reports observed facts — never a judgment about whether those facts satisfy the control.

EU AI Act

The EU AI Act (Regulation (EU) 2024/1689) mapping — “Evidence that supports EU AI Act obligations” — organizes evidence under these obligations:

ISO/IEC 42001

The ISO/IEC 42001:2023 mapping — “Evidence that supports ISO/IEC 42001 AI management system clauses and Annex A controls” — covers Clauses 4 to 10 and Annex A controls: Each control’s evidence comes from the same recorded sources as the EU AI Act mapping — access and roles, agent profiles, models used, guardrails, evaluations, approvals, change history, incidents, AI data governance settings, and event logs. The generated document lists the sections behind each control.

Manual evidence required

Some obligations can’t be observed by Zespan — your AI policy, instructions for use, or the transparency notices in your own product, for example. Those controls are marked Manual evidence required in the coverage list and in the document, with the list of documents you need to attach yourself (the You supply column above). A control can have both collected evidence and manual items.

Coverage

Before you generate, the Compliance page’s Coverage for this period panel runs the same evidence queries each control would use and shows, per control, whether at least one of its sections produced records for the period you’ve chosen — without rendering or storing a document. Each control shows one of three descriptive states: evidence, no evidence for this period (along with which sections came back empty), or manual evidence required. A gap in the underlying data is visible before you generate — and possibly hand to an auditor — the document itself. GET /v1/compliance/frameworks returns each control’s reference and manualEvidence, and coverage results include manualEvidence and the status manual_required. This mirrors what the generated document itself does at render time: a section with no records for the period prints the literal text “No evidence available for this period.” rather than being silently omitted.

reviewedOn / reviewedBy

Every control evidence document — in every format — carries a review-attribution line for its framework mapping: This is deliberately printed on the document itself rather than buried in a settings page. Every mapping was authored and reviewed by Zespan engineering only. Treat a generated control-evidence document as a well-structured starting point for your own evidence collection, not as a substitute for your auditor’s, lawyer’s, or assessor’s own judgment about what satisfies your obligations.

Next steps

  • Evidence packs — the two document kinds and how to generate one
  • Verification — re-checking a generated document’s citations