My client is auditing a finished project. What evidence should I give them for the AI work?
Give the auditor the record, not a summary of it: the handover link for the project, the receipt for each step, the source states behind disputed outputs, and the recorded acceptance decision. Send the evidence offer on this page, mapped to the questions an audit actually asks, within one business day.
An audit request feels adversarial only when answering it requires archaeology. When the work ran through a recording connection, the answer is a link and an index. The handover shows the job as delivered: steps in order, each step's saved result, the producer labels, and the client's own acceptance decision with its date. Receipts behind the steps recompute publicly at https://zambo.dev/verify/ , so the auditor is not asked to trust your export of your own system.
The detail that separates a smooth audit from a hard one is the source states. Auditors rarely dispute that an output exists; they dispute what it rested on. A step whose sources resolved can be walked back. A step whose sources did not resolve was, correctly, flagged before delivery, and the flag is itself evidence of process. Steps not checked are shown as not checked. An auditor who can see the gaps trusts the rest of the record more, not less.
Send the offer even before the auditor asks for specifics; the template below maps each item to the audit question it answers and names the format. If the audit reaches work that ran outside the recorded system, say so in the same message and bound it precisely: which deliverables, which dates, and what partial records exist. Precision about the uncovered part is what makes the covered part credible.
Template: the audit evidence offer
Subject: Evidence pack for [project] audit. 1. Project handover: [link] (steps, saved results, acceptance decision and date). 2. Receipt index: [list or export] (each receipt checks at https://zambo.dev/verify/ ). 3. Source states: available per step on the handover (resolved, not resolved, not checked). 4. Contracts and invoices: [links], for scope and value. 5. Uncovered items: [list, or "none"], with the partial records that exist. Offer: a walkthrough call at the auditor's convenience; questions to [contact].
Worked example
The shape of item 1 and 3 is public: https://zambo.dev/handover/48479a33-d996-4419-a9c8-d1b9a55e62b9 shows a four-step job with one source resolved, one not resolved, and one not checked, readable by any auditor with the link. An evidence pack built from records like this assembles in an afternoon, not a fortnight.
Frequently asked questions
Should I wait for the auditor's specific questions before sending anything?
Send the evidence offer first. Auditors scope their questions to what they believe exists; showing the record's shape early shortens the audit and prevents fishing expeditions into material that has a checkable answer already.
What if part of the project predates my use of recorded work?
Disclose it in the offer, bounded by deliverable and date, with whatever partial records exist (files, messages, invoices). The contrast between the recorded part and the disclosed gap is exactly what makes an auditor trust the recorded part.
Can the auditor check receipts without my help?
Yes. The handover opens in a browser and each receipt recomputes at the public verify page. Your role is providing the index, not operating the check, which is the point of the format.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai