Direct answer

Freelancer Client Handover

A freelancer client handover is one link your client accepts or flags. The link carries the whole job: the goal, the steps in order, the outputs, any open items, and a verifiable receipt for each step. The client opens it in a browser, checks the record, and accepts the job or flags one named step. No delivery call, no folder of attachments, no summary email they have to take your word for. This page covers what the client sees, how acceptance works, and the notes for each trade.

Open a real one first: the worked example handover at zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 is waiting on its client, and this accepted example shows the closed state. Check any receipt free at the public verifier.

Updated October 20, 2026.

What the client sees

The client opens one page, on the link you send, with no account and no signup. At the top: the goal of the job, in the words it was agreed. Below it: the steps in the order they ran, the output each step produced, and anything still open, listed as open instead of smoothed over. Each step carries its own receipt, produced when the work ran through Zambo, the verifiable work layer for AI. The client can check any receipt free at zambo.dev/verify: the check confirms the saved result was not changed after the fact.

What the client does not see matters just as much. Your internal notes stay internal. Your other clients stay invisible. Anything sensitive that touched the job, an email address, a phone number, a key in a transcript, is redacted before the packet is published. The record is complete about the work and silent about everything else. Run a job end to end at the live demo and open the record it produces, or follow a day of work at zambo.dev/today, before you send your first one.

How acceptance works

At the end of the packet sit two controls: Accept and Flag, and they belong to the client alone. Accept closes the job and writes the acceptance into the record with its own receipt, including who decided and when. Flag attaches the objection to one named step, so the fix conversation starts at that step, with that step output open, instead of reopening the whole job on a call. You cannot accept your own handover: the creating account gets refused, and so does the agent that did the work. That refusal is the feature. An acceptance that only the client could make is an acceptance you can show anyone later, next to the invoice, in a dispute, or on the next job pitch.

The two worked examples show both states. Handover bd7e5325-33fd-4c5e-b029-76b781fa2f51 is open, its steps in the packet, waiting on its client. Handover 45434a17-4afc-486a-9646-e689bcee4297 is the accepted example: status accepted, decided by the client, its steps checked. Same packet, two honest states, and the open one is not a failure: it is the record waiting for the only decision that counts.

Notes per role

The packet shape never changes. What changes is what a finished job looks like inside it, trade by trade:

Web developer client handover: the build, the checks it passed, and the deploy step, with the open items listing anything the client still owes you, like content or access.

Designer client handover: the final files, the rounds that produced them, and the decision on each round, so a later change request starts from the approved version.

Consultant client handover: the findings, the work under each finding, and the recommendations as open items the client accepts or flags one by one.

Contractor client handover: the completed stages in order, the record for each stage, and sign-off per stage instead of one argument at the end of the job.

AI automation client handover: the workflow, its runs with their receipts, and the handover of the running system itself, so the client can check what the automation actually did.

Copywriter client handover: the brief, the drafts, and the final copy, with the client acceptance on the exact version they approved.

Video editor client handover: the cuts in order, the notes each cut resolves, and acceptance on the final cut, not on a render three versions back.

Developer client handover: for contract and freelance developers, the repo state, the tests, and the delivery steps, chained on the same record the client accepts.

Agencies running the same routine across a roster will find the multi-client version on agency client handover.

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 recorded work through the Zambo MCP at https://zambo.dev/mcp, 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, which adds private links, your branding, and the acceptance record as PDF and JSON files. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.

Honest limits

Three edges, stated plainly. First, a verifiable receipt proves the saved result was not changed after the fact; it never proves the work was correct, well designed, or worth what you charged. The client still judges the work; the record just settles what the work was. Second, the packet only covers steps that ran through connected tools: work done entirely outside the record has no receipt, and an honest handover lists it as unchecked. Third, the acceptance on the record is a decision record, not a legal contract or a payment: pair it with your normal agreement and invoice, and let each document do its own job. AER-1, the receipt format underneath, is an IETF Internet-Draft (draft-zambo-aer1-24), not a finalized standard.

Frequently asked questions

What is a freelancer client handover?

A freelancer client handover is how a freelancer hands a finished job to a client as one link: the goal, the steps in order, the outputs, any open items, and a verifiable receipt for each step. The client opens the link in a browser with no account, checks the record, and accepts the job or flags a specific step. It replaces the delivery email, the folder of attachments, and the call to walk through both, and it works the same way for a web developer, a designer, a consultant, or any other solo trade.

What does the client see in a freelancer handover?

The client sees one page: the goal of the job at the top, the steps in the order they ran, the output each step produced, anything still open, and the decision controls at the end. Each step carries its receipt, and the client can check any receipt free at https://zambo.dev/verify/ with no signup. They do not see your internal notes, your other clients, or anything you redacted before sending: they see the record of their job, complete about the work and silent about everything else.

How does client acceptance work on a handover?

The client decides from the link you send, and only the client can decide. Accept closes the job and writes the acceptance into the record with its own receipt, including who decided and when. Flag attaches the objection to one named step, so the fix conversation starts at that step instead of reopening the whole job. You cannot accept your own handover: the creating account is refused, which is what makes the acceptance on the record worth showing to anyone later.

Does a handover work for my trade?

Yes, because the shape of delivery is the same in every trade: a goal, steps, outputs, and a client who has to say yes. A web developer hands over a build with its checks, a designer hands over files with the rounds that produced them, a consultant hands over findings with the work under them, a contractor hands over completed stages, an AI automation freelancer hands over the workflow and its runs, a copywriter hands over drafts with the brief they answer, and a video editor hands over cuts with the notes they resolve. The packet is identical; only the outputs inside it change.

How much does a freelancer 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, which adds private links, your branding, and the acceptance record as PDF and JSON files. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.