Know Your Capacity

Why the best infrastructure plans prove resource reality before the field exposes it.

Every major infrastructure program has a moment of truth. It may not arrive in the boardroom. It may not appear in the baseline schedule review. It may not show up when the executive dashboard is still green. It often arrives later, in the field. 

A critical crew is double-booked across two priority packages. Inspectors are planned on days their calendar does not support. A crane is available in the histogram but not in the right window. A shutdown package assumes weekend capacity that does not actually exist. A design discipline looks balanced for the quarter, but the WBS-level view shows a three-week overload that will stop construction from starting on time. 

At that point, the project team does not have a reporting problem. It has a capacity truth problem. 

For years, infrastructure programs have relied on resource-loaded schedules, spreadsheets, monthly histograms, and project-by-project staffing conversations to answer one deceptively simple question: Can we actually deliver the plan? 

The question is becoming harder to answer. Across global infrastructure markets, the volume of capital work is growing while qualified labour, technical specialists, supervisors, inspectors, engineers, and craft resources remain constrained. Infrastructure Australia's 2025 Market Capacity Report identifies labour as the most critical delivery risk, with shortages projected to reach up to 300,000 workers by 2027.¹ In the United States, Associated General Contractors of America (AGC)/National Center for Construction and Education Research (NCCER) 2025 workforce survey found that worker shortages were the number one reason respondents cited for project delays, with 45% of firms reporting delays caused by shortages of their own or subcontractors' workers.²

The practical implication is direct: the next generation of infrastructure delivery will reward organizations that understand their capacity early, continuously, and at the right level of detail. 

Not just total headcount. 

Not just annual staffing plans. 

Not just "we have a resource-loaded schedule." 

Real capacity means knowing which resource, on which calendar, in which period, on which project, inside which WBS package, is creating risk - before the field discovers it the expensive way. 

The hidden weakness in many resource-loaded plans 

Most large infrastructure organizations already have some form of resource planning. That is not the issue. 

The issue is that resource data is often separated from the calendar logic that makes the resource real. 

A resource may appear available for 40 hours in a planning report. But is that resource assigned to a 5x8 calendar, a 6x10 field calendar, a night shift, a shutdown window, or a non-working period? Is the activity calendar aligned with the assigned resource calendar? Does the project plan load work onto days where the calendar says no capacity exists? Are multiple projects competing for the same scarce discipline in the same execution window? 

Without that view, the plan can look responsible and still be impossible. 

That is why the most important business need is not simply resource visibility. It is capacity assurance. 

Capacity assurance connects five questions that should be answered together:

What is the demand? How many hours are required by resource, role, project, WBS, activity, and period? 

What is the real capacity? What do the actual working calendars, shifts, exceptions, and non-working days allow? 

Where does the plan overload the organization? Which periods, resource families, projects, or WBS packages exceed available capacity? 

Is the overload a staffing issue, a sequencing issue, or a calendar issue? The corrective action is different depending on the root cause. 

Can executives trust the plan before committing to the baseline? A plan that cannot prove its capacity is not yet a plan. It is a schedule assumption. 

What public infrastructure examples teach us 

The London 2012 Olympic construction program is still one of the strongest public examples of disciplined major program delivery. The Olympic Delivery Authority (ODA) reported that the Olympic Park was delivered on time and substantially below the budget allocated in 2007, with the International Olympic Committee highlighting the program's early and consistent momentum.³ At peak construction, more than 12,000 people worked on the Olympic Park and Village, and more than 46,000 workers contributed overall.³ 

The lesson is not that every program can copy London 2012. The lesson is that large programs perform better when labour, supply chain, milestones, safety, training, and delivery accountability are treated as an integrated management system rather than disconnected workstreams. The ODA published annual milestones to ensure transparency and accountability, reporting that all were delivered on time and within budget.⁴ 

