Why construction ignored 47 years of its own productivity research and called the workaround “best practice”

Project management has a dirty secret it has spent four decades not discussing.

The single metric the discipline elevated to gospel Earned Value Management did not win because it is the most useful framework for running a construction project. It won because the U.S. Department of Defense required it. ANSI/EIA-748 standardized it in 1998 after DoD made compliance mandatory on major systems acquisitions. PMI codified it. The PMP exam tested it. An entire ecosystem of auditors, consultants, and software vendors built revenue around it. Two generations of project managers learned CPI and SPI as the native language of project health.

Meanwhile, the discipline that actually explains why construction bleeds money resource management has been sitting in plain view since the Carter administration. And the industry has spent 47 years pretending it doesn’t exist.

This is not an academic complaint. It is the reason your last megaproject ran over.

The research has been there since 1979

In the late 1970s, the Business Roundtable not exactly a radical body concluded that U.S. construction was in a productivity crisis serious enough to warrant a multi-year study. The result was the Construction Industry Cost Effectiveness (CICE) project, which ran from roughly 1979 to 1983 and produced over 20 reports. Its capstone, More Construction for the Money, identified labor productivity, contracting practices, and management of the work-front as the dominant levers of project performance.

Read that sentence again. Forty-seven years ago, the largest corporate users of construction services in America formally told the industry: the problem is not your cost variance reports. The problem is what your people are actually doing on site.

The industry responded by founding the Construction Industry Institute (CII) in 1983 at the University of Texas at Austin. Since then, CII has produced hundreds of research publications on workforce productivity, direct work rate sampling, foreman delay surveys, craft time-on-tools studies, and benchmarking across thousands of projects. The findings have been remarkably consistent across four decades:

Across published work-sampling research, direct work actual hands-on, value-adding craft labor has consistently landed between roughly 30% and 55% of paid craft hours on industrial construction projects. The rest is waiting, traveling, looking, fetching, reworking, attending unscheduled meetings, breaks, early quits, late starts, and the organizational friction that fills the gaps. CII’s RT 215 program documented this from the craft workers’ perspective across 1,996 craft respondents and 83 productivity factors (CII RS 215-1, Work Force View of Construction Productivity, 2006). CII’s RT 252 program the Construction Productivity Research Program that ran from 2007 through five formal phases defined construction productivity along three explicit dimensions: direct work rate, labor productivity (hours per unit), and rework rate (RS 252-1 through RS 252-1d, 2009–2013).

These are not contested figures. They are the most replicated findings in construction productivity research, sitting in plain view in the CII catalog for anyone who chooses to read them. A recent published analysis of 84 industrial projects across 2015–2023 found mean direct work rates of 46.4% on traditional projects and 52.9% on projects implementing WorkFace Planning (Neve et al., Frontiers in Built Environment, 2025). Even at the upper bound of best-in-class performance, roughly half of every paid craft hour does not produce installed work.

McKinsey’s 2017 Reinventing Construction report reaffirmed the broader stagnation: global construction labor-productivity growth has averaged just 1% per year over the past two decades, compared with 2.8% for the total world economy and 3.6% in manufacturing. U.S. construction productivity is lower today than it was in 1968. The opportunity cost of closing the gap, by McKinsey’s estimate, is $1.6 trillion annually.

So we have known for almost half a century that the labor we pay for produces installed work less than half the time.

And the industry’s flagship management discipline the one it spent four decades canonizing does not measure this, At all.

How EVM won, and why it wasn’t on merit

EVM is a good cost-and-schedule reconciliation framework. I will say that plainly so the EVM apologists can lower their pitchforks. It is a useful tool for what it does.

But it did not become dominant because project managers chose it after considering alternatives. It became dominant for five structural reasons that have nothing to do with whether it actually improves project outcomes:

1. It had a federal mandate. EVM’s lineage traces to DoD’s Cost/Schedule Control Systems Criteria (C/SCSC), formalized in 1967 under DoDI 7000.2. NDIA and the Electronics Industries Alliance jointly published EIA-748 in June 1998, codifying the modern 32-criteria EVMS standard, and DoD adopted it that August for Major Defense Acquisition Programs. EVMS compliance has been embedded in DFARS 252.234-7002 ever since. NASA, DOE, and civilian agencies followed. The standard is now maintained by SAE International, with EIA-748-D published in 2019 and EIA-748-E in development. Resource management never had a regulatory tailwind. Mandates drive adoption. Research papers do not.

2. It compresses to two numbers. CPI 0.92 and SPI 0.95 fit on an executive dashboard and require no explanation. Utilization deficit, mobilization tax, crew composition drag, and whitespace require context, a willingness to look at the work-front, and an executive who tolerates ambiguity. Executives reward the dashboard, not the truth.

3. It uses data that already exists. Every project has a budget and actuals. Earned value math runs on accounting data the CFO already collects. Resource utilization requires time-on-tools sampling, badge data, foreman delay surveys, and field observation. Most ERP systems don’t capture this. Most owners refuse to fund its collection. The data problem is real, but it is also a choice.

4. It serves the funder policing the spender. EVM is a procurement compliance instrument dressed up as a management discipline. The funder wants to know if the contractor is on budget. The contractor wants to defend their margin. EVM is the agreed accounting protocol for that dispute. It optimizes for contractual posture, not productive output.

5. It indicts the contractor. Resource management indicts the owner. This is the one nobody wants to say out loud, so I will.

A cost variance can always be blamed on scope creep, vendor performance, or change order disputes. A utilization deficit cannot. It points squarely back at the owner’s planning maturity, contracting strategy, work-front sequencing, permit-and-isolation processes, materials staging, and the silo structure that prevents trades from getting clean work fronts in the first place.

The owner is the only party in the contracting chain who has both the visibility and the authority to fix the 55/45 problem. The owner is also the party with the least incentive to surface a metric that says the work-front mess is theirs to clean up.

So nobody surfaces it. And the research literature sits on the shelf.

What PMI’s framework actually says about resources

Open the PMBOK Guide. Any edition. Look up “resources.”

You will find guidance on planning, estimating, acquiring, developing, managing, and controlling resources as inputs to project execution. You will find almost nothing on measuring whether those resources, once acquired, are actually producing installed work at a rate that approximates the rate you are paying for.

The framework treats resources as a procurement problem. The research has been telling us for 47 years that they are a productivity problem.

This is not an oversight. It is a category error baked into the foundation of the discipline. PMI’s center of gravity is knowledge work IT projects, product launches, business transformations where the assumption that “an assigned resource is a working resource” is roughly correct. In construction, that assumption is wrong by a factor of two.

A PMP-credentialed project manager can run a $500M industrial project, generate weekly EVM reports of immaculate quality, hit a CPI of 1.02 at handover, and never once measure the fact that the project paid for roughly twice the labor hours it received. Because nothing in the framework requires them to look.

The math when you actually measure it

Pick a number. Any number.

If your craft labor budget on a major industrial project is $200M and the most recent benchmarked data puts direct work rate at roughly 46% on traditional projects, then $108M of that budget is paying for time that did not advance the work-front. That is the good scenario.

Some of that is unavoidable. Travel time exists. Toolbox talks exist. Some delays are weather or genuine surprises. A realistic best-in-class direct work rate, sustained, sits in the low- to mid-50s and getting there is hard, deliberate work, not a poster campaign about safety culture. CII’s RT 252 Phase V research concluded that wrench time could be increased by approximately 15% on average through disciplined application of activity analysis tools.

The gap between a 46% direct work rate and a 55% direct work rate is $18M on a $200M labor budget. The gap between 40% and 55% is $30M. That is not a rounding error. That is a megaproject’s contingency. That is the difference between a profitable contractor and a litigated one. That is the difference between an owner who delivers on schedule and an owner who is in front of a regulator explaining the variance.

EVM cannot see this gap. By design. The earned value calculation treats every hour billed as an hour earned at the planned rate. The framework is mathematically incapable of distinguishing a productive hour from an unproductive one. You can have a CPI of 1.00 and a direct work rate of 28% on the same project, and the discipline will report it as healthy.

That is not project controls. That is bookkeeping in a project controls uniform.

