Out-of-Scope Change
EVM Terms
Reviewed by forProject Technology - updated Sep 2026
Quick definition: An Out-of-Scope Change is a baseline change that falls outside the existing contract's scope, meaning it requires a formal contractual change to implement.
Because the work wasn't part of what was originally agreed to, an out-of-scope change can't simply be absorbed through internal re-planning -- it has to go through contract modification before the baseline can be updated. This distinguishes it from an In-Scope Change, which can be handled within the existing contract.
Why it matters
Correctly classifying a change as out-of-scope protects both parties -- it ensures new work gets properly priced and negotiated into the contract rather than being absorbed for free into the existing baseline.
Also known as
N/A
Used in
Baseline Change Control
See also
FAQ
What's the difference between an in-scope and out-of-scope change?
An in-scope change fits within the existing contract and can be handled through internal re-planning; an out-of-scope change falls outside the contract and requires a formal contractual change.
Does an out-of-scope change automatically increase the contract price?
Not automatically -- but it typically requires negotiation, which can change the contract's price, schedule, or both.
Definition maintained by forProject Technology.
© 2026 forProject Technology, Inc.
© 2026 forProject Technology, Inc.
