Regulatory affairs and quality get treated as close enough to interchangeable that some companies fold them into one function. They aren’t interchangeable — they ask different questions of the same underlying records — but those records only work if both functions are reading from the same file.
Where the division of labor actually falls
Quality’s job is to run the system that generates and documents evidence — design history files, CAPA records, complaint files, audit findings, supplier controls — under the quality management system regulation, now largely harmonized with ISO 13485 through the QMSR. Regulatory’s job is to take that same evidence and build the case that it satisfies whatever external standard applies: a submission requirement, an inspection question, a labeling claim. The two functions are often reading the identical design history file or CAPA record, but quality is asking whether it satisfies the internal procedure, and regulatory is asking whether it satisfies what FDA actually requires — questions that overlap most of the time and diverge at exactly the moments that matter most.
Where the relationship breaks without a shared file
The failure mode isn’t usually conflict; it’s distance. If regulatory only sees quality data episodically — at a scheduled review, or when a filing forces the question — it discovers a systemic issue at roughly the same moment an inspector does, from the same complaint trend or CAPA log quality has been sitting on for months. And if quality closes a “not reportable” complaint without looping regulatory in on the reasoning, regulatory has no way to defend that judgment when it’s questioned later, because the reasoning was never really regulatory’s to begin with. Neither failure requires bad faith on either side — both are what happens by default when the only scheduled contact between the two functions is a deadline.
Where people get stuck
Treating a “not reportable” decision as purely a quality call
The regulation doesn’t assign that judgment to a department; it assigns it to whoever makes the reportability determination, and that determination needs regulatory’s read of the standard even when quality owns the procedure that generates it.
Waiting for a filing deadline to look at the CAPA log
By the time a submission or an annual report forces the review, a systemic issue that’s been visible in the data for months looks like something regulatory should have caught earlier — because it should have.
Keeping separate, informal tallies of the same nonconformances
When quality’s count and regulatory’s count of the same recurring issue don’t match, neither number survives an inspector’s cross-check.
None of this requires collapsing the two functions into one. It requires treating the quality system’s records as regulatory’s records too — read regularly, not requested occasionally — so the argument regulatory has to make when it counts is built on data regulatory has already seen.
Sources & further reading
- 21 CFR Part 820 — Quality System Regulation ecfr.gov
- Regulatory Academy — What the QMSR Actually Changes regulatoryacademy.com
- Regulatory Academy — How to Read a Complaint File regulatoryacademy.com
- Regulatory Academy — How to Read a CAPA regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
