How-To Guide

Change Order Prevention Guide

Root causes of change orders, prevention strategies at design and preconstruction phases, managing scope creep, and effective tracking.

Last updated: March 2026•Industry Best Practices
Key Statistics

The Design-Build Institute of America reports that projects with poorly defined scope see average change order costs of 5-15% of the original contract value. CMAA data shows that 40% of change orders result from design issues or missing details, 25% from scope creep, and 20% from coordination failures. Every percentage point of change orders translates to margin erosion and schedule risk.

Root Causes of Change Orders

Design Omissions & Conflicts
Missing details, unclear or contradictory specifications, MEP clashes not resolved in design. Example: Structural grid doesn't align with MEP routing; discovered during construction and requires rework.
Scope Creep (Owner-Directed Changes)
Owner requests for additions, upgrades, or substitutions not in the original contract. Example: "Can we use the upgraded finish package instead?" or "Let's add another room here."
Site Conditions
Differing site conditions discovered during construction: unforeseen soil conditions, existing utilities not shown on plans, hidden structural members. These require subsurface investigation to prevent.
Coordination & Sequencing Failures
Trade conflicts that weren't caught during preconstruction. Example: Mechanical ducts and structural beams occupy same space; one trade must relocate, creating rework.
Code/Approval Issues
Design does not meet code as submitted; AHJ requires changes during plan review. Example: Egress paths undersized; must add door or enlarge corridor.
Constructability Issues
Details that are designed but impossible to build, or require expensive/non-standard methods. Example: Specified waterproofing detail cannot be applied in field conditions.

Prevention at the Design Phase

1. Conduct Comprehensive 3D Coordination
Build a 3D model that includes structural, architectural, MEP, and site elements. Run clash detection (often called "interference detection"). Resolve conflicts on screen before design is finalized. This prevents discovering conflicts during construction.
2. Perform Design Review Against Code
Before design is issued for permit, check against IBC/code requirements: egress widths, fire ratings, accessibility, structural compliance. Engage local AHJ early if there's uncertainty about requirements. A design correction now costs dollars; a code rejection during construction costs weeks and thousands.
3. Detail Critical Interfaces
MEP penetrations, beam-column connections, structural/wall interfaces, waterproofing transitions. Provide detailed detail sheets that leave no ambiguity. A vague detail leads to field interpretation and rework.
4. Define Material/Equipment Specs Precisely
Avoid vague language like "as approved" or "equal to." Use prescriptive specifications (specific brands/models) or define performance requirements clearly. "Durock board or equivalent" will cost you change orders and disputes.
5. Site Visit & Verification
Verify site conditions match drawings. Check for existing utilities, easements, or structural conditions that may not be documented. If subsurface conditions are a risk (soil type, groundwater), conduct borings before finalizing foundation design.

Prevention at Preconstruction

1. Conduct a Thorough Design Review Meeting
All trades present. Walk through the drawings together. Ask: "How will you build this?" "What happens when your work meets this other trade's work?" "Do you have what you need to start?" Constructability issues caught here are cheap to fix. Found during construction, they're expensive.
2. Perform a Constructability Review
Constructability review identifies details that can't be built as drawn, or require unreasonable effort/cost. Example: Insulation specified as 6" thick in a 4" cavity. Flag these before construction starts and request design changes.
3. Detailed Clash Detection Review
Use clash detection tools to identify any missed conflicts. Review the results with all trades. Create a punch list of coordination issues to resolve before construction begins (or during a short initial phase if unavoidable).
4. Establish Clear Approval Workflow
Define: Who approves submittals? What's the turnaround time? Who approves RFI responses? Track RFI responses to ensure they come back on time. Delays in approvals breed change orders.
5. Document the Baseline Scope
Create a clear scope statement: What is included? What is explicitly excluded? Owner requests outside the scope will be change orders—but only if the baseline is clear. Without it, disputes arise over what was "supposed" to be included.

Managing Scope Creep During Construction

Require Written Requests for Additions
Never verbally agree to "just add this" or "while we're here, can we." Make the owner submit a written change order request. This prevents disputes about what was supposed to be included and protects you against claims of unauthorized work.
Provide Cost Estimates for Requests
When an owner requests a change, provide a preliminary cost estimate. This creates a pause—they can't claim later that the cost was "unreasonable" if they approved it knowing the impact. It also filters out frivolous requests.
Document Every Decision & Approval
Email confirmation: "Per your request on [date], we are proceeding with [change]. Approved cost is $X. This will add Y days to the schedule." Saves disputes later.
Say "No" to Informal Changes
If a request is outside the scope and the owner won't approve a change order, don't do the work. Performing unauthorized work creates no protection for you and the owner may refuse to pay, claiming it wasn't requested.

Change Order Tracking & Documentation

Even with prevention, some change orders are unavoidable. Track them systematically to control cost and schedule impact:

Maintain a Change Order Log
• Request date and ID number
• Description and reason (design issue, scope addition, code change, etc.)
• Requested amount and approved amount
• Schedule impact (days added)
• Status (approved, pending, denied)
• Supporting documentation (RFIs, daily logs, quotes)
Link to Source Documents
• RFI number that triggered the change
• Daily log entries showing delay impact
• Photos of the condition requiring change
• Email approvals from owner/PM
• Subcontractor quotes and justification
Pro Tip: Tie every change order to supporting documentation (an RFI, a daily log entry, a design change, etc.). A change order without a source is harder to defend. One with clear documentation is legally defensible.

The Cost-Benefit of Prevention

Investment (Design & Preconstruction)
  • • 3D model coordination: $5K–$25K
  • • Clash detection & resolution: $2K–$10K
  • • Constructability review: $3K–$8K
  • • Design refinement: 2–4 weeks
  • Total: $10K–$50K
Benefit (Avoided Change Orders)
  • • Average prevented change order: $50K–$200K+
  • • Schedule delays avoided: 2–4 weeks per issue
  • • Rework costs eliminated: $30K–$100K+
  • • One prevented clash pays for all prevention efforts
  • ROI: 200–800%

The cost of prevention is negligible compared to the cost of fixing problems during construction. A single coordination clash that requires rework costs 5–10x more to fix after concrete is poured than it did to catch in the model.

Related Resources

Construction Change Order Guide
Processing and documenting change orders.
Constructability Review Guide
Identifying buildability issues before construction.
MEP-Structural Clashes
Coordinating mechanical, electrical, plumbing with structure.
Preconstruction ROI
Why planning pays off: data on schedule and cost savings.

Change orders are almost never cheaper than prevention. The time invested in design coordination and preconstruction planning saves multiples of that cost in avoided rework and delays.