Direct answer

Agency Client Handover

An agency client handover is one link that ends the approval scatter. The link carries the scope that was agreed, every deliverable in its final version, the checks each one passed, anything still open, and a verifiable receipt for each recorded step. Every stakeholder on the client side opens the same page, with no account, and the named decision maker accepts the work or flags one specific deliverable. No more approval by reply-all, no more wondering which version the yes in someone's inbox was actually about.

Open a real one first: the worked example handover at zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 is open and waiting on its client. The accepted example, handover 45434a17-4afc-486a-9646-e689bcee4297, was an end-to-end audit handover that a client accepted, and that acceptance minted its own receipt on the record. Check any receipt free at the public verifier. Start your own at zambo.dev/handover.

Updated October 20, 2026.

What an agency actually hands over

Agency delivery is never one file. A campaign handover can carry ad sets and their final copy, landing pages, a media plan with placements and dates, social assets in several sizes, an email sequence, and a results report. A build handover can carry the site itself, content loaded into it, tracking setup, and training notes. Several people inside the agency touched different parts: strategy set the brief, creative produced the assets, media planned the placements, and an account lead promised the dates. The client is being asked to accept the combined result, not any single person's piece of it.

That is why the deliverables list has to be explicit, item by item, with the final version of each item named. Finished means the approved landing page at its live address, the ad copy as it will run, the report covering the agreed period, and the asset files in the formats the statement of work promised. Anything the agency still owes, or the client still owes the agency, goes on the open items list in plain words: the extra product photography, the legal review of one claim, the access needed for the next phase. A handover that hides open items buys a short celebration and a long argument later.

Campaign deliverables: final ad copy and creative, landing pages, media plan, social and email assets, each in its final version.

Build deliverables: the live site or build, loaded content, tracking and analytics setup, and handover notes for whoever maintains it next.

Reporting deliverables: the results report for the agreed period, the data behind the headline numbers, and the recommendations listed as open items for the client to accept or flag.

Standing open items: approvals still owed, assets still owed, and next phase dependencies, named instead of buried in a thread.

What clients check before they accept agency work

A client marketing lead checks the deliverables against the statement of work, line by line, because that document is what their budget was approved against. They check that the landing page says what the ads promise, that the campaign dates and placements match the media plan, that brand rules were followed, and that the report numbers match what they can see in their own accounts. A second stakeholder, often in legal or compliance, checks claims, disclaimers, and regulated wording. A third, often finance or a founder, checks one thing only: is this the complete set we paid for, and is anything we expected missing.

Stakeholders check different things, and they check them at different times, which is exactly why a single shared record matters. When each person reviews a different email attachment on a different day, their comments collide: legal edits copy that creative already finalized, and the marketing lead approves a page that media has since replaced. On one handover page, every reviewer sees the same versions, the same open items, and the flags other reviewers have already raised, so the second review builds on the first instead of restarting it.

Where agency acceptance stalls

Acceptance stalls first on version doubt. The client approved version two of the landing page in a thread, version three went live after an internal fix, and nobody can prove which version the approval covered. It stalls second on scattered sign-off: the marketing lead said yes by email, legal flagged one claim on a call, finance never replied, and the account team cannot tell whether the job is closed or still open. It stalls third on scope drift: the client asks for one more asset as part of the same job, the agency reads it as new work, and the acceptance of everything already delivered gets held hostage to that one dispute.

Each stall has the same root: the decision was never attached to the exact record it decided about. An email yes floats free of the files it approved. A call flag leaves no mark next to the claim it questioned. A scope argument reopens deliverables nobody disputes because there is no per-item decision to point to. The fix is structural, not motivational: put the exact deliverables in one packet, let the client accept the packet or flag one named item inside it, and let that decision be written into the same record, dated, with its own receipt.

The manual way, and how it fails at agency scale

The manual agency handover is a delivery email with a folder link, a PDF summary, and a request for confirmation, followed by days of chasing. It fails quietly. The folder link points to a living folder, so the files the client later opens are not necessarily the files that were delivered. The PDF summary describes the work but is not the work. The confirmation, when it finally comes, is a two word reply that names nothing. Months later, when a claim in an ad is questioned or a page is said to be different from what was approved, the agency reconstructs delivery from timestamps and memory, and the client reconstructs it differently.

Agencies feel this more than solo operators because the cast is bigger. The person who sent the delivery email may have left. The client contact may have changed. Internal handoffs inside the agency mean nobody personally holds the whole story of the job. A handover record does not depend on anyone's memory or continued employment: the packet is the story, readable by whoever inherits the account, on either side, long after the delivery week.

The handover way, step by step

Run the work through tools connected to Zambo, the verifiable work layer for AI, at zambo.dev/mcp, one endpoint with no key, 153 tools in total and 35 on the default surface. Work routed this way, whether it runs in ChatGPT, Claude, Cursor, Gemini, Grok, or another connected client, leaves a verifiable receipt for each recorded step. When the job is ready, assemble the handover at zambo.dev/handover: the agreed goal and scope at the top, the steps in order, the final deliverable for each step, the checks that ran, and the open items stated honestly.

