Scoping an ICP Audit Across a Mixed Operator Portfolio
A midstream company operates 1,240 miles of hazardous liquid pipeline across three states and has held ICP certification for two years. Its annual internal audit plan proposes a single combined audit covering all three states, using one lead auditor and two team members. The lead auditor is a corrosion specialist who has never audited control-room operations. State A's pipeline is 18 months old with no findings to date; State B's system was acquired 14 months ago and has never been audited under the current program; State C has had three repeat findings on operator qualification in two consecutive cycles. The program manager argues that a combined audit saves travel cost and that the acquired system can wait until next year because integration is still underway. The audit budget covers 22 auditor-days.
1. Should the audit be combined into one event or split? Justify using risk and audit-effectiveness reasoning, and identify what the 22 auditor-days can realistically support.
Read the worked answer
Split the plan. Three drivers argue against a single combined event:
- Competence mismatch. The lead auditor's corrosion background does not cover control-room operations, which is a distinct scope. A combined audit led by someone who cannot credibly evaluate that area produces a coverage gap, not an efficiency.
- Repeat findings signal weakness. State C's three repeat OQ findings across two cycles mean the prior corrective actions were not effective. That system needs a focused, deeper look, not a share of a generalist audit's attention.
- Acquired system risk. A 14-month-old acquisition that has never been audited is exactly the population where program elements (procedures, training records, MOC) most often fail to transfer. Deferring it converts an unknown into an unmanaged risk.
Budget reality: 22 auditor-days across three systems is roughly 7 days each before travel and reporting, which is thin for a first audit of an acquired system. Recommend prioritizing State B and State C this cycle with named competence (add a control-room-qualified auditor for the operations scope), and a lighter surveillance event for State A. Deferral of State B is the weakest option because the risk grows with time, not shrinks.
2. The program manager proposes measuring audit success by 'zero findings.' How should the ICP program respond, and what metric better reflects program health?
Read the worked answer
Reject 'zero findings' as a success metric. It rewards weak auditing and punishes honest detection, creating an incentive to soften scope or downgrade findings. Better indicators:
- Finding closure effectiveness - percentage of corrective actions verified effective at the next audit, not just closed on paper.
- Repeat-finding rate - the State C pattern is the real signal; a falling repeat rate shows the corrective action loop works.
- Coverage against plan - were all program elements and all systems audited within the intended cycle?
- Detection distribution - findings by element, to show the audit is actually probing, not skimming.
A program with zero findings and 100% coverage on a newly acquired, never-audited system should trigger a quality review of the audit itself, not a celebration.