The Cost of Waiting: Why Idle Time Needs Its Own KPI
On a major project, waiting rarely looks dramatic. A crew stands by for a permit. An engineering squad pauses while a design note sits in review. A supplier holds fabrication because a technical query remains unanswered. A commissioning team is mobilized, but the system is not ready, the vendor is delayed, or the handover dossier is incomplete.
None of this may appear as a single red flag in the dashboard. The schedule still shows progress. Cost reports still book hours. Productivity measures may explain a poor week as weather, access, or “site constraints.” Yet capacity has been consumed without producing the asset.
That is the point. Waiting is not just an inconvenience. In capital-intensive, high-risk projects, it is a direct cost of delivery. It consumes scarce labor, plant, management attention, contract entitlement, float, and organizational trust. It also hides inside categories that project controls already track, but rarely isolate well enough to manage.
Professional bodies have been circling this issue for years, even if they use different language. The Project Management Institute and APM emphasize flow, governance, decision-making, and benefits delivery. AACE International focuses on cost, schedule, productivity, and delay analysis. The Construction Industry Institute has long studied front-end planning, constructability, materials management, and rework. Lean construction research treats waiting as one of the classic forms of waste. ISO project management guidance, infrastructure authorities, and industry groups such as IOGP and the Energy Institute all point toward the same conclusion: poor coordination and weak readiness create cost long before a formal delay event is declared.
The problem is that many projects still measure activity more carefully than they measure blocked capacity. That is why idle time needs its own KPI.
Waiting Develops Long Before The Site Goes Quiet
Waiting is often treated as a construction problem because that is where it becomes visible. In reality, it starts much earlier. It builds through unresolved assumptions, late decisions, weak interfaces, slow reviews, incomplete data, and optimism about readiness.
Concept And Feed Create The Conditions
At concept and front-end engineering design, waiting is often created by ambiguity rather than physical obstruction.
Examples are familiar:
A process design depends on an operating philosophy that has not been agreed.
Plot plan development stalls while stakeholders debate future expansion space.
Environmental or regulatory assumptions remain provisional.
A make-or-buy decision delays the procurement strategy.
Brownfield survey data is incomplete, so tie-in philosophy remains open.
Utility demand forecasts keep changing, delaying equipment sizing.
This is not always bad. Early uncertainty is normal, and some decisions should wait for better information. The issue is unmanaged latency. When teams cannot distinguish deliberate deferral from slow governance, the project carries hidden delay into later phases.
CII research has repeatedly emphasized the value of front-end planning because decisions made early shape downstream cost and performance. The same principle applies to waiting. If the project enters FEED with unresolved ownership, unclear decision rights, and weak data maturity, later teams will spend time recovering from early ambiguity.
Detailed Engineering Turns Waiting Into Queueing
In detailed engineering, waiting often appears as review backlog. Engineering teams wait for client comments, vendor data, discipline inputs, hazard study actions, model reviews, and technical query responses.
On EPC projects, this can become a loop:
Engineering issues a drawing for review.
The client, operations, or third-party reviewer returns late comments.
Procurement cannot issue a final package.
The vendor delays fabrication or submits queries.
Construction receives late or revised information.
Field change and rework follow.
Each step may look manageable in isolation. Together, they create queueing delay.
The schedule may show an activity called “client review” with a planned duration. It may not show how many deliverables are sitting in that queue, how old they are, whether reviewers have capacity, or whether comments return in a form the contractor can use. Workflow data often tells the truth before the baseline schedule does.
Procurement Waits For Decisions, Data, And Priorities
Procurement waiting is especially costly because it masks itself as market delay or supplier performance. Suppliers do cause delays, but buying teams also wait for internal prerequisites.
Common blockers include:
Unresolved technical bid evaluations
Late material requisitions
Incomplete vendor document requirements
Changes in specification after inquiry
Unapproved inspection and test plans
Delayed commercial clarifications
Late logistics decisions for oversized cargo
Regulatory certification requirements not confirmed early
In mining, energy, and industrial manufacturing projects, long-lead equipment can determine the critical path. A few weeks of waiting for technical clarification may translate into months of downstream impact if it misses a manufacturing slot, inspection window, port booking, or shutdown campaign.
AACE International’s work on cost engineering and schedule delay analysis treats entitlement and causation with care. That discipline matters. Yet for management purposes, every unanswered request for information, late approval, and unresolved technical query is also a signal of lost flow.
Construction Exposes The Hidden Backlog
Construction turns upstream waiting into visible idle time. Crews wait for access, permits, scaffolding, isolation certificates, materials, work packs, cranes, quality hold points, survey control, inspection release, or preceding trades.
In brownfield oil and gas modifications, a mechanical crew may be ready to install piping but cannot work because operations has not released the area. In utilities work, a contractor may mobilize for cable pulling but wait for outage approval. In infrastructure programs, earthworks may stop because temporary traffic management, land access, or utility diversions are not complete.
These are not small irritants. Field labor is perishable. A lost day cannot be stored and used later at no cost. Acceleration, resequencing, overtime, stacking of trades, and claims often follow.
Lean construction methods such as the Last Planner System focus strongly on constraints, reliable promises, and percent plan complete. That aligns closely with waiting measurement. If planned work is not made ready, the lost capacity should be visible, coded, and discussed.
Commissioning And Handover Are Especially Exposed
Commissioning teams often inherit every remaining problem. They wait for systems, vendors, spares, energization, permits, loop checks, punch list closure, operating procedures, trained operators, cybersecurity approvals, regulatory inspections, or final handover dossiers.
The waiting looks different from bulk construction. It is fragmented, technical, and interface-heavy. One missing vendor technician can hold a package. One incomplete software configuration can stop an integrated test. One late safety case approval can delay start-up.
Commissioning also has higher sensitivity to sequence. Teams cannot simply “work around” certain prerequisites without increasing safety and quality risk. A forced start-up, rushed handover, or incomplete readiness check can move waiting cost from the project account into operations, where it appears as poor reliability, deferred maintenance, or production loss.
Why Normal Project Controls Often Miss The Waiting Cost
Most project control systems can identify late activities, cost variance, and productivity trends. They are less effective at separating productive work from paid-but-blocked time.
That is not a failure of project controls as a discipline. It is a design issue. Many control systems were built to answer questions such as “Are we on schedule?” and “Are we within budget?” They are less direct when the question is “How much capacity did we lose because the work was not ready?”
Schedules Show Delay, Not Always Idleness
A critical path schedule can show that an activity started late, finished late, or lost float. It may not show whether the assigned resources were productively redeployed, partially used, or standing by.
Schedules also contain logic assumptions that may hide waiting:
Activities are too summary-level to reveal blocked work fronts.
Constraints are captured in notes, not coded data.
Review cycles are planned as fixed durations, even when queues grow.
Contractor interfaces are shown as milestones, not active dependencies.
Permit and access constraints sit outside the schedule system.
Commissioning prerequisites are split across multiple trackers.
Schedule risk analysis can model uncertainty, but the model is only as useful as its inputs. If waiting is buried in broad activity durations, contingency consumption, or “site delays,” the project has little chance to manage it precisely.
Productivity Reports Can Misclassify Lost Time
Productivity measures usually compare earned quantities with labor hours. That is valuable, but it can create confusion.
A crew that installs fewer meters of cable than planned may appear unproductive. In reality, the crew may have waited four hours for access, two hours for a permit update, and one hour for a missing cable drum. The production rate during actual work may have been acceptable.
Without separating waiting from working, management may reach the wrong conclusion. They may pressure the contractor for productivity when the real issue is client-driven access. Or they may approve acceleration while the underlying constraints remain untouched. That can make costs worse.
Crew-hour analysis helps. If timesheets, daily reports, and foreperson logs capture idle reasons consistently, the project can distinguish labor efficiency problems from readiness failures.
Cost Reports Book The Money, Not The Cause
Cost reports record labor, equipment, supervision, preliminaries, indirects, and claims exposure. They may show burn rate and earned value variance. The cause of waiting often sits elsewhere.
Idle time may be charged as normal labor, standby, disruption, delay, nonproductive time, or change. Some contract models encourage detailed coding. Others make waiting harder to see because contractors spread the cost into unit rates, prolongation claims, or commercial correspondence.
RICS and contract management guidance frequently stress the importance of records, notices, substantiation, and contemporaneous evidence. That is essential for entitlement. But a project director needs earlier visibility than a claim file provides. If waiting only becomes clear during dispute preparation, the management system has failed.
Conventional Reporting Smooths The Signal
Weekly and monthly reports tend to average waiting out. A bad Tuesday disappears inside a reasonable week. An access delay on one work front is offset by progress elsewhere. Several small review delays are reported as “engineering slightly behind.”
This smoothing is dangerous in major projects because waiting compounds. A delayed approval may become a late purchase order. A late purchase order may become a missing module. A missing module may change erection sequence. A changed sequence may increase work at height, temporary works, and interface congestion.
Systems thinking matters here. Waiting is rarely a single cause and effect chain. It is a network behavior. Small local delays create system-wide friction when buffers are thin, interfaces are dense, and decisions are slow.
Waiting Has Different Forms, And Only Some Of Them Are Waste
Good projects do not try to remove all waiting. Some standby is necessary in high-risk work. Some pauses protect safety, quality, assurance, and regulatory compliance. The mistake is treating all waiting as either acceptable overhead or avoidable waste.
The useful distinction is between four categories.
Category | What it means | Example | Management response |
Productive work | Time spent creating verified progress toward the asset or deliverable | Welding, testing, engineering calculations, vendor fabrication, approved inspection | Measure output, quality, and productivity |
Necessary standby | Time deliberately held to manage risk, assurance, or operational constraints | Emergency response cover, weather window readiness, SIMOPS controls, critical lift hold points | Plan, justify, and minimize exposure |
Avoidable waiting | Time lost because prerequisites were late, unclear, missing, or poorly coordinated | Crew waiting for permit, engineer waiting for approval, supplier waiting for data | Code, escalate, remove causes |
Systemic delay | Recurring waiting caused by governance, planning, incentives, or capability gaps | Persistent late reviews, repeated access failures, chronic vendor data delays | Treat as a project system problem, not a local issue |
This distinction prevents simplistic productivity commentary. A shutdown crew waiting for gas testing before confined space entry is not automatically waste. A marine spread waiting on a defined weather window may be part of the execution strategy. A commissioning team holding before energization may be observing a critical control.
The problem starts when waiting is neither designed nor governed. If standby is not planned, if its owner is unclear, or if the same delay code appears every week, the project has an avoidable cost problem.
The Consequences Go Well Beyond Lost Hours
Waiting has obvious commercial and schedule impacts. It also changes behavior.
Contractors respond to uncertainty by protecting themselves. They build float into plans, increase supervision, submit notices, hold resources offsite, price higher risk, or pursue claims. That may be rational behavior under the contract, but it reduces trust and increases transaction cost.
Supervisors respond by resequencing work. That may help in the short term, but repeated resequencing creates congestion, inefficient work fronts, and diluted accountability. Crews start jobs they cannot finish. Materials move twice. Temporary works remain longer than planned. Quality records lag the physical work.
Safety can suffer too. Waiting creates pressure to recover time. That pressure can lead to overtime, fatigue, stacked trades, short-cut planning, or starting work before prerequisites are fully mature. Human factors research, including work promoted by industry safety bodies, consistently warns that production pressure and degraded planning increase the chance of error. The issue is not that people become careless. It is that the system pushes them into harder conditions.
Quality also takes a hit. Late information and interrupted flow increase the chance of rework, missed inspections, incomplete documentation, and handover defects. By the time start-up arrives, the project may have converted waiting into punch list burden.
Organizationally, chronic waiting drains credibility. Teams stop believing lookahead plans. Daily coordination meetings become explanation sessions. Senior leaders ask for recovery plans while the same constraints remain unresolved. The project becomes busy, but not necessarily effective.
How To Measure Waiting Without Creating Another Reporting Burden
A waiting KPI must be precise enough to guide action, but simple enough to survive field conditions. The goal is not to punish teams for every pause. The goal is to reveal lost capacity and remove repeat causes.
Start With A Clean Definition
A practical definition could be:
Waiting time is planned or unplanned capacity that is available to perform approved work but cannot proceed because one or more prerequisites are absent, delayed, unclear, or controlled by another party.
This definition matters because it avoids arguing about general inefficiency. It focuses on readiness. Was the labor, equipment, engineering resource, vendor, or commissioning team available? Was the work approved and planned? What prerequisite stopped it?
The KPI should separate:
Waiting hours for labor and supervision
Waiting hours for key equipment, vessels, cranes, or spreads
Awaiting approval time for deliverables and decisions
Awaiting information time for technical queries and RFIs
Awaiting access, permit, isolation, inspection, or handover
Awaiting materials, vendor attendance, spares, or documentation
A single blended metric can be useful at executive level, but the project team needs cause-level data.
Use Delay Codes That Match Real Work
Many projects already have delay codes. Few have codes that are consistently used, trusted, and analyzed.
Useful waiting codes are specific enough to act on. For example:
Awaiting client approval
Awaiting engineering clarification
Awaiting vendor data
Awaiting material delivery
Awaiting workface access
Awaiting permit or isolation
Awaiting inspection release
Awaiting preceding trade
Awaiting system handover
Awaiting regulator or third-party action
Awaiting weather window, where weather is a defined constraint
Awaiting management decision
The code set should avoid catch-all buckets such as “other,” “site issue,” or “coordination.” Those terms may be convenient, but they destroy the management value of the data.
Ownership should also be coded with care. Internal, contractor, client, operations, vendor, regulator, utility provider, and third-party interface are different management problems. They may need different escalation routes.
Connect Field Records With Workflow Data
Waiting measurement becomes powerful when it links field data to workflow data.
Sources can include:
Daily reports and foreperson logs
Timesheets with nonproductive time categories
Equipment standby records
Permit-to-work and isolation system timestamps
RFI and technical query aging
Document review cycle times
Vendor data registers
Material availability and warehouse issue data
Constraint logs from lookahead planning
Interface registers and action trackers
Schedule activities, milestones, and float trends
Commissioning completions, system handover, and punch list status
No single source is perfect. Daily logs may be subjective. Permit data may show timestamps but not root cause. Schedule data may be too high-level. Workflow systems may omit informal decisions. Together, they create a more reliable picture.
This is where project controls should work with construction, engineering, procurement, commissioning, contracts, and HSE, not sit apart from them. Waiting is a cross-functional signal.
Track Both Lagging And Leading Indicators
A lagging KPI tells how much waiting happened. A leading indicator warns that waiting is about to become embedded.
Useful lagging measures include:
Waiting hours as a percentage of total available hours
Waiting cost by cause and owner
Lost critical equipment or vessel days
Number of planned tasks not started due to missing prerequisites
Average age of blocked work fronts
Repeat waiting events by contractor, system, area, or discipline
Useful leading indicators include:
Rising RFI or technical query aging
Increasing late approvals or review cycle overruns
Growth in constraints inside the lookahead window
Falling plan reliability in weekly work planning
More work packs issued with open prerequisites
Permit queues growing before peak execution periods
Increase in “ready but not released” work
More vendor document comments returned late
More schedule activities starting without full material availability
More commissioning tests deferred due to incomplete systems
These weak signals deserve attention before the earned value curve turns down. By the time CPI, SPI, or milestone variance shows a major problem, the waiting pattern may already be expensive to unwind.
Treat Waiting Data As Evidence, Not Ammunition
A waiting KPI will fail if teams see it as a blame tool. Contractors will underreport. Supervisors will hide downtime. Client teams will challenge coding rather than remove constraints.
The better approach is commercial honesty. Waiting data can support contract administration where needed, but its first purpose is control. It should help the project answer three questions:
What capacity did we lose?
What stopped the work?
What decision or condition would prevent recurrence?
That framing matters in alliancing, EPC, reimbursable, lump-sum, target cost, and framework contracts. Incentives differ, but unmanaged waiting costs someone. Often it costs everyone.
What Recurring Waiting Patterns Reveal About The Project System
A single waiting event may be bad luck. A repeated pattern is diagnostic.
If engineering deliverables wait too long for approval, the issue may be unclear authority, overloaded reviewers, late operations involvement, or too many approval gates. If procurement repeatedly waits for technical clarification, the issue may be immature design release, weak vendor engagement, or poor specification control. If site crews wait for permits every morning, the issue may be permit capacity, shift planning, SIMOPS congestion, or unrealistic work packaging.
Patterns often point to one of several deeper problems.
Governance Is Too Slow For Execution Speed
High-risk projects need controls. They also need timely decisions. Decision latency becomes a project cost when governance forums meet too infrequently, decision rights are unclear, or senior leaders revisit settled matters without acknowledging the cost.
A practical test is simple: does the project know the average cycle time for key approvals and decisions? If not, it is managing governance by anecdote.
Planning Is Activity-based Rather Than Constraint-based
A schedule can say work should happen next week. That does not mean it can happen next week.
Constraint management asks whether the work is truly ready. Are drawings approved? Is material available? Is access granted? Are permits understood? Is preceding work complete? Are inspection resources booked? Are vendors confirmed?
Lean construction has pushed this thinking for years. The weekly plan should not be a wish list. It should be a commitment based on removed constraints.
Interfaces Are Under-managed
Major projects fail at the seams. Contractor to contractor. EPC to owner. Construction to operations. Marine to port. Utility provider to infrastructure contractor. Commissioning to vendor. Regulator to project team.
Interface registers help, but only if they track living dependencies, dates, owners, and consequences. If interface management is reduced to periodic meetings and static registers, waiting will grow in the gaps.
Supply Chain Readiness Is Confused With Purchase Order Placement
Issuing a purchase order is not the same as securing readiness. Projects still wait because designs change, submittals lag, inspection release is late, expediting is weak, shipping documents are incomplete, spare parts are missed, or site storage cannot receive the goods.
The World Bank, OECD, and national infrastructure bodies often discuss procurement capacity, supply chain risk, and public investment delivery in broader terms. The project-level lesson is direct: procurement is a flow system, not a transaction log.
Contractors Adapt To The System They Are Given
Contractors are not passive. They respond to payment terms, risk allocation, access reliability, change behavior, supervision quality, and claim culture.
If a contractor expects frequent waiting, it may mobilize less aggressively or protect its best resources for more reliable work elsewhere. If the contract pays standby, the contractor may have less incentive to challenge readiness problems. If standby is not recognized, the contractor may pursue disruption claims later.
Commercial management needs to understand these behaviors. The question is not whether contractors should be “more productive.” The question is whether the contract and project system reward readiness, transparency, and reliable delivery.
The Questions Senior Leaders Should Ask
Senior leaders do not need every waiting code. They need the right questions, asked consistently.
Start with these:
Which work fronts are ready, partially ready, and blocked?
How many labor hours, equipment hours, or vessel days did we lose to waiting last week?
Which three causes account for most waiting?
Which causes are repeating across contractors, areas, or systems?
What approvals or decisions are past their agreed cycle time?
Which constraints are inside the next 21 to 42 days of work?
Are we starting activities without full prerequisites to protect the schedule narrative?
What waiting is caused by our own governance, operations, or assurance processes?
Where are contractors pricing, claiming, or behaviorally responding to waiting risk?
What start-up or handover risks are we creating by pushing incomplete work downstream?
The tone matters. These questions should not sound like a hunt for culprits. They should surface system constraints early enough to act.
How To Reduce Avoidable Waiting Without Weakening Controls
Reducing waiting does not mean bypassing permits, rushing reviews, accepting incomplete engineering, or cutting assurance. In high-risk industries, that would be false economy. The objective is to make necessary controls predictable, capable, and integrated with the work plan.
Several actions make a practical difference.
Make Readiness Visible Before Mobilization
Do not mobilize scarce crews, vessels, cranes, or vendor specialists based only on schedule dates. Use readiness checks for work packs, systems, shutdown windows, access, materials, permits, inspections, and handover documentation.
For shutdowns and turnarounds, this discipline is critical. The execution window is short, and idle time during a major outage can be extremely expensive. Work should enter the frozen execution plan only when prerequisites are genuinely mature or when the risk is explicit and owned.
Put Approval-cycle Times Under Management Control
Engineering reviews, technical queries, vendor documents, management decisions, and regulatory submissions all need cycle-time targets. More than that, they need capacity planning.
If reviewers are overloaded, adding pressure will not solve the queue. Assign review capacity, clarify authority, reduce unnecessary approvers, separate critical from noncritical reviews, and track aging publicly. Governance should protect decisions from drift.
Build Constraint Logs That People Trust
A constraint log should not be a dumping ground. It should show the blocked item, owner, required date, consequence, escalation route, and closure evidence.
The best logs connect directly to lookahead planning. If a constraint threatens planned work, it receives attention before it creates waiting. If it repeats, it becomes a management issue, not an administrative item.
Align Permit Capacity With The Work Plan
Permit-to-work systems are essential barriers in operating facilities, brownfield work, utilities, and offshore environments. Waiting often occurs because permit demand exceeds processing capacity or because work packs lack the information needed for approval.
This is not solved by pushing permit authorities to work faster. It is solved by matching permit planning to execution planning, improving work pack quality, staggering starts, clarifying isolations, and giving operations enough notice to support safe release.
Protect Commissioning From Inherited Waiting
Commissioning should have its own readiness logic, not just inherit construction progress. System completion, punch clearance, vendor availability, spares, procedures, training, permits, energization, and handover dossiers must be tracked as prerequisites.
Operational readiness deserves the same discipline. A project can be mechanically complete and still not ready to start if operating procedures, maintenance plans, training, emergency response arrangements, or regulatory approvals lag behind.
Use Commercial Mechanisms Carefully
Contracts can help or hurt. Waiting measurement should align with notice provisions, standby rules, change management, and pain-gain or incentive structures. If the contract makes transparent reporting risky, the project will get distorted data.
Commercial teams should work with project controls to define acceptable evidence, coding rules, and reporting cadence. That reduces disputes and gives both parties a clearer basis for management action.
Close The Loop On Repeated Causes
The most valuable waiting report is not the one with the largest number. It is the one that changes next week’s plan.
If the same cause reappears, assign a corrective action at the system level. For example:
Late client reviews may require approval triage and reviewer capacity.
Repeated material shortages may require expediting changes and site kitting.
Access delays may require a new operations interface routine.
Permit queues may require earlier permit walkdowns.
Vendor attendance delays may require a revised call-off model.
Handover delays may require earlier dossier assurance.
Avoidable waiting falls when teams stop treating symptoms as isolated events.
The Professional Takeaway
Waiting is one of the most expensive costs that major projects still under-measure. It hides inside labor hours, standby, review cycles, material delays, permit queues, contract notices, productivity variance, and commissioning slippage. It grows across the project life cycle, from unclear FEED decisions to late handover prerequisites.
Project leaders do not need another vanity metric. They need a practical measure of lost capacity, coded by cause, owner, and consequence. That measure should sit beside schedule, cost, safety, quality, and productivity because it explains why those indicators move.
The cost of waiting is real. Treating avoidable waiting as a measurable performance issue makes it visible early enough to manage, and it reframes idle time for what it is: a direct cost of project delivery.
