Change Orders: REAs, Constructive Changes, and Pricing Modifications

Government contracts rarely execute exactly as written. When requirements change, you need change orders — formal modifications adjusting scope, price, or schedule.

Why change orders matter:

• Protect your profitability — Changes that increase costs deserve compensation
• Adjust schedules — Changes often impact delivery dates; get time extensions
• Document scope creep — Prevent unpaid additional work from eroding margins
• Create revenue opportunities — Well-managed changes can increase contract value

The Changes clause (FAR 52.243-1 through 52.243-7):

Nearly every government contract includes a Changes clause authorizing the contracting officer to direct changes to:

• Drawings, designs, or specifications
• Method of shipment or packing
• Place of delivery
• Time of performance (accelerations)
• Other scope elements within the general scope of the contract

Your rights under the Changes clause:

When the government directs a change:

1. You must comply — Even if you disagree with pricing, perform the changed work
2. You're entitled to equitable adjustment — If the change increases costs or time, you can request compensation
3. You must provide notice — Written notice within specified timeframes (typically 30 days)

In-scope vs. out-of-scope changes:

In-scope changes: Modifications within the general scope of the contract that the CO can direct under the Changes clause.

Out-of-scope changes: Work so different from the original contract that it represents a new procurement. These generally require competition (unless an exception applies).

Cardinal change doctrine:

A "cardinal change" is so substantial it's effectively a new contract. Courts hold that such changes exceed the CO's authority under the Changes clause and may entitle you to additional relief or even terminate the contract.

Not all changes come as formal written change orders. Sometimes government actions effectively change the contract without official modification.

Directed changes:

Formal written changes ordered by the contracting officer under the Changes clause. These are clear, documented, and typically easier to price and negotiate.

Example directed changes:

• "Modify the widget design to include the enhanced cooling system per revised Drawing D-42"
• "Accelerate delivery schedule — complete Phase 1 by March 15 instead of April 30"
• "Change delivery location from Norfolk to Jacksonville"

Constructive changes:

Government actions or inactions that effectively change contract requirements without formal modification. These are harder to identify and require careful documentation.

Common types of constructive changes:

1. Defective specifications:

Government-provided specs that are impossible to meet, contain errors, or require more work than anticipated. If you must do extra work to overcome defective specs, that's a constructive change.

2. Oral directions:

When the COR, project manager, or other government personnel verbally direct changed work. Even though oral directions aren't binding, if you comply and the government accepts the work, it may be a constructive change.

3. Over-inspection or rejection of conforming work:

If the government rejects work that actually complies with specifications (imposing higher standards), the increased effort is a constructive change.

4. Government-caused delays:

Late access to facilities, delayed approvals, untimely government-furnished property/information — these delays can be constructive changes entitling you to schedule and cost adjustments.

5. Defective government-furnished property/information:

If GFP or GFI is defective, late, or incomplete, causing you additional costs, that's a constructive change.

Proving constructive changes:

To recover for constructive changes, you must prove:

1. Government actions (or inactions) changed contract requirements
2. You incurred additional costs
3. You provided timely written notice
4. The change was not your fault

Documentation is everything:

Constructive changes are harder to prove than formal changes. Document everything: emails, meeting notes, photos, contemporaneous cost records, and written notifications to the CO.

When a change increases your costs or impacts schedule, you submit a Request for Equitable Adjustment (REA) seeking compensation.

What is an REA?

An REA is a detailed proposal asking the CO to adjust contract price and/or schedule to compensate for the impact of a change. It's not yet a "claim" — it's a negotiation proposal.

Components of a strong REA:

1. Executive summary:

• What changed
• When the change occurred
• Contractual basis (Changes clause, defective specs, etc.)
• Bottom line: cost and schedule impact

2. Background and narrative:

• Detailed chronology of events
• Original contract requirements
• What actually happened
• How it differed from the contract

3. Contractual basis:

• Cite specific contract clauses
• Reference FAR provisions
• Legal theories supporting your entitlement

4. Cost impact analysis:

• Direct labor (hours and rates)
• Materials
• Subcontractor costs
• Indirect costs (overhead, G&A)
• Profit/fee

5. Schedule impact analysis:

• Critical path delay
• Time extension requested
• Impact on downstream milestones

6. Supporting documentation:

• Timesheets and labor records
• Invoices and receipts
• Emails and meeting notes
• Photos or technical documentation
• Expert opinions if applicable

Cost vs. pricing analysis:

Cost analysis: Detailed breakdown of actual or estimated costs. Used when you have access to detailed cost data.

