Open a vessel and you learn things. Some of what you learn demands work you did not plan: a corroded nozzle, a cracked support, wall loss past the retirement limit on a line that was only scheduled for a visual. This is discovery work, and no turnaround escapes it.
The trouble is not that discovery happens. The trouble is when nobody can say, at any given moment, how much of it has happened, what it costs, and whether each piece of it was actually justified by a finding. That is when scope growth stops being a technical reality and becomes a budget argument.
Every scope addition starts as a finding
The discipline that keeps discovery honest is a single rule: no work order without a finding behind it.
A finding is a record: what was observed, on which asset, by whom, with the measurement or photo that supports it. A scope addition is a decision made on that finding: repair now, defer with justification, or monitor. When every addition traces back through a decision to an observation, three good things follow:
- The growth is auditable. The turnaround manager can answer "why did mechanical scope grow 18 percent" with a list of findings, not a shrug. The answer might be uncomfortable, but it is real.
- Deferral becomes a legitimate outcome. Not every finding demands work this outage. A documented deferral, with the finding, the engineering rationale, and a date it must be revisited, is a responsible decision. An undocumented one is a liability. The finding-first rule makes the difference visible.
- The estimate conversation changes. Discovery contingency stops being a blind percentage and starts being calibrated: last turnaround on this unit generated this many findings of this kind, costing this much. Three outages of honest finding data is a better basis for the next estimate than any industry rule of thumb.
The approval path has to be fast
Discipline fails when it is slow. If routing a finding to a decision takes two days, crews route around the process, and the work gets done off the books, which is exactly the outcome the process existed to prevent.
The path that works in practice:
- Capture at the point of discovery. The finding is recorded in the field, on the asset's record, with photos, before the crew moves on. Minutes, not a form filed at end of shift.
- Triage on a cadence. A standing review, once or twice per shift, where the materials and inspection leads look at new findings and sort them: clear repair, needs engineering, defer candidate.
- Decision with named authority. Each finding gets a disposition from someone with the authority to give it, recorded on the finding itself. The estimate and schedule impact attach at the same moment.
- Work order linked back. The added work order references the finding. When the work closes, the finding closes, and the loop is complete.
Run at that speed, the process is faster than the workaround, and people use processes that are faster than the workaround.
What honest growth buys you
A turnaround that tracks discovery this way ends with something rare: a defensible account of where the money went. The overrun review is a walk through findings and decisions instead of a hunt through emails. The deferred items are queued for the run cycle with their justifications attached. And the next turnaround's planners inherit a finding history that tells them where this unit hides its surprises.
Scope growth you can explain is a cost. Scope growth you cannot explain is a credibility problem, and credibility is what gets the next budget approved.
intelliPROJECTS links field findings to dispositions and added work orders so the growth trail builds itself during execution, with intelliINSPECT capturing the findings where they are made. If your discovery process currently lives in a change-order spreadsheet, the finding-first rule is worth adopting regardless of the tool.