That London story did not end when construction was complete. The post-Games legacy is now carried forward by the London Legacy Development Corporation, which is responsible for the development of Queen Elizabeth Olympic Park and for ensuring that the London 2012 legacy continues to deliver long-term benefits for east London and beyond.⁵ The former Olympic Park has been transformed from a four-week event site into a 560-acre, free-to-enter urban district with six former Olympic and Paralympic venues in active public use, including London Stadium, London Aquatics Centre, Copper Box Arena, Lee Valley VeloPark, and Lee Valley Hockey and Tennis Centre.⁶ Its next chapter is broader still: East Bank is adding a £1.1 billion cultural and education quarter with UCL East, London College of Fashion, V&A East, Sadler's Wells East, and BBC Music Studios, while the wider Park is positioned as an innovation district connected to Here East, Plexal, new homes, parklands, and sporting venues.⁷ For the "know your capacity" story, this matters because London planned capacity at two horizons at once: first, the labour and construction capacity needed to deliver the Games; second, the long-term civic, commercial, cultural, and operating capacity needed to keep the assets useful after the closing ceremony. That is the executive standard infrastructure owners should apply to today's programs: the best resource plan does not only ask whether the baseline can be built; it asks whether the assets, people, calendars, and operating model can sustain value for decades. 

A more recent transport example is the A14 Cambridge to Huntingdon scheme in the UK. The £1.5 billion road project opened to traffic eight months ahead of schedule, and Highways England attributed that achievement to an integrated client team, common goals and targets, and a shared vision of success.⁸ The project employed more than 14,000 people in total, peaked at up to 2,500 workers on site, and required 14 million construction hours.⁸ Costain's project reflection adds another important detail: the team created a cloud-based single source of truth for project data and spent months refining report content and frequency with the client.⁹

That is the kind of story executives understand. Better visibility does not guarantee success by itself, but it creates the conditions for better decisions: earlier escalation, better sequencing, clearer ownership, and fewer surprises. 

North America offers the same lesson. In the United States, the Metropolitan Transportation Authority’s (MTA) Long Island Rail Road Main Line Third Track project was completed on schedule and $100 million below budget. The $2.5 billion expansion added a 9.8-mile third track between Floral Park and Hicksville, renewed five stations, eliminated eight at-grade railroad crossings, upgraded seven railroad bridges, and was delivered during the pandemic. MTA leadership credited design-build contracting and other innovative project management strategies for helping deliver the program faster, better, and cheaper.¹⁰ 

The public record does not publish the underlying resource-control room for that project. But the delivery lesson is still relevant: a live-rail expansion with stations, bridges, crossings, utilities, systems, community interfaces, and operating constraints can only stay controlled when the owner and delivery team understand work windows, trade sequencing, and scarce resources early enough to act. 

Canada provides a parallel example in Metro Vancouver's Canada Line. The automated rapid transit line connecting Vancouver, Richmond, and Vancouver International Airport officially opened three-and-a-half months ahead of schedule, on budget, and six months before the 2010 Winter Olympics.¹¹ A U.S. Federal Transit Administration case study also described the Canada Line as a driverless automated light rail system delivered on budget and ahead of schedule in time for the Games.¹² 

Again, the useful lesson is not that every owner should copy the procurement model or the project context. The lesson is that an immovable public deadline changes the value of capacity visibility. When the team can align construction, systems, stations, testing, commissioning, and opening readiness around constrained labour and calendar windows, resource understanding becomes a schedule-control asset rather than a monthly reporting exercise. 

The cautionary side is just as important. Hinkley Point C shows how major infrastructure forecasts can change materially when productivity and duration assumptions shift. Électricité de France (EDF) 2024 update outlined scenarios for Unit 1 becoming operational in 2029, 2030, or 2031, with completion costs revised to £31-34 billion in 2015 values. EDF stated that civil engineering costs and the longer duration of the electromechanical phase were the two main reasons for the cost revision. ¹³ 

