HelonicHelonic
Business Case

The $10,000 Eraser: Calculating the Real Cost of Preconstruction Catches

Helonic is an AI construction drawing analysis platform for teams researching preconstruction roi during drawing review.

Why finding issues early is the highest-ROI activity in construction

Everyone in construction knows that catching errors early is better than catching them late. It's obvious. But when you're justifying the cost of a new tool or an additional preconstruction review cycle, "better" isn't enough. You need numbers.

So let's put real numbers on it.

What is the 1-10-100 rule in preconstruction?

The 1-10-100 rule says a coordination issue costs about $1 to fix in design, $10 in preconstruction, and $100 after the work is in place.

$1
In Design

Cost to fix an error while still on the architect's screen

$10
In Preconstruction

Cost to fix via RFI before construction starts

$100
In the Field

Cost to fix through rework after construction begins

The exact ratios vary by project, but the principle is consistent: errors compound. A missing dimension costs almost nothing to add to a CAD file. The same missing dimension, discovered when the framer is standing there waiting for an answer, costs an RFI cycle plus idle labor. Discovered after the framing is complete? Now you're looking at rework.

The 1-10-100 rule is actually conservative. Some studies put the field multiplier at 150x or higher for certain types of errors.

How do hard clashes and soft clashes differ in preconstruction cost?

When people think about coordination issues, they usually think about hard clashes, the duct that runs through a beam, the pipe that conflicts with a column. These are dramatic. They're also, paradoxically, easier to catch. BIM software excels at finding them. They're visually obvious when you federate models.

The bigger cost driver? Soft clashes. These are the issues that don't involve physical overlap but still require rework:

Missing Information

A dimension that isn't shown. A material that isn't specified. A detail reference that leads to a blank page.

Conflicting Information

The plan says one thing, the schedule says another. The spec contradicts the detail. The elevation doesn't match the section.

Code Violations

Egress widths that don't meet code. Fire ratings that aren't continuous. ADA clearances that fall short.

Constructability Issues

Sequences that can't be built as drawn. Access that doesn't exist for maintenance. Tolerances that can't be achieved.

These soft clashes are harder to find because they require reading and understanding the documents, not just overlaying 3D models. They're also responsible for a disproportionate share of RFIs and change orders.

What does a single missed coordination conflict actually cost?

A single missed conflict, such as a duct through a beam, routinely costs tens of thousands once crews are on site, based on composite project data rather than a hypothetical.

Scenario: Plumbing Riser Conflicts with Structural Column

The plumbing drawings show a 4" waste stack in a chase location that conflicts with a structural column shown on the framing plans. The issue isn't discovered until the plumber arrives to rough in.

Plumber standby time (4 hours @ $85/hr)$340
Emergency RFI processing (architect + engineer review)$450
GC coordination time (PM + Super)$320
Reroute design and approval$800
Additional materials (offset fittings, longer runs)$275
Plumber rework labor (reroute installation)$680
Schedule impact: 2 days (framing crew idle)$2,400
Drywall patch (wall opened for reroute)$450
Total Cost of One Missed Conflict$5,715

That's one conflict. One. On a typical commercial project, preconstruction review might catch 20-50 issues that, if missed, would have similar or greater impact.

How do you calculate the ROI of catching issues in preconstruction?

Preconstruction review ROI is the avoided field cost of each caught conflict minus the cost of the review itself, which is usually a small fraction of one missed clash.

Example: $15M Commercial Office Project

Without Enhanced Precon Review
Issues caught in precon:25
Issues discovered in field:18
Avg. field issue cost:$4,500
Field rework cost:$81,000
With AI-Assisted Precon Review
Issues caught in precon:40
Issues discovered in field:3
Avg. field issue cost:$4,500
Field rework cost:$13,500
$67,500
Rework Avoided
~$3,000
Annual Tool Cost
22x
ROI

This is a conservative calculation. It doesn't include:

  • Schedule acceleration costs when multiple issues compound
  • Relationship damage with owners and architects from repeated RFIs
  • The time your PMs and engineers save on manual review
  • Reduced exposure to claims and disputes

