How do I document scope changes so a client can't dispute them later?
Document each change before you do the work: a short written change note naming what is added or removed, the price effect, and the schedule effect, agreed by the client in writing and attached to the job's record. Review the receipt and actual deliverable before accepting a handover.
Scope creep rarely arrives as a decision; it arrives as a sentence in a call ("while you're at it") that both sides remember differently at invoice time. The defence is decided in that moment: pause the addition, write the note, get the agreement, then do the work. The note takes three minutes and is the only version of the change that cannot be renegotiated by memory.
The note's four fields are the fields disputes actually turn on. What changes, in concrete deliverable terms. What it costs, including "included, this once" when that is the truth, because a free change recorded as free cannot later be billed or denied. What moves: the deadline effect, stated even when it is "no change." And the agreement: the client's written yes, or their recorded acceptance where the change rides on a handover step.
Keep the notes with the job, numbered, so the final invoice can cite them line by line: original scope, change 1, change 2. When the work itself is recorded step by step, changes land as new steps on the same record, visibly later than the original steps and under their own dates, which is the chronology a scope dispute is really about.
Template: the scope change note
Change note [number], [date], job [name]. Change: [the deliverable added, removed, or altered, in one or two sentences]. Price effect: [amount added / no change / included this once]. Schedule effect: [new date / no change]. Agreed by: [client name], [date], via [message or acceptance on the job record]. Filed with: the job's record and the invoice file. Rule: no note, no work; the note precedes the change, never follows it.
Worked example
Sample: mid-project, a client asks for a second language version of a delivered report. The note reads: Change 2, adds the translated version, price effect +[amount], schedule effect delivery moves two days, agreed by the client the same afternoon. At invoice time the line is cited, not argued. On recorded work the added version also appears as later steps on the job, the shape visible in the step lists of the public handovers across this section. (Sample scenario; no live record is cited.)
Frequently asked questions
The client agreed on a call and resists paperwork. What do I do?
Send the note as a summary of the call and ask for a one-word confirmation in reply: "Confirming what we agreed: [note]. Reply yes and I will start." A confirmed summary is written agreement, and the small friction now is cheaper than the dispute later.
Small changes feel too minor for a note. Where is the line?
The line is price or schedule: any change that touches either gets a note, however small. Pure clarifications inside the agreed deliverable do not, and the note habit stays light enough to survive because of that line.
We already started the changed work without a note. Now what?
Write it today, dated today, marked as confirming the change agreed on the call of [date], and get the confirmation before the next change. A late note is weaker than a timely one and far stronger than none.
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