Feature · Audit export
Requirements, acceptance criteria, test cases, evidence, and signatures are linked as the work happens — not assembled in a spreadsheet the week before an audit. When the audit comes, you export a ready package instead of reconstructing one.
Availability · Team and up — the self-building matrix and audit-package export are cloud features.
The problem
The traditional path is a scramble: chase down who tested what, hunt for screenshots, rebuild a traceability matrix by hand in a spreadsheet, and hope nothing was missed. It’s days of work, it’s error-prone, and it produces a document that’s stale the moment it’s finished.
How it works
Requirements link to acceptance criteria, criteria to test cases, test cases to signed evidence and the tester who attested it. The matrix is a by-product of doing the work — not a separate document someone maintains.
When an auditor or customer asks, produce a structured package — the matrix plus the signed evidence behind every verdict — without reopening sessions or reconstructing history.
Because the links are live, gaps are visible: a requirement with no test case, a criterion never verified, a test that’s gone stale. You find the hole before the auditor does.
When something breaks, the record shows when it last passed, who ran it, and what they saw. The audit trail doubles as the fastest way to understand a regression.
Where it fits
Audit export is what makes the discipline upstream worth it. It draws directly on signed evidence and the sessions behind them (session capture), and shares the same structured links that coding agents read (agent-ready context).
FAQ
It maps each requirement to the acceptance criteria, test cases, evidence, and sign-offs that verify it — so you can prove every requirement was tested and see any that weren’t. Microfilm builds this continuously as testing happens rather than after.
The traceability matrix plus the signed, append-only evidence behind each verdict — the requirement, its acceptance criteria, the test cases, what the tester saw, and the attestation that signed it.
No. The self-building traceability matrix and audit-package export are cloud capabilities on the Team plan and up. The free desktop app captures and signs evidence locally.
Yes. Because requirements, criteria, test cases, and evidence are linked live, untested requirements and stale tests are visible as gaps in the matrix.
Create a workspace for your team, or download the free capture app and record your first session.