Download Mobile App
Scope creep is additional project work accepted without an explicit change to the plan. A small request can be reasonable, but the team still needs to understand its effort, owner and effect on delivery. This worksheet helps you calculate the size of a change before agreeing to it.
Calculate the proposed increase in effort
Use the same unit for the original estimate and the added work. Hours are convenient when the team has comparable estimates. Include implementation, review, testing and documentation in both figures.
Scope increase (%) = added estimated effort ÷ original approved effort × 100.
If the approved baseline was 80 hours and new requests add 20 hours, the increase is 20 ÷ 80 × 100 = 25%. The proposed total becomes 100 hours. This describes estimated effort growth; it is not a prediction that the calendar deadline will move by 25%.
Keep the original baseline visible. If you later approve a revised baseline, label its date and retain the original so readers know which comparison the percentage describes. Do not divide by a zero or unknown baseline; estimate the work first.
A worked change request
Imagine a team preparing a customer dashboard. The approved estimate is 80 hours. A new export request requires 10 hours of implementation, 6 hours of testing and 4 hours of documentation and review. That is 20 added hours and a 25% increase against the baseline.
Suppose only 8 hours of unallocated capacity remain before the intended release. The 12-hour gap needs a decision. The team could reduce the request, move other work, add genuinely available capacity or revise the date. It should not assume that everyone can absorb the gap.
Record the assumptions behind each estimate. If testing effort is uncertain, use a range and discuss both ends. An estimate of 16–24 added hours would represent 20–30% growth against the same 80-hour baseline.
Five checks before saying yes
- Goal: explain how the request supports the agreed outcome. An unrelated improvement may belong in a later project.
- Ownership: name the person responsible for delivering the change and the person authorised to approve it.
- Capacity: include existing commitments, review work and dependencies, not just implementation time.
- Tradeoff: state what will move, shrink or wait if the change is accepted.
- Record: link the request, evidence and approval from the affected tasks.
These are review prompts, not a statistically validated risk score. A large percentage is a reason to discuss the plan, but there is no universal percentage at which a project must stop. Urgent mandatory work may still need to proceed through an explicit decision.
Copyable change record
- Request: what will change, and who requested it?
- Reason and evidence: which user need, defect or obligation does it address?
- Baseline: approved scope, estimate unit and baseline date.
- Added work: implementation, review, testing and documentation estimates.
- Dependencies: inputs required before work can begin.
- Decision: accept, reduce, defer or reject, with the approver and date.
- Revised commitment: owner, acceptance condition and effect on other work.
Use a decision log to preserve the reason for the change. A team dependency map helps when the request affects another team's milestone.
Keep discussion connected to execution
In Edworking, keep the change note with the project document and link it from the affected tasks. Use the product demo to explore that workflow. If a review call changes the decision, update the written record and notify the affected owners rather than leaving the new commitment only in the conversation.
At the next review, compare the estimate with what you learned. If the work is larger than expected, make a new decision while retaining the previous baseline and approval. This makes scope growth visible without pretending that every early estimate will be precise.
Common calculation mistakes
Do not mix hours with task counts. Do not subtract cancelled work from added work without showing both, because a small net change can conceal a major change in direction. Do not equate effort growth with cost or schedule growth without a separate estimate.
The calculation is useful when it leads to a clear choice. Before accepting the next request, write its effort range, the available capacity and the proposed tradeoff. Then assign the decision to a named approver.
