In-Scope Change
EVM Terms
Reviewed by forProject Technology - updated Sep 2026
Quick definition: An In-Scope Change is a baseline change that falls within the existing scope of a contract and therefore doesn't require a formal contract modification.
An In-Scope Change re-plans remaining work using the budget and schedule already authorized under the contract, without altering its scope, price, or delivery terms. Because no new contractual scope is added, it's typically approved through the contractor's internal baseline change control process rather than a customer action. It's the counterpart to an Out-of-Scope Change, which does require a contract modification.
Why it matters
Distinguishing in-scope from out-of-scope changes keeps the performance baseline meaningful -- budget should only be added when new contractual work is actually authorized, not used to mask performance problems. Mixing the two up can make a project's cost and schedule variances look better, or worse, than they really are.
Also known as
N/A
Used in
Baseline Change Control; Baseline Change Request
FAQ
What's the difference between an In-Scope Change and an Out-of-Scope Change?
An In-Scope Change stays within the contract's existing scope and budget; an Out-of-Scope Change adds new scope and requires a contract modification.
Does an In-Scope Change require customer approval?
Not typically -- it's usually handled through the contractor's own internal baseline change control process rather than a formal reprogramming action.
Definition maintained by forProject Technology.
© 2026 forProject Technology, Inc.
© 2026 forProject Technology, Inc.