Pricing analysis: Comparison to market prices, prior quotes, or independent estimates. Used when detailed costs aren't available.

Most REAs use cost analysis with detailed supporting records. The more documentation, the stronger your REA.

Submission timing:

Submit REAs promptly after quantifying impact. Don't wait months — timely submission demonstrates good faith and improves credibility. Most contracts require notice within 30 days and REA submission within 60-90 days.

Pricing change orders requires balancing fair compensation with government scrutiny. Multiple pricing methods exist.

1. Lump sum (firm fixed price):

Propose a total price for the changed work. Government prefers this because it caps their cost. You bear risk if actual costs exceed estimate.

When to use: Well-defined changes where you can estimate costs confidently.

2. Time and materials (T&M):

Price based on actual hours at specified labor rates plus materials at cost. Government pays actual costs up to a ceiling.

When to use: Uncertain scope where costs are hard to estimate. Common for troubleshooting or undefined repair work.

3. Cost-reimbursement:

Government reimburses actual costs plus fee. Requires cost accounting and government oversight.

When to use: Highly uncertain work, R&D, or when the government wants cost visibility.

4. Not-to-exceed (NTE) pricing:

T&M or cost-reimbursement with a ceiling price. Common compromise when scope is uncertain but government wants cost protection.

Pricing components:

Direct costs:

• Labor: Hours × loaded rates (or base rates with separate indirect)
• Materials: Purchase price + handling if applicable
• Subcontracts: Subcontractor price + administrative burden if allowed
• ODCs: Travel, equipment rental, etc.

Indirect costs:

• Fringe benefits (if not in loaded rates)
• Overhead (applied to direct labor)
• G&A (applied to total cost input)

Profit/fee:

• Reasonable profit on changed work
• Typically 10-15% on fixed-price changes
• Lower on cost-reimbursement (5-10%)
• Varies by risk, complexity, and contract type

Common pricing pitfalls:

• Underpricing to be "cooperative" — Don't leave money on the table
• Inflating costs to "negotiate down" — Harms credibility; government sees through it
• Omitting indirect costs — Apply overhead and G&A to change work
• Failing to include profit — You're entitled to reasonable profit on changed work
• Poor documentation — Unsupported costs will be challenged or denied

Negotiation strategies:

The REA is an opening proposal, not a final offer. Expect negotiation. Be prepared to:

• Explain and defend your cost buildup
• Provide additional documentation
• Compromise on disputed elements
• Accept partial payment if some costs are questionable

Contracts impose strict notice requirements for changes. Missing deadlines can forfeit your right to adjustment.

Typical notice provisions:

Most Changes clauses require:

• Written notice within 30 days — Notify CO of changed conditions or constructive changes
• REA submission within 60-90 days — Submit detailed cost proposal
• Notice before performing disputed work (when possible) — If you believe work is changed, notify before starting

What constitutes proper notice:

Effective notice includes:

• In writing — Email is acceptable if contract allows electronic communications
• To the contracting officer — Not the COR or project manager (though cc them)
• Describes the change — What changed, when, and how it differs from the contract
• Reserves right to equitable adjustment — State that you're reserving the right to seek adjustment
• Estimate of impact (if known) — Provide rough cost/schedule impact if you can

Example notice language:

"This letter provides notice under FAR 52.243-1, Changes—Fixed-Price, that the verbal direction from [Name] on [Date] to [describe changed work] constitutes a change to contract requirements. This change will impact cost and schedule. We are proceeding with the work as directed and reserve our right to request equitable adjustment for the cost and schedule impacts. We will submit a Request for Equitable Adjustment within 60 days after quantifying the full impact."

Don't wait until the deadline:

Provide notice as soon as you recognize a change. Waiting until day 29 looks like gamesmanship. Early notice demonstrates good faith and gives the CO opportunity to clarify or modify direction.

Continuing performance requirement:

Even when you've provided notice and reserved rights, you must continue performing. The Disputes clause requires diligent performance pending resolution of changes.

Notice for constructive changes:

Constructive changes require notice even though there's no formal change order. When you encounter defective specs, over-inspection, or oral directions, notify the CO immediately:

• Describe the government action or inaction
• Explain why it constitutes a change
• Request formal direction or clarification
• Reserve right to equitable adjustment

Waiver of notice defects:

Sometimes COs waive late or defective notice if you have a good excuse or the government wasn't prejudiced. But don't count on it — comply with notice requirements strictly.

