I am a freelance writer. How do I prove a published draft came from my work?
Prove lineage, not authorship in the abstract: keep the job's record from brief to publication, research steps with their sources, each draft version saved as its own step, and your edit steps labelled as yours. Review the receipt and actual deliverable before accepting a handover.
Writers meet this question in three costumes: a client who suspects the piece was bought or generated wholesale, an editor who needs the sourcing behind a claim, and the portfolio moment, where the published text is the only visible part of a long process. All three are answered by the same artefact: the lineage record.
Build it as the work happens. The brief is step one. Research steps carry their source states, which is what an editor checking a claim actually needs. Each draft is saved as its own step when it is finished, so versions cannot blur; the receipt for each (AER-1, IETF Internet-draft-zambo-aer1-21) fixes that draft's text at that date. Your substantive edits are steps with your label. The final step is the published version, with its link.
The chain this creates is the strongest form of the answer because it is also the most useful one day to day: the same record that proves lineage answers the editor's source questions, settles the client's process questions, and gives you a portfolio exhibit that shows the work, not only the result. Writers have always kept drafts; the change is that the drafts now sit in a record a stranger can verify instead of a folder only you can open.
Checklist: the writer's lineage record
1. Step 1: the brief, saved as received. 2. Research steps: sources named, states shown (resolved, not resolved, not checked). 3. Draft steps: every submitted version saved whole, one step per version, dated. 4. Edit steps: your substantive passes, labelled, with the changed draft as the saved result. 5. Final step: the published version and its URL. 6. Delivery: the handover link goes to the client or editor with the final draft. Keep the record with your contracts file for the piece.
Worked example
Sample: a feature article delivered in three drafts. The lineage record shows the interview notes step, research steps with four sources resolved and one not, draft one, the writer's restructure step, draft two, the editor's requested changes as a step, and the published link. A later question about a statistic in paragraph nine walks back to the research step that sourced it. Public handovers in this section show the step-chain shape. (Sample scenario; no live record is cited.)
Frequently asked questions
Does the lineage prove I wrote every word?
It proves the process the record shows: the drafts as saved, the edits as labelled, the sources as checked. If the AI drafted a section, the record shows that step too, and your edit steps show your work on it. Lineage is evidence about how the piece came to be, which is the honest and useful claim.
My drafts live in a document editor with version history. Is that not the same?
Version history is a strong internal record inside your account. The lineage record adds the parts documents lack: the research and its sources, the labels, and a check path (the handover plus public receipt verification) that an editor or client can use without your account.
What if the client publishes without crediting me?
The lineage record is your dated evidence of the work behind the published piece, kept in your own records. What you do with it contractually is your call; having it is the difference between a claim and a demonstration.
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