The Storage Building That Grew: How a Small Yes Became Scope Creep
A regional district we will call Cedar Ridge approved a modest project in early 2022: a single-bay storage building for its public works fleet, budgeted at roughly $340,000. Eighteen months later it was a three-bay structure with a staff washroom, a mezzanine, and a backup generator, and the cost had passed $700,000. No one decided to double the project. It happened one reasonable request at a time. The story is worth retelling because nothing in it was reckless — and that is exactly why scope creep is so hard to catch.
The first addition came at the second site meeting. With material lead times stretching and prices climbing through 2022, a manager pointed out that ordering steel for one bay now versus three bays later would mean paying twice and waiting twice. It was a genuinely good point. The team added two bays "while we are at it." Nobody updated the budget line, because it felt like a procurement decision, not a scope decision.
How small yeses compound
Each later change had the same shape: locally sensible, individually small, never weighed against the project's original purpose or funding envelope. Once you see the pattern, you can name it.
The washroom: "crews are already on site, the rough-in is cheap now."
The mezzanine: "we have the height, it is a waste not to use it."
The generator: "with the outages last winter, it would be irresponsible not to."
Each request came from a different person, so no one saw the running total of additions.
The failure was not bad judgment on any single item. It was the absence of a place where additions were collected, costed against the baseline, and approved or declined as a group. Scope creep rarely arrives as one big bad decision. It arrives as a dozen defensible ones that no one ever added up.
Where it could have been caught
The early-warning signs were all present months before the budget broke. A disciplined team would have treated each as a trigger to pause and re-baseline rather than absorb the change.
A baseline nobody could point to. The approved scope lived in an email thread, not a one-page document. When you cannot show the original deal in thirty seconds, every new idea looks like part of it.
Changes framed as anything but changes. "Procurement," "good housekeeping," "just being practical" — the language hid the fact that scope was moving. Name a change a change and it gets the scrutiny it deserves.
No single owner of the scope. Decisions were made in the meetings where they came up. A named project lead who must sign off on any addition forces the running total into the open.
Cost of delay used to justify, never to test. The 2022 supply squeeze made "do it now" sound urgent. The same logic should have prompted the question: does this still fit the budget and the purpose we were funded for?
A lightweight change log would have stopped this. One row per requested addition, with its cost, its sponsor, and a yes or no decision against the baseline. Reviewed at each site meeting, it turns invisible drift into a visible list — and a list of seven changes totalling $360,000 is a conversation a steering committee can actually have, instead of a surprise at the end.
Cedar Ridge eventually got a useful building. But it was funded as a storage shed, delivered as a small facility, and the gap had to be explained to a council that had approved something much smaller. The lesson is not to say no to good ideas. It is to make every good idea pass through one visible door, so the project you finish is still the project you started.
If you want a second set of eyes on scope, change control, and baselining before a project drifts, XNM's program & project delivery advisory can help you set up controls that catch creep early.