Scope Creep Starts in the Engagement Letter, Not the Client
Scope creep is usually a drafting problem, not a client problem. The engagement letter phrases that invite it, and the clauses that prevent it.
Scope Creep Starts in the Engagement Letter, Not the Client
Most firms treat scope creep as a client behaviour problem. It is usually a drafting problem. The letter defines the deliverable but never defines the boundary, so when the quick question turns into three hours of work, there is nothing to point at.
The 4pm email
A client emails late on a Thursday. They have had an offer accepted on a buy-to-let and want to know how it changes their position for the year. It is a reasonable question. It is also not in the letter, and nobody on the team is quite sure whether it is or it is not.
So it gets answered. It takes ninety minutes, it does not get recorded anywhere, and it quietly resets the client's expectation of what the fee covers. Repeat that across a client base and the recovery rate drops without a single difficult conversation ever taking place.
Three phrases that invite creep
Scope creep rarely arrives through a clause someone argued over. It arrives through filler that nobody read closely because it sounded reassuring.
"and any related matters"
Related to what, and decided by whom? The client reads this as generous. You read it as narrow. Neither reading is written down.
"as required"
Required by the engagement, or required by the client? A phrase that hands the volume dial to the person who is not paying by the hour.
"ongoing support"
The most expensive two words in practice management. Unbounded in hours, in channel and in subject matter, and almost always priced as though it were a rounding error.
A scope is not a description of the work. It is a description of the edge of the work.
What a bounded scope actually looks like
Four elements, and the last one is the one most letters are missing. Name the deliverable in the client's language rather than the filing's. State the frequency, including how many rounds of review are included. List the exclusions explicitly, because an exclusion the client has read is worth more than one they could have inferred. Then give the out-of-scope work somewhere to go.
That last part matters. A boundary with no route across it just makes the firm the obstacle. A boundary with a stated route makes it a process: we will scope it, quote it, and start once you have approved it.
Price the boundary, do not police it
An out-of-scope clause only works if a mechanism is attached to it. Without one, enforcement falls to whichever team member happens to receive the email, and they will almost always choose the relationship over the clause. That is the right instinct and the wrong outcome.
Attach a change order, a stated rate and a sign-off step. Then the answer to the 4pm email is not no. It is: happy to look at that, here is what it costs, confirm and we will begin. Nobody has to be the bad guy, because the letter already had the conversation.
Why templates drift
Most firms did write a good letter once. Then it was copied for the next client, trimmed because a paragraph felt heavy, copied again, and three years later the exclusions have quietly disappeared while the fee has stayed flat. Nobody made that decision. It happened one duplicate at a time.
The fix is structural rather than editorial: a single source template, versioned, with the scope and exclusions built from the service selected rather than retyped each time. If a partner improves the wording, every letter issued afterwards carries the improvement. Drift stops being the default.
The letter is the conversation, held early
Every awkward exchange about fees is a conversation that was available months earlier, in writing, when neither side was under pressure and the relationship was at its warmest. Scope creep is what it costs to skip that conversation.
Reviewing your own template is a short exercise. Open the last engagement letter you sent and find the sentence that tells the client what is not included. If it takes more than ten seconds to locate, your clients will not have found it either.
Write the boundary once, use it everywhere
FigsFlow builds your scope, exclusions and out-of-scope terms into the proposal and engagement letter as you price the work, so the boundary is in every letter that leaves the practice.
See how it works