Scope creep starts in the proposal: how to write scope a client can't misread

The project is three weeks in when the client mentions "the other pages". You never discussed other pages. They're sure you did. Both of you reread the proposal, and the line that should settle it says "website redesign".

Scope creep is usually blamed on clients. More often it starts in the proposal, in a line that meant one thing to you and another to them. The fix is less about firmness during the project and more about precision before it.

Where the misunderstandings come from

Outcomes written as scope. "A website your team can update" is a goal, not a deliverable. It doesn't say how many pages, which templates or how much training.

Quantities left out. "Page designs" could mean five or fifteen. "Revisions" could mean one round or as many as it takes.

Maybes treated as yeses. Something mentioned on the call ("maybe photography?") ends up half in, half out: not priced, but not excluded either.

Copied wording. When the proposal starts from the last one, last client's assumptions ride along with it.

Write countable lines

Each line of scope should pass a simple test: could someone who wasn't on the call tell whether it's been delivered?

• "Design and build of 8 pages (home, 3 location pages, 4 service pages)" passes.
• "Website redesign" doesn't.
• "Two rounds of revisions on the designs" passes.
• "Revisions as needed" doesn't.

Countable lines also make pricing honest, because each one can carry its own price.

Turn the maybes into choices

Anything the client might want, but hasn't decided on, belongs in the proposal as a priced option they can add, not in a vague sentence and not left out. "Photography: half-day shoot, available as an extra" settles it now. If they add it, it's in. If they don't, it's out, and both of you can see that.

Say what's not included

A short list of exclusions is the cheapest protection you have: ongoing hosting, content writing, photography, third-party licenses, whatever usually causes the "I thought that was included" conversation in your line of work. Clients rarely object, and it saves both sides a hard conversation later.

Write down your assumptions

Most scope disputes are really assumption disputes. "The client supplies all page copy." "The booking system stays the one you already use." "Feedback within five working days of each delivery." When an assumption turns out wrong, there's a clear, calm basis for changing the plan or the price.

Agree how changes work, before you need to

Add one paragraph on what happens when the client wants something new: you'll confirm the extra work and its price in writing before starting it. Then follow it the first time it comes up. Clients learn the process from what you do, not what you wrote.

A quick self-check

Take your last proposal and, for each scope line, ask:

1. Could a stranger tell whether this was delivered?
2. Does it have a quantity?
3. Is everything mentioned on the call either priced, offered as an option or excluded?

Any line that fails is a future disagreement. Rewrite it now, while it costs nothing.

Where Accord fits

Accord is the proposal tool we make for consultants, agencies and freelancers. You paste your call notes, and it drafts the scope, deliverables and terms from what was said on the call. Every price comes from your own catalog and every total is calculated, never guessed by AI. Optional extras sit in the proposal for the client to choose, with live totals, and your client comments, approves or declines from one link. One honest limit: approval in Accord isn't a legally recognized e-signature, so if your contracts need one, keep that step.

Whatever you write proposals in, start with the next one: count every line, price every maybe, and list what's not included.