What evidence should I keep in case a client threatens legal action over AI-assisted work?
Keep five things from the start of every job: the agreement and scope, the deliverables exactly as sent, the step receipts with their source states, the client's recorded acceptance, and the full correspondence. Preserved in original form, that set answers the questions any claim about AI-assisted work actually turns on.
Scope: general information about organising evidence, not legal advice. If a claim has been made or threatened in writing, involve a lawyer in your jurisdiction early; this list helps that first meeting go faster.
Legal threats over AI-assisted work usually reduce to three factual disputes: what was agreed, what was produced and how, and what the client accepted. Evidence kept from day one answers all three without reconstruction. The agreement set: the contract or proposal, the scope messages, and every agreed change, each with dates. The production set: the step receipts, which fix what the AI produced at the time it produced it, and the source states, which show what the outputs rested on, including anything unresolved that was flagged before delivery.
The acceptance set is the one freelancers most often lack: a recorded client decision on the delivered work, with its date, bound to the exact version accepted. "They seemed happy on the call" is not an acceptance record. The correspondence set completes the picture: the full thread, exported, not the highlights.
Two habits make the sets real. First, preservation discipline: originals unchanged, fixes delivered as new versions, nothing deleted when a relationship sours. Second, separation: keep a copy of the whole set in storage you control, because evidence that lives only inside platforms and chat tools is evidence you rent. The checklist below is written to be completed per job, in minutes, while the work is fresh.
Checklist: the five evidence sets, per job
Agreement set: contract or proposal; scope thread; agreed changes with dates. Production set: receipt index for the job; source states per step; the tools and producer labels as recorded. Acceptance set: the handover link; the recorded decision and its date; the version identifier accepted. Correspondence set: full exported thread; delivery message; any complaint and your reply, in order. Storage set: one folder per job, two copies in storage you control, named [client]-[job]-[date]. Complete at delivery, not at dispute.
Worked example
The production and acceptance sets in one public object: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 shows steps with saved results and the client decision recorded with its date. A job file built around records like this one is what "kept from day one" looks like when the other sets are added around it.
Frequently asked questions
The threat has already arrived and my records are thin. Now what?
Preserve everything that exists today, in original form, and write a dated account of the job from the records you have. Do not reconstruct receipts you never made; a candid, bounded record serves you better than an invented complete one, with your lawyer and with the facts.
Do receipts prove the work was good or original?
No, and this page does not claim otherwise. A receipt proves the saved result was not changed since it was saved. Quality and originality are argued from the work and the process record, which is why the source states and your own steps belong in the sets.
Should I send the evidence to the client when they threaten me?
Send the handover and the acceptance record through your lawyer's guidance if a claim is live. The evidence sets are kept so that first conversation is short; who sends what, and when, is a legal decision, not a records decision.
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