On this page
Scope creep is what happens when a project gradually becomes more than what you quoted for, without anyone explicitly agreeing to the expansion. It’s rarely dramatic. It’s usually a series of small things: “while you’re at it, could you also…”, an extra round of revisions that wasn’t in the brief, a new stakeholder who wants changes after sign-off. Each individual ask seems reasonable. Cumulatively, they add up to a project that takes significantly longer than you planned and earns you less per day than you intended.
Most freelance comms consultants are too accommodating about scope creep, particularly early in a client relationship when they want things to go well. The result is that the pattern gets established and repeats on every subsequent project.
Why it happens
Scope creep happens for two main reasons. The first is a vague brief: if the original scope wasn’t clearly defined, neither party has a shared reference point for what’s in and what’s out. The second is that clients genuinely don’t always know in advance what they’ll need. Projects evolve. New requirements emerge. This is normal and not a sign of bad faith, it just needs to be handled explicitly rather than absorbed silently.
The fix for the first cause is a clear brief and contract. The fix for the second is a process for dealing with changes when they arise, rather than a policy of either refusing all changes or accepting them all for free.
How to spot it early
The moment a client asks for something that wasn’t in the original scope, that’s the moment to address it, not at the end of the project when you’re trying to reconcile how many hours you’ve spent. A good prompt is to ask yourself: “Is this in the brief?” If the answer is no, the change needs to be discussed before you do the work, not after.
This doesn’t mean every small accommodation needs a formal change request. It means being conscious of the difference between a brief clarification (which is part of the original scope) and an addition (which isn’t), and being clear with the client about which category something falls into.
Having the conversation without it being awkward
The most effective way to handle scope changes is to establish the process at the start of the project, not introduce it mid-project when it can feel like a sudden change in tone. A working agreement that includes a note on how scope changes will be handled, “if the brief changes, I’ll send a short note confirming the additional work, time, and cost before proceeding”, makes it routine.
When a change comes up, be matter-of-fact about it. “That’s outside the original scope, I’ll send over a brief note on the additional time and cost before I start.” Most clients who request additional work expect to pay for it. The ones who don’t will tell you, and that’s a useful thing to know early.
A form to work from
The scope change request form documents what was originally agreed, what is being added, the cost and time implications, and records client sign-off. Comes as an editable Word document and a PDF reference version.
Related articles
- How to write a freelance contract that protects you
- How to onboard a new client properly
- How to write a project debrief that actually improves your next campaign
Scope Change Request Form
Editable Word document and PDF reference version.