Can I get a client-ready proof report without giving the client my raw chat history?
Yes. Send the handover, not the chat. A handover presents the job the way a client needs it: the steps in order, each step's saved result, the source states, and a place to Accept or Flag. Your prompts, drafts, dead ends, and raw chat history stay on your side of the link.
Redaction and sharing choices are explained below. Nothing here promises confidentiality or legal privilege; what you share is your decision.
Raw chat history is bad evidence and worse manners. It mixes the work with your thinking, your experiments, other clients' context, and the AI's false starts, and then asks the client to dig the delivery out of it. Clients do not want the excavation; they want to check the delivery. The handover is built as that check: a summary receipt over the job's steps, each step openable, each result recomputed in the browser.
What the client sees is chosen by the record's design, not by your redaction skills at midnight. Steps and their saved results. Which sources were resolved, not resolved, or not checked. The producer label on each step, so AI assistance is visible where it happened rather than confessed in general. And the decision state: pending until the client Accepts or Flags, which is recorded with the decider and the time.
Keep two boundaries in view. The record proves the saved results were not changed since they were saved; it does not prove the work was correct, and it does not make anything confidential by itself. If a step's saved result contains something sensitive, that step is the wrong thing to share: run client-facing work so its record is shareable from the start, and keep internal exploration in separate jobs.
Checklist: what the client sees, and what stays with you
The client sees: the steps in order; each step's saved result; source states (resolved, not resolved, not checked); the AI label recorded per step; the summary receipt; the Accept or Flag decision and its state. Stays with you: raw chat transcripts; prompts and instructions beyond what a step's record carries; drafts and discarded attempts in other jobs; other clients' work; your internal notes. Rule of thumb: if it is a step of the delivered job, it belongs in the handover; if it is your workshop, it does not.
Worked example
Open https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 as a client would. You can check all four steps and read the recorded acceptance without ever seeing a chat transcript, a prompt, or the producer's workspace. That separation, full checkability with zero raw history, is the feature.
Frequently asked questions
Will the client see that AI did parts of the work?
Yes, where the record says so. Each step carries the producer label recorded when it ran, so AI assistance is visible at step level. That honesty is usually what the client wanted: not a confession, a record.
Can I remove one step from a handover before sending it?
A handover presents the job's record as saved; quietly dropping a step would break the summary that ties the steps together and would surface the moment the client checks. If a step should not be shared, it belongs in a separate job, not in this delivery.
Is the handover link private?
The link is the key: anyone holding it can open the handover. Treat it like the delivery itself and send it through the channel you already trust for the work. Do not post it publicly unless the record is meant to be public.
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