Corrective Action Program Best Practice 27 – Screen for Corrective Scope That Solves More Than One Condition Report
You’ve got an emergency diesel generator out of service for a maintenance repair. The work goes fine, the crew reinstalls the covers, pulls the lockout tags, and runs the required surveillance test to prove the diesel starts and loads as designed. Everything checks out. Diesel’s back in service, condition report closed.
Three days later, in the same week, a second condition report on that same diesel comes up for correction — a different deficiency, unrelated to the first, legitimately its own unique issue. So the crew tags it out again, does the repair, pulls the tags again, and runs the exact same surveillance test again to prove the diesel still starts and loads as designed.
Nothing about either condition report was wrong. Both were real, both were correctly written up as distinct issues. But the diesel was taken out of service twice instead of once, got tagged and untagged twice instead of once, and got run through a full retest twice instead of once — and nobody caught it until the end-of-week schedule review, when someone asked the obvious question: why didn’t we just do these jobs together.
Hi there! Gain access to this article with a StrategyDriven Insights Library – Total Access subscription.
| Subscribe to the StrategyDriven Insights Library Sign-up now for your StrategyDriven Insights Library – Total Access subscription for as low as $15 / month (paid annually). Not sure? Click here to learn more. |
About the Author









Leave a Reply
Want to join the discussion?Feel free to contribute!