Even the people who mandated EVM stopped believing in it

If EVM were the management discipline its defenders claim, you would expect its strongest advocates to be the agencies that pioneered it. The opposite is true. The federal apparatus that built and mandated EVM has been quietly stepping back from it for over a decade.

In January 2018, the Section 809 Panel, a 16-member advisory body established by Congress under the FY2016 National Defense Authorization Act to recommend acquisition reforms published Volume 1 of its Final Report. Section 4 was devoted entirely to the use of EVM on software programs running Agile methods. The Panel’s specific recommendation, #19, was bounded: eliminate the EVM mandate for Agile software development. But the language it used to justify the recommendation was not bounded. In what should give any defender pause, the Panel concluded that “another substantial shortcoming of EVM is that it does not measure product quality.” It went on to observe that a program could perform ahead of schedule and under cost on every EVM metric while delivering a capability that was unusable to the customer. The Panel’s broader implementation language read more sweepingly: program managers should be able to choose appropriate monitoring methods for their programs rather than be mandated to use EVM.

The contractor base agrees. In the 2010 Grant Thornton Government Contractor Industry Survey, of the federal contractors subject to mandatory EVMS, only 37% believed EVM was a cost-effective management approach. The 2013 18th Annual Survey, conducted with a different respondent pool, reached substantially the same conclusion: only 41% of EVMS-required contractors considered it a cost-efficient management tool, and only 34% reported ever receiving meaningful feedback from government personnel on the EVM data they were required to produce.

Read that again. After four decades of regulatory enforcement, fewer than half of the contractors forced to use EVM believe it is worth what it costs them to produce. This is not what a healthy management discipline looks like. This is what regulatory capture looks like.

The walk-back is no longer just sentiment — it is showing up in the regulations themselves. In September 2015, DoD Class Deviation 2015-O0017 raised the validated-EVMS threshold from $50M to $100M, meaning a contractor on a $99M cost-type contract no longer needed a formally validated system. The pace has accelerated. As part of the May 2025 Federal Acquisition Regulation Overhaul, DFARS Subpart 234.2 was rewritten and the EVMS reporting threshold was lifted from $20M to $50M (published in the Federal Register at 90 FR 5727, January 17, 2025, and implemented through DFARS Class Deviation 2026-O0011 in February 2026). For firm-fixed-price contracts of any dollar value, the current DFARS now explicitly discourages the use of EVM. The Pre-Award and Post-Award Integrated Baseline Review clauses were stripped out. DCMA has restructured its EVMS Compliance Metrics into a tiered system that explicitly deprioritizes most checks. EIA-748 itself is being reissued as Revision E, collapsing the 32 guidelines down to 27.

The mandate that built the EVM industry is being unwound in real time, by the same institutions that built it.

This does not mean EVM is going away tomorrow. It remains required for major defense development contracts, the IBR is still mandatory, and the audit ecosystem is too deeply entrenched to disappear. But the trajectory is unmistakable. The Pentagon believes in EVM with substantially less conviction than it once did. Civilian project managers in construction are roughly a decade behind that recognition.

If the federal procurement system that invented EVM is now publicly admitting that the metric does not measure product quality, the rest of the discipline should be asking what it has been pretending to manage for forty years.

Stop calling it best practice

EVM is a federally-mandated procurement compliance tool that the discipline has spent 40 years dressing up as a management philosophy. It is fine at what it does. It is not what construction project managers should be optimizing toward.

Resource management measured, instrumented, made visible, with the same rigor we apply to cost variance is the actual discipline of running construction. The research has been there since 1979. The frameworks exist. The metrics exist. The benchmarking data exists. None of it is novel. All of it has been ignored because the answer points at the wrong people.

I am tired of pretending this is a complicated debate. It is not. It is a courage problem.

If you are a project director on a program above $100M and you cannot tell me your craft direct work rate within five percentage points, you do not have a project controls function. You have an accounting function with a project controls letterhead.

The Business Roundtable said this in 1983. CII has been saying it ever since. McKinsey said it again in 2017. The next megaproject your organization underwrites will say it once more, in the form of a $40M overrun nobody can quite explain.

Forty-seven years of research is not an academic curiosity. It is a standing indictment. The only question is when the industry decides to read it.

Kyle Mussmacher is a Project Director with 30 years in industrial construction and the author of The Utilization Deficit: Why Construction Bleeds Money in the Gaps Nobody Measures. He writes at constructionresourceutilization.com.

---

Sources

• Business Roundtable, More Construction for the Money: Summary Report of the Construction Industry Cost Effectiveness Project, January 1983. (archived PDF)
• Business Roundtable, Construction Productivity Measurement, Report No. A-1, 1982.
• Business Roundtable, CICE: The Next Five Years and Beyond, 1988.
• Construction Industry Institute (CII), Work Force View of Construction Productivity, RS 215-1, 2006.
• CII, Construction Productivity Research Program — Phases I–V, RS 252-1 series, 2009–2013, including IR 252-2a Guide to Activity Analysis, IR 252-2b A Guide to Construction Rework Reduction, and IR 252-4d The Construction Productivity Handbook.
• CII Research Team 319, Advanced Work Packaging: Design through Workface Execution, 2013–2015 (designated CII Best Practice in 2015).
• Neve et al., “Examining the impact of Advanced Work Packaging and WorkFace Planning on direct work rates of on-site construction workers: a comparative analysis,” Frontiers in Built Environment, 2025.
• McKinsey Global Institute, Reinventing Construction: A Route to Higher Productivity, February 2017.
• EIA-748, Earned Value Management Systems, first published by NDIA and EIA in June 1998; currently EIA-748-D (SAE International, 2019), with EIA-748-E in development (reducing guidelines from 32 to 27). (Note: commonly referred to as “ANSI/EIA-748,” though ANSI dropped from the designation in 2005.)
• U.S. Department of Defense, DoDI 5000.02, Operation of the Adaptive Acquisition Framework; DFARS 252.234-7002, Earned Value Management System.
• Section 809 Panel, Report of the Advisory Panel on Streamlining and Codifying Acquisition Regulations, Volume 1, January 2018, Section 4 (Earned Value Management for Software Programs Using Agile), Recommendation #19. (DTIC — full report) (DTIC — Recommendation 19)
• Grant Thornton LLP, 15th Annual Government Contractor Industry Survey (2010), EVM cost-effectiveness findings; 18th Annual Government Contractor Industry Survey (2013), EVMS cost-efficiency findings (reported via Grant Thornton press release, January 16, 2013).
• DoD Class Deviation 2015-O0017, Earned Value Management System Threshold (September 28, 2015), raising the validated-EVMS compliance review threshold from $50M to $100M.
• Federal Register, 90 FR 5727 (January 17, 2025), updates to DFARS Subpart 234.2 — Earned Value Management System; DFARS Class Deviation 2026-O0011 (February 2026); FAR Subpart 34.2 (May 2025 FAR Overhaul revisions).
• DCMA Manual 2303-01 Volume 3, Surveillance: Earned Value Management; DCMA EVMS Compliance Metrics (DECM) v8.0 prioritization framework.

Construction’s biggest cost is the one nobody is measuring. Here’s the empirical case.

 

The Premise

Every project  from a $20M turnaround to a multi-billion-dollar capital build runs on a number that never makes the dashboard:

The percentage of paid hours that actually convert into installed work.

Call it wrench time. Tool time. Direct work. After thirty years inside mega-project execution, I’ve come to call it something else the Utilization Deficit. It’s the structural, recurring, quantifiable gap between what owners pay for and what gets built. It’s also the thesis I spent the last two years putting into a book.

This is not a productivity essay. Productivity asks: how fast does a tradesperson swing a hammer? The Utilization Deficit asks the harder question:

How often does the hammer ever leave the toolbox in the first place?

In fifty years of empirical data hundreds of thousands of observations across dozens of countries, the answer has been remarkably consistent. And remarkably ignored.

Exhibit A: The 32% Number Isn’t New. It’s the Baseline.

A study of US power plant projects in the 1970s found that only about 32% of daily construction activity was direct work, roughly 28% went to support tasks, and about 40% was wasted or idle time .

