Rework is everywhere on construction projects, and almost everyone underestimates it. The visible costs — demo, re-installation, material waste — make it onto a cost report. The invisible costs — superintendent time, crew standby, schedule compression, subcontractor premium for out-of-sequence work — mostly don’t. Add them together and rework is consistently one of the largest single line items on projects that seem to be tracking fine on paper.
The harder question is where it comes from. Not all rework is the same. Some is genuinely unavoidable: owner scope changes, unforeseen conditions, genuine design evolution. But a large share traces directly to information problems — drawings that don’t agree with each other, specs that contradict the details, coordination gaps between disciplines that no one reconciled before the trades hit the field.
That share is preventable. This post explains how to size the problem, where rework actually originates, how it compounds into change orders and RFIs, and where in the project timeline the fix is cheapest.
How big is the rework problem?
Rework is notoriously hard to measure precisely — most of it gets absorbed into productivity losses and labor overruns that never appear as a discrete line. Industry studies estimate it runs in the range of 5–9% of contract value on typical commercial projects, though project teams almost uniformly believe their figure is lower than the actual. Some of the gap is accounting: when a crew re-hangs ductwork because the structural framing wasn’t where the drawing said it would be, the cost usually lands in labor variance, not a rework line.
What’s more useful than an aggregate percentage is understanding the cost curve. A conflict caught during plan review — in the documents, before anything is built — costs the time it takes to issue a coordination note and a revised sheet. The same conflict caught in the field, after the work is installed, costs demolition, re-work, a change order to cover the extra labor and material, and schedule time while the crew works around the problem.
Flikt’s own data, documented across real projects, puts that ratio at roughly ten to one: an error that costs one unit of effort to fix in review costs ten units to fix in construction. That’s not a marketing claim — it’s the basic economics of concrete versus paper.
Where rework actually comes from
Construction rework has multiple root causes, and the right prevention strategy depends on which category you’re dealing with.
Scope changes and owner decisions
When an owner changes program mid-design or adds scope after construction starts, rework is the price. There’s limited mitigation here — these are deliberate decisions. The goal is to push them as early as possible, and to price them at design time rather than construction time.
Unforeseen site conditions
Existing-conditions surprises — buried utilities, soil bearing failures, structural conditions hidden in walls — generate rework that no amount of document review prevents. Pre-construction investigation reduces it; it never eliminates it.
Design errors and coordination failures
This is the preventable category, and it’s larger than most project teams account for. It covers:
- Spec-vs-drawing conflicts. The drawing details one product or assembly; the specification calls another. Both are “correct” in isolation; they just disagree, and the field has to pick one.
- Cross-sheet conflicts. Dimensions, elevations, or details that don’t reconcile across sheets. Structural assumes a floor-to-floor height that MEP hasn’t planned for.
- Cross-discipline conflicts. Structure, mechanical, electrical, and architecture each solve their own scope — and the seams between disciplines don’t align. A shear wall lands where a duct main has to go. A fire-protection head conflicts with a beam. An electrical panel alcove occupies the same space as a plumbing riser.
- Missing-coordination gaps. Something required is simply absent where it should appear: fire-alarm coverage not carried onto a new structure, an accessibility clearance nobody accounted for, a detail referenced but never drawn.
On one real project in Flikt’s data, más de 40 órdenes de cambio traced directly to conflicts entre 2D plan sheets — not scope changes, not site surprises, not bad weather. Documents that didn’t agree with each other. One structural-MEP conflict alone — a shear wall colliding with duct routing — carried $28,000–$45,000 in rework plus 14–21 days of schedule.
That single conflict, caught during plan review, is a coordination note. Caught in the field, it’s a six-figure line item by the time you add general conditions and schedule compression.
Rework, change orders, and RFIs: how they compound
These three aren’t the same thing, but they’re tightly connected, and the total cost of a coordination failure is usually all three together.
An undetected conflict typically surfaces first as an RFI — the field asks for clarification. If the answer to the RFI requires physical changes to work already installed, it becomes rework. If the rework costs more than the original scope, it becomes a change order. Each step in that chain adds cost and schedule: the RFI eats superintendent and PM time; the rework eats trade labor and material; the change order triggers a pricing and approval cycle before work can restart.
The true cost of change orders in construction breaks out the administrative overhead — the project management hours, schedule float consumed, and subcontractor premium for out-of-sequence work — that rarely appears in the change order value itself. On complex projects, the indirect cost can exceed the direct cost.
The thread through all of it: a single coordination failure in the documents typically generates an RFI y a change order y rework, in sequence. Preventing the document error prevents all three. That’s why the cost of change orders and the cost of rework are so closely correlated on the same projects.
Where the fix is cheapest: the pre-construction window
The cost of fixing a conflict is lowest before anything is built, and it drops sharply the earlier you catch it. The progression looks like this:
In design: A conflict surfaced before documents are issued is a coordination note. The designer updates the sheet; no field impact.
At bid / design review: A conflict surfaced before mobilization costs a clarification and a revised issue. No demo, no out-of-sequence crew work, no field disruption.
During construction, work not yet installed: Typically an RFI plus minor replanning. Some schedule impact; no demolition.
After work is installed: Demo, reinstall, change order, schedule impact, potential follow-on trade impacts. Ten-to-one ratio applies here.
This is why pre-construction QA is the highest-leverage intervention. The same effort that catches twenty coordination gaps during plan review would catch — at best — twenty change orders during construction, each requiring a separate resolution cycle, field disruption, and cost. The work is identical; the unit cost is not.
The practical implication: a thorough document review immediately before bid, while the full set is issued but before mobilization, is the window where the ten-to-one ratio works in your favor. Anything caught there costs a fraction of the same catch in the field.
Flikt’s approach: find the conflicts in the documents
The reason coordination failures persist isn’t that project teams don’t know they’re expensive. It’s that finding them in a large drawing set is slow, manual, and fatigue-prone. A senior reviewer reading hundreds of sheets against each other — structure against MEP, MEP against architecture, drawings against specs — will catch most of the high-probability conflicts and miss some of the cross-sheet ones that require holding two details in mind simultaneously.
Flikt runs Plan de revisión de construcción con IA directly on 2D PDF drawing sets — no BIM, no model exports, no modeling staff required. It reads the full document set the way a comprehensive review should: every sheet against every other sheet, drawings against specs, and across all disciplines simultaneously. It surfaces the spec-vs-drawing mismatches, cross-sheet conflicts, cross-discipline spatial conflicts, and missing-coordination gaps described above.
The benchmark Flikt uses to characterize drawing quality is conflictos por cada 100 hojas — the count of real, actionable coordination issues normalized by drawing-set size. It’s a concrete, comparable metric that lets owners and GCs evaluate drawing quality across design teams and project revisions. The data behind it — real conflict counts from real projects, including the 40-change-order case above — is on la página de evidencia.
For a full breakdown of conflict taxonomy and what the review catches versus what BIM clash detection catches, see detección de interferencias sin BIM and the conflicts per 100 sheets benchmark.
Where to focus if rework is already a problem on your projects
If you’re a general contractor seeing chronic rework on projects, the diagnostic starts with source attribution: what share of your change orders and rework traces to coordination failures in the documents, versus scope changes, versus unforeseen conditions? If it’s more than a third coordination-related, the intervention point is plan review — not field process, not subcontractor selection.
The right sequence:
- Review the documents comprehensively before bid — not just discipline-by-discipline, but across disciplines and against the specs.
- Benchmark drawing quality — conflicts per 100 sheets gives you a number you can track across design teams and revisions.
- Resolve conflicts before mobilization — the ones you surface in review are worth ten times their cost if left to the field.
For GCs who want to take this into a formal QA process, the pre-construction QA checklist y revisión de constructibilidad cover the full workflow.
If you’re an owner or developer who’s absorbing rework costs through GC contingency and schedule, the conversation to have is with your design team — and the question is how comprehensively the documents were reviewed before they were issued. The cost of rework in construction is largely a cost of information problems, and information problems are caught in review.
Flikt reviews your 2D plan sets for cross-discipline conflicts before construction — no BIM required, no modeling staff. Start with Plan de revisión de construcción con IA, review the documented results on la página de evidencia, o run the numbers for your own project.
¿Listo para detectar conflictos a tiempo?
Sube tu conjunto de planos y obtén detección de conflictos con IA, no se requiere BIM.