Rework on site: the 12-18% of the budget nobody measures (and how to cut it from the office)

The first difficulty isn't reducing rework. It's seeing it.

Rework wears a disguise. It shows up as:

• "The team's overtime this week"
• "One more round of document revisions"
• "A minor field adjustment"
• "A change order the client approved"
• "The delivery slipped a little"

None of those phrases sound like a loss. All of them are.

Why it goes unmeasured

There's no one to charge it to. If the error originated in design but was caught on site, whose cost is it? Since the answer is uncomfortable, it gets diluted.

It becomes normalized. After years, redoing deliverables is seen as "just how the business works," not as a fixable anomaly.

There's no box to check. Cost control systems track construction line items, not redone office hours.

This is the data point that changes the conversation.

When something goes wrong on site, the instinctive reaction is to look at execution: the contractor, supervision, logistics. But the studies point elsewhere: most errors were already baked into the information that reached the site.

What this looks like in practice

• The drawing was out of date relative to the model.
• The budgeted quantity didn't match the final design.
• Two disciplines used different criteria for the same thing.
• A routing change wasn't propagated to every document.
• The construction detail didn't account for a clash visible in the model.

None of that gets fixed on site. It gets fixed earlier, at the office, where the cost of correcting it is a fraction of the alternative.

The 1-10-100 rule

A classic quality rule that applies perfectly here: fixing an error in design costs 1. Fixing it in planning costs 10. Fixing it on site costs 100.

It's not a metaphor: it's the difference between changing a number in a model and demolishing something already built.

In engineering and infrastructure projects, rework almost always comes from one of these six places.

1. The data lives in two places

The model says one thing and the spreadsheet says another. Someone exported it, adjusted it by hand, and from then on the two versions diverged. Every project revision widens the gap.

2. The criterion lives in someone's head

How a line item is measured, what's included, what's excluded. If only one person knows, the result changes every time someone else does the work. And when that person leaves, the criterion leaves with them.

3. Changes don't propagate

The alignment changes. The model gets updated, but not the quantities, not the budget, not the detail drawing. Every document left un-updated is rework waiting to happen.

4. Review depends on the human eye

Checking naming, layers, consistency across drawings. It's tedious work, and the error slips in precisely because it's tedious.

5. Every team delivers differently

Two sections of the same project, done by two people, come out with different formats and criteria. The time spent reconciling them is pure rework.

6. Information arrives late to whoever needs it

The site starts working off revision B while the office is already on revision D. Nobody did anything wrong — the workflow simply isn't connected.

Notice the pattern: all six have a manual step where information can split off from its source. That's exactly where you intervene.

You don't need a management system or a consultant. You need three metrics and one month.

Metric 1 — Rework hours

Ask the team to log, in a shared sheet, the hours spent redoing something already delivered or already calculated. No detail needed: date, person, what was redone, how many hours.

What you'll discover: most companies are surprised by the total after the first month.

Metric 2 — Revisions per document

How many times the same deliverable gets issued before it's approved. If your documents routinely reach revision D or E, that's not rigor — something upstream is failing.

Practical benchmark: more than 3 revisions per document as a regular pattern signals a process problem, not client pickiness.

Metric 3 — Gap between budgeted and actual quantity

The gap between what the take-off said and what was actually built. It's the hardest-hitting metric, and the one that convinces leadership fastest.

How to present it

Rework hours per month        x  Loaded hourly cost   =  Monthly loss
Monthly loss                  x  12                   =  Annual loss
Annual loss / Revenue                                 =  % of the business

That last percentage is the one that unlocks budgets. If it comes out between 5% and 15%, you're in the industry's normal range — which is exactly the problem.

The interventions with the best cost-to-impact ratio, ordered by ease of implementation.

Level 1 — Connect the data to its source (weeks, high impact)

Have quantity tables, reports, and summaries generate directly from the model, instead of being exported and adjusted by hand.

What it eliminates: origin #1 and #3 from the previous module. If the table regenerates from the model, it can't fall out of date.

Typical cost: a tool like this is built in 1-3 weeks.

Level 2 — Automatic verification before delivery (weeks, high impact)

A button that checks naming, layers, required parameters, and consistency, and returns a report of what doesn't comply.

What it eliminates: origin #4 and a good chunk of #5. Review stops depending on someone having a good day.

Valuable side effect: the team learns the standard by using the tool, with no manual required.

Level 3 — Criteria written into the tool (weeks-months, structural impact)

Have the measurement rule embedded in the process, not in one person's head.

What it eliminates: origin #2, the most costly one long-term because it walks out the door when someone resigns.

Level 4 — Connected flow between office and site (months, high impact)

Have the published information always be the current version, with traceability of what changed.

What it eliminates: origin #6.

The plan has to work without stopping production. Nobody is going to halt projects to fix processes.

Days 1-30 — Measure without changing anything

• Shared sheet to log rework.
• At month's end, a one-hour meeting where the number goes on the table.
• Identify the three tasks that generate the most rework.

Cost: zero. Just the discipline of logging.

Days 31-60 — Attack the first one

• Take the number-one task on the list.
• Write the exact criterion on one page: what's in, what's out, what rule, what exceptions.
• Build or commission the automation for that single task.
• Run it in parallel with the manual method for two revision cycles, comparing results.

Why in parallel: it builds team confidence and catches whether the criterion was misunderstood.

Days 61-90 — Consolidate and measure the effect

• Replace the manual method with the tool.
• Re-measure the rework metric for that task.
• With the number in hand, decide whether to attack the second one.

By the end of 90 days, you have: a real measurement, one task solved, and a business case built on your own data to justify the next step. That's worth more than any theoretical presentation.