That study is half a century old. The number has barely moved.

Modern wrench-time benchmarking puts the industry average at 25–35%, with best-in-class organizations targeting 55–65% . The Construction Industry Institute’s Phase V research demonstrated that wrench time can be increased by an average of about 15 percentage points using activity analysis methods alone without adding a single craft hour.

Translation: The average job site is operating at roughly half the capacity its headcount and payroll already imply.

You’re not short on people. You’re short on the people you’ve already hired.

Exhibit B: 200,000 Observations Tell the Same Story

The Insight-AWP Time on Tools database, drawn from tens of thousands of observations across very large projects in Western Canada, the US Gulf Coast, and Western Europe approaching 200,000 data points  confirms the same band. The geography changes. The contractors change. The technology changes.

The percentage doesn’t.

That’s what makes the Utilization Deficit a structural phenomenon, not a project-specific failure and why I dedicated an entire chapter to its persistence across eras and geographies. If your wrench time matches a 1976 boiler retrofit, the variable isn’t the workforce. It’s the system inside which the workforce is asked to operate.

Exhibit C: The Megaproject Tax

McKinsey Global Institute’s Reinventing Construction analysis put hard numbers on what every operations leader feels in their gut:

            •          98% of megaprojects suffer cost overruns of more than 30%, and 77% are at least 40% late .

            •          In the United States, the construction sector’s labor productivity is lower today than it was in 1968 .

            •          Globally, construction labor-productivity growth has averaged about 1% per year over the past two decades, against 3.6% in manufacturing .

            •          If construction productivity caught up with the broader economy, the sector’s value-added would rise by an estimated $1.6 trillion about 2% of global GDP .

Every one of those overruns is, at its core, a Utilization Deficit problem with a different surname. Permits. Materials. Engineering. Scope. They all manifest as the same observable: paid crews not converting hours into installed quantities.

When 98 of 100 megaprojects overrun and the productivity needle hasn’t moved in 80 years, that’s not a string of bad luck. That’s a system performing exactly as designed.

 

Exhibit D: The Energy Infrastructure Pattern

A 2025 Boston University study covering 662 energy infrastructure projects across 83 countries, totalling $1.358 trillion in investment, found that more than three-fifths experienced cost overruns particularly on projects exceeding 1,561 MW in capacity .

The same study identified a non-linear failure mode most schedule risk models still don’t price: once construction time delay exceeds 87.5%, the cost escalation rate significantly increases .

Translation: there’s a cliff edge. Projects don’t degrade linearly they hit a threshold where utilization collapses and cost escalation accelerates. The Utilization Deficit doesn’t just bleed margin. Past a certain point, it compounds.

What the Industry Got Wrong

Orthodoxy says: if productivity is low, push the crew harder, add supervision, tighten reporting cadence.

The data says the opposite. A worker measured at 28% wrench time isn’t lazy. They’re a capable person trapped inside an inefficient system. Pre-stage the materials, sequence the permits, eliminate the travel dead time, fix the tool crib bottleneck and the same person delivers 50% more installed work without moving any faster.

This is the white space. The gap between scheduled and actual. The hours that hit a timesheet but never a deliverable. This is what owners are paying for and almost universally failing to measure.

I’ve spent three decades watching organizations confuse activity with output, and reporting cadence with control. The white space is where that confusion compounds  and it’s the chapter of the book I argued hardest to lead with.

The Carrying Cost Nobody Reports

Here’s the math that should be on every steering committee agenda:

If your project is running at 30% utilization, your effective workforce is roughly one-third of your nominal workforce. A 300-person crew is performing the work of 100 productive workers. The other 200 aren’t absent. They’re present, paid, badged on, and unable to convert hours into installed quantities because the system around them won’t let them.

At a fully burdened craft rate of $100–150/hour on a major capital project, every percentage point of utilization deficit translates to seven-figure carrying costs per month — costs that never appear on a variance report because they were baked into the baseline.

You’re not over-budget. You were never on-budget. The estimate just assumed a productivity rate that empirical data has been refuting for fifty years.

The Carrying Cost Nobody Reports

Here’s the math that should be on every steering committee agenda:

If your project is running at 30% utilization, your effective workforce is roughly one-third of your nominal workforce. A 300-person crew is performing the work of 100 productive workers. The other 200 aren’t absent. They’re present, paid, badged on, and unable to convert hours into installed quantities because the system around them won’t let them.

At a fully burdened craft rate of $100–150/hour on a major capital project, every percentage point of utilization deficit translates to seven-figure carrying costs per month costs that never appear on a variance report because they were baked into the baseline.

You’re not over-budget. You were never on-budget. The estimate just assumed a productivity rate that empirical data has been refuting for fifty years.

The Bottom Line

The empirical record is unambiguous. Across fifty years, hundreds of thousands of observations, dozens of countries, every major project class:

Construction routinely converts 25–35% of paid hours into installed work, while planning baselines assume 55–65%.

That gap has a name. It has a cost. It has a fix.

Ignoring it is the most expensive decision the industry keeps making and the one I wrote a book to put on the table.

Sources

            •          Griffis & Farr (2000), citing 1970s US power plant productivity study

            •          Construction Industry Institute, Phase V Research, IR 252-2a Guide to Activity Analysis

            •          Insight-AWP Time on Tools historical database

            •          McKinsey Global Institute (2017), Reinventing Construction

            •          McKinsey & Company (2015), The Construction Productivity Imperative

            •          McKinsey & Company (2024), Delivering on Construction Productivity Is No Longer Optional

            •          Boston University Institute for Global Sustainability (2025), Beyond Economies of Scale: Learning from Construction Cost Overrun Risks and Time Delays in Global Energy Infrastructure Projects

Kyle Mussmacher is a 30-year construction operations professional and the author of The Utilization Deficit (2026), available on Amazon in Kindle, paperback, and hardcover. He writes on resource utilization, mega-project execution, and white space management at constructionresourceutilization.com.

Capital construction is being measured by indices that were designed to answer a different question. Owners are paying nine figures a year for the difference, and most of them don’t know it.

The thing nobody on the dashboard is asking

Open the project controls report on any major capital program in North America right now,  petrochemical complex, transmission corridor, gigafactory, semiconductor fab, LNG terminal, data centre campus and you will find two numbers in roughly the same place on the cover page.

Cost Performance Index. Schedule Performance Index.

Both are useful. Both have done their job for forty years. Both answer questions that mattered enormously when Earned Value Management was codified in U.S. Department of Defense procurement in 1967 and adopted by the construction industry over the following two decades.

Neither answers the question that has quietly become the most expensive one on the program.

That question is: how much of the labor we paid for last week turned into permanent installed work?

CPI compares earned value to actual cost. It tells you whether you are spending at the rate you planned to spend. SPI compares earned value to planned value. It tells you whether you are installing at the rate you planned to install. Both indices take the baseline as a given and ask whether reality matches it.

The baseline is where the problem hides.

The baseline was built from estimator productivity norms. Those norms usually expressed in hours per unit of output assume a crew that starts the shift with tools in hand, material staged, and a work front open. They assume the security gate took five minutes. They assume the shuttle ran on time. They assume the lunchroom didn’t overflow. They assume the engineering drawing was right the first time and the permit was already issued and nobody had to walk back to the lay-down yard for the missing fitting.

Those assumptions are baked into the unit rate. They were never measured. And every dollar that flows through CPI passes through them without ever being interrogated.

That’s the gap. It has been there the whole time.

What forty years of research actually says

The construction productivity research literature is unambiguous about the size of the gap.

The Business Roundtable’s Construction Industry Cost Effectiveness Project, conducted between 1977 and 1983, was the first serious study at scale. Its Report A-1, Measuring Productivity in Construction, concluded that the U.S. construction industry had no common definition of productivity and no standard way to measure it. The Construction Industry Institute (CII) was founded in 1983 specifically to address that finding. Forty years of continuous research has followed.

The conclusions have been stable for decades.

Construction work-sampling studies,  the methodology where trained observers record what each worker is doing at random instants throughout a shift consistently find that direct work, defined as hands-on installation of permanent work, occupies 30 to 35 percent of paid craft time on typical sites. Best-practice operations reach 50 to 55 percent. The Insight-AWP public database includes roughly 200,000 such observations across major industrial projects in Western Canada, the U.S. Gulf Coast, and Western Europe.