Strong documentation makes or breaks change order recovery. Document changes in real-time — not months later when you're preparing the REA.

What to document:

1. The change event:

• Date and time
• Who was involved (names, titles)
• What was said or directed
• How it differs from the contract
• Photos or screenshots if applicable

2. Contemporaneous communications:

• Save all emails (don't delete anything)
• Document phone calls with follow-up emails confirming discussion
• Prepare meeting minutes (even informal meetings)
• Memorialize oral directions in writing

3. Cost records:

• Segregate change-related costs from base contract work
• Use separate job codes or WBS elements for changes
• Require timesheets to identify change work
• Track materials and subcontractor costs separately

4. Schedule impacts:

• Update CPM schedule showing change impacts
• Document critical path delays
• Analyze float consumption
• Show cause-and-effect between change and delay

5. Technical documentation:

• Photos of defective GFP or conditions
• Test results showing specification problems
• Engineering analyses
• Drawings showing as-built vs. as-designed

Best practices:

Keep a change log:

Maintain a spreadsheet tracking all potential changes:

• Change number (C-001, C-002, etc.)
• Date identified
• Description
• Status (noticed, REA submitted, under negotiation, resolved)
• Estimated cost impact
• Estimated schedule impact

Use daily reports or logs:

Daily progress reports should note changed conditions, government directions, delays, or other events that may lead to changes. These contemporaneous records are powerful evidence.

Confirm verbal directions in writing:

After any verbal direction from government personnel, send a confirming email:

"This email confirms our discussion today in which you directed [describe work]. We understand this is a change from the contract requirements in [specify how]. Please confirm this direction in writing or via formal modification. We are proceeding as directed and reserve our right to equitable adjustment."

Organize files by change:

Create a folder for each significant change containing all related emails, cost records, photos, and documentation. This makes REA preparation much easier.

Train your team:

Project managers, foremen, and engineers must understand the importance of documentation. They're the ones encountering changes in real-time — they need to document immediately.

Learn from others' mistakes. Avoid these common change order pitfalls:

1. Performing changed work without notice:

Mistake: Government directs change verbally or through defective specs. You comply without written notice, then try to claim adjustment months later.

Fix: Provide written notice immediately when you recognize changed conditions. Reserve your rights before performing the work.

2. Missing notice deadlines:

Mistake: Contract requires notice within 30 days. You wait 45 days. CO denies adjustment based on late notice.

Fix: Track notice deadlines carefully. Set calendar reminders. Submit notice early, not at the deadline.

3. Inadequate cost documentation:

Mistake: Submit REA with lump sum cost estimate but no supporting records. CO denies or drastically reduces adjustment.

Fix: Provide detailed cost buildup with supporting documentation. Show your work. Unsupported costs will be challenged.

4. Absorbing changes to "be a good contractor":

Mistake: Try to maintain good relationship by absorbing change costs. Margins erode, contract becomes unprofitable.

Fix: Professionalism includes asserting your rights. Submit REAs for legitimate changes. The government expects it.

5. Inflated REAs:

Mistake: Submit REA with padded costs expecting negotiation. CO sees through it; your credibility suffers.

Fix: Submit realistic, well-supported REAs. Negotiation will happen anyway, but starting with credible numbers builds trust.

6. Waiting too long to submit REA:

Mistake: Wait until contract completion to submit all REAs. Memories fade, documentation is lost, government is skeptical.

Fix: Submit REAs promptly after quantifying impact. Contemporary submissions are more credible and easier to negotiate.

7. Failing to segregate costs:

Mistake: Mix change costs with base contract costs in accounting records. Can't prove actual impact when submitting REA.

Fix: Use separate job codes or WBS elements for each significant change. Track costs separately in real-time.

8. Accepting "full and final" release language carelessly:

Mistake: Sign modification settling one change with language releasing "all claims." Later discover it waived your rights to other pending changes.

Fix: Read every word of modifications. Negotiate to limit release language to the specific change being settled. Don't sign away rights to other claims.

9. Poor schedule impact analysis:

Mistake: Claim schedule delay without CPM analysis showing critical path impact. CO denies time extension.

Fix: Maintain updated CPM schedule. Perform critical path analysis showing how the change delayed completion. Demonstrate cause and effect.

10. Not involving the contracting officer:

Mistake: Work everything out with the COR or project manager, never involving the CO. Later discover only the CO has authority to agree to changes.

Fix: COR can't modify the contract. Direct all formal change requests, notices, and REAs to the contracting officer. Copy the COR, but engage the CO.