Scope creep in marketing projects, and how it starts

Aug 22
3 min read

Updated: 2 days ago

Introduction

No project fails because of one large unauthorised request. It fails because of eleven small ones, each of which was easier to absorb than to discuss.

By the time anyone notices, the timeline has slipped, the margin has gone, and both parties feel the other has behaved unreasonably. Both are usually acting in good faith.

1. Scope creep in marketing projects arrives as small favours

The pattern is consistent. A quick extra version for a different platform. One more revision. A logo tweak while you are in there. Could you also look at the other page.

Each request is genuinely small and refusing it feels petty. Fifteen of them constitute a substantial amount of unpaid work and a deadline nobody can meet.

The problem is not the requests. It is that each one is decided informally, so there is no point at which the accumulation becomes visible to anyone.

2. The root cause is usually a vague original scope

Creep is a symptom. The disease is a scope written in activities rather than quantities.

"Social media content" invites an unbounded interpretation. "Twelve posts per month, two formats, one round of revisions each" does not, because both parties can see when a request falls outside it.

Most creep disputes are actually disagreements about what was originally agreed, and they are resolved by writing the original agreement in countable terms.

3. Write the exclusion list

The most effective single sentence in a scope document is the one saying what is not included.

Adjacent work is where ambiguity lives: does a website project include writing the copy, does a campaign include photography, does a build include training, does content include design.

Listing five things explicitly out of scope prevents more difficulty than three pages describing what is in it.

4. Use a change note, not a conversation

The mechanism that works, and it is deliberately lightweight.

Any request outside scope gets a short written note: what is being added, what it costs, what it does to the timeline. Agreed by reply before work starts.

Two lines, not a form. The purpose is not bureaucracy — it is making the trade-off visible at the moment it is made, rather than at the end when the invoice or the delay appears.

5. Price small additions honestly, including the disruption

The cost of a small change is rarely the work itself.

It is the context switching, the re-review, the re-approval and the knock-on to whatever was scheduled next. A thirty-minute change can cost half a day once those are counted.

Quote the real figure. Clients accept a fair price for a genuine addition; what damages a relationship is absorbing four changes silently and then being visibly resentful about the fifth.

6. Allow a small buffer, and say that you have

Rigid scope management is its own problem. Some flexibility keeps the relationship functional.

A stated allowance — a few hours a month for small requests, included — handles the genuinely trivial items without a change note each time.

Say it explicitly, and say what happens when it is used up. An unstated buffer gets treated as unlimited, which is where this started.

7. Watch for creep in the other direction

Clients experience the reverse problem and it is discussed far less.

Deliverables quietly reduced. A senior person who pitched the work replaced by a junior. Reports arriving later and thinner. Meetings cancelled. Six posts a month becoming four.

Both parties should track delivery against the original countable scope. That single document protects the buyer at least as often as the supplier.

8. Review scope against delivery monthly

The habit that prevents the whole problem: a short monthly comparison of what was agreed against what has been delivered and requested.

Three columns — in scope, delivered, added — reviewed by both sides. Ten minutes.

Discrepancies surface while they are small and adjustable. Without it, the reckoning happens at the end of the engagement, when the only available options are an awkward invoice, an unhappy client, or a supplier absorbing a loss and losing interest in the work.

Conclusion

Creep accumulates through small requests that are individually reasonable, and the underlying cause is a scope written as activities rather than counts.

Define deliverables in quantities, publish an explicit exclusion list, handle additions with a two-line change note agreed before work starts, price them including disruption, state a small included buffer, watch for reduction as well as expansion, and compare scope against delivery every month.