FMI Corporation’s 2023 Labor Productivity Study, which surveyed more than 250 senior leaders at U.S. self-performing contractors, estimated that labor inefficiency cost the U.S. construction industry between thirty and forty billion dollars in 2022 alone. Sixty-three percent of contractors named lack of qualified craft labor as the top productivity factor on their projects.

None of this is new. None of it is contested.

What’s new is the math the gap implies on a modern megaproject.

A typical large capital program runs 1,500 to 2,500 craft. At a fully burdened rate of $130 to $150 per hour across a 50-hour billable week, weekly labor spend lands somewhere between $10 million and $20 million. If 30 to 50 percent of that labor is not converting into installed work, and the literature says it isn’t  the gap is $4 to $9 million a week. Annualized: nine figures, on a single program.

A multi-billion-dollar capital build is not absorbing that loss as inefficiency. It is absorbing it as schedule slip, contractor claims, and management’s eventual quiet acknowledgment that

“construction is hard.” Those are downstream symptoms. The upstream cause is that nobody put the gap on the dashboard.

Why CPI and SPI never caught it

This is the part owners need to understand and most don’t.

CPI and SPI are not failing. They are succeeding at exactly what they were designed to do. The problem is what they were designed to do.

Earned Value Management came out of a procurement environment in the 1960s where the central question was contract control. Was the contractor delivering against the contracted scope at the contracted rate? CPI and SPI answered that question rigorously and have continued answering it for sixty years.

What no one asked, because the procurement model didn’t require it, was whether the contracted rate itself reflected a productive use of labor. The contractor priced the unit rate. The owner accepted it. The unit rate absorbed the deficit. CPI then measured whether actual cost matched the unit rate. The deficit became invisible the moment the contract was signed.

That worked when capital programs were small enough that the deficit, even at thirty or forty percent, fit inside a tolerable risk envelope. A two-hundred-million-dollar build absorbing twenty million in unmeasured labor inefficiency was a problem. A four-billion dollar program absorbing four hundred million is a different category of problem.

The capital scale changed. The measurement regime didn’t.

What an empirical answer looks like

There is a way to put the gap on the dashboard. The methodology is not new. The translation to executive readability is.

Three metrics, calculated from data the owner already collects supplemented by activity sampling that has been standard CII practice since the 1980s.

Utilization Deficit Index (UDI). One minus the ratio of productive installed hours to paid site hours. Bounded between zero and one. Reports weekly. Sits on the same page as CPI and SPI. A UDI of 0.50 means the owner is paying for one hundred hours to obtain fifty hours of productive installed work. Calibrated against the published direct work rate literature: typical programs land at 0.40 to 0.55, best-practice at 0.30 to 0.40, anything above 0.55 is an active constraint.

Carrying Cost of Deficit (CCD). UDI multiplied by paid hours multiplied by the fully burdened rate. Reports the deficit in dollars. Reported as both Total CCD — the full financial weight of the gap — and Addressable CCD, which subtracts the irreducible floor imposed by mandatory non-productive activities like legally required breaks, regulatory security screening, and essential safety stand-downs. The floor is real. Naming it is what separates a credible measurement from a marketing claim.

Logistics Drag Coefficient (LDC). The share of the deficit owned by the site logistics function — traffic, parking, shuttle, security throughput, lunchroom capacity, in-area material movement — versus the share owned by engineering, planning, supply chain, or QC. LDC turns the executive conversation from “the deficit is large” into “the deficit lives here, and this function holds the lever.”

The metrics are not proprietary. The math is forty years old. What’s new is putting them next to CPI and SPI on the cover page of the executive report and asking the program sponsor to explain the gap.

What an owner should demand

For any owner running a capital program above five hundred million dollars, four questions are now legitimate to put on the table.

What is our weekly UDI? Not estimated. Not assumed. Measured against an activity sample drawn under the standard CII protocol.

What is our Total CCD and what is our Addressable CCD? Not “labor cost.” Not “productivity.” The dollars we are paying for hours that are not converting into installed work, and the portion of those dollars we can credibly close.

What is our LDC and which function owns it? Not “everyone is responsible.” A specific number with a specific owner.

What is our trajectory? UDI moves. So does LDC. The right question is not “what is our number” but “is it improving, and at what rate, and against what intervention.”

These four questions are not radical. They are the questions a CFO asks about every other line item on a balance sheet that runs into nine figures. The fact that they are not currently asked of construction labor on most major capital programs is a measurement-regime artifact, not an industry necessity.

What this is not

The argument is not that EVM should be retired. CPI and SPI continue to measure what they were designed to measure, and on capital programs they remain essential.

The argument is that EVM is incomplete. The half it does not measure has become the more expensive half. The literature has been clear about this for thirty years. What has been missing is a translation layer that puts the established research on the same page as the financial reports executives already read.

That translation exists now. Whether owners adopt it is a function of whether they decide the question is worth asking.

For programs at modern megaproject scale, the question is no longer optional. The deficit is no longer absorbable. And the indices on the cover page of the program report do not see it, because they were never designed to.

The decision to look is the hard part.

Everything that follows from that decision — methodology, measurement protocol, intervention prioritization — is forty years old and well documented.

The only question is whether owners are prepared to demand the number. The literature, the data, and the math have been waiting.

Kyle Mussmacher is the author of The Utilization Deficit*. He writes on construction resource utilization, measurement gaps in capital programs, and the structural distance between paid labor and installed work on megaprojects.* #ConstructionManagement #CapitalProjects #Megaprojects #ProjectControls #EarnedValueManagement #ConstructionProductivity #ProjectManagement #ConstructionIndustry #LeanConstruction #CFO #CapitalEfficiency #ConstructionFinance #ProjectFinance #UtilizationDeficit #ConstructionResourceUtilization

Why construction is about to spend millions scaling a problem nobody has measured and what my book warned was coming.

I wrote a book about this. I called it The Utilization Deficit. The argument, in one sentence: every contractor in Canada pays for roughly 100 hours of labour to get roughly 55 hours of installed work, and nobody is measuring the other 45.

Last week, on a construction webinar hosted by On-Site Magazine, an insurance executive named David Bowcott summarized the entire thesis without meaning to. The panel featured Procore, CMiC, EllisDon, and PLATFORM Insurance. The topic was agentic AI digital employees, embedded in workflows, executing work instead of just summarizing it. And in the middle of a polished vendor conversation, Bowcott said this:

           “We don’t have a knowledge problem. We have a capacity and consistency problem.” Then everyone moved on.

They shouldn’t have. Because that sentence is the entire premise of my book and the entire reason most of the AI investments this industry is about to make are going to fail.

The sentence, decoded

“We don’t have a knowledge problem.” Translation: contractors are drowning in data. BIM, schedules, IoT, cost systems, safety reports, daily logs, drawings, RFIs, submittals. More information than any team can process.

“We have a capacity and consistency problem.” Translation: the people paid to do the work don’t have time to do the work. They’re chasing paper, reconciling systems, updating logs, producing reports.

That is the utilization deficit. Named by an insurance executive on a construction webinar, and nodded at by the rest of the panel as if it were wallpaper.

In the book, I call the 45% white space — the administrative, coordination, and consistency work absorbed into every paid hour that does not produce installed work. It is not fraud. It is not laziness. It is the carrying cost of running a project the way projects are run. It sits on every P&L. Nobody measures it. Nobody reports it. Nobody owns it.

And now we’re about to hand it a bigger budget.

What AI agents actually do

Procore has AI agents in open beta. CMiC is building them. EllisDon is already deploying them on Palantir Foundry. The use cases the panel listed — RFIs, submittals, daily logs, QA/QC, materials coordination, schedule reconciliation, compliance  are real. The agents work. The ROI stories are coming in.

Here’s the problem.

Every one of those use cases sits inside the 45%. Every one of them is white space  the administrative carrying cost between units of installed work. The vendors are selling machines that make the non-value-add activity faster, cheaper, and more consistent.

