Process mapping for regulatory operations: documenting how things actually work, not how the SOP says they should
Learn to map regulatory operations workflows as they actually function, surface the gap between SOP and practice, and read a finished map for waste and compliance risk.
Process mapping for regulatory operations: documenting how things actually work, not how the SOP says they should
Every regulatory operations team has two processes: the one written in the SOP and the one that actually happens on Tuesday morning when the IRB portal is down and a continuing review is due. The first is tidy. The second is what your department actually does. The first is what auditors read. The second is what your coordinators live.
I have spent a great deal of time watching the gap between these two. It is, I have come to believe, the most important real estate in any regulatory operation. It is where unnecessary effort lives. It is where compliance risk lives. It is where every reasonable improvement opportunity you will ever encounter lives. And it is invisible to anyone who reads only the SOP.
In Module 2 you learned that cross-training reveals which processes a team actually depends on. Now we map them. Not the SOP version. The version that exists.
What you will learn
By the end of this lesson, you will be able to: