The document that settles what is in, what is out, when something counts as done, and what a change costs.
Use this template — freeNo card. The template opens in the editor.
Most scope disputes are not disagreements about the work. They are two people remembering a conversation differently. A scope of work is worth writing precisely because it removes the memory from the argument — and the out-of-scope column does more of that work than the in-scope one.
In scope / out of scope
the two columns the whole document exists for
Numbered terms
change control and acceptance criteria, cross-referenced
Pricing table
what the scope costs, and what a change costs
Cover
both parties and the date
Timeline
phases, milestones and dependencies
Diagram
the delivery process
Variable fields
names and dates from one entry
Send the document as a link rather than an attachment and it reports back: when it was opened, which sections held attention and for how long, what was skipped, and whether the reader came back on a later day.
It measures what was on screen and for how long. It cannot tell you whether someone read a word, and it does not claim to — and every recipient can see exactly what is recorded, from a link on the document itself.
A proposal argues for the work. A scope of work defines it, once the argument is won — which is why this one is written to be referred back to rather than read once.
Yes. Variable fields carry the client name and dates through the document, so reusing it is one entry rather than a search and replace.