That is a real productivity gain. It is also a dangerous one.

Because if you do not measure the deficit first, you will use AI to industrialize it. That is the warning at the centre of my book, and the industry walked straight into it in real time on that panel.

The math nobody is running

The Utilization Deficit spends a full chapter on this, but here is the compressed version.

Say you run a $500M project with $200M of direct labour. On a 55/45 split, roughly $90M of that labour is carrying cost  paid hours not producing installed work. Some of that is unavoidable. A lot of it is not.

Now deploy AI agents across RFIs, submittals, logs, and reconciliation. You speed up the administrative layer by 30%. That feels like a win. Your dashboards show it. Your CFO is happy.

But what actually happened? You made your waste layer more efficient. The carrying cost is still there. The 45% is still 45%. You have not reclaimed a single hour of installed work. You have automated the symptoms of a problem you never diagnosed.

Worse: the vendors now own the record. Your workflows, your bottlenecks, your exceptions all flowing through their platform, priced on consumption. Your carrying cost is now a line item on someone else’s invoice.

What the leaders are actually doing

Read the EllisDon story carefully. They didn’t buy agents. They spent years building a

unified data ontology on Palantir Foundry. They structured safety, schedule, estimating, cost, logistics, and field data into a single operational view. Then they pointed agents at it.

That sequence matters. The foundation came first. The automation came second. And the foundation is the expensive part  years of structuring work, not a SaaS licence.

Most contractors do not have that foundation. They have systems. They do not have structure. They are about to buy agents and point them at fragmented, inconsistent, untagged data, and the agents will cheerfully automate the mess.

This is the gap. This is the sequence problem. And it is exactly what the book was written to prevent.

The order of operations

Before you buy an agent, you need three numbers. The book devotes its second half to building them.

Your utilization baseline. What percentage of paid hours produce installed work? What percentage is carrying cost? By trade, by crew, by phase, by project. Not an industry benchmark. Yours.

Your white space map. Where is the 45% sitting? Which processes, which handoffs, which meetings, which approvals, which waiting? Not guesses. Measured.

Your leverage points. Which slices of the 45% are the largest, most repeatable, and most automated ? That is where agents earn ROI. Everywhere else, they are theatre.

Without these numbers, an agent is a tool in search of a problem. With them, it is a precision instrument.

The vendors will not give you these numbers. The vendors are not incentivized to give you these numbers. Their business model is consumption. The more of the 45% that flows through their platform, the better their quarter.

The uncomfortable conclusion

AI agents are not the problem. They are a real and valuable technology, and the contractors who deploy them well will outperform the ones who don’t. That part is true.

But deploying them well requires knowing what you’re automating. And the industry is about to skip that step at scale which is why I wrote the book now, and not in five years when the cheques have already cleared.

The utilization deficit is the question every AI investment should answer before the cheque

is signed. How much of the 45% will this recover? How will we measure it? What’s our baseline? If the vendor cannot answer those questions, you are not buying productivity. You are buying velocity on waste.

Measure first. Automate second.

In that order. Always.

The Utilization Deficit is available on Amazon in Kindle, paperback, and hardcover.

Every contractor wave you bring onto site is burning weeks of productive time before a single meaningful unit of work gets installed. Nobody budgets for it. Everyone pays it.

There’s a cost hiding in your project schedule that doesn’t show up in your cost report, doesn’t get flagged in your earned value analysis, and almost never makes it into a lessons learned debrief.

It’s the price of starting.

On large capital projects  especially multi-contractor, phased-execution programs the workforce doesn’t arrive and immediately produce. There’s a ramp. A slow, expensive, entirely predictable ramp that the industry has somehow decided doesn’t need to be planned for.

I call it the Mobilization Tax.

What It Is

The Mobilization Tax is the utilization loss incurred between a contractor’s first day on site and the point at which their workforce reaches productive capacity.

It isn’t caused by incompetence. It isn’t caused by bad contracts or poor scheduling. It’s caused by the basic reality of deploying human beings into a complex, active worksite for the first time.

Think about what actually happens in those first weeks:

Workers are completing site-specific orientations and safety inductions

Supervisors are learning the access control system, the lay down areas, the material flow

Crews are waiting on badging, PPE fitment, and system access

Tool and equipment setups are being sorted out

The contractor’s internal coordination structure is still taking shape

 Workers are building mental maps of the site — where things are, who to call, what the unwritten rules are

None of those people are installing anything. They’re on the clock, on your project, and their utilization is functionally near zero.

On a small project, this is noise. On a mega-project with multiple contractor waves mobilizing across a multi-year schedule, this is a serious, recurring, compounding drain.

Why Nobody Plans For It

The Mobilization Tax goes unmanaged for one reason: it’s treated as a transition, not a cost.

Project schedulers see mobilization as a phase, not a performance variable. The contractor “mobilizes” in Week 1, and then by implication, they’re ready to work. The baseline productivity assumption kicks in. The schedule starts counting.

But the workforce doesn’t know that. They’re still figuring out where the bathroom is.

There’s also a contract problem. Most agreements are structured around deliverables, milestones, and installed quantities. The ramp-up period doesn’t violate anything  the contractor isn’t in default. They’re just slow. And slow-but-compliant is invisible to the tracking systems most projects use.

The result is a systematic gap between planned productivity and actual productivity in the early weeks of every contractor deployment — a gap that hits every wave, every phase, every new crew introduction. It compounds across the life of the program.

What It Actually Costs

Let me make this concrete.

Take a contractor mobilizing 50 workers over two weeks. Assume a blended rate of $75/hour, a standard 40-hour week, and a realistic mobilization utilization rate of 30% for the first two weeks — compared to a steady-state target of 70%.

That’s a utilization gap of 40 percentage points across 100 worker-weeks.

The math:

100 workers × 40 hours × 2 weeks = 8,000 hours paid

At 30% productive utilization: 2,400 productive hours

At 70% target: 5,600 productive hours

Loss: 3,200 hours of productive capacity

At $75/hour: $240,000 in unrecoverable utilization loss — from a single mobilization wave

Now scale that. A program with six contractor waves mobilizing across three years isn’t losing $240K. It’s losing multiples of that — quietly, predictably, and invisibly.

The Compounding Problem

What makes the Mobilization Tax particularly brutal on mega-projects is that it compounds.

Phased programs don’t mobilize once. They mobilize in waves — new scopes, new trades, new subcontractors layering in as the work evolves. Each wave pays the tax. Each wave takes weeks to reach productive capacity. And because the schedule usually doesn’t account for this ramp, the productivity shortfall from Wave 1 is still being recovered when Wave 2 hits.

You’re not managing one mobilization. You’re managing overlapping mobilization curves, each dragging the overall workforce utilization down while the project expects a steady state output.

This is one of the core reasons mega-projects chronically underperform against their early phase productivity forecasts. It’s not a planning failure. It’s an unrecognized structural cost.

What You Can Do About It

The Mobilization Tax can’t be eliminated — but it can be measured, planned for, and partially mitigated.

1. Build mobilization curves into your baseline. Stop assuming Day 1 productivity equals steady-state productivity. Model a ramp curve  25–30% in Week 1, 45–50% in Week 2, 60–65% in Week 3  and build that into your labour forecast. You’ll have a more honest schedule and a visible target to manage against.
2. Sequence onboarding to protect the first week. The fastest way to accelerate the curve is to front-load the administrative drag. Pre-credential workers before they arrive. Run orientation cohorts in advance. Have badge packages ready. Every hour you reclaim from administrative ramp-up in Week 1 is an hour that goes into productive work.
3. Assign mobilization mentors or buddy supervisors. Experienced site workers who know the access points, the material flow, the unwritten rules — pairing new arrivals with them cuts the site-familiarity ramp significantly. This is especially valuable on complex sites where physical navigation alone costs days of productivity.
4. Track mobilization utilization separately. If you’re not measuring it, you’re not managing it. Build mobilization utilization as a distinct KPI in your workforce tracking system. Give it a target. Report against it. The act of measurement alone changes how teams approach the ramp-up period.
5. Negotiate mobilization support terms in contracts. Some of the most progressive capital programs now build contractor onboarding support into their contract structure  site orientation services, pre-credentialing windows, dedicated mobilization coordination. If you’re running a multi-contractor site, absorbing some of that ramp cost centrally is often cheaper than watching it erode contractor productivity week after week.