Redact before you publish: client internal names, personal email addresses, and anything from another account come out of the packet. Then send the client one link. Stakeholders open it in a browser with no account. The named decision maker clicks Accept to close the job, and that acceptance is written into the record with its own receipt, or clicks Flag on one deliverable, which starts the fix conversation at that item with its output open. You cannot accept your own handover: the creating account is refused, which is what makes the client's acceptance worth showing to finance, to a successor account lead, or in a scope dispute.

Two real records, and what each one shows

The open worked example, bd7e5325-33fd-4c5e-b029-76b781fa2f51, shows a handover in its waiting state: steps in the packet, decision still owed. That is the honest state of most agency work in delivery week, and the page shows it without dressing it up as closed. Your clients will spend time on a page like this, checking items before the decision maker acts, and that checking time is the system working, not failing.

The accepted example, 45434a17-4afc-486a-9646-e689bcee4297, shows the other end. It was an end-to-end audit handover: the work ran, the packet was assembled, the client reviewed it and accepted, and the acceptance itself minted a receipt on the record. For an agency, that closed record is the asset. It closes the invoice conversation, it anchors the case study you are allowed to tell, and it is the baseline the next phase gets measured against. Present both examples to a prospect and you are showing a delivery process, not promising one.

What the record proves, and what it does not

A receipt on a step proves the saved result of that step was not changed after the fact. A stakeholder can check it free at zambo.dev/verify with no signup, and the check either matches the saved result or it does not. The acceptance receipt proves who accepted the packet and when, and that the decision was made by the client, not by the agency on the client's behalf. Together they settle questions of fact: what was delivered, in which version, and who said yes to it.

The record does not prove the campaign will perform, the creative is good, or the strategy was right. Performance lives in the client's own ad and analytics accounts, and creative judgment stays with the people paid for it. Nor does the packet replace the statement of work or the invoice: it sits between them, proving the delivery that the invoice charges for was the delivery the client accepted. AER-1, the open receipt format underneath, is an IETF Internet-Draft, draft-zambo-aer1-24, not a finalized standard, and the page says so because a record that overclaims would defeat its own purpose.

Variants: retainers, white label work, and phased projects

On a retainer, hand over monthly in the same shape: this month's deliverables, this month's report, this month's open items. A run of monthly accepted packets becomes the renewal file, showing a client exactly what a year of fees bought, month by month, each month closed by their own acceptance. In white label work, where the agency delivers through a partner, the packet protects the producing agency: the end client accepted specific deliverables on specific dates, even if the conversation ran through someone else's brand.

On phased projects, hand over per phase and let each phase close before the next begins. Phase acceptance is the gate that keeps a phase three argument from reopening phase one: the record shows phase one was checked and accepted as delivered, so later discussion starts from what changed since, not from a fresh dispute about old work. Large agencies can also hand over internally, account team to media team to creative team, using the same packet shape, so the client facing handover at the end is assembled from records that already exist.

What it costs

Public handovers are free to send and free for the client to open. For $0.99, a Day Pass covers 24 hours of full recorded work through the Zambo MCP, which is the practical way to run a delivery day: assemble the packet, run the final checks, and send the link inside the same paid window. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402. Frame it against the cost of one stalled approval cycle: one round of stakeholder chasing costs more in account time than a month of passes.

Honest limits

A handover only covers steps that ran through connected tools. Work produced entirely outside the record, a phone negotiation, a deck edited offline and never routed through Zambo, has no receipt, and an honest packet lists it as unchecked rather than implying coverage. The acceptance on the record is a decision record, not a contract amendment or a payment: keep the statement of work, the change order process, and the invoice doing their own jobs. And a receipt proves the saved result was not changed; it never proves the result was correct, on brand, or effective. The client still judges the work. The record settles what the work was and who accepted it.

Frequently asked questions

What is an agency client handover?

An agency client handover is how an agency hands a finished campaign, build, or reporting period to a client as one link: the agreed scope, every deliverable in its final version, the checks each one passed, any open items, and a verifiable receipt for each recorded step. Stakeholders open the link with no account, check the items, and the named decision maker accepts the work or flags one specific deliverable, which ends approval scatter across inboxes.

Who accepts an agency handover when the client has several stakeholders?

One named decision maker accepts, after the other stakeholders have reviewed the same packet. Legal can flag a claim, the marketing lead can flag a page, and finance can see the complete deliverable list, all on the one record, before the decision is made. Accept writes the decision into the record with its own receipt, including who decided and when. The agency cannot accept its own handover: the creating account is refused.

What should an agency include in a client handover?

Include the scope and goal exactly as agreed, every deliverable in its final version with live addresses where work lives online, the receipt for each recorded step, and the open items named with who owes them. Add reporting for the agreed period where the engagement includes it. Leave out internal notes, other client material, and personal contact details: redact before publishing, so the packet is complete about this job and silent about everything else.

How does an agency handover help with scope disputes?

It ties the client's acceptance to the exact deliverables that were in the packet on the date they accepted. When a later request is described as part of the original job, both sides can open the accepted record and compare: if the item is not in the deliverables list and not in the open items, it is new work, and the change order conversation starts from evidence instead of from two conflicting memories of a delivery email.

How much does an agency client handover cost?

Public handovers are free to send and free for the client to open. For $0.99, a Day Pass covers 24 hours of recorded work through the Zambo MCP at https://zambo.dev/mcp, which runs 153 tools in total with 35 on the default surface. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.

Related