Scope creep
Factual definition
Scope creep is the gradual expansion of a project’s requirements beyond what was originally agreed, usually without extra time or budget.
Where it shows up in private equity
Scope creep appears wherever a fixed plan meets a changing question:
- Consulting engagements. A sponsor hires advisors for commercial or operational diligence on a set scope and fee.
- Value-creation plans. A portfolio company’s plan after close keeps gaining initiatives without gaining people or budget.
- Portfolio-company IT projects. A system upgrade adds features, sites or integrations as it runs.
In each case, the cost lands on someone. Either the advisor works for free, the plan’s original priorities slip, or the project overruns.
Recognize added questions outside the agreed assignment
Hypothetical: the engagement was supposed to cover just the plant’s cost structure, but by week three the client keeps adding questions about sales and logistics too. The lead consultant flags the scope creep before the team quietly works nights to cover it for free.
What 25% of creep costs an advisor
Hypothetical. A sponsor hires advisors for a 12-week, $300,000 engagement on a target’s plant costs. Requests are added one at a time, and no one changes the agreement. By the end, the work has grown 25%.
Weekly cost of the team = $300,000 ÷ 12 weeks
Weekly cost of the team = $25,000
Extra work = 12 weeks × 25%
Extra work = 3 weeks
Unpaid value of the extra work = 3 weeks × $25,000
Unpaid value of the extra work = $75,000
Real size of the engagement = $300,000 + $75,000
Real size of the engagement = $375,000
The advisor absorbs $75,000, or the original plant-cost work gets thinner to make room. Neither choice was made on purpose.
What creep costs a portfolio company
Hypothetical. After close, a portfolio company adopts a value-creation plan with 5 initiatives. A 3-person team owns the plan. Each person has 100 working days for it in the plan period. Each initiative needs 60 person-days to finish.
Team capacity = 3 people × 100 days
Team capacity = 300 person-days
Work in the original plan = 5 initiatives × 60 person-days
Work in the original plan = 300 person-days
The original plan fits exactly. Over the following months, 3 initiatives are added. The team stays at 3 people.
Initiatives now in the plan = 5 + 3
Initiatives now in the plan = 8
Time available per initiative = 300 person-days ÷ 8
Time available per initiative = 37.5 person-days
Shortfall per initiative = 60 − 37.5
Shortfall per initiative = 22.5 person-days
Work now required = 8 initiatives × 60 person-days
Work now required = 480 person-days
Total shortfall = 480 − 300
Total shortfall = 180 person-days
Initiatives that cannot finish in the period = 180 ÷ 60
Initiatives that cannot finish in the period = 3
Extra time needed for the same team = 180 person-days ÷ 3 people
Extra time needed for the same team = 60 working days
The company now has two outcomes, neither chosen. If the team spreads its time evenly, all 8 initiatives are unfinished at the end of the period. If it works in order, 3 initiatives slip by 60 working days, and they may be the ones the original plan ranked highest.
The fix is the same as in an engagement. Each added initiative needs a decision: add people, extend the timetable, or drop a lower-ranked initiative to make room.
The change-order clause that prevents it
Hypothetical clause in the engagement letter:
Any work outside the statement of work requires a written change order before it begins. Each change order states the added work, the fee and the effect on the timetable, and is approved by both parties.
Under that clause, the first extra request triggers a decision. The logistics review is written up as 3 weeks and $75,000.
New fee with the change order = $300,000 + $75,000
New fee with the change order = $375,000
New timetable = 12 weeks + 3 weeks
New timetable = 15 weeks
The work is the same as in the creep case. The difference is that the client chose it, priced it and scheduled it.
Make the trade-off explicit at the next request
Hypothetical example.
A client adds a logistics review to an agreed plant-cost assignment. Before saying yes, the project lead identifies what the new question requires: shipment data, interviews and analysis that are absent from the original plan.
The lead offers concrete choices. The client can replace a lower-priority task, extend the timetable and agree any budget change, or commission the additional work separately.
The team records the chosen scope and updates the workplan. Those choices depend on the actual engagement terms. A new request does not automatically authorize extra fees.
An unexpected finding may also make additional work necessary. Flag the reason and the effect on the existing plan rather than silently absorbing it.
The aim is an explicit decision about the changed work, not refusing every request after the project begins.
Where Scope creep fits
Explore this term in the glossary cloud →