Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
How to Export Your ADMT Decision Record: Producing the File a Reviewer Can Actually Read
The short answer: An export is the decision record in producible form: for any decision, the notice given, the decision and its date, the principal reasons and data summary, the explanation and its sent date, and every request and response — readable by someone who has never seen your systems, with the hash chain available to show the sequence has not been altered. The kit builds export into the workflow because retention without producibility is storage, not a record: Colorado's duty is to retain records that show compliance, and a record that cannot be shown shows nothing.
Check your duties and dates — free Build your first notice — free
What is the decision-record export? It is the packaged output of the kit's hash-chained record for a case, a period, or the whole register — the artefact you hand to an internal reviewer, an auditor, or your own future self answering a person's question a year later. The record it draws on is described in How to Keep ADMT Records for Three Years; this guide is about producing it well.
What a complete export contains, per decision
The export mirrors the six-item decision file: (1) the pre-use notice text as given, with its date; (2) the decision — type, state, date, outcome; (3) the principal reasons and data summary as captured at decision time; (4) the explanation with its sent date, where adverse; (5) the person's requests — opt-out, access, correction, review — with receipt dates; (6) the responses and outcomes with dates, including re-runs. Completeness is per decision, not per system: an export that has notices in bulk but cannot pair them to decisions fails its purpose.
Context items travel with the export where they explain the case: the notice text version in force, the reviewer identity for a review outcome, the exception position where an opt-out was not offered. Anything a cold reader would need to ask a follow-up question about should either be in the export or findable from it by reference.
Readable cold: the stranger test
Hand the exported case to someone outside the team — a manager from another department works — and ask them to narrate it back: what was decided, what the person was told and when, what they asked, what happened. Every place their narration stalls is a defect in the export, not in the reader. Internal codes without their meanings, reason labels without the underlying facts, dates without the events they belong to: these are the usual stall points.
Readable cold also means self-contained formats: documents that open without your production systems, in the order events happened, with the person's documents separated from system noise. An export that requires the tool vendor's dashboard to interpret has failed the deployer-control principle — your record must outlive and out-read your vendor relationships, as argued in Vendor vs Deployer.
Worked example: Elm Creek Family Services
Example — fictional business, real duty structure. Elm Creek is a fictional services provider that formalised its export practice after an internal review exposed the partial-chain failure. Its quarterly export routine now runs like this:
- Sample: each quarter, 25 cases are drawn at random from the period's roughly 600 decisions and exported in full — all six items per case.
- Stranger test: a manager from the finance team narrates each sampled case back; this quarter 24 of 25 narrate cleanly, and one stall (a reason code without its meaning) produces a template fix, not a blame.
- Integrity: every sampled export is verified against the hash chain at production: 25 of 25 verify in sequence.
- Scheduled export: the quarter's full record is exported and stored with its retention date (three years on), independent of the operational system — 612 decisions, complete chains.
- Request path: when a person asks about their case, the same per-case export is produced in minutes — this quarter it served 7 access answers and 3 reviews.
Integrity: showing the export is the record, unaltered
The kit's record is hash-chained: each entry's SHA-256 fingerprint incorporates its predecessor's, so an export can be checked against the chain — an altered or inserted entry breaks the sequence detectably. The export's job is to preserve that checkability: include the chain references with the entries, and verify the export against the live record at production time as a matter of routine.
Integrity answers the second question every reviewer asks (the first being 'show me'): 'how do I know this is what was recorded at the time?' A business that can answer both questions from the same artefact has a record; a business that answers the second with 'our database is reliable' has an assertion. The chain mechanics are explained in Hash-Chained Decision Records.
When exports happen: on request, on review, on schedule
Three triggers should produce exports without improvisation. On a person's matter: access answers, corrections, and reviews all draw on the case export — producing it should be a button, not a project, or response quality will vary with staff availability. On internal review: the quarterly register review samples cases from exports, not from live screens, because the export is what an outsider would see. On schedule: periodic full exports are the retention safety net — the record copied out of the operational system, stored with the retention dates, so a system migration or vendor exit never strands the chain.
Each trigger has the same acceptance test: complete per decision, readable cold, integrity verified. Build the triggers into the calendar with owners, the same way the deadline duties have owners — an export process that exists only in one person's habits is a single point of failure wearing a procedure's clothes.
Common export failures, and the fixes
Four failures recur. The unpaired bulk export: thousands of notices, no decision linkage — fix by exporting per case. The screenshot export: images of dashboards, unsearchable and unversioned — fix by exporting the underlying entries as documents. The partial-chain export: the decision without the follow-on requests — fix by defining the export as the full case, always. The vendor-locked export: a proprietary format needing the vendor's tools — fix by requiring a readable export in the contract, per the deployer-control clauses.
The kit's export exists to make all four failures structurally unlikely: per-case packaging from the chain, in readable form, under the business's own account. Whichever stack you use, write the four failures into your acceptance test and run it quarterly. Start from the plan that matches your volume, and see the documents an export contains by generating them in the free generator.
- Define the export as the full case: all six items, paired per decision, in event order
- Apply the stranger test quarterly — a cold reader narrates the case back; every stall is an export defect to fix
- Verify each produced export against the hash chain as routine, not as an audit event
- Wire the three triggers — person requests, internal sampling, scheduled full exports — with owners and dates
- Test your stack against the four failures: unpaired bulk, screenshots, partial chains, vendor-locked formats
Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.
Related guides
- How to Keep ADMT Records for Three Years: What Goes in the File and Why the Chain Matters
- Vendor vs Deployer: Who Owes the ADMT Notice?
- Hash-Chained Decision Records: Why Tamper-Evidence Is the Point of the Record
- Colorado AI Act Automated Decision Notices: What to Send
See all ADMT guides for the full set.
Frequently asked questions
What should an ADMT record export contain?
Per decision: the pre-use notice with its date, the decision (type, state, date, outcome), the principal reasons and data summary, the explanation with its sent date where adverse, and every request and response with dates — the complete case.
Why does readability matter if the data is complete?
Colorado's duty is to retain records that show compliance. A complete but unreadable export does not show anything to the person reviewing it. The stranger test — a cold reader narrating the case back — is the practical check.
How does the hash chain help an export?
Each entry's SHA-256 fingerprint incorporates the previous entry's, so the export can be verified against the chain: altered or inserted entries break the sequence detectably, answering 'how do we know this is what was recorded?'
How often should full exports happen?
On a schedule that matches your retention practice — the worked example uses quarterly sampling plus a full quarterly export stored with its retention date — and additionally whenever a person's case must be produced.
Who should be able to produce an export?
Named roles with export rights (in the kit, account seats), not everyone with database access. Production of the record is a controlled act, and the record contains personal data and decision reasoning.