The Bottom Line

Your project is paying a tax on every contractor mobilization whether you track it or not.

The choice isn’t whether to pay it. It’s whether to pay it blind or pay it with your eyes open  with a plan to reduce it, a baseline that accounts for it, and a tracking system that tells you how much it’s actually costing.

Most projects pay it blind.

The ones that don’t are the ones that finish closer to the schedule they planned.

Kyle Mussmacher is the author of The Utilization Deficit and the founder of a blog  focused on construction resource utilization. He writes about the workforce productivity gaps hiding in plain sight on large capital projects.

https://www.amazon.ca/UTILIZATION-DEFICIT-Construction-Bleeds-Measures/dp/B0GXGCCKK8

I spent the first years of my construction career waiting to work.

Not because I didn’t want to. Because the system wouldn’t let me.

I’d show up ready to go. Tools in hand. And then I’d wait. Wait for a work package that wasn’t ready. Wait for materials that were delayed in delivery. Wait for the trade ahead of me to finish so I could access the area. Wait for a scaffold that hadn’t been built. Wait for information that hadn’t arrived.

If you’ve ever worked on the tools in construction, you know exactly what I’m talking about. That frustration of being on the clock, wanting to be productive, and having nothing you can do about it.

That frustration never left me. It followed me from the field into project management, into operations, into leadership. And everywhere I went, I saw the same thing: the construction industry has accepted unproductive time as normal. It’s baked into every estimate, absorbed into every budget, and invisible in every cost report.

I refused to accept it.

So I studied it. For years. Across projects. Across trades. Across organizations. I wanted to understand why construction labour productivity has barely improved in decades while every other industry has transformed. I wanted to quantify what everyone on the tools already knows but nobody in the boardroom measures.

What I found is this:

Only 55% of paid labour hours on construction projects produce installed work.

The other 45% disappears into what I call white space — the structural gap between resource supply and resource demand. It’s the piping crew waiting for scaffold. It’s the electrician standing by for mechanical completion. It’s 2,000 workers losing 40 minutes every morning getting through the gate. It’s $12 million on a single project consumed by paid time with no scheduled scope.

And nobody is measuring it.

The construction industry has built world-class systems for telling you what happened yesterday. SPI. CPI. Earned value. Variance analysis. These are rear-view mirrors. They tell you where you’ve been, not where the money is going.

White space is a leading indicator. It tells you where tomorrow’s cost growth is hiding — before it shows up in your forecast.

I wrote a book about it.

The Utilization Deficit: Why Construction Bleeds Money in the Gaps Nobody Measures is available now on Amazon.

This book is for every tradesperson who’s ever sat idle waiting for a system that wasn’t designed for their productivity. It’s for every project manager who’s looked at a labour report and known the numbers didn’t tell the whole story. It’s for every executive who’s watched budgets disappear into gaps nobody can explain.

It captures everything I’ve learned about resource utilization, carrying cost, and the measurement gap that costs the construction industry hundreds of billions of dollars every year.

But more than that — it’s a challenge.

Stop accepting that 45% waste is normal.
Stop being satisfied with reports that only look backward.
Stop paying for nothing.

Start measuring white space.
Start quantifying the untapped productive hours you’re already funding.
Start seeing the millions in savings hiding in the gaps between your trades.

The money is there. It’s always been there. The industry just hasn’t been willing to look.

This book is my attempt to change that. I hope it changes how you see your next project.

Link to the book in the comments.

ConstructionManagement #ResourceUtilization #ConstructionProductivity #LeanConstruction #ProjectManagement #ConstructionIndustry #LabourProductivity #MegaProjects #ConstructionLeadership #WhiteSpace #CarryingCost #ConstructionCostManagement #EarnedValueManagement #ConstructionOperations #NewBookRelease

Every project has a schedule. Every project has a budget. Almost none of them have a whitespace strategy. That’s not an oversight — it’s the single most expensive norm in the construction industry.

!” Kyle Mussmacher   !” April 2026   !” 9 min read

Here’s a question that should keep every project director awake at night: what happens to a $140/hour ironworker when there’s no iron to set?

He doesn’t vanish. He doesn’t pause his billing. He stands in a laydown yard, or he gets moved to a task that doesn’t need him, or most perversely he gets sent home and remobilized three days later at twice the coordination cost. His wages still accrue. The crane he was supposed to feed still sits on the pad burning rental. The concrete crew downstream that needed his embeds still waits.

That dead time between productive tasks is whitespace. And the construction industry, globally, has made a collective decision not a conscious one, but a decision nonetheless to pretend it doesn’t exist.

 WHAT WHITESPACE ACTUALLY IS

Whitespace is the unproductive interval between planned work scopes where labor, equipment, and site infrastructure are mobilized but not generating value. It’s not the lunch break. It’s not the weather day. It’s the structural gap in how work is sequenced, contracted, and deployed that guarantees a portion of every crew-hour purchased produces nothing.

In a well-run manufacturing plant, this concept has a name: idle time. It’s measured, reported, and minimized with religious intensity. Toyota built an empire on eliminating it. In construction? We don’t even have a standard field for it in most project controls software .

You can’t manage what you refuse to name. And the construction industry has spent decades refusing to name the gap between work packages as anything other than “Boat” or “schedule logic.” Those are planning euphemisms. Whitespace is a cost event.

The distinction matters. Float is an abstraction on a Gantt chart. Whitespace is a foreman watching his crew drink coffee at 9:15 AM because the area they were supposed to work in hasn’t been turned over. Float costs nothing on paper. Whitespace costs

$800–$2,400 per crew per day in loaded labor alone before you touch equipment, supervision, or the knock-on delays it creates downstream.

 THE ANATOMY OF A WHITESPACE EVENT

Whitespace doesn’t appear because someone made a single bad decision. It’s emergent. It comes from the collision of systems that were each designed in isolation and never reconciled against the reality of a shared physical site.

SEQUENCING GAPS

Work Package A Finishes Tuesday. Work Package B in the same area can’t start until Thursday because the turnover process requires an inspection that’s only scheduled on Wednesdays. Two full days of whitespace for every trade staged in that zone. Multiply it across 40 areas on a mega-project and you’ve just manufactured a month of dead time nobody will ever report.

MOBILIZATION ASYMMETRY

Contractors mobilize based on contractual milestones, not work-face readiness. A mechanical crew might arrive on-site two weeks before their prerequisite civil scope is complete because their contract says “mobilize by March 1” and nobody updated the constraint when civil fell behind. Those two weeks aren’t tracked as whitespace. They’re tracked as “on-site” and billed accordingly.

THE SHARED SERVICES BOTTLENECK

Cranes, scaffolding, rigging teams, and material handlers are shared across multiple trades. When the schedule compresses, these resources don’t scale linearly. They create queues. A crew that could be productive waits 90 minutes for a crane pick that was supposed to take 20. That 70 minutes is whitespace, invisible, unmilled to any work package, and repeated across every crew on the hook that day.

TYPICAL CREW-DAY UTILIZATION — INDUSTRIAL MEGA-PROJECT

 

 

 Productive Hours    Whitespace (Non-Productive)

Look at that chart. On a typical industrial project, more than half of every crew-day is whitespace. Instrumentation crews,  the ones doing the most coordination-dependent work  routinely lose two-thirds of their available hours. And yet nobody on the project team has “whitespace” in their job title, their KPIs, or their morning standup agenda.

 WHY NOBODY MANAGES IT

This is the part that should genuinely bother you. The Financial opportunity is staggering. A $2 billion mega-project with 55% average whitespace across its labor force is carrying roughly $400–$600 million in non-productive labor cost. Even a modest 15-point improvement in utilization would recover $100M+ without adding a single worker or extending the schedule by a day.

So why isn’t every owner, every EPC, every Construction Management firm obsessing over this?

1. THE CONTRACTING MODEL HIDES IT

Lump-sum contracts push whitespace risk to subcontractors, who bury it in their bids as a cost of doing business. Cost-plus contracts push it to owners, who see labor hours billed but have

