Government contractors · Federal & state software delivery
For government software delivery, Microfilm captures your testing as you run it, signs each record, and maps it to the requirement it verifies — so the test descriptions, test reports, and requirement-to-test traceability your contract owes as deliverables assemble themselves instead of being reconstructed before delivery.
Government software contracts — defense, civilian federal, and federally-funded state programs alike — make traceable test evidence a condition of delivery: test descriptions, test reports, and a current requirement-to-test traceability matrix, owed as contract data items. Microfilm captures that evidence as you test, signs it, and maps each record to the requirement it verifies — so the deliverable is a by-product of the work, not a scramble before the delivery review.
Availability · Capture and signing are free forever on the desktop app. The self-building traceability matrix and the shareable live-link export are Team-and-up cloud features.
What Microfilm is · Microfilm is a desktop app and cloud service that records software QA testing as it happens and turns it into signed, tamper-evident, audit-ready evidence — readable by both human auditors and AI coding agents.
The pain
On a government program the obligation is plain: deliver test descriptions, test reports, and a current requirement-to-test traceability matrix as data items. But when the evidence lives in scattered screenshots, chat threads, and a spreadsheet someone re-keys the week before delivery, the deliverable is reconstructed from memory — slow to assemble, hard to attribute, and to the program office, a missing or unattributable artifact is a problem at the delivery review.
How it maps
Your testers run the work; Microfilm turns each step into the contractual test-evidence artifact it owes — captured, signed, and mapped to the requirement it verifies.
Each session is recorded against the requirement and test case it exercises — screen, narration, and what the tester observed — captured at execution, the raw material of the test descriptions and reports the contract calls for.
Every verdict is signed by the tester who ran it and written to an append-only log, time-stamped at execution — the attributable, tamper-evident record an acquirer can rely on, not a screenshot reconstructed later.
A failed requirement routes back to the ticket with what was observed and a link to the capture — so it’s closed with context, not a one-line note that stalls at the next review.
Requirement → test case → signed evidence stays linked live as the work happens, so the traceability matrix the contract owes is current by construction — and an untested requirement surfaces as a gap before the program office sees it.
The strongest version of the deliverable isn’t a static binder assembled at the end — it’s a scoped, read-only link to the live traceability matrix, where every requirement maps to the signed evidence that verifies it and the program office searches and confirms it themselves. Each verdict reads in plain language — “Verified — signed by [tester], unaltered since capture” — not a raw signature to decode. Access is scoped to the delivery and time-bounded, never a login to anything else. (Team plan and up.)
Your contract ↔ Microfilm
Government software contracts call for test-evidence artifacts as deliverables — by whatever name your contract uses. Microfilm doesn’t sign your contract or make acceptance decisions; it emits the artifacts those deliverables are made of, captured as the work happens.
Every requirement mapped to the test that verifies it, kept current through delivery.
Requirement → test case → signed evidence links maintained live, exportable — or shareable as a read-only live link — on demand.
Documented test procedures and results, delivered as contract data items.
Each session recorded against the requirement it exercises, with a signed verdict and observations, assembled into the test documentation the contract calls for.
Records the acquirer can attribute and trust at the delivery review.
An append-only evidence log where every verdict is signed by the tester who ran it and time-stamped at execution.
Evidence that every requirement was exercised across development.
Coverage that stays linked live, so an untested requirement surfaces as a gap before the program office sees it.
FAQ
No. Microfilm produces the signed, traceable test evidence your deliverables are built from — test descriptions, test reports, and a live requirement-to-test traceability matrix. Assembling and submitting the contract data items, and any acceptance decision, rest with you and the contracting authority; Microfilm holds no authorization or certification.
It gives the program office attributable, tamper-evident evidence mapped to each requirement — or a scoped, read-only live link to the traceability matrix they can search and verify themselves, with each verdict shown in plain language rather than a raw signature to decode.
Yes. Because requirements, test cases, and evidence are linked live, an untested requirement or a stale record shows up as a visible gap in the matrix before a delivery review.
Yes. The same test-evidence obligation runs through defense, civilian federal, and federally-funded state programs — Medicaid, benefits, and child-support systems among them. The artifacts and traceability are the same regardless of which agency owns the contract.
Capture and signing are free on the desktop app. The self-building traceability matrix and the shareable live-link export are cloud capabilities on the Team plan and up.
The artifacts and traceability Microfilm produces support your contractual test-evidence deliverables and the acquirer’s review; Microfilm holds no authorization or certification, and validation and any acceptance decision rest with the contracting authority. Whether your contract cites it as an STD/STR data item, a CDRL deliverable, a VRTM, or IEEE 1012 verification, the evidence trail is the same.
Create a workspace for your team, or download the free capture app and record your first session.