How do I build an annual AI work report for clients?
Build it from the year's job index, not from memory: every deliverable with its handover link and recorded acceptance, volumes and turnaround by period, the year's significant decisions and changes, and a short methods note on how AI was used. When the index was kept all year, the report is an afternoon of assembly.
Annual reports fail in December for January reasons: the year's work exists as scattered deliveries, and the report becomes archaeology. The index-first practice in this file exists precisely so this page's job is selection and framing, not excavation. If the index was kept, start there; if it was not, build the index first from invoices and handovers, accept the afternoon it costs, and let it be the last time.
The report's content follows what clients actually value in a year review: what was delivered (with the record links, so any line can be opened), what was decided (the acceptances, change notes, and scope calls, in their dated form), and what the pattern shows (volumes by period, turnaround, the work types growing or shrinking). The methods note earns its place: one honest page on how AI was used across the account, which tools for which work, and how the client checked it, because that page is the one forwarded inside client organisations.
Send it as its own handover and record the client's response on it. An annual report that itself gets accepted closes the year the way each deliverable did, and the acceptance becomes the first record of the next year's index.
Template: the annual AI work report
1. Cover: client, period, preparer, one-paragraph summary of the year. 2. Deliverables: every handover, dated, with its acceptance state; grouped by quarter. 3. Decisions: the year's acceptances, change notes, and scope changes, in date order. 4. Patterns: volumes by period, turnaround, work-type mix, one paragraph of interpretation. 5. Methods note: how AI was used, by work type, and how the client verified it (links to the verify path). 6. Next year: open items carried forward, each with an owner. Delivery: as a handover; the client's response recorded on it.
Worked example
Each deliverable row opens onto a record of the shape of https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 , accepted, its steps dated inside the year. A report whose every line resolves like that is read differently from a PDF of claims: the client samples two rows, finds them exact, and believes the other forty.
Frequently asked questions
Should the report include work the client did not accept or that failed?
Yes, in the decisions section, with its outcome recorded. A year report that omits the rejected and the redone reads as marketing; the complete one reads as an account, and accounts are what renewals are negotiated from.
How much interpretation belongs in the patterns section?
One paragraph, clearly framed as your reading. The report's credibility comes from its records; interpretation is welcome precisely because the reader can check the numbers it interprets, in the rows above it.
We have no index for this year. How bad is the rebuild?
One afternoon per substantial client, from invoices outward: each invoice finds its deliverables, each deliverable its handover, each gap marked honestly. Then adopt the January setup in this set so the rebuild happens exactly once.
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