no mechanism to distinguish productive hours from whitespace. Neither model creates a feedback loop. Neither model creates accountability. The cost is real but the line item doesn’t exist.

2. THE TOOLS AREN’T BUILT FOR IT

Primavera tracks activities. Procore tracks documents. Nothing in the standard construction tech stack tracks the gap between activities at the crew level. Earned value tells you whether you’ve done the work you planned. It tells you absolutely nothing about whether the labor you mobilized was doing that work — or standing in a parking lot waiting for it.

3. NOBODY OWNS IT ORGANIZATIONALLY

The project manager owns the schedule. The superintendent owns the field. The contracts manager owns the subcontracts. Whitespace lives in the seams between all three  and in construction’s rigidly siloed org charts, seams are where accountability goes to die. Managing whitespace requires a cross-functional view that most project organizations are structurally incapable of producing.

4. THE INDUSTRY CONFUSES ACTIVITY WITH PRODUCTIVITY

This is the deepest problem. Construction culture equates presence with progress. If workers are on-site, if cranes are swinging, if material is moving  the project “feels” productive. Nobody wants to be the person who says “yes, we have 2,000 workers on site, and 1,100 of them aren’t producing value right now.” That conversation requires a kind of honesty the industry hasn’t developed the appetite for.

THE GLOBAL WHITESPACE COST A CONSERVATIVE ESTIMATE

$1.6 Trillion / Year

Global construction output ≈ $13.5T annually.

Labor typically represents 40–50% of project cost ≈ $5.4T–$6.7T.

Average whitespace across all project types ≈ 30–45%. Conservative mid-range whitespace cost: $1.6T+ in nonproductive labor spend, every year, worldwide.

Read that number again. $1.6 trillion. That’s not a rounding error. That’s larger than the GDP of Australia. It’s the single biggest efficiency failure in the global economy, and it doesn’t have a Wikipedia page.

WHY THE GLOBAL COMMUNITY HASN’T ADOPTED IT

The honest answer is uncomfortable: managing whitespace requires the industry to admit that its current model of work execution is fundamentally broken.

That’s a hard sell. The construction industry is one of the most conservative on Earth — not politically, but operationally. Methods that were standard in 1985 are still standard today. The apprenticeship model, the trade jurisdictions, the paper-based turnover processes, the contractual structures  all of it is load-bearing. Changing any one piece threatens the others.

Whitespace management isn’t a plugin. You can’t bolt it onto an existing project and hope for results. It requires rethinking how work is sequenced at the constraint level, how trades are mobilized against work-face readiness instead of contractual dates, how shared resources are allocated dynamically instead of by seniority or loudest-foreman-wins. It requires real-time data infrastructure that most job sites still don’t have. And it requires someone;  a person, a team, a function whose entire job is to see the gaps between the work and close them.

The industry has avoided this because it’s systemic surgery, not cosmetic. And in a sector that operates on thin margins with enormous liability exposure, systemic surgery feels like a risk nobody wants to own.

 THE FINANCIAL OPPORTUNITY IS OBSCENE

But here’s the thing about avoiding systemic surgery: the patient is still bleeding.

Every mega-project that runs over budget is, at some non-trivial percentage, paying for whitespace it never quantified. Every owner who wonders why their $500M project came in at $720M is looking at the wrong line items. The overrun isn’t in steel prices or change orders  or at least, it’s not only there. It’s in the 1,200 crew-days of dead time that never appeared in a single report because no one was measuring it.

The firm that figure this out First will have an advantage that’s almost unfair. A contractor who can demonstrate 15–20% better crew utilization than their competitors can bid lower, deliver faster, and still make higher margins. An owner who demands whitespace metrics from their delivery partners will see genuine cost performance instead of the Fiction that lives in most monthly progress reports.

This isn’t theoretical. The data exists. The math works. The tools to measure and manage whitespace can be built with technology that already exists , time-and-motion capture, constraint-based scheduling, real-time resource allocation, crew-level utilization dashboards. The only thing missing is the decision to treat whitespace as what it is: the largest controllable cost on every project, hiding in plain sight.

The global construction industry doesn’t have a labor shortage problem. It has a labor utilization problem. We don’t need more workers. We need to stop wasting half the ones we already have.

 WHERE THIS GOES

The projects that will define the next decade data centres, energy transition infrastructure, semiconductor fabs, nuclear new-build cannot afford the whitespace tax that prior generations tolerated. The capital intensity is too high. The timelines are too compressed. The skilled labor pool is too thin to absorb the waste.

Someone is going to crack this. Some owner is going to mandate whitespace reporting as a contract requirement. Some contractor is going to build a utilization-first delivery model and start winning every bid they enter. Some consulting firm is going to walk into a boardroom, show the board what their whitespace is actually costing them, and change the conversation permanently.

The question isn’t whether whitespace management becomes a discipline. It’s whether you’re the one who brings it — or the one who keeps pretending the gap doesn’t exist while your competitors close it.

 

 

FIND YOUR WHITESPACE

Construction Resource Utilization Consulting delivers crew-level utilization audits that quantify your whitespace and build the roadmap to close it.LEARN MORE

© 2026 Construction Resource Utilization Consulting  | constructionresourceutilization.com

CONSTRUCTIONRESOURCEUTILIZATION.COM !” BLOG

Announcing “The Utilization Deficit” is coming soon

Every mega-project has the same dirty secret. Not corruption. Not schedule slip. Not even scope creep. It’s simpler than that and more expensive.

You’re paying for labour that isn’t producing anything. Not because people are lazy. Because the system was designed to waste them.

Resource estimation pads crews. Scheduling fragments productive hours. Governance layers add overhead nobody measures. And the gap between what you’re paying for and what you’re getting; that’s the Utilization Deficit . It starts at estimation, compounds through execution, and by the time someone notices the budget is bleeding, the cause is buried under three layers of reporting that were never built to surface it.

The utilization deficit doesn’t show up in your dashboards. That’s the problem. It shows up in your costs.

The Utilization Deficit is a Field guide for construction leaders who suspect their resource management model is broken and want the language and the math to prove it.

WHAT THE BOOK COVERS

This isn’t a textbook, and it isn’t a manifesto. It’s a practical breakdown of why large-scale construction organizations hemorrhage productive capacity, written by someone who has spent twenty years watching it happen from inside the machine.

• The Utilization Deficit ;Defined and Quantified
• White Space ; Where Supply Outruns Demand
• Carrying Cost ; The $85/hr Line Item You Can’t Find
• The Silo Tax ; What Fragmented Trade Management Costs
• Crew Productive Hours Ratio ; The Metric Nobody Tracks
• Non-Productive Time ; Naming It, Measuring It, Killing It
• Portfolio-Level Trade Management ; A Different Model

 08 The Audit ; How to Find the Deficit in Your Own Organization

Each chapter connects concepts to dollar impact. Every chapter is grounded in real project data; names changed, numbers not. The burdened labour rate isn’t hypothetical. The crew ratios aren’t theoretical. The waste is real, and so are the recovery opportunities.

WHO THIS IS FOR

Construction executives and project directors who control resource budgets on projects north of $100M. Operations leaders at EPC Firms and owner-operators who’ve been told “Utilization is Fine” by the same team that can’t explain a 40% non-productive time variance. Anyone who’s sat in a governance review and thought: we’re measuring the wrong things.

WHY NOW

Labour costs on mega-projects are accelerating. Skilled trade availability is shrinking. And the margin for waste that the industry has tolerated for decades is compressing in real time. The organizations that Figure out utilization First don’t just save money  they unlock capacity they didn’t know they had. The ones that don’t will keep wondering why projects that should work on paper never do.

You don’t have a labour shortage. You have a utilization problem dressed up as one.

The book drops soon. If you want to be the first to know, get in touch at constructionresourceutilization.com  or just keep reading this blog. The deficit isn’t going anywhere. But your ability to ignore it might be.

Get notified when The Utilization Deficit launches and receive a free excerpt from the Carrying Cost chapter.

GET EARLY ACCESS

© 2026 Construction Resource Utilization Consulting. All rights reserved.

