Scope creep in an outsourced engagement rarely happens deliberately. It happens gradually, as small additional requests get absorbed without either side noticing the arrangement has moved beyond what was originally agreed. A written scope document is what stops that drift before it starts, and it costs nothing to put in place beyond a short conversation up front.
What does a written scope document actually prevent?
Ambiguity about what falls inside a fixed fee and what would need a separate conversation, which protects both the firm’s budget and the provider’s capacity to deliver consistently, a principle set out in our article on fixed fee versus hourly billing. Without that reference point, both sides end up relying on memory and goodwill, which works fine until volume increases or a new task type appears.
Why does this matter for a fixed-fee structure specifically?
The fixed fee only stays fair to both sides if the scope it was priced against stays the same. A written document is the reference point when it’s unclear whether something falls inside it, detailed further in our article on what a complete back office actually includes. Priced packages only work as fixed fees because the scope behind each one is written down, not implied.
How scope creep actually happens in practice
It rarely arrives as one obvious overreach. A firm asks for “just one more document” reviewed this week, or a slightly different task type gets folded into an existing arrangement because it seemed close enough. Each request looks small in isolation. Over a few months, a written scope document is the only thing that makes it visible that the arrangement has quietly expanded well past what either side originally priced or planned for.
The risk runs in both directions. A provider that quietly absorbs extra work without flagging it is effectively working below the agreed rate, which is unsustainable and eventually shows up as declining quality or missed deadlines elsewhere. A firm that assumes an expanding set of tasks is still covered by the original fixed fee can be caught out when the provider eventually has to raise the scope question, often later and more awkwardly than if it had been addressed early.
What belongs in a written scope document
A useful scope document is specific rather than general. It names the task types covered, the volume or frequency assumed when the fee was set, the systems or file access involved, and what would trigger a scope conversation rather than being silently absorbed. Vague language such as “general paralegal support” invites exactly the drift a written scope document is meant to prevent, because neither side has a clear line to point to when a new request arrives. The more specific the document, the less room there is for genuine disagreement later about whether something was included.
Why this protects the working relationship, not just the fee
Firms sometimes assume a written scope document is primarily there to protect the provider’s margin. In practice it protects the relationship on both sides. A firm that knows exactly what is and isn’t covered can ask for more capacity confidently, through the same process described on our dedicated paralegal team page, rather than testing the boundary informally and hoping it holds. A clear written scope document turns a potentially awkward conversation about “is this still included” into a routine, low-friction check.
What good practice looks like
Revisiting the scope explicitly when a firm’s needs genuinely change, rather than letting the boundary drift without either side deciding to move it, consistent with the approach on our How It Works page. This mirrors the same principle behind why supervision needs to be in writing: verbal understandings degrade over time, and a written scope document gives both sides something concrete to check requests against.
Where scope discipline fits into onboarding
The scope conversation isn’t a one-off at the start and then forgotten. It is set during the onboarding timeline alongside the confidentiality agreement, and it is the same written scope document both sides return to during the first 30 days of the engagement, when the working relationship is still being tested and small scope questions come up most often.
By the time a firm reaches the point covered in our article on what changes over the first three months, the written scope document should have already been revisited at least once, either to confirm it still matches the work actually being done or to update it deliberately where it doesn’t. That habit, checked early and kept up, is what keeps a fixed-fee arrangement fair for years rather than months.
The Solicitors Regulation Authority’s guidance on clarity around costs and instructions reflects the same underlying principle: clients and providers alike are better served when what has been agreed is written down rather than assumed.
Want a written scope document that actually holds up over time?
We can walk you through how our scope agreements are structured before you sign anything.
Confidential · No obligation · Typically a 20-minute call
Frequently Asked Questions
What happens if a firm’s needs genuinely grow beyond the original scope?
A scope conversation is had explicitly, and the agreement is updated in writing, rather than the boundary drifting informally.
A scope conversation is had explicitly, and the agreement is updated in writing, rather than the boundary drifting informally.
Does a written scope document make an engagement less flexible?
No, it makes changes deliberate rather than accidental. Flexibility still exists, just through an agreed process rather than drift.
No, it makes changes deliberate rather than accidental. Flexibility still exists, just through an agreed process rather than drift.
Who is responsible for flagging when a request falls outside agreed scope?
Both sides share this responsibility, though a well-run provider should proactively flag it rather than simply absorbing extra work without discussion.
Both sides share this responsibility, though a well-run provider should proactively flag it rather than simply absorbing extra work without discussion.
How often should a written scope document be reviewed?
Whenever a firm’s needs change materially, rather than on a fixed schedule, since scope creep tends to follow real shifts in workload rather than the calendar. A brief annual check is still worth doing even when nothing has obviously changed, simply to confirm both sides still agree on what the written scope document covers.
Whenever a firm’s needs change materially, rather than on a fixed schedule, since scope creep tends to follow real shifts in workload rather than the calendar. A brief annual check is still worth doing even when nothing has obviously changed, simply to confirm both sides still agree on what the written scope document covers.
