What records should I be able to produce if a client requests all files and receipts behind a deliverable?
Be able to produce the production packet: the job record exported whole (steps, receipts, source states), the deliverable files as delivered, the inputs and client-supplied materials list, the change and decision history, and the acceptance record. If your index is kept, the packet assembles in hours; the readiness is the practice, not the scramble.
Scope: general information about record readiness, not legal advice. What you must produce, to whom, and on what timeline can be set by your contract and by law; your lawyer reads demands, this page builds the cupboard they are answered from.
The request arrives in two tones: cooperative (a client's audit, a regulator behind them, a new vendor taking over) and adversarial (a dispute warming up). The packet is identical in both, which is the point of preparing it as a standing capability: tone changes nothing about what you hand over, because what you hand over was assembled by routine, not selected under pressure. Selective production is where practices get hurt; complete production from an index is where they get believed.
The packet's contents mirror the deliverable's life: the record of its making (job export with receipts), the thing made (files as delivered, matching the acceptance), the materials it was made from (inputs list, including client-supplied items with their arrival dates), and the decisions around it (changes, approvals, the acceptance itself). Each element exists already in the systems this file builds; production is an export and an index walk, not an investigation.
Set your own service standard before anyone asks: the packet producible within two working days for any deliverable of the last contract period, tested annually on a random deliverable. The test is the difference between readiness as a claim and readiness as a fact, and it takes one staff member one afternoon a year.
Template: the production packet
1. Cover sheet: deliverable, client, request date, produced-by, contents list. 2. Job record export: steps, receipts, source states, complete. 3. Files as delivered: the exact delivered versions, with the delivery date from the handover. 4. Inputs list: third-party and client-supplied materials, with arrival dates and rights notes. 5. Decisions: change notes, approvals, the acceptance record. 6. Production log: who assembled the packet, when, and anything not producible, named plainly with its reason. Readiness standard: any deliverable's packet inside two working days; annual random test, result filed.
Worked example
The packet's core in live shape: a deliverable's record like https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 exports with its steps and its recorded acceptance together, which is items 2 and 5 arriving as one object. A practice whose deliverables all sit in records of that shape passes the two-day standard without effort, because production is a retrieval, not a project.
Frequently asked questions
Must we produce records for work a client has not paid for?
That is a contract and legal question, and demands with deadlines go to your lawyer first. The readiness point stands independent of the answer: whichever way the obligation resolves, you will be glad the packet exists and is complete before the argument starts.
What about records containing other clients' material?
The packet is per deliverable and scoped to it. Cross-client material enters only where a step genuinely touched it, and then it is flagged in the production log for your lawyer's eye before release, which is another reason the log exists.
How far back should producibility reach?
Match your retention schedule: contract period plus dispute window at minimum. Beyond the schedule, production becomes best-effort archaeology, and the schedule, set deliberately, is the defensible line.
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