Building the regulatory QMS: SOPs, process documentation, and governance structure — Inspection Readiness and Regulatory Quality Management

Free Lesson Preview

Continue with the Regulatory Coordinator track

View the Regulatory Coordinator track for current pricing and enrollment options.

Already enrolled? Sign in

Building the regulatory QMS: SOPs, process documentation, and governance structure

Teaches the RC to design a quality management system specifically for the site's regulatory operations, distinguishing between a QMS as a governance structure and a collection of SOPs, and applying risk-based documentation hierarchy with defined governance for authoring, review, approval, training, and revision.

22 min

A QMS is not a binder of SOPs

Module 4 closed with the mechanics of managing inspections -- the preparation, the conduct, the response, the follow-up. That sequence is important. But it is, by nature, event-driven: something happens, and the site responds. Module 5 asks a different question entirely. Not "How do we handle an inspection?" but "What is the standing system that makes our regulatory operations consistently good, whether or not anyone is watching?"

That system is the quality management system. And I want to begin with the most common misunderstanding I encounter when teaching this material: the belief that having SOPs is the same thing as having a QMS. It is not. Not even close.

I have visited sites -- more than I care to count -- where the regulatory coordinator proudly displayed a shelf of SOP binders, color-coded by domain, each bearing a revision date and an approval signature. Impressive to look at. And functionally meaningless. When I asked staff to describe the relationship between the consent version tracking SOP and the protocol amendment implementation SOP, they could not. When I asked when the essential records SOP had last been reviewed against current practice, no one knew. When I asked who was responsible for initiating SOP revision when a process changed, the answer was "I think it's supposed to be the QA office." It was not the QA office. Nobody had that responsibility.

Those sites had SOPs. They did not have a quality management system. The distinction matters because ICH E6(R3) Section 3.10 does not ask sites to write procedures. It asks sites to implement a quality management system -- a system that defines processes, documents procedures, assigns governance responsibilities, and includes systematic review mechanisms. The SOPs are artifacts of the system. They are not the system itself.