An on-the-job incident occurs, and your operational, safety, and compliance teams immediately launch an investigation.
The findings are approved, and the writer is ready to update the SOP accordingly, right?
Not so fast.
Is there a clear process for translating those findings into corrective action documentation? Do you know which documents within the system are affected?
And what happens if the same incident occurs after the investigation?
Approved findings are only the beginning. No investigation is complete unless you establish a truly implementable revision plan that translates findings into actionable, long-term prevention.
In this blog post, we’ll focus on the steps involved to build a strong revision plan.
But first, some fundamentals.
What is an SOP Revision Plan?
The thing to remember is that an SOP revision plan isn’t the same as an SOP revision:
SOP revision plan: A structured, strategic process that defines the who, what, where, when, and why related to reviewing, validating, and approving incident-driven SOP updates.
Updating the SOP: The SOP writer changes the documentation to what the revision plan stipulates.
That’s the simple definition. The steps to take in order to build a revision plan, however, can get complicated. So let’s see if we can simplify those as well.
Step One: Review and Double-Check the Findings
Even the most comprehensive findings can miss a game-changing detail, which is why the first step in building your revision plan is to make sure nothing is left to chance.
Like so many other problem-solving endeavors, begin by asking key questions, such as:
• Is the root cause connected to training, equipment, communication, or human error? If so, what specifically contributed to the incident, and why?
• Are there disparities between the SOP and actual work performed? Is the problem with the actual SOP itself?
• Does the corrective action properly and accurately address the problem and all documents, forms, checklists, etc. that need revising?
It’s also worth mentioning that findings which impact one area of the organization can impact another area not easily identified.
For instance, there may be multiple versions of a procedure being used in other locations. Or the findings may affect a procedure that applies across the entire organization.
Taking this step is an opportunity to effectively ensure the findings account for all needed revisions.
Better-safe-than-sorry definitely applies.
Step Two: Define Revision Scope
Defining revision scope is where you turn what you’ve learned in step one into specific documentation change—including where corrective action belongs, and how far those revisions ned to extend within the system.
In addition to determining all affected documentation, revision scope accounts for:
• What must be added, removed, or further clarified in existing documentation
• How the revisions address the finding
• Which similar procedures are impacted, and if any of this extends outside of the revision scope
Now it’s time to apply the litmus test.
Step Three: Validate Revisions
This step can be best summed up as: where revisions meet real-world application.
You know which documents to change, and why. The validation process determines if the revisions are accurate, reasonable, and practical.
Operational Reality: Does the revision realistically address all underlying causes? Can corrective action be practically applied?
Technical Reality: Is the revised procedure technically correct? Can it be accurately followed and understood?
Prevention Reality: Does this keep the problem from recurring? Or are there other risks that need to be addressed?
If there was ever a time when tiny details and specifics matter, it’s here.
Step Four: Assign Ownership
A revision can’t effectively move through the workflow if no one owns it. Or, for that matter, if everyone does.
Ownership isn’t just about who does what and when. It establishes a record of verification that the revision is being properly examined by exactly the right people.
That might include, but isn’t always limited to:
• Revision owner who makes the document change
• SME who provides technical expertise
• Safety/compliance reviewer who evaluates risks and regulatory implications
• Person or persons who provide approval and final authorization
Clearly defined ownership helps ensure that validated changes are made as intended and receive the appropriate technical, safety, compliance, and approval reviews.
Step Five: The SOP Revision Backlog
The SOP revision backlog is where your revision plan comes to life.
In other words, it’s where everything you’ve learned to this point is itemized, organized, and prioritized. This allows the SOP writer to organize revisions, and keep the revision process flowing smoothly.
A backlog would appear as a chart or table that might include the following headers:
• Finding
• Affected Documents
• Revision Scope
• Priority
• Owner
• Validation
• Approval
• Status
This allows competing revision requests to be prioritized by safety, compliance, and operational impact. All affected employees and processes are established. And procedural improvement is solidly defined.
The SOP writer now has a clear incident findings roadmap to set procedure revision priorities, and ultimately make revisions more operationally effective.
Final Thoughts
SOP improvement—and incident preparedness—starts with a solid revision plan.
Maybe you can’t prevent every incident from occurring.
But as this blog post has hopefully established, a revision plan helps you better control how you respond, and perhaps lower the chances of that incident occurring again.