Back to Blog
Before the SpadePreconstructionAugust 2026Interactive field note

One lie in the programme

Access Was Assumed

The programme says installation starts on Day 9. The delivery truck cannot reach the workfront. Which date is lying?

By Duc Hoang, PMP

Composite example, not a client programme

Break the baseline

Switch a readiness condition off. Orange is waiting created by a missing gate; black is work on the controlling path.

Can the delivery vehicle actually reach and turn at the workfront?

Ready

Has the temporary-works owner certified the platform for the planned plant?

Ready

Are custody, inspection records and interface data ready with the equipment?

Ready

Is the temporary supply available at the point and quality the test plan assumes?

Ready

Illustrative completion

Day 19
Baseline sequence
Controlling gate

None missing

Parallel delay absorbed

None in this state

Mobilisation

Critical

Work: Day 03

Survey and set-out

Critical

Work: Day 35

Working platform release

Critical

Work: Day 59

FIM receipt and inspection

4d float

Work: Day 35

Main installation

Critical

Work: Day 916

Testing and handover

Critical

Work: Day 1619

The civil workfront sequence controls the baseline.

Every enabling condition is ready at its planned point, so no waiting is added.

Which access condition is most often missing from your baseline?

The visible late activity is often not the failed control

Installation is where the delay becomes visible: the crew waits, the crane stands, or the delivery is turned away. But the failure usually happened earlier. A road was described as “available” without a route survey. A platform date had no signed release criterion. Owner-supplied equipment had no named custody point. Temporary power existed somewhere on site, but not at the voltage, location or quality the test method required.

None of those is background information. Each is an enabling activity with an owner, a required-by date, acceptance evidence and a successor. If the programme carries only the successor, it can be logically tidy and physically impossible.

If the programme cannot name who makes access true—and what evidence proves it—access is not planned. It is hoped for.

The causal model

Two branches converge before installation

The platform branch and the FIM branch run in parallel. Installation cannot begin until both finish. That is why a delay can consume float without moving completion—and why another delay can suddenly become critical.

Civil workfront

Road gate
Mobilisation
Survey
Platform gate

FIM interface

FIM handover
Receipt + inspection

Convergence

Main installation
Power gate
Testing + handover

Installation start = max(platform release, FIM receipt)

max(Day 9, Day 5) = Day 9

Read the orange before the black

The black bar is productive work. The hatched orange segment is time spent waiting for a condition that the baseline assumed would already be true. Treating both as one longer activity hides responsibility and makes recovery discussions less useful.

Critical path
Mobilisation → Survey and set-out → Working platform release → Main installation → Testing and handover
Total float
Time an activity can move without delaying project completion in the current scenario.
Gate evidence
The signed record, survey, inspection or test that releases the next activity—not an optimistic date.

From assumption to control

The workfront-readiness register belongs beside the programme

A planner cannot own every access condition. The planner can make the interface visible, connect it to the work and force a dated evidence conversation before the crew arrives.

Road access

Owner
Site logistics / civil lead
Acceptance evidence
Approved route survey and logistics plan
If it is not ready
Resequence mobilisation or complete temporary access works

Platform

Owner
Temporary-works owner
Acceptance evidence
Signed platform release certificate
If it is not ready
Hold plant delivery and close temporary-works actions

FIM handover

Owner
Owner / supplier interface lead
Acceptance evidence
Inspection, custody and interface-data record
If it is not ready
Quarantine, conditionally accept or resequence installation

Temporary power

Owner
Electrical package lead
Acceptance evidence
Commissioning and power-quality record
If it is not ready
Provide temporary generation or move the test window

Five questions for the baseline review

  1. What physical condition releases this activity?
  2. Which party owns making that condition true?
  3. What document or inspection proves readiness?
  4. Is the gate linked with visible float and a real calendar?
  5. What dated record will support delay attribution later?

What this model cannot tell you

  • It does not determine contractual entitlement, extension of time (EOT) or cost responsibility.
  • It omits resources, weather, calendars, permits and productivity.
  • The waiting periods are teaching inputs, not benchmark durations.
  • A real baseline must be tested against the approved access, logistics, temporary-works and interface plans.

The procurement model changes who owns the gate

Under a single EPC package, equipment availability, logistics and installation may sit behind one contractual interface. Under a free-issue-material strategy, the owner may control supply while the contractor controls receipt, preservation and installation. The programme still needs both sides of the handover: the owner's delivery obligation and the contractor's acceptance evidence.

Companion playbook

FIM versus EPC: the one-page decision sheet

Compare control, interface load, logistics, warranties and schedule ownership before choosing a procurement model.

Further reading: GAO Schedule Assessment Guide