Direct answer

Copywriter Client Handover

A copywriter client handover is one link that fixes the approved words in place. The link carries the brief, the research the copy rests on, the drafts in order, the final copy exactly as it will be published, and a verifiable receipt for each recorded step. The client opens it with no account, reads the final version against the brief, and accepts those exact words or flags one passage. It replaces approval by email reply, where the client says yes to a draft, someone edits it afterward, and the published text is nobody's approved version.

Updated October 20, 2026.

What a copywriter actually hands over

Copy delivery looks light, a document of words, and that lightness is the trap. Behind the final page sit the brief and its audience, the research into the product, the customer language, and the claims that had to be checked, the headline variants that were tested against each other in drafting, the drafts with client comments on each, and the decisions about tone that were made in conversation and exist nowhere on paper. The client is not really accepting a document. They are accepting a specific text, produced by a specific process, to speak in their name to their customers.

A handover packet makes that visible. The brief at the top, as agreed, including the claims the client supplied and stands behind. The research and drafting steps in order, with their outputs. The final copy presented as the deliverable, complete: headlines, body, calls to action, and the small text, captions, button labels, and error messages that projects forget until launch. Then the open items: the testimonial awaiting permission, the statistic the client is confirming with their data, the legal review of one claim, each named so acceptance covers everything except what is openly listed as pending.

What clients check before they accept copy

Clients read for three things. First, accuracy: are the product facts, prices, names, and claims right, and are the claims the ones they are willing to stand behind in public. Second, voice: does this sound like us, or like a copywriter's idea of us, a check that usually happens by reading aloud and listening for the sentence that jars. Third, completeness: is everything here, the landing page and the email and the short version for the ad, in matching words, or will someone on their team improvise the missing pieces later in a different voice.

They also check, often silently, what the copy replaced. A founder who wrote the original page will compare lines. A marketing lead will check the new copy against the messaging document. These comparisons happen against documents the copywriter may never have seen, which is why the packet's inclusion of the brief matters: acceptance is recorded against the brief the copy was written to, so a later claim that the copy missed a message can be checked against what was actually commissioned, not against every document in the company.

Where copywriter acceptance stalls

It stalls on the edited approval. The client approved draft two, their assistant fixed a few things while loading it, the designer shortened a headline to fit, and the published page now contains sentences nobody approved and the copywriter never wrote. When a customer complains about a claim, everyone reaches for the approved version and discovers it does not exist as a single object. It stalls on scattered feedback: comments in a document, changes in an email, a voice note with three more edits, and the copywriter's honest uncertainty about whether the current draft includes all of them.

It stalls, most painfully, on scope memory. The project was a landing page; the client remembers the email sequence being included; the copywriter remembers it being quoted separately. Because delivery and acceptance happened in chat threads, there is no deliverables list with a decision on it to consult. The handover creates that list as a matter of routine: what was briefed, what was drafted, what is final, what is open, and the client's acceptance of exactly that set, recorded once, readable forever.

The manual way, and why email approval is not approval

The manual handover is a document link and a message asking for sign off, and the sign off, when it comes, is a reply that says approved, or perfect, or ship it. That reply names nothing. It does not identify the version, the date of the draft it refers to, or whether the small text was included. Shared documents make it worse, because the document keeps changing after approval: the approved text and the current text share a link and a title while quietly diverging, so the approval ends up attached to whatever the document says today.

Copywriters absorb the cost of this informality in revision loops. Without a fixed approved version, every later edit request can be framed as a correction of something that was never right, rather than as a change to something that was accepted. A fixed packet reverses the framing with evidence instead of attitude: here is the text, here is when you accepted it, here is the receipt under the record. New edits are welcome, priced as new work or covered by the revision terms, but they start from the accepted words.

The handover way, step by step

Draft and research 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. Writing and research assistance in ChatGPT, Claude, Gemini, Grok, or another connected client leaves a verifiable receipt per recorded step. At delivery, assemble the handover at zambo.dev/handover: brief, research, drafts with the feedback each answered, the final copy as the deliverable, and the open items.

Redact anything that belongs to another client or an unpublished plan, then send one link. The client opens it with no account, reads the final text, checks any receipt free at zambo.dev/verify, and accepts those exact words or flags one passage, so a revision request arrives with its target already named. You cannot accept your own handover: the creating account is refused, which makes the acceptance on the packet a genuine client decision on a specific text, the thing email approval only gestures at.

• Put the brief at the top, including which claims the client supplied and owns.
• Show drafts in order with the feedback each draft answered, behind the final copy.
• Present the final copy complete: headlines, body, calls to action, and microcopy together.
• Name open items such as permissions and pending confirmations, so the accepted text is the whole delivery.
• Keep other clients' work and unpublished plans out of the packet entirely.

Two real records, and what each one shows

The open worked example, bd7e5325-33fd-4c5e-b029-76b781fa2f51, is a packet in the state most copy sits in during approval week: finished, sent, and waiting for the client to actually decide. The accepted example, 45434a17-4afc-486a-9646-e689bcee4297, was an end-to-end audit handover whose client reviewed the record and accepted it, minting a receipt for that acceptance. Audit writing and copywriting share the same delivery risk: words that will be relied on later must be identifiable exactly as they were when they were accepted.

For a copywriter, the accepted record is also a portfolio with permission built in. It shows a real client received, checked, and accepted your work, in full, with the process visible. Shown to a prospect with identifying details handled properly, it demonstrates something a sample folder cannot: not just that you can write, but that your delivery process ends in a recorded yes, on a named text, on a known date.

What the record proves, and what it does not

A receipt proves the saved result of a step was not changed after the fact, and any reader can confirm it free at zambo.dev/verify with no signup. Applied to copy, that means the final text in the accepted packet is the final text that was saved when the packet was made: if the words differ later, they were changed later, by someone, and the packet is the baseline that shows it. The acceptance receipt proves who accepted that text and when.

The record does not prove the copy will convert, rank, or persuade: performance depends on the offer, the audience, and the channel, and no honest copywriter promises otherwise in a delivery document. It does not prove a claim in the copy is true: claims supplied by the client remain the client's, which is why the packet notes who supplied them. It is not a contract or a rights transfer. AER-1, the open receipt format underneath, is an IETF Internet-Draft, draft-zambo-aer1-24, not a finalized standard.

Variants: web copy, email sequences, and brand messaging

A website copy handover should present the copy page by page in the order a visitor reads, with headlines and microcopy included, because approval of a page the client read as a document will be tested against the page as built. An email sequence handover should present the sequence in send order with subject lines, since the client is accepting a timed argument, not five separate letters, and a flag on email three should not reopen email one. A brand messaging handover should weight the source material: the approved phrases, the banned phrases, the voice examples, because that packet becomes the document the client's whole team writes from.

For retainer copywriters, hand over monthly in the same shape and let the accepted packets accumulate into the client's copy library: every published text, as approved, findable in one place. When the client asks, a year later, what exactly the spring campaign said, the answer is a link, not a search through a departed employee's inbox.

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, enough to finish a delivery: final draft assembled, packet built, link sent. 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. One revision loop correctly identified as new work, instead of absorbed as a fix, covers the cost many times over.

Honest limits

Frequently asked questions

Related

• Freelancer client handover: one link your client accepts or flags
• Client sign off template: the fields a sign off record needs
• Designer client handover: final files, rounds, and a real approval
• Client acceptance form: get copy sign off in writing
• Client approval page: the deliverable acceptance record
• Proof of work for clients: attach it to the invoice