Project Approval Vs Readiness: Why Sanction Doesn't Mean Start
Updated: Oct 11
A project can be fully approved and still not be ready to execute.
That is not a contradiction. It is one of the most common failure points in complex capital projects. A board approves funding. A joint venture sanctions the development. A government authority announces a major infrastructure scheme. A sponsor releases the execution budget. The project team hears one word: start.
Yet underneath that formal approval, the work may still depend on immature engineering, unplaced contracts, pending permits, unresolved interfaces, weak logistics plans, unclear site access, incomplete operating procedures, and resourcing assumptions that no one has tested against the real construction sequence.
Approval gives permission. Readiness proves capability.
In oil and gas, EPC, mining, utilities, marine, infrastructure, and major construction, that difference is not academic. It is the difference between controlled execution and expensive improvisation. Many troubled projects do not fail because no one approved them. They fail because approval was mistaken for preparedness.
Approval Answers A Different Question Than Readiness
Project approval usually answers a governance question.
Should the organization commit capital, authorize the next phase, sign the major contract, release long-lead procurement, or proceed to execution?
That decision may rely on a business case, cost estimate, schedule, risk assessment, investment paper, contracting plan, and executive recommendation. In a well-governed organization, it should also reflect assurance findings and stage-gate evidence. PMI, APM, ISO 21502, AACE International, and professional bodies such as ICE and RICS all stress in different ways that projects need structured governance, defined decision points, and reliable information to support investment decisions.
Execution readiness asks a different question.
Can the project now perform the approved scope safely, productively, and predictably with the information, resources, access, contracts, permits, materials, and controls currently in place?
Those two questions overlap, but they are not the same.
A project may be commercially justified but physically constrained. It may be strategically urgent but technically immature. It may be funded but unable to access the workfront. It may have an approved baseline that depends on procurement dates the supply chain has not accepted. It may begin construction while design teams still resolve the details construction crews need next month.
A sanction paper often contains assumptions. A readiness assessment tests whether those assumptions have become executable facts.
For example, an EPC project may receive full notice to proceed based on a Class 3 estimate, a level 3 schedule, and a contracting strategy that assumes civil works can begin while detailed engineering continues. That may be reasonable if early works are well defined, permits are in hand, underground risks are understood, temporary facilities are available, and interface control is disciplined.
The same decision becomes dangerous if early works depend on unconfirmed geotechnical data, late drawings, unclear utility diversions, incomplete battery-limit definitions, and a contractor mobilization plan built around best-case access.
The difference between those two scenarios is execution readiness.
The phrase Project Approval vs Readiness matters because too many governance conversations collapse both ideas into one milestone. “Approved” becomes shorthand for “ready.” It should not.
What Readiness Really Includes
Readiness is not a single certificate. It is a set of mature conditions across the project system. In complex capital work, one missing condition can block several others.
A useful readiness view covers at least the following areas.
Engineering Maturity
Engineering readiness is more than having drawings in progress. It means the design information needed for the next execution window is complete, checked, approved, and constructible.
That includes:
Defined scope boundaries and battery limits
Approved design basis and technical specifications
Mature plot plans, layouts, tie-in lists, and equipment data
Completed interdisciplinary checks
Resolved HAZOP, constructability, and operability actions for relevant packages
Clear field change and technical query processes
Drawings released in the sequence the field actually needs
The risk is not only “incomplete design.” It is design that is complete enough to support approval but not complete enough to support production.
A brownfield refinery project may have enough engineering to justify investment, but not enough verified site data to confirm tie-in locations, isolation philosophy, asbestos presence, buried services, or shutdown work packs. That gap does not stay in engineering. It appears later as field holds, hot work delays, workface congestion, variation claims, and safety exposure.
Procurement And Supply Chain Status
Procurement readiness tests whether materials, equipment, and services will be available when the execution plan requires them.
Long-lead items are obvious, but many projects lose time on less visible constraints: valves, cable trays, specialist coatings, temporary power equipment, spare parts, vendor documentation, lifting frames, commissioning consumables, and test equipment.
A project is not ready simply because purchase requisitions have been raised. The readiness question is sharper:
Can procurement status support the schedule, and are the remaining risks understood?
This includes approved vendor lists, technical bid evaluations, purchase orders, expediting plans, logistics routes, customs requirements, inspection and test plans, preservation requirements, and vendor data delivery. In the Gulf and other import-heavy project markets, customs clearance, port congestion, heat-sensitive storage, and last-mile transport can be as important as the manufacturing date.
Contracting Strategy And Commercial Readiness
A contracting strategy may look sound on paper, yet still be too immature to execute.
The chosen model needs to match design maturity, risk allocation, market capacity, owner capability, and the need for speed. Lump sum EPC, reimbursable construction management, EPCM, alliance-style arrangements, framework call-offs, and specialist packages each need different levels of definition and owner involvement.
Commercial readiness includes:
Contracts awarded or clearly on track for award
Scope splits that contractors can price and execute
Interface responsibilities that are explicit
Payment, change, and claim mechanisms that fit the risk profile
Insurance, bonds, guarantees, and regulatory registrations in place
Mobilization obligations that match site reality
Many claims start before the contractor sets foot on site. They start when the owner tenders an incomplete package, pushes risk downstream, and then expects the contractor to recover time lost to missing information or late access.
Permits, Access, And Approvals
Permit readiness is often treated as an administrative workstream. On many projects, it is on the critical path.
Construction permits, environmental approvals, marine permits, road closure approvals, blasting permissions, notices to regulators, utility outage approvals, right-of-way access, land handover, port passes, security clearances, hot work permissions, and SIMOPS approvals all affect execution.
A linear infrastructure project may be approved at the program level but remain blocked section by section by land acquisition, municipal approvals, utility diversions, environmental constraints, or third-party access agreements. The schedule may show continuous production. The site may only offer disconnected workfronts.
Temporary access arrangements can also be misleading. A project may have enough access to mobilize cabins and plant, but not enough to move heavy modules, maintain emergency routes, operate cranes safely, or support peak labor.
Logistics, Constructability, And Workface Planning
Execution readiness lives at the workface.
Can crews perform planned work safely and productively when they arrive? Are drawings, materials, permits, tools, equipment, scaffolds, isolations, method statements, quality hold points, and supervision ready together?
The Construction Industry Institute has long emphasized the value of front-end planning, constructability, materials management, and work packaging. The exact tools vary between organizations, but the principle is stable: field productivity depends on constraint-free work.
Weak logistics plans damage productivity quickly. A mining project may approve a remote processing plant, but if accommodation, water, fuel, road maintenance, medical response, laydown, and seasonal access are underdeveloped, execution turns into a daily survival exercise. The schedule logic may remain elegant. The site will not.
How Approved Projects Enter Execution Unprepared
Most organizations do not intentionally launch unready projects. They drift into it through pressure, optimism, fragmented governance, and a belief that the team can “sort it out during execution.”
That phrase should make senior leaders uncomfortable.
Execution is the most expensive place to resolve basic uncertainty. Once contractors mobilize, vessels sail, shutdown windows open, or tunneling crews start, every missing decision has a burn rate.
Political And Stakeholder Pressure
Public infrastructure and utility projects often face announcement pressure. A scheme becomes politically visible before the delivery model is mature. Dates enter speeches, media releases, funding agreements, and stakeholder commitments. Once a public date exists, technical teams may struggle to reset expectations, even when permits, land, design, or procurement are not ready.
The same dynamic appears in energy transition projects, water infrastructure, mining expansions, and port developments. Strategic urgency can be real. Demand growth, regulatory commitments, decarbonization targets, and national development plans all matter. Yet urgency does not manufacture readiness.
Commercial And Funding Pressure
Capital approvals often come with funding windows. Teams may fear losing budget if they do not commit. Joint ventures may need to meet investment milestones. Developers may need to secure offtake commitments or lender confidence. Contractors may face bid validity deadlines or escalation exposure.
These pressures can push teams to place contracts, release early works, or start mobilization before the work is mature.
Sometimes that is a valid business decision. Early commitment may protect schedule or secure scarce capacity. The problem starts when the organization treats a conscious risk decision as if no risk remains.
A better approach is to say clearly: “We are authorizing limited execution under defined constraints, with named assumptions, hold points, and recovery options.” That is very different from pretending the full project is ready.
Schedule Pressure And Recovery Bias
The most persistent readiness trap is the belief that later phases will recover early immaturity.
The schedule shows engineering catching up. Procurement float absorbs vendor delays. Construction resequences around missing workfronts. Commissioning compresses. Operations accepts a shorter familiarization period. Everyone knows the plan is tight, but the baseline still assumes future recovery.
Experienced project directors know how that story usually ends. Field teams burn hours waiting on information. Supervisors split crews across inefficient workfronts. Temporary works multiply. Quality records lag. Commissioning inherits incomplete systems. Operations receives assets with punch lists, missing spares, and late training.
Recovery is possible, but it is not a strategy unless it is backed by resources, logic, and proven constraints removal.
Fragmented Accountability
Unready execution also happens when responsibility falls into gaps between functions.
Engineering says construction started too early. Construction says engineering missed the required dates. Procurement says technical bid evaluations were late. The permits team says operations delayed the submission. Operations says project delivery did not involve them early enough. Contractors say access was not available. The owner says the contract required progress.
All may be partly true.
Readiness needs integration. Interfaces must be owned, not observed. This is especially important in brownfield, offshore, shutdown, and marine work where simultaneous operations, production constraints, weather windows, permits to work, vessel availability, and isolation plans interact tightly.
The Cost Of Starting Before The Project Is Ready
Poor readiness does not cause one type of harm. It spreads across the project.
Cost Growth
Immature starts create cost through standby, rework, acceleration, disruption, claims, expediting, premium freight, temporary facilities, redesign, inefficient labor, and management overload.
For this reason, AACE International’s cost engineering guidance and recommended practices place strong emphasis on estimate maturity, basis of estimate, risk analysis, and change control. If scope definition is weak, the approved budget may simply be a priced assumption.
Once execution begins, the cost of correcting assumptions rises. A late design change to foundation loads may trigger rebar rework, formwork changes, concrete demolition, crane resequencing, and schedule delay. A missed vendor interface may affect piping, electrical, controls, and commissioning. Small assumptions rarely stay small.
Schedule Slippage
Schedule delay from weak readiness is often misdiagnosed.
The report may say “contractor underperformance” or “late productivity ramp-up.” The deeper cause may be that the contractor never received a stable, constraint-free workfront. Labor productivity cannot compensate for unavailable drawings, missing materials, or incomplete permits.
This is common in shutdowns and turnarounds. The calendar window is fixed. If work packs, isolations, spares, scaffolding, lifting plans, inspection scopes, and contractor readiness are incomplete, the team spends the outage solving problems that should have been solved before the plant came down.
Productivity Loss
Productivity loss is one of the least visible consequences because it hides inside timesheets.
Crews wait. Supervisors chase clarifications. Equipment moves twice. Materials sit in the wrong laydown area. Welders lack revised isometrics. Electricians pull cable before trays are released. Civil crews pour around embedded items that later change. Marine crews wait on weather windows because permits or cargo are late.
Each event may look manageable. Together they erode the plan.
Safety And Quality Exposure
Readiness is also a safety issue.
When work starts with incomplete information, teams rely more on improvisation in the field. Temporary access replaces permanent access. Congested areas increase lifting and dropped-object risk. Late method statements reduce time for review. SIMOPS controls become reactive. Fatigue rises when teams chase recovery.
Regulators and industry bodies, including the Energy Institute and IOGP in high-hazard sectors, consistently promote systematic risk management, management of change, competence, and barrier thinking. Starting work before hazards, controls, responsibilities, and interfaces are mature weakens those principles.
Quality suffers in similar ways. Inspection and test plans may lag behind fabrication. Hold points may be missed under schedule pressure. Preservation requirements may be unclear. Turnover dossiers may be incomplete. Commissioning then receives assets that are mechanically complete on paper but not ready for safe and efficient start-up.
Claims And Relationship Damage
Unready projects create fertile ground for disputes.
Contractors claim delays, disruption, acceleration, scope growth, late information, restricted access, and sequence changes. Owners respond with notices of poor performance, failure to mitigate, or lack of resources. The commercial relationship becomes defensive.
This is not only a legal problem. It distracts leadership, slows decisions, and damages trust across the supply chain. When every instruction is viewed through a claims lens, project execution slows and costs more.
Weak Operational Readiness
The final damage often appears near handover.
Operations may receive an asset that is physically built but not ready to operate. Training is late. Maintenance strategies are incomplete. Spares are missing. Vendor manuals are not approved. Control room procedures are draft. Regulatory dossiers lag. Performance testing is compressed. The start-up team inherits open construction issues.
Operational readiness should begin early, not after mechanical completion. ISO asset management guidance, commissioning good practice, and industry experience all point to the same lesson: the operating organization must be prepared alongside the physical asset.
Leading Indicators That Sanction Has Outrun Readiness
Senior leaders do not need to wait for failure. Unreadiness leaves signals.
Some of the clearest indicators include:
Design is still moving in areas needed for early construction
If key drawings remain under internal review, interdisciplinary checks are incomplete, or technical queries are rising before major work starts, construction readiness is weak.
The schedule depends on best-case procurement
If delivery dates rely on vendor optimism, unapproved drawings, no customs allowance, or premium freight not yet approved, procurement risk is probably underplayed.
Permits and access are described as “expected” rather than secured
Expected approvals are not execution conditions. They are assumptions until granted.
Contracts are not aligned with the work sequence
If major contractors are not appointed, scope splits are disputed, or interface obligations are vague, mobilization may create motion without progress.
Temporary arrangements are carrying permanent workload
Temporary roads, laydown, access platforms, power, water, or accommodation may be acceptable for early works. They become a risk when the project relies on them for peak execution.
The risk register is full, but the constraint register is thin
A risk may or may not occur. A constraint is already blocking readiness. Mature projects manage both.
Commissioning and operations are treated as later concerns
If systemization, turnover planning, spares, procedures, training, and performance test requirements aren't visible during execution planning, the project's back end is exposed.
The plan relies on future recovery
If the answer to every current gap is “we will catch up later,” the project may be approved, but it is not under control.
Responsibilities are unclear at interfaces
Battery limits, tie-ins, utilities, data handovers, marine spreads, third-party assets, regulator submissions, and vendor support all need named owners.
Readiness reporting is based on activity rather than evidence
“In progress” is not readiness. Evidence includes approved documents, issued contracts, granted permits, delivered materials, trained resources, signed access agreements, and completed work packs.
These indicators do not always mean execution must stop. They do mean leaders should limit, condition, or resequence authorization until they understand the exposure.
Practical Controls That Separate Approval From Readiness
Good governance does not slow projects for the sake of process. It makes speed safer by forcing clarity before irreversible commitments.
Use Stage Gates For Maturity, Not Ceremony
Stage gates should be decision points, not calendar events. A gate should test whether the project has reached the maturity required for the next risk exposure.
For a sanction gate, that may mean the business case is sound, and the plan is credible. For an execution gate, it should mean the project has enough verified readiness to start defined work.
The key word is defined. A project may be ready for piling in Area A, but not ready for steel erection in Area B. It may be ready for offshore survey work, but not ready for hook-up. It may be ready for early procurement, but not ready for full construction mobilization.
Decision papers should avoid broad claims such as “ready for execution” unless the evidence supports the full scope.
Define Maturity Criteria Before The Gate
Do not negotiate readiness in the gate meeting. Agree on the criteria in advance.
Typical criteria include:
Engineering deliverables required for the next execution window
Procurement packages placed, delivered, or risk assessed
Permits granted or confirmed for the approved work
Construction work packs complete and released
Access, laydown, utilities, and logistics available
Contractors mobilized with approved plans and competent supervision
Interface agreements signed
HSE plans, method statements, and emergency arrangements approved
Quality plans, inspection points, and turnover requirements defined
Commissioning systemization and operational input in place
Not every criterion applies to every phase. Early works can proceed with targeted criteria. Full execution needs broader evidence.
Maintain A Constraint Register
A traditional risk register is necessary, but it is not enough.
A constraint register tracks items that prevent execution now or will prevent execution soon unless resolved. It should include the owner, required decision date, impact, dependency, current status, and escalation path.
Examples include:
Permit for night work not yet granted
Pipe rack access blocked by utility diversion
Vendor data late for electrical design
Heavy haul route survey incomplete
Subcontractor camp capacity below planned manpower
Tie-in isolation procedure not approved by operations
Marine spread awaiting port clearance
Commissioning spares list not finalized
The constraint register should drive readiness meetings. If it becomes a reporting artifact, it loses value.
Create Hold Points And Decision Thresholds
A hold point is a deliberate pause unless evidence is complete. It protects the project from sliding into higher-risk work by momentum alone.
Useful hold points include:
Start of mass excavation
First concrete in a critical area
Mechanical erection
Energization
Introduction of hydrocarbons or process chemicals
Offshore sail-away
Shutdown start
System handover to commissioning
Performance testing
Handover to operations
Decision thresholds also matter. For example, a project may allow construction start if 90-day work packs are complete, critical permits are granted, and long-lead materials for that window are on site or committed. Make that threshold explicit and get it approved at the right level.
Do not hide exceptions. If leaders choose to proceed below threshold, the decision should record the exposure, mitigations, accountable owner, and review date.
Measure Engineering Maturity Honestly
Percent complete can mislead. Engineering progress should show whether execution deliverables are approved, coordinated, and usable.
Better indicators include:
Approved-for-construction deliverables by area and discipline
Technical queries by type and aging
Interdisciplinary check status
Model review closeout status
Vendor data status and impact on downstream design
HAZOP and design review action closeout
Field change trends
Constructability action closure
The question is not “how much engineering has been spent?” It is “what can the field build without avoidable interruption?”
Test Construction Readiness At The Workface
Construction-readiness assessments should be practical and field-led. They should test the next planned work, not the project in general.
A workface is ready when supervision can answer basic questions with evidence:
What exactly will be built?
Which drawings and specifications apply?
What materials are available and released?
Which permits and isolations are required?
What equipment, scaffolding, lifting, access, and temporary works are ready?
What quality checks and hold points apply?
What hazards and SIMOPS interfaces exist?
Who approves changes?
What happens if the work cannot proceed?
If those answers are unclear, the project is planning activity, not production.
Questions Leaders Should Ask Before Authorizing Execution
Sponsors and project directors do not need to manage every detail. They do need to ask questions that expose whether the approval case has translated into executable readiness.
Before authorizing major execution activity, ask:
What work are we actually ready to start?
Avoid accepting “construction” as a single answer. Break readiness down by area, discipline, system, contract, and time window.
Which assumptions in the sanction case remain unresolved?
Every business case contains assumptions. List the ones still open and decide whether they are acceptable for the next commitment.
What are the top constraints that can stop productive work in the next 30, 60, and 90 days?
This shifts the conversation from general risk to near-term execution reality.
Are permits, access, and third-party approvals granted for the planned workfronts?
Verbal confidence is not enough for critical activities.
Are the right contracts in place, and do they match the maturity of the scope?
If the owner is pushing uncertain scope into fixed-price packages, expect claims or inflated pricing.
Can procurement support the sequence we have approved?
Ask for evidence by package, not a blended percentage.
What design information is still moving, and where will it hit the field?
Late design is manageable only if its impact is visible and contained.
Who owns each major interface?
If ownership is split or implied, it is not owned.
What would make us stop, slow down, or resequence work?
Strong leaders define stop conditions before the project is under pressure.
10. Is operations ready for the asset we plan to hand over?
Readiness includes people, procedures, spares, maintenance systems, regulatory obligations, training, and start-up support.
These questions are not bureaucratic. They protect capital.
Different Sectors, Same Readiness Problem
Details vary by sector, but the pattern is familiar.
On an offshore project, sanction may occur before hook-up readiness is proven. Topsides modules may be fabricated, but offshore execution still depends on vessel availability, weather windows, permits, SIMOPS plans, flange management, temporary power, bed space, and commissioning system boundaries.
On a metro or highway project, funding approval may precede land access, utility diversions, traffic management approvals, ground condition resolution, and community stakeholder agreements. The project can start, but not flow.
On a utility upgrade, the asset owner may approve execution before outage windows, spares, switching plans, regulator notifications, and customer impact arrangements are mature. The project then compresses critical work into unsafe or inefficient windows.
On a brownfield petrochemical modification, the investment may make sense, but readiness depends on plant data, isolation plans, production constraints, hazardous area classification, hot work controls, tie-in packs, and operator training.
On a mining expansion, the board may approve capital based on commodity demand and processing capacity, while execution still depends on camp availability, water supply, access roads, heavy equipment lead times, environmental commitments, and community agreements.
On a commissioning program, mechanical completion may be declared while loop checks, cause-and-effect testing, flushing, drying, reinstatement, punch closure, spares, and operating procedures lag behind. As a result, the start-up team is forced to finish construction.
The common lesson is simple: approval is a decision event. Readiness is a delivery condition.
A Better Way To Authorize Start
The best organizations do not treat readiness as a late checklist. They build it into governance from the start.
They make readiness visible in the approval paper. They separate full sanction from staged authorization. They use independent reviews when risk is high. They let teams start limited work when it's genuinely ready, while holding back activities that depend on unresolved prerequisites.
They also avoid false certainty. If a project is being pushed early for political, commercial, or schedule reasons, they say so plainly. They record the trade-off. They assign owners. They define limits. They track constraints aggressively. They protect the field from being asked to deliver what the project system has not prepared.
That approach is commercially mature. It recognizes that speed has value, but unmanaged speed destroys value.
A practical authorization model might look like this:
Decision | Main Question | Evidence Needed |
Funding approval | Should capital be committed? | Business case, estimate basis, risk view, strategic fit, governance approval |
Early works release | Which limited work can safely begin? | Permits, access, engineering for that scope, contracts, HSE controls, constraints review |
Major execution authorization | Can the project sustain productive execution? | Mature design, placed contracts, procurement status, logistics, work packs, interface control |
Commissioning start | Can systems be tested safely? | Mechanical completion evidence, quality records, procedures, isolations, trained team |
Operational handover | Can the asset be operated and maintained? | Training, spares, manuals, regulatory closeout, maintenance plans, performance evidence |
This structure does not prevent risk. It makes risk visible before the project increases its exposure.
The Professional Takeaway
Sanction is a serious milestone. It confirms that the organization has chosen to commit. But it should never be confused with proof that the project is ready to execute.
Project approval confirms permission to proceed. Execution readiness confirms the ability to proceed with control.
That distinction protects cost, schedule, safety, quality, contractor performance, and operational outcomes. It also gives senior leaders a more honest view of what they are authorizing.
A project that starts before it is ready may still finish, but it will pay for the missing maturity through disruption, rework, claims, delay, and difficult handover. A project that treats readiness as a governed condition gives itself a far better chance of delivering the value that approval was meant to unlock.
