Practices
The problem
“Our SOPs sit in a shared drive with names like final_v3, so in an audit we cannot show which version was in effect on the day of the batch, and it becomes a finding.”
The cost: a finding for a document you had all along.
Your SOPs and what your stage needs, in one place.
Keep your own SOPs with their versions and review dates, and learn which rules apply at your stage.
What you get today
Your SOP library
Each SOP keeps its owner and status. Each version keeps its change summary, author, approver, and effective and retired dates.
SOPs due for review are listed, and a weekly digest names them.
Starter content you edit
The glossary, stage roadmap and role paths are a starting point.
Your team edits, marks reviewed or archives each item to fit how you work.
Learn the rules
Start with the orientation, then the topics for your stage and the path for your role.
Questions
Can we bring our existing SOPs?
Yes. Each SOP goes in the library with its versions and review dates.
Who approves a new version?
A named person on your team. The approval keeps who and when.
Related
Bring one SOP and its versions to a walkthrough.