15.2 Constructive Changes, REAs & Claims
Key Takeaways
- A constructive change arises when Government action or inaction effectively changes the contract without a formal modification—such as defective specs, acceleration pressure, or unauthorized direction the contractor reasonably follows.
- An REA (request for equitable adjustment) is typically a pre-claim negotiation request for cost/time relief; a claim under the Contract Disputes Act is a written demand for a sum certain (or other relief) as a matter of right, seeking a CO decision.
- Contractors generally must provide timely notice of constructive changes and impacts; Government teams should document directions, stop unauthorized COR freelancing, and settle meritorious REAs before they harden into claims.
- Impact documentation (schedules, cost segregation, contemporaneous records) is essential for both REAs and claims; unsupported lump-sum demands are weak on the exam and in practice.
- Claim certification themes apply when statutory/regulatory thresholds are met—know conceptually that larger claims require proper certification, not that you memorize every historical dollar figure as the only tested point.
15.2 Constructive Changes, REAs & Claims
Quick Answer: Constructive changes occur when Government action or inaction effectively changes the work without a formal mod. Contractors may seek relief through an REA (negotiation request) and, if needed, a CDA claim (written demand as a matter of right seeking a CO decision). Master notice, impact documentation, settle early, and certification awareness for claims above applicable thresholds.
Section 15.1 covered formal modifications. Real contracts also generate informal change dynamics: a COR insists on a higher standard than the PWS, drawings conflict, the Government delays access, or leadership “encourages” acceleration without a change order. Those facts feed constructive change theory and the REA → claim → disputes pipeline. FAI 4.1.4 Manage Changes (~10Q) tests whether you can prevent, recognize, and resolve these events—not whether you can litigate like a board attorney.
Constructive change theory
A constructive change is not a magical extra clause. It is a doctrinal label for situations where the Government, by act or omission, changes the contractor’s obligations in a way that should have been handled as a formal change—yet no proper CO modification was issued (or the formal paper does not match reality).
| Constructive change theme | Illustrative fact pattern |
|---|---|
| Unauthorized direction | COR directs extra work; contractor performs; CO never signed a mod |
| Defective specifications | Contractor follows defective Government design and incurs extra cost |
| Constructive acceleration | Government refuses justified time extension but insists on original completion, forcing overtime/extra resources |
| Constructive suspension / delay | Government delays site access, approvals, or GFP so performance costs rise |
| Superior knowledge / failure to disclose (conceptual) | Government withholds vital information it should have shared, causing extra work |
| Over-inspection / impossibility themes | Government enforces a standard beyond the contract, or makes performance effectively impossible as written |
Key elements conceptually:
- A Government act or failure to act (not pure contractor mismanagement).
- That act changes the work, method, timing, or cost burden relative to the contract.
- The contractor is entitled (if facts prove out) to an equitable adjustment-type remedy as if a formal change had been ordered—often after notice and proof of impact.
Exam trap: Every cost overrun is a constructive change. False. Contractor inefficiency, bid error, and subcontractor default are usually contractor risk, not constructive change.
Exam trap: If the CO later ratifies or issues a formal mod, constructive-change chaos disappears automatically without pricing. Not quite—formalizing is good, but impact still needs settlement if costs/time already shifted.
Scenario A — Spec gold-plating. PWS requires commercial-grade paint. Inspector rejects work unless aerospace-grade coating is used, citing “my preference.” Contractor complies under protest. Constructive change risk: enforcing a higher standard than the contract without a CO change order.
Scenario B — True contractor problem. Contractor understaffed its fixed-price crew and misses milestones. No Government interference. Not a constructive change—performance risk sits with the contractor under the fixed-price bargain.
Preventing constructive changes (Government-side discipline)
Best administration avoids constructive changes:
| Control | Practice |
|---|---|
| Single voice for direction | Only CO issues contractual directions that change work |
| COR appointment limits | COR monitors and recommends; does not redesign the bargain |
| Written channels | Confirm material technical directions in writing; elevate disputes |
| Timely decisions | Late approvals and GFP failures create delay claims |
| Spec quality | Defective or ambiguous specs are claim fuel—fix pre-award when possible |
| Schedule honesty | If delay is excusable/compensable under the clauses, process extensions rather than silent acceleration |
Guiding Principles link: Communication and documentation failures are often the root cause of constructive change litigation. “I thought the COR could approve that” is not a defense strategy—it is an exam wrong answer.
REA vs claim (conceptual distinction)
CON 3990V loves the vocabulary split between a request for equitable adjustment (REA) and a claim under the Contract Disputes Act (CDA) framework implemented in FAR 33.2 themes.
| Feature | REA (typical teaching model) | Claim (CDA) |
|---|---|---|
| Purpose | Negotiate cost/time adjustment, often after change or constructive change | Demand relief as a matter of right; start formal disputes clock toward CO decision |
| Tone | Business negotiation / settlement | Formal written demand seeking decision |
| Outcome path | Bilateral mod settlement preferred | CO final decision → appeal paths (15.3) |
| Certification | Generally not the CDA claim certification (unless it is actually a claim) | Certification required when claim amount meets threshold rules |
| Interest | Typically not CDA interest until it is a proper claim (conceptual) | Interest themes attach to proper claims (15.3) |
Practical continuum:
Event (change / constructive change / delay)
→ Notice + impact records
→ REA negotiation → bilateral mod (best)
→ If unresolved: CDA claim to CO
→ CO final decision
→ Appeal (BCA or COFC) or ADR
Exam cue: Calling something an “REA” does not stop it from being a claim if the writing is a CDA demand for a sum certain as a matter of right. Substance controls labels. Conversely, a cooperative pricing proposal after a change order may be pure REA negotiation, not yet a claim.
Notification duties
Most contracts and FAR-family clauses expect prompt notice when the contractor believes Government conduct is changing the work or causing compensable impact.
Why notice matters:
| Stakeholder | Benefit of timely notice |
|---|---|
| Government | Can stop unauthorized directions, fund properly, mitigate, or issue a formal change |
| Contractor | Preserves rights; avoids “you never told us” defenses |
| File | Creates contemporaneous evidence of what happened when |
Government receipt of notice should trigger:
- Acknowledge and investigate.
- Verify whether a CO direction exists or should be issued/withdrawn.
- Direct the contractor how to proceed (perform / stop / await mod).
- Start impact tracking expectations.
- Negotiate REA or prepare for claim analysis.
Scenario C — Silent accumulation. Contractor performs six months of “extra” COR tasks, then drops a multi-million REA with no prior notice. The file fight becomes brutal—notice failures hurt credibility even when some extra work is real. Exam answers favor timely notice + contemporaneous records.
Documenting impacts
Whether REA or claim, proof wins:
| Document type | Use |
|---|---|
| Daily reports / logs | What work occurred and why |
| Schedule updates (as-planned vs as-built) | Time impact / critical path themes |
| Cost reports segregating change work | Dollars tied to the change event |
| Correspondence / direction emails | Government act that caused the change |
| Photos, RFIs, submittal logs | Technical causation |
| Modified estimates vs bid baseline | Quantum support |
Segregation principle: Separate base contract costs from change-related costs. Global “total cost” dumps without causation are weak.
Reasonableness: Fixed-price contractors still must show the change, not merely that the job was harder than hoped.
Settling before claim
Policy and professional practice favor settlement:
- Faster mission recovery
- Lower legal cost
- Better team relationships
- Cleaner obligation and funding control
- Avoids CDA interest growth and appeal risk
Settlement tools:
- Bilateral modification pricing the equitable adjustment and releasing the specific change impact when appropriate.
- Partial settlements (time now, cost later—or vice versa) with clear reservation language.
- ADR even before a formal claim hardens (15.3).
- Scope correction—if the “extra” work should not have been directed, stop it and price residual impact.
Exam trap: “Never settle; always force a claim so the board decides.” Wrong culture for Manage Changes. Boards exist when settlement fails—not as the first stop.
Exam trap: “Always pay any REA to keep the contractor happy.” Wrong. Pay meritorious, supported adjustments; deny or negotiate weak ones with a reasoned basis.
Certification of claims (threshold awareness)
Under the CDA framework, contractor claims above an applicable dollar threshold generally must be certified—a formal statement that the claim is made in good faith, supporting data are accurate to the best of the contractor’s knowledge and belief, the amount accurately reflects the contract adjustment for which the contractor believes the Government is liable, and the signer is authorized.
What CON 3990V needs conceptually:
| Theme | Takeaway |
|---|---|
| Threshold awareness | Larger claims require certification; tiny claims may not—know that a threshold exists |
| Purpose | Deters inflated claims; enables fraud remedies if false |
| Defects | Missing/defective certification can impair the claim’s procedural validity until cured |
| Who signs | Authorized contractor official—not a random tech on site |
You are not primarily tested as a case-law historian on every historical threshold change. You are tested on recognizing that certification is a real claim requirement at threshold and that uncertified large “claims” are procedurally problematic.
Government claims and bilateral reality
The Government can also assert claims (e.g., defective pricing themes, overpayments, liquidated damages under clauses). The same CDA architecture funnels disputes toward CO decisions and appeals. For Manage Changes exam items, most stems are contractor-side constructive change / REA / claim, but remember the system is two-way.
Integration map
| Upstream | This section | Downstream |
|---|---|---|
| Formal mods & scope (15.1) | Constructive change when formality fails | CDA disputes process (15.3) |
| Quality / inspection (14.2) | Over-inspection constructive change | Claims quantum |
| Admin communications (5.3) | Notice & documentation quality | Settlement vs litigation |
| Ethics (5.1) | False claims / false certification risk | Integrity enforcement |
CON 3990V closed-book anchors
- Constructive change = Government-caused change without proper formal mod dynamics.
- Not every overrun is constructive—causation and Government act matter.
- REA negotiates; claim demands as of right under CDA themes.
- Notice + contemporaneous impact records are survival tools.
- Settle meritorious REAs with bilateral mods when possible.
- Certification applies to claims at threshold—substance over labels.
Bottom line: Constructive changes convert informal Government pressure into legal adjustment rights. Prevent them with CO-only direction, fix them with documented REAs and bilateral pricing, and escalate only when needed to proper CDA claims with notice, proof, and certification awareness. On CON 3990V, reward the theory, separate REA from claim, and choose settlement discipline over both denial-by-default and pay-anything culture.
Which situation best illustrates a constructive change?
Which statement best captures a conceptual difference between an REA and a CDA claim?
Why is timely contractor notice of a constructive change or impact important for both parties?
A contractor submits a large written demand for a sum certain, asserts entitlement as a matter of right, and requests a Contracting Officer decision, but provides no claim certification though the amount is above the applicable certification threshold. What is the best assessment?