Scope creep is project work that gradually expands beyond the agreed scope without a corresponding change to fee, schedule, or authorization.
Definition
Scope creep can occur when a client adds review rounds, requests new analyses, or changes design assumptions and the project team absorbs the effort without documenting its effect. Unclear exclusions, informal requests, and internal rework can also make it difficult to distinguish added scope from completing the original work. Firms may identify it by comparing actual tasks, hours, deliverables, and schedule with the agreement and approved changes. Their tracking methods vary: some flag hours against task budgets, while others log requests and review them at project meetings. Scope creep describes a management condition, not a legal conclusion that extra compensation is owed. It is not the same as a properly authorized change order, and it does not include every overrun, such as inefficiency or correction of the firm's own error. Owners monitor it because unpriced work can affect project margin and staff capacity.
How owners use it
- Compare new requests and revisions with the original scope and approved changes.
- Have project managers record added tasks, hours, and schedule effects as they arise.
- Review repeated unbilled effort by client, project manager, and service type.
- Example: A project has 40 hours budgeted for review and uses 52; 52 - 40 = 12 hours above budget to investigate.
