Inspection Deferral on Ageing Plant: How to Justify It to an Auditor

The due date on a safety-critical separator is six weeks away. The turnaround it was planned into has moved, the weather window for access…

A mature offshore production platform operating at dusk on a calm sea, the kind of ageing asset where an inspection deferral decision must be justified

The due date on a safety-critical separator is six weeks away. The turnaround it was planned into has moved, the weather window for access has closed, and operations want the unit to keep running. Someone has to decide whether the inspection can wait, and sign their name to it.

On ageing oil, gas and process plant, an inspection deferral is a normal engineering decision, not a failure. Shutdowns slip, campaigns are cut short by weather, scaffold and specialist inspectors are double-booked, and production commitments change. What turns a reasonable deferral into an audit finding, or worse, is a deferral that cannot show why it was safe, who agreed, and what happened next.

Recent editions of API 510 for pressure vessels and API 570 for piping treat deferral as a documented procedure rather than an administrative extension: a risk assessment, approval by named roles before the original due date, and records updated before the equipment runs past it. Check the clause in the edition your site works to. The practical question is what that documentation needs to contain. The easiest way to answer it is to look at a deferral the way an auditor or verifier will.

Why inspection deferrals happen on ageing plant, and where they go wrong

On a fixed offshore platform, a vessel internal can depend on a shutdown that has moved by a season. On an LNG receiving terminal, piping inspection on a boil-off gas line can depend on send-out commitments that leave no outage window. On a refinery hydroprocessing unit, a high-pressure separator in wet sour service may be due between turnarounds. None of these deferrals is wrong in itself.

They go wrong in three predictable ways. The justification is a single line of free text (“no access, low risk”). The approval comes after the due date has already passed. Or the same item is deferred again and again, each time on its own merits, until a five-year interval has quietly become nine.

What an auditor asks about every inspection deferral

A defensible inspection deferral answers seven questions. If any one cannot be answered from the record, the deferral is not ready to sign.

1. Which safety-critical element is being deferred, and what does it protect?

Start with the item’s role, not its tag number. Is it a safety-critical element, and if so, which performance standard does it support, and which verification activity does this inspection satisfy? A deferral on a riser emergency shutdown valve or a relief device protecting an LNG tank is a different decision from one on a utility water line. Where the element is part of a safety instrumented function, a proof-test deferral also has to be checked against its target under IEC 61511.

2. What do we know about its condition today?

List the evidence: last inspection date, method and effectiveness, measured thickness trend, and any open findings. Name the active damage mechanisms under API RP 571 for the service as it runs now, which on ageing plant may not be the service it was designed for. If the item has a risk-based assessment under API RP 580 and API 581, record its current risk and the date it was last reviewed. If the history is thin or inherited from paper records, say so; we covered grading inherited inspection records in an earlier article.

3. How much margin is left at the deferral date?

Project the condition forward to the proposed new date at the measured corrosion rate, or a conservative one if the rate is uncertain. Does the item stay above its required thickness with margin to spare? If not, or if it carries a known flaw, a fitness-for-service assessment under API 579-1 / ASME FFS-1 belongs in the package. The same remaining life arithmetic that supports a life-extension case supports a deferral.

4. What interim measures cover the deferral period?

A deferral is a trade: the inspection moves, and something else covers the gap. Typical measures are external or on-stream thickness checks at the critical points, tighter integrity operating window limits under API RP 584, increased inhibitor or sampling, reduced operating pressure, or more frequent walkdowns. Each one needs an owner and a frequency, and if a temporary repair or open anomaly is part of the picture, it must stay on the live register for the whole period.

5. What is the new date, and is it fixed?

“Next turnaround” is not a date. A defensible deferral gives a specific date, and that date should be no later than the margin from question 3 allows. If the inspection is planned into a future campaign, the campaign must exist on the plan.

6. Who approved the deferral, and was it before the due date?

Approval should sit at a level that matches the consequence: the inspector and the integrity engineer at minimum, plus the technical authority and operations management for safety-critical elements. All of it should be signed before the original due date, not after it. An overdue item cannot be deferred retrospectively; it is simply overdue.

7. Has this inspection been deferred before?

A first deferral with a strong evidence base is routine. A second deferral of the same item needs a fresh assessment and a higher approver. A third should be very hard to sign. Recording the count makes this visible; leaving it to memory does not.

See how ONE links every deferral to the performance standard it affects. Explore the Performance Standards module.

How to stop inspection deferrals stacking into a backlog

Individually justified deferrals can still add up to a problem. Across a multi-site estate, ten reasonable deferrals a quarter become a register nobody reviews as a whole, and deferred inspections quietly pile up behind the next shutdown.

Three habits prevent that:

Report deferrals by performance standard, not just by asset. A count of deferred verification activities against each safety-critical element group shows where assurance is thinning, which is what a verifier, a board or a ministerial reviewer actually needs to see.

Keep deferred items visible until they close. A deferral is not resolved when it is approved; it is resolved when the inspection is done and the results are recorded. Deferred items should stay on the same live view as overdue ones.

Feed the deferrals into the next plan. When the shutdown comes, every deferred inspection should already be on the candidate list with its evidence attached, which is the starting point for turnaround inspection planning that does not grow on the day.

On ageing plant, a well-run deferral process is also an efficiency tool. It lets the integrity team move inspection effort to the windows that suit production and weather, without spending the safety margin to do it.

Where ONE fits

ONE keeps the deferral next to everything it depends on. The Performance Standards module links safety and environmental critical elements to their performance standards and verification activities, reports the number of anomalies against each standard, and runs a change management request-and-review process for the standards themselves. Risk Based Assessment holds the risk basis and inspection frequency, and assessments are superseded rather than overwritten, so past decisions stay reviewable. Anomaly / Defect Management captures reviews and sign-offs, keeps a live temporary repair register, and records every change in a history log, so overdue and deferred items stay visible until they are resolved. Operators of mature assets such as Apache North Sea use ONE to keep performance standards current, with technical authority sign-off and a record of every change.

Deferrals stacking up across your sites? Ask an integrity engineer how ONE puts each one on a single, auditable record, or book a short demo.

Frequently Asked Questions

An inspection deferral is a formal, time-limited decision to carry out a scheduled inspection after its due date, supported by a documented risk assessment and approval. It differs from a planned interval change because it applies to one due date on one item. Pressure vessel and piping inspection codes such as API 510 and API 570 expect deferrals to be documented and approved before the original due date.

Deferring an inspection on safety-critical equipment is acceptable when current condition evidence shows enough margin to reach the new date, the active damage mechanisms and their rates are understood, and interim measures cover the extra period. The decision should be documented, approved at a level matching the consequence of failure, and completed before the inspection falls due.

An inspection deferral is normally approved by the responsible inspector and an integrity or pressure equipment engineer, with operations management agreeing to any interim operating limits. For safety-critical elements, many operators also require the technical authority to sign. Approval should be recorded with names and dates, and given before the original due date.

Common interim measures include on-stream or external thickness checks at critical locations, tighter integrity operating window limits, increased chemical inhibition or sampling, reduced operating pressure and more frequent operator walkdowns. Each measure should have an owner, a frequency and a record of completion, and should stay in place until the deferred inspection has been done.

The same inspection can be deferred more than once, but each further deferral should need a fresh engineering assessment and a higher level of approval. Repeated deferrals can stretch an interval well beyond what the risk basis supports, so many integrity teams track the number of deferrals per item and set a limit after which the inspection must be carried out.