What to put in a scope of work (and why a handshake isn't enough)

The first person who built a bridge probably said "we need a bridge." Their mate asked how. "We'll figure it out."

Two people and a pile of rocks, fine. A $20,000 remodel where the client assumed the railings were included, not fine. Somebody eats that, and it's usually you.

Nearly every job that goes sideways goes sideways the same way. The work was good. The problem was that two people had different pictures in their heads on day one and nobody wrote it down.

A scope of work is not a contract lawyer's job

People hear "scope of work" and picture twelve pages of clauses. It doesn't need to be that. It needs to be the shortest document that leaves no room for two readings.

If you write nothing else, write these five things.

1. What's included

List the deliverables, not the activities. "Design and build a five-page website" is an activity. "Home, About, Services, Contact and one blog template, built and live on your hosting" is a deliverable. The second one has an end. The first one doesn't.

Be specific about quantities. Two rounds of revisions. Twelve cameras. Forty edited photos. A number is a boundary; an adjective isn't.

2. What's specifically not included

This is the line most people skip, and it's the one that does the work.

It feels cold to write. In practice clients like it, because they finally know exactly what they're buying. And the exclusions you write are the ones you've been giving away for free:

• "Includes the site build. Does not include copywriting or photography."
• "Includes two rounds of revisions. Further rounds quoted separately."
• "Includes standard fixtures. Client-supplied fixtures installed at cost."

You are not being difficult. You are answering, once, in writing, a question that would otherwise come up halfway through the job when you're tired and it's easier to say yes.

3. The price, and what triggers a new one

The total matters less than the sentence next to it. Something like: work beyond this scope is handled as a written change order with its own price, approved before it begins.

That single line converts every future "can you quickly…" from a favour into a quote. It doesn't make you say no. It makes the price the answer instead of your goodwill.

4. The deposit and the payment terms

A deposit isn't about cash flow, though it helps. It's the moment the client commits. Someone who won't put money down before you order materials is telling you something worth listening to.

Say what the deposit reserves, when the balance is due, and what happens if it isn't.

5. Dates, described honestly

Don't promise a date you can't control. "Good-faith estimate, may shift for scope changes or delays outside our reasonable control" is both true and enough. A date you miss costs you more trust than a range you hit.

The part people get wrong

A scope of work only does its job if the client has actually read it and said yes before the work starts. A document you send afterwards, when there's already an argument, is not a scope. It's evidence in a dispute you're already losing.

Five minutes at the front. Every time.

What "signed" should mean

Whatever you use, you want a record of three things: who agreed, when they agreed, and exactly what they were looking at when they did. That last part matters most, and it's the one an email thread handles worst — the document gets edited, re-sent, edited again, and afterwards nobody can say which version was the agreed one.

Keep the version they signed. Not a copy that's been touched since.