Why does one missed drawing conflict cascade into more cost?

One missed drawing conflict rarely stays isolated; it cascades into adjacent trades, re-work, and schedule slip that the single-issue ROI number understates.

Consider: The plumbing reroute from our example might push the waste stack into a different wall cavity. That cavity might have been sized for a 2" pipe, not 4". Now the drywall framing has to change. The electrical boxes in that wall have to move. The finish schedule for the adjacent room might shift because the wall thickness changed.

One issue becomes three. Three becomes eight. The $5,700 problem becomes a $25,000 problem, and it all started with a conflict that was visible in the drawings, if someone had looked.

Why is a typical drawing review not enough to capture preconstruction ROI?

Every GC reviews drawings before construction; the ROI gap is how thoroughly and how consistently that review covers every sheet, not whether a review happens.

Manual review has limits:

Time Pressure

The bid deadline is Thursday. The IFC package is 400 sheets. Your PE has two other projects. Something is going to get skimmed.

Attention Limits

After 4 hours of reviewing mechanical plans, your eyes start to glaze. You're not finding issues, you're looking at pages.

Expertise Gaps

Your best PM knows commercial interiors cold. But this is a healthcare project with medical gas requirements she's never seen before.

Revision Fatigue

You reviewed the 50% CDs thoroughly. The 100% set arrives with 47 sheets revised. Who has time to re-review everything?

Automation doesn't replace human judgment. It extends human attention. It ensures that every sheet gets the same level of scrutiny, every time, regardless of schedule pressure or fatigue.

What numbers should you use when pitching preconstruction review?

When pitching preconstruction review to leadership, lead with avoided clash cost, RFI volume, and schedule days recovered rather than tool features.

1
Your Current Change Order Rate

What percentage of project cost goes to owner-caused vs. design-error change orders? Industry average is 5-10% of contract value.

2
Hours Spent on Manual Review

How many PE hours go into preconstruction document review per project? What's the fully-loaded cost of that time?

3
RFI Volume

How many RFIs does each project generate? What percentage are for issues that were visible in the documents but missed?

4
Recent Expensive Misses

What was the last field issue that cost more than $10,000? Could it have been caught in document review?

If you can prevent one $50,000 change order per year, just one, you've paid for the tool many times over. Most teams find dozens of issues per project.

How does Helonic change the ROI of preconstruction review?

Tired of discovering coordination issues after construction starts? Helonic's AI can scan your PDFs and flag missing information, conflicting details, and coordination issues in seconds, while the cost to fix them is still measured in dollars, not thousands.

The cheapest change order is the one you never have to process.

Book a Demo

Practitioner insight

Nobody in a leadership meeting argues with the 1-10-100 idea. They argue with whether it applies to their jobs. The pitch that lands is the one where you pull up your own last three projects and point at the field issues that were sitting right there in the drawings all along. Once a VP sees a $40,000 change order that a reviewer could have caught in an afternoon, the tool cost stops being the conversation. Bring their numbers, not ours.

Source: Conversations with preconstruction directors and estimating leads at commercial general contractors building internal business cases for review tooling, synthesized from Helonic customer interviews, 2026.

More Questions About Preconstruction ROI

