In multi-party work, one unacknowledged dependency or obsolete instruction can cause several teams to do the wrong work correctly—and then pay to do it again.

Projects involving owners, contractors, specialists, suppliers, regulators, and sequential dependencies are vulnerable to late discovery. Work can be technically competent and still wrong because it used an obsolete plan or missed a dependency. Published rework estimates vary sharply, so a pilot should measure its own preventable rework rather than promise a universal savings rate.

Contents (6 sections)

Evidence snapshot

Supported by cited sources
FindingScope or qualification
A 2026 ASCE contractor study estimated average precompletion rework at 0.38% of contract value and 0.76% including estimated postcompletion work.Exploratory sample; observed range 0.02%–7.34% and substantial underreporting.
A 2018 longitudinal study found mean reported rework around 0.39% of contract value.Direct reported cost; narrower than many industry claims.
Older studies report much higher ranges, including roughly 5% average direct cost or 2%–20%.Definitions and project mix differ; no single national rate is defensible.
NIST estimated inadequate information interoperability cost U.S. capital facilities $15.8 billion annually in 2002 dollars.Old model based on 70 organizations.

What the evidence does not prove

Supported by cited sources

Some rework is legitimate change or learning. Direct-cost systems undercount indirect burden while retrospective surveys can inflate it. Existing software already manages many coordination records; behavior and incentives may be the core problem.

Why different stakeholders can care

Proposed

Owners gain cost and schedule reliability; contractors gain fewer disputes; workers gain clearer instructions; customers and taxpayers gain value; and insurers and regulators gain traceability.

Question to investigate

Open question

What The Solar Guild must test

Research question

Define a preventable-rework taxonomy before the pilot and measure incidents against the team's own baseline rather than an imported industry percentage.

Core sources

Supported by cited sources
ASCE — What Field Rework Actually CostsLongitudinal construction rework studyNIST — Cost of Inadequate InteroperabilityCII — Guide to Construction Rework Reduction

References and limits

This page is published by The Solar Guild. Sources are listed so readers can inspect the basis of the page. A project statement is not independent proof unless the page identifies supporting outside evidence.

  • Problem 11 in The Solar Guild — Twenty Problems Worth Testing v1.0
  • Direct source links are provided above; quantitative claims retain their stated scope and qualification
  • The Solar Guild's response is explicitly separated from evidence that the problem exists