Every mature turnaround runs stage gates: scope freeze, planning complete, execution readiness. The gates diligently check materials, scaffolding, permits, and crane bookings. Then they ask whether inspection is ready, someone says yes, and the gate closes.
That yes is often unexamined, and it is where the schedule risk hides. Inspection is a discovery function: it generates the scope growth that breaks turnarounds. An inspection function that arrives half-ready does not fail visibly on day one. It fails on day nine, as findings pile up faster than they can be evaluated.
What each gate should actually verify
Scope freeze: is the inspection scope traceable?
- Every inspection work item traces to a driver: a due date from the schedule, an open finding, a damage-mechanism concern, or a regulatory commitment. Items that trace to "we always look at that" deserve a challenge; unexplained scope is unmanageable scope.
- The deferred list is explicit. What was considered and cut, with a named acceptor of the risk. The list that hurts you is the one that was never written.
- History has been mined. Prior findings on in-scope equipment reviewed, so known bad actors carry contingency in the plan rather than arriving as surprises.
Planning complete: can the work execute without improvisation?
- Work packs exist at task granularity, with procedures, prior data, drawings, and acceptance criteria attached. A pack that says "inspect exchanger" is a placeholder, not a plan.
- Access and inspection are coordinated. Insulation stripping, scaffolding, and vessel opening sequenced against the inspection plan, so crews are not idle in front of unopened equipment.
- Evaluation capacity is planned like craft labor. Findings will need engineering disposition daily. If the plan has no named evaluators with reserved hours, the finding queue becomes the critical path around day five.
- Contractor data flow is contracted. NDE subcontractors capture into the owner's system or sync at shift cadence. Data delivered at demobilization is data unavailable during execution, when it was needed most.
Execution readiness: will the record assemble in real time?
- Field capture is proven on this site, devices in hand, offline sync tested in the actual units, crews trained before the first shift, not during it.
- The finding pipeline is live: capture, screening, disposition, work order, with owners on each state and a queue visible to turnaround management.
- Daily reporting is generated from the record, not composed each evening. If status requires a nightly spreadsheet ritual, the truth will lag the field by a day, and decisions will be made on the lag.
The gate question that matters most
At each gate, one question separates real readiness from asserted readiness: if a finding appears at 03:00 on day six, trace its path to a disposition. Who screens it, who evaluates it, where does the repair scope land, and how does management see it at the 06:00 meeting? A team that answers fluently is ready. A team that starts the answer with "well, normally" is not, and the gate is the last cheap place to find that out.
Closeout deserves its own gate criterion set at the start: findings land on equipment records, repairs carry evidence, sign-offs happen in the field. Turnarounds that build the record during execution do not have a closeout phase worth fearing.
intelliPROJECTS gives the inspection function this gate visibility, scope traced to drivers, packs at task level, and a live finding pipeline, with the record assembling as work happens. Bring your next outage's gate checklist to a demo and test it.