The point is not to criticize one project. Hinkley Point C is an extremely complex first-of-a-kind national infrastructure program. The lesson for every infrastructure leader is broader: when long-duration work depends on constrained specialist labour, calendar windows, productivity assumptions, and sequencing logic, small blind spots can become very large changes in outcome. 

From resource-loaded to capacity-proven 

A resource-loaded schedule is valuable. But in large infrastructure programs, resource loading alone is not enough. 

A schedule can be loaded and still be misleading. 

It can contain demand without proving capacity. 

It can show hours without validating calendars. 

It can identify a peak without explaining the driver. 

It can show a resource family overload without revealing the project, WBS, or activity causing it. 

It can support a monthly report while failing to help the planner take action this week. 

This is where the next level of project controls becomes powerful. 

The goal is not to create another dashboard. The goal is to create a capacity control room: a place where executives and planners can see whether the plan is executable, where it is exposed, and what decision is needed next. 

For an executive, that means seeing total demand, available calendar-adjusted capacity, overload at risk, unstaffed work, calendar exceptions, and plan confidence in one view. 

For a planner, it means drilling from a portfolio histogram into the resource, then the project, then the WBS package, then the activity driving the overload. 

For a project controls leader, it means distinguishing between a real labour shortage and a schedule quality issue: missing calendar days, non-working-day load, resource over-capacity, or an activity calendar that does not match the assigned resource calendar. 

For the PMO, it means turning the same resource-loaded data into repeatable enterprise reporting inputs, instead of rebuilding spreadsheets every month. 

This is the value Audiit's Resource and Calendar Load delivers: expose demand, prove capacity, isolate overload drivers, validate calendars, and turn resource-loaded detail into reusable reporting feeds. The supporting views are designed around the same logic, including calendar capacity, enterprise histograms, project/WBS/activity drill-down, overload drivers, calendar exceptions, and hours-based corporate reporting feeds.¹⁴

The technical details matter, but the executive message is simpler: 

You cannot control what you cannot see. You cannot trust the capacity you have not proven. And you cannot protect the baseline if the resource picture only becomes clear after execution starts. 

The business value of knowing capacity early 

When infrastructure teams understand the full resource picture, they gain more than better reporting. 

They gain decision time. 

They can re-sequence work before the baseline is approved. 

They can move inspections to calendars that actually support the work. 

They can identify whether a peak is caused by a single project, WBS package, discipline, or shutdown window. 

They can see underload opportunities and pull work forward. 

They can separate staffing gaps from planning defects. 

They can turn resource discussions from opinion into evidence. 

Most importantly, they can move from reactive recovery to proactive control. 

In constrained infrastructure markets, that shift matters. Labour shortages, productivity pressure, and cross-sector competition for scarce skills are not temporary noise. They are now part of the delivery environment. McKinsey's research argues that stagnant productivity and constrained workforce growth could create a cumulative construction output shortfall of up to $40 trillion by 2040, with ripple effects for infrastructure, housing, net zero, and industrial growth.¹⁵

That means the winning organizations will not be the ones with the most reports. 

They will be the ones who can answer the hardest question with confidence: 

Can we prove the plan is executable before the field proves it is not? 

A better conversation for infrastructure leaders 

The next steering committee conversation should not stop at schedule variance, cost variance, and risk register items.

It should include capacity proof. 

Where are we overloaded? 

Which resources are driving the constraint? 

Which projects are competing for the same labour? 

Which WBS packages are exposed? 

Which calendar assumptions are invalid? 

Where do we have underload that can be used to smooth the plan? 

Which exceptions need planner action before they become field disruptions? 

That is the conversation Audiit helps infrastructure teams create. 

Not as a one-time analysis. 

Not as a spreadsheet rebuild. 

Not as a disconnected dashboard. 

As a repeatable way to turn resource-loaded schedules and working calendars into decisions, leaders can trust. 

Know your capacity before the field teaches it to you.

See Your Data in Action

Book a Resource Load + Calendar Load walkthrough and see how Audiit can expose capacity risk from project, WBS, activity, resource, calendar, and period.

Book Now