What is the best way for an agency to report AI work to every client?
Report from the record, the same way for every client. Each job already produced its receipts as it ran; the report is a packet built from them: a plain summary, the step record, the source states, the client's recorded decision, and the next actions. One format, every client, no screenshots.
Agency reporting usually means an account manager reconstructing the month from chats, tickets, and memory, then writing it up persuasively. It is slow, it varies by who writes it, and a sharp client can tell it was assembled for the meeting. The alternative is to stop writing reports and start issuing them: the work's own record, packaged the same way every time.
The packet's discipline is what makes it scale. Every client gets the same six parts (the template below), generated from the same underlying receipts, so a client who learns to read one packet can read every future one, and your team stops inventing formats. The steps are checkable behind the summary, because the packet is a view over receipts, not a replacement for them. Where a step is marked not checked, the packet says so, which reads as confidence rather than weakness: agencies lose clients over discovered gaps, not disclosed ones.
The decision state closes the loop. Each delivery in the packet carries its acceptance state: accepted, flagged with the reason, or pending with the release on hold. Your status meeting becomes a review of exceptions instead of a recital, and the client's signature moment happens inside the record, where it stays available when the invoice is questioned in month four.
Template: the per-client reporting packet
1. Period summary in plain words: what shipped, what is in flight, what is blocked. 2. Work index: every job in the period, one line each, linked to its record. 3. Step record per job: steps, results, producer labels. 4. Source states: counts of resolved, not resolved, and not checked, with the not checked items listed as review actions. 5. Decisions: acceptances and flags with decider and date. 6. Next actions: what the agency does next, what waits on the client. Attach the packet export to the invoice it covers; keep the live links as the checkable originals.
Worked example
The packet's unit is public: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 shows one delivery as a client reads it, steps checked, acceptance recorded, release ok to release. An agency packet is that unit, repeated per job and rolled into the index above, which is why clients can audit a month in minutes instead of scheduling a call.
Frequently asked questions
Does every client get the same format, even small ones?
Yes, and that is the efficiency. A small client gets a short packet because their month was short, not a different format. One template, generated from the record, is what makes agency-wide reporting cheap enough to do weekly.
What do we do about work a client flagged?
The flag is in the packet with its reason and the response: redone step, new receipt, new decision. A flag handled inside the record closes the issue; a flag handled in email reopens it every time someone searches the thread.
Can clients compare our packet against the raw record?
They should. The packet links to the underlying steps and receipts, and the client can open any line and check it. A report that survives that comparison is the retention tool, not the summary.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
8. Agencies, clients, and handovers
- How do I buy an AI activity record for a whole project instead of separate chat logs?
- How do I pass proof of AI work through an agency chain to the end client?
- How do I report AI work done on a monthly retainer?
- How do I win clients by proving my AI work is real?
- How do I show a client AI work in progress instead of only at delivery?
- What proof should an agency give clients for AI-generated work?
- How does an agency hand over AI work to a client?
- How do I document my work so I can bill a client for it?
- How do I track the work my team does for clients?
- How do I show my manager what my team actually delivered this week?
- I run a dev shop. How do I put proof on every client build update?
- I am an agency owner. How do I get proof for every deliverable across all client accounts?
- I am an operations manager. How do I review AI work without reading every chat?
- How do I show a new manager the history of a project they inherited?
- What records should I prepare before holiday client handoffs?
- What records should a client receive when an AI project is handed over?
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