Scope, time, cost: when scope creeps, which one gives?
Published 12 November 2026
Every project is a deal between scope, time and cost. When the client asks for more, one of the other two has to move. If nobody decides which, the decision gets made for you, and it is usually the agency's margin or the team's evenings.
Most PMs know the triangle. Fewer use it out loud. The extra page, the third round of amends, the "quick" tweak to the homepage all get absorbed, one at a time, because each one feels too small to argue about. Nobody tracks the total until the budget report at the end shows a project that made no money.
This post covers what really gives when you can't have all three, what it costs when nobody chooses, and how to capture scope creep and amends rounds so you can manage them against the budget as they happen.
The triangle in one paragraph
Scope is what you deliver. Time is when you deliver it. Cost is what it takes to deliver it, in hours, people and money. The three are tied together: change one and at least one of the others moves. Quality sits in the middle of the triangle. It is the thing that gets squeezed when the three sides are pulled in different directions and nobody admits it.
What gives when you can't have all three
When new work arrives, there are only four real outcomes. Three are choices. The fourth is what happens when you don't make one.
Hold time and cost, flex scope. The new request goes in, something else comes out, or the request moves to a phase two. This is the cleanest option for fixed budgets and fixed launch dates, and the one clients find easiest to agree to once they see the swap written down.
Hold scope and time, add cost. More people, freelancers or overtime. It works, but it is rarely linear. Two extra developers in week six do not halve the remaining work, because someone has to brief them. Price the onboarding, not just the hours.
Hold scope and cost, move the date. The same team does more work over a longer period. Cheap in fees, expensive if the date was tied to a launch, an event or a media buy. Check what the date is attached to before you offer this one.
Nobody chooses, so quality gives. Testing gets shortened, the team works late, the final round of polish disappears. The project ships on time and on the quoted fee, and everyone involved knows it isn't as good as it should be. This is the default outcome on most agency projects, and it is the one nobody signed off.
What it costs when nobody decides
Absorbed scope doesn't disappear. It turns up somewhere else, usually later and usually bigger.
Margin. Ten small favours of two hours each is a week of someone's time. On a fixed fee project, that comes straight off the profit, and nobody notices until the final report.
The team. If the date and the fee are fixed and scope keeps growing, the extra work happens in evenings and weekends. Do that on every project and you lose people.
The client relationship. Raising a change at the point it is asked for is a normal conversation. Raising ten of them as a surprise invoice at the end is an argument, and you will probably lose it.
The next estimate. If absorbed work never gets logged, your actuals understate what the job really took. The next project gets priced on the wrong numbers and the cycle repeats.
How to capture scope creep as it happens
Scope creep is hard to manage because it arrives in small pieces, in calls, in Slack, in feedback documents. The fix is a single change log that every request goes into before any work starts on it. Not just the big ones. The small ones are where most of the margin goes.
For each entry, record:
What was asked, by whom and when. In plain words, with the source: the call, the email, the feedback round.
In scope or out. Checked against the agreed Scope Statement, not against memory. If the scope was never written down, start there.
The impact on all three sides. Extra hours and cost, days added to the timeline, and anything that comes out of scope to make room.
The decision and who made it. Approved and billed, absorbed as goodwill, swapped for something else, or declined. With a name and a date.
The habit that makes this work is logging the request before you agree to it. "Let me check what that does to the timeline and come back to you today" is a perfectly professional answer, and it gives you the space to make the choice deliberately.
Rounds of amends are scope too
Amends are where agency scope leaks fastest, because everyone expects some and nobody counts them. Three things keep them under control.
Define a round in the contract. One round means one set of consolidated feedback from one named person, received in one go. Five people sending comments across a week is not one round.
Count rounds per deliverable. Keep a running total against what was contracted, so everyone can see when a deliverable is on its last included round.
Treat the next round as a change. When round three starts on a two round deliverable, it goes in the change log with an hours estimate, like any other request. Tell the client before you start the work, not after.
| Deliverable | Rounds contracted | Rounds used | What happens next |
|---|---|---|---|
| Homepage design | 2 | 2 | Next round is logged and quoted as a change |
| Launch video edit | 3 | 1 | Two included rounds remain |
| Email templates | 2 | 3 | Third round absorbed as goodwill and logged |
An example. The point is that every round is visible, including the one you gave away.
Managing it against the budget
A change log on its own is a list. It becomes a management tool when you read it against the budget every week. Four figures are enough:
Budget agreed. The original fee, plus any changes the client has approved in writing.
Spent to date. Hours logged, at cost or at rate, whichever your agency reports on.
Forecast to complete. What the remaining work will take, honestly, including approved changes not yet started.
Absorbed and pending. The value of goodwill you have given away, and the value of changes still waiting for a decision.
If spent plus forecast is heading past the agreed budget, you know which way the triangle is tipping while there is still time to choose. Agree a simple rule up front, such as absorbing small requests up to an agreed share of the budget and quoting everything beyond it, so the decision for each change doesn't have to be argued from scratch.
Then share the log. A short weekly view of approved, absorbed and pending changes turns scope from an awkward topic into a routine one. Clients rarely object to a change they saw coming. They object to the invoice they didn't.
Something always gives. The only question is whether you choose it, or find out at the end.
A change log with impact on scope, time and cost, an amends tracker per deliverable, and a dashboard showing budget used, goodwill absorbed and changes still waiting for a decision. Founding members get it free, with the Scope Statement and Estimate & Assumptions Log.
12 templates live · lifetime access · 14 day refund