What is the ROI of preconstruction plan review?
The return comes from moving fixes earlier, where they are cheaper. The CII 1-10-100 rule puts the cost of correcting an error at roughly $1 in design, $10 in preconstruction, and $100 in the field. On a project with meaningful rework exposure, avoiding even a handful of field corrections usually covers the review cost several times over. The honest answer for any specific job depends on how much rework that team is currently absorbing.
How much does preconstruction review save per project?
Preconstruction review savings vary with project size, delivery method, and how coordinated the set already is, so treat any single figure with suspicion. The mechanism is consistent: catching a conflict on a sheet removes an RFI cycle, a possible change order, and any installed work that would have needed removal. The most defensible number is the one you calculate from your own last few projects rather than an industry average.
What is the cost of skipping preconstruction review?
The cost shows up as RFI volume, change orders, and schedule slip rather than as a line item, which is what makes it easy to ignore. Conflicts that were sitting in the drawing set get discovered by a foreman instead of a reviewer, and each one then consumes an RFI, a response cycle, and sometimes rework. None of that appears in a budget as the price of not reviewing.
How long does preconstruction plan review take?
Manual review of a full set by experienced staff runs many hours and scales with sheet count, which is why most teams sample rather than read everything. AI-assisted review changes the shape of the work: the tool reads every sheet and flags candidates, and the reviewer spends their time confirming or dismissing those flags instead of hunting for them. The human judgment step does not go away.
What is the 1-10-100 rule in construction?
The 1-10-100 rule is a cost-escalation heuristic: an error costs roughly $1 to fix in design, $10 to fix in preconstruction, and $100 to fix in the field once work has been installed. The ratios are approximate and vary by trade and error type. What holds across projects is the shape of the curve. Every handoff an error survives adds more completed work that has to be undone, so the cost of the fix keeps growing even though the error itself never changed.
Which costs more on a project, hard clashes or soft clashes?
Soft clashes usually cost more in aggregate, even though hard clashes get more attention. A duct running through a beam is dramatic, and model-based coordination finds it reliably. A missing dimension, a detail reference pointing at a blank sheet, or a schedule that contradicts the plan requires someone to read and understand the documents to catch. Those gaps slip past federated models and show up later as RFIs and change orders.
How do I calculate what a single missed coordination conflict actually cost?
Add up every line the conflict touched, not just the rework labor. That means trade standby time, the emergency RFI cycle at the architect and engineer, GC coordination hours, redesign and approval, extra materials, the corrective installation, patching, and the days other crews lost waiting. The composite plumbing riser conflict in this article lands around $5,700. Most teams stop counting at the rework invoice and undercount the real number badly.
What numbers should I bring to leadership to justify a preconstruction review tool?
Bring four of your own numbers rather than industry averages. Your change order rate split between owner-driven and design-error causes, the fully loaded cost of the engineer hours you already spend on document review, your RFI count per project and what share came from issues visible in the documents, and the last field issue that cost more than $10,000. Numbers from your own jobs survive scrutiny in a way a vendor's benchmark slide does not.
Does AI-assisted review change the preconstruction ROI math?
AI-assisted review changes the input cost of preconstruction, not the escalation curve, and the curve is the reason precon review pays off at all. A tool like Helonic lowers the cost of a thorough pass over a large set, so more sheets get real scrutiny instead of a skim under bid-deadline pressure. The return still comes from the same place: issues caught on paper cost a fraction of the same issues caught after installation. Automation widens coverage. It doesn't replace the reviewer's judgment.
MS

Milind Sagaram

Co-founder & CEO, Helonic

Milind is the co-founder and CEO of Helonic, where he leads product and go-to-market for AI-powered construction drawing analysis. He works closely with general contractors, project managers, estimators, and owners to understand how drawing quality drives project outcomes - and where AI can reduce RFIs, change orders, and rework. Milind has interviewed hundreds of construction professionals across project delivery roles, from preconstruction estimators at ENR top-400 contractors to facilities directors at institutional owners, and uses those conversations to shape both product direction and the way Helonic talks about the work.

Areas of focus
  • Construction project delivery and preconstruction
  • RFI and change order economics
  • Owner and GC workflows for drawing QA/QC
  • Estimating risk and bid-stage scope assessment

How this page was researched: Reviewed against the CII 1-10-100 cost-escalation literature, current fully loaded labor and RFI processing rates used in the composite scenario, and the change order and RFI figures Helonic collects from general contractor preconstruction teams.

Last reviewed by Milind Sagaram · August 20, 2026

Related Resources

See what Helonic catches on your drawings

Upload your PDF set and we'll walk you through every coordination conflict, code gap, and dimension mismatch our AI flags.