The industry says it needs half a million new workers. The data says it’s wasting 40% of the ones it already has. One of these problems is solvable without a single new hire.

Kyle MussmacherApril 2026 9 min read

 

Every year, the same headline hits every trade publication: the construction industry needs hundreds of thousands of new workers or the sky will fall. In 2026, the number is approximately 500,000. Last year, it was 439,000. The year before, north of 500,000 again. The number moves. The narrative doesn’t.

And every year, the industry’s collective response is the same: recruit harder. Market better. Tell high schoolers that construction is a “career of choice.” Build more apprenticeship pipelines. Raise wages.

None of this is wrong. All of it is incomplete. Because the construction labor crisis isn’t primarily a supply problem. It’s a utilization problem. And until the industry is willing to say that out loud, it will keep hemorrhaging productivity while begging for bodies.

You don’t have a headcount shortage. You have a wrench-time problem dressed in workforce development clothing.

THE NUMBER NOBODY WANTS TO TALK ABOUT

Roughly 40% of a construction worker’s time on site is non-productive. Not marginally unproductive. Not “could be optimized.” Forty percent — spent waiting, idle, reworking, walking to the wrong location, or standing around because materials aren’t staged, tools aren’t available, or the preceding trade hasn’t cleared the work face.

That means on a project with 1,000 craft workers, 400 full-time equivalents worth of labor capacity is being vaporized every single day. Not by lazy workers. Not by bad attitudes. By bad systems. By fragmented work packaging. By project teams that treat resource synchronization as someone else’s job.

Let that sink in. A two-trillion-dollar industry is operating at roughly 60% labor effectiveness — and its primary strategic response is to hire more people into the same broken system.

WHY THE LABOR NARRATIVE SURVIVES

The labor shortage narrative persists because it’s convenient. It externalizes the problem. If we can’t find enough workers, then cost overruns and schedule slippage aren’t management failures — they’re market conditions. Nobody gets fired for a labor shortage. Plenty of people should get fired for a utilization rate that would be career-ending in any other industry.

Manufacturing solved this decades ago. Aerospace solved it. Automotive solved it. They built integrated planning systems, synchronized resource flows, and treated idle time as a defect — not an inevitability. Construction, despite being a $13 trillion global industry, still largely plans work in siloed spreadsheets, sequences trades by tribal knowledge, and accepts that a third to half of every labor dollar buys nothing.

Goldman Sachs Research (Feb 2026): US construction labor productivity has fallen at an average pace of 0.6% per year since 1965. Economy-wide productivity grew at 1.6% per year over the same period. Among all major G10 countries, the US has experienced the largest decline.

This isn’t a measurement artifact. Researchers at the University of Chicago confirmed the productivity decline is real and not the result of statistical error. The estimated hours per square foot to build a single-family home are nearly identical in 1993 and 2026. Thirty-three years. No improvement. Every other industry on earth would consider that an emergency. Construction considers it Tuesday.

THE REAL BOTTLENECK: WORK PACKAGING AND RESOURCE SYNCHRONIZATION

When a worker is standing idle on a construction site, the instinct is to blame the worker or blame the shortage. The correct response is to ask: why is the work face not ready?

In most cases, it’s one of four failures, none of which are solved by hiring:

Materials aren’t staged. Someone ordered them. Nobody coordinated delivery with the installation window. The steel is on site. It’s just in the lay down area 400 meters from where it’s needed, and the crane that was supposed to move it is rigged on a different lift.

The preceding trade hasn’t cleared.Electrical can’t pull wire because mechanical hasn’t hung duct. Mechanical can’t hang duct because structural hasn’t finished overhead steel. Nobody sequenced these work packages as an integrated system. They were planned in parallel by three different subcontractors who never looked at each other’s schedules.

Information is missing. The IFC drawings haven’t been issued for that area. Or they were issued, but with a hold on two penetrations that nobody flagged until the crew was already mobilized and standing in front of a concrete wall with no markings.

The work package itself is garbage. It’s too big, too vague, or sequenced against the physical logic of how the work actually gets built. It was written by a planner who hasn’t been on a scaffold in ten years, and it treats “install piping” as a monolithic activity rather than a synchronized chain of supports, spools, fit-up, welding, NDE, and hydro-test — each with different crew compositions, different material dependencies, and different quality hold points.

Every one of these is a resource utilization failure. Every one is solvable. And none of them require a single additional hire.

THE MEGA-PROJECT MULTIPLIER

If utilization waste is painful on a $50M commercial build, it’s catastrophic on a mega-project. Data centers. LNG facilities. Nuclear refurbishment. Semiconductor fabs. These are the projects driving the 2026 construction spending boom — and they are uniquely vulnerable to resource utilization failure because of their scale, complexity, and overlapping trade density.

On a mega-project, a 5% improvement in labor utilization doesn’t save a little money. It changes the project’s financial trajectory. It compresses schedule. It reduces carrying costs — the silent killer I’ve written about before — because every day you shave off a project with $2M/day in carrying costs is $2M you don’t burn.

And yet. Most mega-projects still resource-load their schedules with labor histograms built from averages, then act surprised when peak workforce requirements are 30% higher than planned. The workforce isn’t insufficient. The planning was.

You don’t need 30% more workers at peak. You need to stop building your resource plan from averages and start building it from constraint logic.

WHAT ACTUALLY MOVES THE NEEDLE

1. STRUCTURED WORK PACKAGES WITH CONSTRAINT CHECKS

Every work package should be constraint-checked before release: materials confirmed delivered and staged, preceding work confirmed complete, permits and quality docs in hand, tools and equipment available. If a single constraint isn’t met, the package doesn’t release. Full stop. This is not radical. This is basic manufacturing discipline applied to construction. The fact that it’s still uncommon tells you everything about the industry’s relationship with waste.

2. INTEGRATED RESOURCE PLANNING ACROSS TRADES

Stop letting every subcontractor plan in isolation and then “coordinate” at a weekly meeting where nobody changes anything. Resource planning must be integrated at the work face level — meaning trades are sequenced against each other spatially and temporally, with explicit handoff criteria and buffer management. This is systems thinking. Construction pretends it can’t do systems thinking because every project is “unique.” Every surgical patient is also unique. Surgeons still use checklists.

3. UTILIZATION AS A PRIMARY KPI

Most projects track schedule performance and cost performance. Almost none track labor utilization as a primary metric. If you’re not measuring wrench time, you’re not managing it. And if you’re not managing it, you are paying for it — every single day, on every single crew, on every single trade.

4. SHARED-SERVICE CONTRACTING ON MULTI-TRADE PROJECTS

On large projects with dense trade overlap, shared-service models — where common resources like scaffolding, rigging, and material handling are managed centrally rather than duplicated across subcontractors — eliminate one of the largest sources of idle time and resource conflict. This requires a different contracting philosophy and a different project governance model. It also saves millions.

THE EMPLOYMENT SIGNAL

Here’s the part nobody in workforce development wants to hear: the most valuable construction professionals in 2026 are not the ones who can recruit more bodies. They’re the ones who can extract more value from the bodies already on site.

Project managers who understand constraint-based planning. Resource coordinators who can synchronize ten trades across a multi-level work face. Construction planners who build schedules from installation logic rather than from calendar math. Consultants who can walk a site, diagnose a utilization problem in 30 minutes, and articulate the fix in language that both the field superintendent and the VP of capital projects can act on.

That’s where the industry’s real talent gap lives. Not in the trades. In the management layer that’s supposed to create the conditions for tradespeople to do productive work — and is failing at it, systemically, at scale.

The firms that figure this out will outperform. The ones that keep blaming the labor market will keep writing the same post-mortem on every project: “Workforce availability impacted the schedule.” No. Your utilization strategy impacted the schedule. The workforce was there. You just couldn’t keep them productive.

STOP HIRING INTO WASTE. START FIXING THE SYSTEM.

I help construction organizations diagnose utilization failures and build the planning systems, work packaging discipline, and contracting strategies that turn idle time into productive capacity — without adding headcount.

If your mega-project is bleeding labor dollars and your instinct is to mobilize more crews, we should talk first.

kyle@constructionresourceutilization.com →