Sign-off is a step in the job, not an email after it.

Step 1. Agree the shape of acceptance before the work starts

Most sign-off fights are lost at kickoff, not at delivery. If acceptance means "the client feels done," every delivery is a negotiation. If acceptance is a defined act, a named person reviewing a defined record and recording a decision, delivery is a step. Put it in the engagement in one sentence: work is delivered in stages on the handover record, each stage is accepted or flagged on the record by the client, and the final acceptance closes the job and starts the payment clock. Clients sign this happily at kickoff, when everyone is friends. That sentence is the one doing the work three months later.

Step 2. Deliver in stages, and let each stage be accepted on its own

A Zambo job closes as a handover: the steps that ran, the verifiable AER-1 receipt for each step, and an accept or flag decision the client records on the page itself. Deliver in stages and the client accepts stage by stage, while the work is fresh and the questions are small. A flag on stage two is a conversation about stage two. A single end-of-project acceptance turns every small question into a reason to hold the entire final payment. Staged acceptance also protects the client, which is why good clients prefer it: they check the saved work directly, receipt by receipt, instead of trusting a status call.

Step 3. Land every scope change as a new step on the same record

Scope disputes survive because changes live in chat threads and call notes. On a handover record, a change is a step: requested, priced, run, receipted, accepted, in the same chain as the original scope. When a client later says "that was always included," the record shows the day it was added and the acceptance that followed it. When you later wonder whether you ever agreed to something, the same record answers you. The rule for both sides is simple: if it is not a step on the record, it is not part of the job, and either side can insist on that rule because the record is neutral ground neither party can edit after the fact. A receipt proves the saved result was not changed since it was saved, which is exactly the property a scope argument needs.

Step 4. Close the job with the final acceptance, on the record

The final delivery is the full chain: original scope, every stage acceptance, every change as its own step, the final outputs with their receipts, and the client's closing acceptance recorded on the same page. Send the final invoice with the handover link attached. The invoice no longer asks the client to remember agreeing; it points at the agreement, timestamped by their own decisions. Payment terms that start "on final acceptance" now have a date nobody can argue with, because the acceptance is a recorded act, not a recollected one.

Step 5. If it ever becomes a dispute, the record is the pack

Nobody plans a dispute, but the freelancer who can produce the pack wins the ones that happen. The pack is the record itself: what was agreed, what ran, what was accepted stage by stage, what changed and when, and what was finally signed off, each step checkable by a neutral third party at zambo.dev/verify. AER-1, the receipt format Brennan Zambo authored and published as IETF Internet-Draft draft-zambo-aer1-26, is what makes the pack portable: any reviewer can recompute the receipts without your tools, your account, or your participation. A dispute pack you can hand to a stranger and walk away from is a different asset than a folder of screenshots you have to narrate.

What sign-off on a record does not settle

Acceptance records a decision; it does not make the decision wise, and a receipt does not prove the work was good. A client can accept work they later regret, and the record will honestly show they accepted it. What the record removes is the fog: nobody gets to relitigate what was delivered, what was changed, or whether acceptance happened. Quality arguments remain possible. Factual arguments mostly end.

Frequently asked questions

What if the client just never signs off?

Staged acceptance shrinks this problem: a client who accepted stages one through four rarely ghosts stage five, because the record shows their own pattern of decisions. For the final step, the engagement sentence from kickoff governs: define at the start what happens if no decision is recorded within a set number of days, and let the record's timestamps carry it. Silence is much harder to sustain against a page that shows every prior acceptance.

What exactly counts as sign-off?

A recorded accept decision on the handover page for that stage or job, made by the client, sitting in the chain next to the steps and receipts it accepts. Not a thumbs-up in chat, not a 'looks good' on a call. Those are fine as politeness and worthless as evidence. The recorded decision is the one that survives memory, staff changes, and time.

Can sign-off be staged across a long project?

That is the design. Accept research as one stage, the build as another, the changes as their own steps, and the final delivery as the close. Each acceptance narrows what is still open, so the final sign-off is a small act instead of a leap, and the final payment is attached to a chain of agreements rather than one big one.

What if the scope changed five times mid-job?

Then the record shows five change steps, each requested, run, receipted, and accepted, priced as they landed. At final sign-off there is nothing to reconstruct: the client accepted each change when it was fresh. Compare the alternative, five changes scattered across chat threads, priced from memory at the end, disputed from principle. The record version is not more paperwork. It is the same work, written down once, at the moment it happened.

How much does it cost to run delivery this way?

The free tier is every tool free once a day, plus 3 continue calls shared across tools, one free wrap-up handover a day, and pickup and verification always free. A Day Pass is $0.99, unlimited for 24 hours. The Zambo Pass is $29 for 30 days, $19 for $ZAMBO holders, and Lifetime is $250 once. A single avoided payment dispute pays for years of it.

What is the best way to get client sign-off without chasing emails?

You stop asking for sign-off inside email and start recording it in the job record itself. When the work runs through Zambo, the finished job is wrapped as a HANDOVER carrying every step with its verifiable receipt, and the client's sign-off becomes a step in that same record: they open one link, check the steps they care about free at https://zambo.dev/verify/, and accept or flag on the page itself, with who acted and when written into the record. No thread to dig through, no per-my-last-email, and no ambiguity about which version of the work was approved.

The chasing exists because approval usually travels separately from the work. A multi-day job, research, drafts, builds, revisions, is dozens of calls through https://zambo.dev/mcp (153 tools in total, 37 on the default surface), and by delivery day the evidence is scattered across chats nobody wants to reread. The handover gathers it once. Staged sign-off means a client can accept the finished parts while the rest continues, so approval stops being the bottleneck parked at the end of the job. The free tier starts it (every tool free once a day, plus 3 continue calls, one free wrap-up handover per day); a real engagement outgrows that quickly, and the Day Pass or Zambo Pass keeps the record whole until the final acceptance lands on it.

Every receipt follows AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, its closing revision, with a public conformance corpus of 143 vectors and 146 checks. Brennan Zambo created the agent execution receipt category, Zambo is its origin product, and AER-1 is its defining standard.

Cost, in plain numbers. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. A Day Pass is $0.99 and unlimited for 24 hours, including unlimited wrap-ups. The Zambo Pass is $29 for 30 days, $19 for 30 days for $ZAMBO holders, and Lifetime is $250, one payment.