Turnaround inspection scope gets built two ways. The defensible way derives it from equipment history: due dates, open findings, measured deterioration, and known damage mechanisms. The common way copies the last turnaround's scope sheet, adds whatever people remember being worried about, and trims to fit the budget in a meeting.
The copied scope fails in both directions at once. It inspects equipment that three consecutive outages found clean, and it misses the exchanger whose last two bundle pulls showed accelerating tube loss, because that acceleration lives in two separate contractor reports nobody read side by side.
What history has to say, if you can hear it
Equipment history answers four scoping questions directly.
- What is due? The inspection schedule's lookahead over the outage window, plus items due shortly after that would otherwise force an online inspection or a deferral. This is the non-negotiable core of scope, and it should arrive as a query, not a research project.
- What is open? Findings dispositioned as "repair at next opportunity" and monitor items whose recheck lands in the window. Every one of these is scope that was already decided; the only failure mode is forgetting it, and forgotten prior commitments are the most embarrassing audit finding available.
- What is moving? Corrosion rates trending up, remaining life shrinking faster than planned, repeat findings on the same circuit. Trend analysis is where scope earns its money: the vessel that was fine twice and marginal once is exactly the one the copied scope sheet gets wrong.
- What does the mechanism say? Damage mechanisms assigned to circuits imply where to look and with what method. If the mechanism review says wet H2S in the overhead, the scope should show targeted examination there, and the absence of such coverage should require a signature.
Why the mining usually fails
The obstacle is rarely analysis, it is retrieval. History scattered across contractor PDFs, prior turnaround folders, and a retired engineer's hard drive cannot be queried, only excavated, and excavation does not fit a planning calendar. This is the compounding return on capturing inspection data against durable equipment identities in the first place: scoping the next outage becomes reading the record instead of reconstructing it.
Where the record is thin, be honest about it in the scope. Equipment with no usable history is not low risk, it is unknown risk, and unknowns earn a look.
From history to a scope that survives challenge
- Start with the derived list: due items, open commitments, trend flags, mechanism coverage. Generate it from the record before any meeting opinions arrive.
- Tag every line with its driver. When the budget challenge comes, and it comes every time, items defend themselves. Cuts become explicit risk acceptances with names attached, not silent deletions.
- Add discovery contingency where history predicts it. Equipment with a pattern of surprise findings gets contingency hours and materials in the plan. Scope growth you predicted is schedule management; scope growth you did not is a crisis.
- Close the loop after execution. What the turnaround actually found, versus what history predicted, is the calibration data for the next scope. Sites that score their own predictions get better at this every cycle; sites that do not repeat the same scope forever.
A scope built this way changes the budget meeting. The argument stops being whose worry list wins and becomes which named risks the site will accept, which is the argument worth having.
intelliPROJECTS builds the scope from the same records intelliINSPECT, intelliNDT, and intelliINTEGRITY assembled during prior work: due dates, open findings, and trends in one queryable history. Bring your last scope sheet to a demo and see what the record would have added.
