Your Real Critical Path May Be an Approval Chain
A project can have steel in the air, equipment on order, crews mobilized, and respectable progress curves, while the real critical path sits in an inbox, a regulator’s queue, a client review cycle, or a management approval forum that meets once a month.
That is not a scheduling technicality. In oil and gas, EPC, infrastructure, utilities, mining, marine, and major construction, many projects aren't delayed by the activity everyone watches. They are delayed by the decision that allows that activity to start, continue, or be accepted.
The visible schedule may show excavation, fabrication, module delivery, cable pulling, pressure testing, energization, commissioning, and handover. The controlling chain may be somewhere else: a permit to work near live assets, a late approved-for-construction drawing, a class approval, a vendor document review, a technical query awaiting client response, a commercial authorization for a change, or a board decision on a scope option.
Experienced project teams know this pattern. The problem is that conventional CPM schedules often treat approvals as minor administrative tasks. They are given short durations, weak logic, generic names, or no logic at all. As a result, the schedule can report confidence while the project quietly loses control.
Approval Chains Form Across The Whole Project Life Cycle
Approval risk does not start during construction. It builds from the earliest development decisions and compounds through every phase.
During concept and feasibility, the project may depend on site-selection approval, land access, environmental screening, grid-connection studies, concept endorsement, funding gates, and early regulator engagement. These may sit outside the engineering schedule, yet they shape scope, design basis, location, execution strategy, and contracting route.
At this stage, a delayed decision can appear harmless because the team still has studies to perform. In practice, unanswered questions start to harden into assumptions. The project team may progress layouts, quantities, estimates, and schedules based on unresolved land, environmental, capacity, utility, or operating constraints. Later, when the decision finally lands, the team treats the rework as an engineering issue rather than the predictable result of an approval gap.
In FEED, the approval chain becomes more technical and more commercial. Design basis memoranda, plot plans, process safety documents, hazardous area classifications, equipment philosophies, tie-in strategies, contracting plans, cost estimates, and long-lead procurement recommendations all need review. Each approval influences downstream engineering and procurement.
A FEED package may look nearly complete, but if the client has not approved the design basis, if operations has not accepted the shutdown philosophy, or if the regulator has not closed out environmental conditions, detailed engineering starts on unstable ground. The schedule may show FEED deliverables finishing on time. The real question is whether they are accepted, usable, and connected to the next phase.
In detailed engineering, approval chains multiply quickly. Drawings, specifications, design reviews, model reviews, interdisciplinary checks, HAZOP actions, constructability comments, technical queries, concessions, deviations, and vendor documents all interact. A pump vendor drawing can hold the civil foundation design. A late electrical load list can hold substation procurement. An unresolved piping class deviation can hold material take-off, purchase orders, fabrication, and site installation.
Procurement brings another layer. Purchase requisitions, bid technical evaluations, bid clarifications, commercial approvals, award recommendations, expediting reports, inspection and test plans, manufacturing data books, shipping releases, customs documents, and site receiving inspections all carry approval dependencies. Long-lead equipment does not move because a bar on the Gantt chart says “manufacture.” It moves because drawings are approved, materials are released, deviations are resolved, quality plans are accepted, payments or letters of credit are in place, and logistics approvals are complete.
During construction, approvals become workfront controls. Permits, method statements, lift plans, temporary works designs, excavation permits, isolation certificates, access permits, inspection notifications, test packs, material releases, and field change approvals decide what crews can actually do. A contractor can have labor available and still lose productivity because the approved workface is fragmented or unavailable.
Commissioning, start-up, and handover are even more approval-heavy. Systems need mechanical completion acceptance, punch list classification, preservation records, pre-commissioning test acceptance, energization authorization, operating procedures, regulator notifications, performance test protocols, spares acceptance, training sign-offs, and final documentation. Many late-stage delays come from acceptance and readiness decisions, not from the physical act of turning a valve or starting a motor.
Formal guidance supports this broader view of project control. PMI, APM, ISO 21502, AACE International, and professional bodies such as ICE and RICS all treat governance, stakeholder engagement, risk, change, interfaces, and communication as integral to project delivery. CII research has long emphasized front-end planning, alignment, constructability, and information flow as drivers of project performance. In high-hazard sectors, IOGP, the Energy Institute, class societies, and regulators also strongly emphasize assurance, verification, competence, and controlled decision-making.
The practical implication is simple: approval work is project work when downstream execution depends on it.
Why CPM Schedules Often Understate Approval Risk
The Critical Path Method is not the problem. Poorly represented decision logic is the problem.
A well-built CPM schedule can model submissions, reviews, approvals, resubmissions, regulatory windows, information dependencies, and decision gates. Many schedules do not. They include physical work in detail and treat approvals as short-duration placeholders, level-of-effort tasks, constraints, or narrative assumptions.
That creates several blind spots.
First, schedules often show review cycles as single activities. A schedule may include “client review, 10 days,” followed by “issue AFC.” Real review cycles rarely behave that cleanly. Comments may arrive late. Comments may conflict. The contractor may need to respond. The engineer may need to revise. The client may need a second review. A regulator may require clarification. If the first submission quality is poor, one 10-day review can become a chain of resubmissions and waiting time.
Second, schedules often confuse document production with document acceptance. Producing a drawing is not the same as having an approved drawing that procurement or construction can use. This distinction matters in EPC and infrastructure work, where approved status codes control purchase, fabrication, installation, inspection, and payment.
Third, decision latency is rarely visible. A decision may need input from engineering, commercial, legal, operations, HSE, finance, the asset owner, a joint venture partner, or a government entity. Actual elapsed time can far exceed technical review time. The schedule may allow for engineering analysis but not for decision forum availability, delegation limits, escalation, or sponsor absence.
Fourth, regulator response times are sometimes treated as external risk rather than scheduled logic. In permitting, environmental approvals, marine consents, road closures, grid connections, pressure system approvals, aviation clearances, and hazardous operations, external review is not background noise. It is a dependency. The project cannot wish it away by placing the activity in a risk register while the baseline assumes an ideal response.
Fifth, escalation paths are rarely modeled. Teams say, “If it is late, we will escalate.” That may be true, but escalation itself takes time. Senior leaders need briefing notes, options, cost and schedule impacts, legal input, and decision authority. Where joint ventures, public sector clients, regulators, insurers, lenders, or multiple asset owners are involved, escalation can become a schedule activity in its own right.
AACE International’s recommended practices on scheduling and forensic schedule analysis emphasize logical relationships, realistic durations, constraints, progress status, and contemporaneous updates. That principle applies just as much to permit approvals or vendor drawing cycles as it does to civil works. If an activity consumes time, has predecessors, has successors, carries uncertainty, and can delay completion, it belongs in the schedule logic.
The Cost Of Ignoring Approval-driven Critical Paths
Approval delays rarely stay contained. They move through the project system and show up later as procurement delays, field inefficiency, claims, cost growth, and low schedule confidence.
Procurement often feels the impact first. Late vendor data can block design completion. Late approval of vendor drawings can block manufacturing release. Late commercial authorization can block purchase order award. A delayed inspection and test plan can block factory inspection. A delayed shipping release can strand equipment that is physically complete but contractually or logistically unable to move.
The result is not only late delivery. It may mean premium freight, resequenced fabrication, supplier claims, lost production slots, extended expediting, or accepting incomplete documentation to protect the schedule. Each workaround carries risk.
Construction feels approval delays as lost workfront. Crews need drawings, materials, permits, access, isolations, scaffolding, temporary works, approved methods, and inspection hold point releases. If one part is missing, productivity drops.
A brownfield contractor may mobilize for a tie-in campaign, only to find that operations have not approved the isolation procedures. A marine contractor may have vessels ready, but the weather window is lost because port clearance or seabed intervention approval is late. A miner may complete earthworks, but structural installation waits on revised foundation loads from late vendor information. A highway project may have plant and crews ready for night works, but traffic management approval lags behind the construction plan.
These examples are common because complex projects are dense networks of permissions. Physical work moves only when the permission system allows it.
Construction sequencing also suffers. When approvals arrive out of sequence, teams cherry-pick work. That can preserve visible progress but damage flow. Crews jump between areas. Temporary works remain in place longer. Access routes clash. Rework increases. Inspection lots become fragmented. Supervisors spend more time finding executable work than controlling quality and safety.
Commissioning exposes hidden approval debt. A project may report high construction progress, yet commissioning cannot proceed because test packs are incomplete, vendor representatives are not booked, cause-and-effect matrices are not accepted, energization permits are pending, operating procedures are not approved, or punch lists are disputed. At that point, the schedule has few recovery options. The project has turned an early approval delay into late critical-path pressure.
Claims and commercial disputes follow predictable lines. Contractors may allege late information, late access, late approvals, changes, disruption, acceleration, or prolongation. Owners may challenge entitlement if the schedule did not show approval activities as critical or if the contractor did not provide timely notice. Consultants and claims practitioners, including those working under common forms used in international construction, often focus on contemporaneous records, notices, logic, causation, and mitigation. Weak approval tracking makes that analysis harder.
Cost growth is the commercial shadow of approval delay. Teams pay for standing time, remobilization, extended preliminaries, extra supervision, resequencing, expediting, engineering rework, storage, demurrage, and loss of productivity. Some costs are obvious. Others hide in lower earned value performance, diluted management attention, and reduced confidence in forecasts.
Schedule confidence also erodes. If the schedule team cannot tell which approvals control which work packages, forecast dates become opinion rather than analysis. Progress meetings then chase symptoms. Everyone debates why construction is slipping, while the root cause sits in unresolved design decisions, unanswered technical queries, or unsigned commercial instructions.
How To Make Approval Dependencies Visible And Controllable
The goal is not to turn every email into a schedule activity. The goal is to identify approval dependencies that can control time, cost, access, procurement, safety, quality, or handover, then manage them with the same discipline applied to physical work.
A practical control system has several parts.
Build An Approval Register That Is Tied To The Schedule
An approval register should not be a static document list. It should identify each material approval, the owner, reviewer, required date, contractual turnaround, current status, number of review cycles, downstream activities affected, and escalation path.
For complex programs, the register should cover at least:
Approval type | Typical downstream impact |
Regulatory permits and consents | Site access, marine works, environmental controls, commissioning, start-up |
Client design reviews | AFC drawings, procurement release, construction workpacks |
Vendor drawings and data | Foundations, interfaces, fabrication, inspection, shipping |
Technical queries and concessions | Field execution, quality acceptance, design integrity |
Commercial authorizations | Purchase awards, change implementation, claims position |
Management decisions | Scope freeze, funding release, risk acceptance, handover readiness |
The register becomes powerful when each critical approval has explicit logic in the integrated schedule. For example, “approve transformer drawings” should link to “release transformer manufacturing,” “complete substation foundation design,” and “issue cable sizing for construction” where those dependencies are real.
Use Decision Logs For Choices That Affect Scope, Cost, Or Sequence
A document register tracks submissions. A decision log tracks choices.
Major projects often delay because the team has analysis but no decision. For example, whether to replace or refurbish a brownfield asset, whether to accept a deviation from specification, whether to resequence a shutdown, whether to split a package award, or whether to proceed with temporary facilities.
A useful decision log records:
The decision required
The options under consideration
The accountable decision-maker
The required decision date
The consequence of no decision
The downstream activities affected
The current blocker
The escalation route
This avoids the vague status of “under review.” It also helps senior leaders see which decisions are holding value, not just which documents are late.
Track Turnaround Times And Approval Aging
Approval performance needs metrics. Not decorative dashboards, but measures that show whether the review system can support the schedule.
Useful measures include:
Approvals due in the next lookahead period
Approvals overdue by age band
Average and range of review turnaround by reviewer group
First-pass acceptance rate
Number of resubmission cycles
Technical queries open beyond agreed response time
Vendor documents late against the supplier document register
Regulatory submissions awaiting response
Approvals on or near the schedule critical path
Approval aging is especially useful. An approval that is one day late may be noise. An approval 30 days late and blocking procurement release is a schedule threat. Aging also exposes stuck items that routine meetings normalize over time.
Set Decision Service Levels And Escalation Thresholds
Many organizations use service levels for document control but not for decisions. That leaves project teams dependent on goodwill and availability.
A decision SLA should define expected response times for classes of approvals, while allowing exceptions for complex technical or regulatory matters. For example, a low-risk technical query may need a short response cycle. A safety-critical design deviation may require formal review and cannot be rushed without proper assurance.
Escalation thresholds should be clear before the item is late. If a vendor document blocks manufacturing release and has not been reviewed by a set date, who is contacted? If a regulator requests clarification, who owns the response? If a sponsor decision is needed before a procurement award, when is the briefing pack due?
This is where governance and schedule control meet. ISO 21502 and project governance guidance from bodies such as APM emphasize clarity of roles, authority, decision-making, and stakeholder engagement. In practice, that means the schedule must reflect how the organization actually decides.
Track Regulatory Milestones As Real Schedule Drivers
Regulatory approvals require special treatment because the project does not control the reviewer. The project does control submission quality, timing, completeness, engagement, response discipline, and contingency planning.
Regulatory milestone tracking should show:
Pre-application engagement dates
Submission readiness reviews
Required supporting studies
Formal submission dates
Statutory or expected review periods where applicable
Clarification requests
Resubmission dates
Public consultation interfaces where relevant
Permit conditions that affect design, procurement, construction, or operations
This applies across many sectors: environmental permits for industrial plants, marine licenses for offshore works, rail possessions, road occupancy permits, building approvals, grid connection agreements, pressure equipment approvals, hazardous area compliance, and operating permits.
Treating these as external notes in a risk register is not enough. If a permit controls access or start-up, it needs a place in the network logic.
Connect Review Workflows To Construction And Commissioning Readiness
Digital workflows help only if they connect to execution. A document management system may show transmittals, comments, and statuses. The schedule may show activities. The gap between the two is where risk hides.
Integrated review workflows should connect document status to workpack release, procurement release, inspection release, system turnover, and commissioning authorization. If a construction workpack requires 20 approved inputs, the schedule should not treat the workpack as ready because 18 are complete. The missing two may be the ones that matter.
This is especially important in modular work, offshore campaigns, shutdowns, and brownfield tie-ins. The field window may be short. Missing one approval can waste the whole window.
Leading Indicators That Approvals Are Taking Over The Critical Path
Approval-driven delays usually signal themselves before they show up as missed milestones. The signs are visible if the project looks for them.
Watch for these leading indicators:
Growing approval backlogs across client, engineer, vendor, regulator, or internal management queues
Repeated resubmissions of the same drawings, calculations, procedures, or technical queries
Late vendor data affecting multiple engineering disciplines
Unresolved technical queries that stop field decisions
Long review cycles with no clear owner for closure
Sponsor or decision-maker unavailability during key gate periods
Rising use of assumptions in design, procurement, or construction planning
More “approved with comments” documents used as the basis for downstream work
Workpacks released with missing permits, drawings, materials, or inspection plans
Construction progress maintained through resequencing rather than planned flow
Increasing number of field change requests caused by late information
Commissioning systems mechanically complete but not accepted for testing
Commercial instructions delayed while the contractor proceeds at risk
A single indicator may not prove that approvals control the project. Several together should trigger a serious review.
The most dangerous pattern is false progress. Engineering reports high percent complete because deliverables are issued, while approval status lags. Procurement reports packages placed, while vendor drawings remain unapproved. Construction reports quantities installed, but missing test documentation blocks system completion. Commissioning reports preparation underway, while energization approval is not secured.
That is how a project can look advanced and still be far from finishable.
Experienced project directors often sense this before the dashboard shows it. They hear phrases like “awaiting client response,” “pending regulator feedback,” “subject to vendor confirmation,” “assuming approval next week,” or “we will escalate if needed.” Those phrases are not harmless. They are schedule logic trying to escape from narrative form.
The Questions Leaders Should Ask
Hidden approval chains become visible when leaders ask sharper questions. Generic status questions invite generic answers. Better questions connect approvals to consequences.
Project directors and sponsors should ask:
Which approvals are on the longest path to mechanical completion, start-up, or handover?
Which decisions must be made in the next 30, 60, and 90 days to protect the forecast?
Which approvals have no named accountable owner?
Which items are being progressed on assumption rather than approval?
Which overdue approvals affect access, procurement release, or commissioning readiness?
Which decision forums are too slow for the schedule they are meant to support?
Which regulator, client, partner, or operator interfaces need senior engagement now?
Engineering managers should ask:
Are we measuring issued deliverables or accepted deliverables?
Which vendor data delays are holding engineering completion?
Which technical queries are blocking construction workpacks?
Which design review comments are repeating across cycles?
Are “approved with comments” documents creating downstream ambiguity?
Which assumptions will cause rework if they are wrong?
Procurement leaders should ask:
Which purchase awards depend on commercial or technical approvals not yet secured?
Which suppliers cannot start manufacturing because drawings or data are not approved?
Which inspection and test plans are holding fabrication or release?
Which logistics permits, customs documents, or shipping releases are time-critical?
Which vendor document delays affect multiple packages?
Construction and commissioning leaders should ask:
Which planned workfronts lack approved drawings, permits, materials, access, or isolations?
Which permits are single points of failure for the lookahead plan?
Which system handovers depend on documentation acceptance rather than physical completion?
Which punch items need client or operator decision?
Which commissioning approvals need regulator, utility, vendor, or operations participation?
Senior decision-makers should ask one more uncomfortable question: What are we pretending is administrative that is actually critical?
That question changes the tone of governance. It moves the discussion from “Why is the contractor late?” to “What permission, decision, or acceptance is controlling the next step?” It also forces the project to distinguish between effort and readiness.
The schedule should show both.
A practical way to start is to run an approval chain review alongside the next schedule update. Take the current critical path and near-critical paths. Then ask whether each downstream activity has all required approvals. Where it does not, insert the missing approval activity, assign a realistic duration, connect the logic, and update the forecast. Repeat the exercise for procurement release, construction workpacks, commissioning systems, and handover packages.
The result may be uncomfortable. A path once shown through physical installation may shift to a regulator response, technical query, vendor drawing cycle, client design acceptance, commercial authorization, or sponsor decision. That discomfort is useful because it reflects the project more honestly.
For major capital projects, schedule confidence comes from modeling the work system as it really behaves. That system includes cranes, crews, fabrication yards, vessels, shutdown windows, and commissioning teams. It also includes reviewers, approvers, regulators, operators, governance boards, and decision-makers.
The professional takeaway is concise: effective schedule management must track not only the work that must be completed, but also the approvals that allow that work to happen. If the logic omits those approvals, the real critical path may be hidden in plain sight.
