What proof should an agency give clients for AI-generated work?
Give the same three-part proof on every deliverable: the handover, showing the steps and what each rested on; the decision record, where the client accepts or holds on that same object; and the export, so the client keeps the evidence in their own files. One standard, every account, no exceptions for small jobs.
Agencies improvise proof per client until a dispute prices the improvisation. The standard on this page is deliberately small enough to survive contact with a busy studio: three parts, attached to the delivery itself, identical whether the job is a landing page or a quarterly campaign.
Part one, the handover: the job's steps in order, saved results, producer labels, and source states where research underlies the work. Part two, the decision: the client's acceptance or hold recorded on the handover, by the client, with its date, which closes the "we never approved that version" class of argument at birth. Part three, the export: the record in files the client keeps, because evidence that lives only in the agency's systems is evidence the client rents.
The standard's commercial value is uniformity. Account managers stop assembling bespoke proof packs. Clients learn one reading pattern and apply it across every engagement. And when work passes through sub-agencies or freelancers, the chain rule from this cluster applies: forward the record, add your layer's steps, never summarize it away.
Checklist: the agency proof standard
Per deliverable: 1. Handover link created from the job, steps and source states visible. 2. Delivery message names the link and asks for the decision on the record. 3. Client decision recorded (accept, or hold with the step named). 4. Export delivered or confirmed in the client's files. 5. Job indexed in the account's record index with the link and decision date. Account-level: the standard written into the delivery runbook; sampled monthly by the account lead for compliance.
Worked example
One deliverable's proof, public: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 carries parts one and two on a single object, steps plus the client's recorded decision. An agency whose every delivery opens like this has answered the proof question structurally, not rhetorically.
Frequently asked questions
Do clients actually want this much proof?
Clients want the option of it, exercised lightly. Most will sample a step or two and accept; the standard's value is that sampling is possible and the decision is recorded, which changes the relationship even when the record is barely opened.
What about white-label concerns, our brand versus the tool's?
The handover is the delivery object; present it inside your account's normal delivery flow and message. What the client experiences is your agency's standard, which is the brand asset being built.
Small jobs make the standard feel heavy. Where is the floor?
The three parts are the floor, and they are minutes at delivery because the record was built during the work. What scales with job size is the summary you write around the record, not the record itself.
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