How Regulatory Affairs Works With Manufacturing

The regulatory affairs and manufacturing relationship runs on a question that sounds simple and usually isn’t: does this change need to go back to FDA. Manufacturing owns the floor — the process, the batch record, the equipment — and regulatory affairs owns the answer to that question, which means the relationship mostly lives in the gap between a change that feels routine to the people making it and a change that legally isn’t.

In brief

A device change doesn’t need to be dramatic to require a new 510(k) — 21 CFR § 807.81(a)(3) requires one whenever a change to manufacturing process, components, or method could significantly affect safety or effectiveness, and FDA’s own guidance notes that testing showing no actual effect doesn’t settle the question; the standard is whether the change could affect it.
For an approved drug, a comparable judgment call runs through 21 CFR § 314.70: a manufacturing change is sorted into major (FDA approval required before distribution), moderate (a 30-day notice), or minor (reported in the annual report) — and manufacturing rarely has the regulatory context to make that call alone.
Even when a change doesn’t trigger a new submission, the quality system still requires the device master record to be updated and the change documented. The record has to keep matching reality whether or not a filing was required.
The relationship works the same way the regulatory affairs and R&D relationship does: showing up at change-control review before a change ships beats reviewing a deviation report after the fact.

Where the judgment call actually sits

On the device side, § 807.81(a)(3) sets a standard that’s easy to state and hard to apply: a change in manufacturing process, components, or method of manufacture requires a new 510(k) if it could significantly affect the device’s safety or effectiveness. FDA’s own guidance flags the gap this creates — manufacturers sometimes read test data showing no actual effect as proof a filing isn’t needed, but the regulation asks whether the change could affect safety or effectiveness, a lower and harder-to-rule-out bar. The documentation burden sits with the manufacturer either way; FDA expects a defensible rationale on file for the decision, filed or not. On the drug side, § 314.70 runs a similar judgment call through a more structured funnel: major changes need a prior-approval supplement, moderate changes need a 30-day notice before distribution, and minor changes just go in the annual report. Sorting a specific change into the right bucket is exactly the kind of call manufacturing shouldn’t be making without regulatory affairs in the room.

What makes manufacturing bring you in early

The credibility that earns an early seat at change control is the same credibility that earns one at a design review: being precise about which changes are an actual regulatory trigger and which are a cautious preference, and being willing to say so in both directions. A regulatory reviewer who treats every nonconformance or CAPA as a potential regulatory event trains the floor to stop raising things early; one who can tell the difference between a real § 807.81(a)(3) trigger and routine process tuning becomes someone manufacturing actually wants at the table before a change ships, not after. Reading the device master record or batch record directly, instead of relying on a manufacturing summary of it, is part of the same discipline — the two documents don’t always say the same thing, and the gap between them is usually what an inspector finds first.

Where people get stuck

Reviewing the change after it already shipped

By the time a manufacturing change reaches regulatory affairs as a completed change-control form, it may already be running on the floor. The same late-stage-checkpoint problem that shows up in the R&D relationship applies here with a shorter runway.

Calling every deviation a regulatory event

Treating routine nonconformances as though they carry the same weight as a genuine § 807.81(a)(3) trigger erodes trust the same way an over-called design finding does — and trains the floor to stop looping regulatory affairs in early.

Signing off from the summary instead of the record itself

A device master record or batch record doesn’t always match the summary written about it. The gap between the two is routinely what an inspector finds, and routinely what a regulatory affairs review that only reads the summary misses.

A manufacturing change that never needed FDA’s attention is, most of the time, the actual goal — not every change is supposed to trigger a filing. What makes the relationship work is regulatory affairs catching the ones that do before they’ve already happened, and that only works from inside the change-control process, not downstream of it.

Sources & further reading

eCFR — 21 CFR § 807.81, When a Premarket Notification Submission Is Required ecfr.gov
eCFR — 21 CFR § 314.70, Supplements and Other Changes to an Approved NDA ecfr.gov
Regulatory Academy — How to Read a Device Master Record regulatoryacademy.com
Regulatory Academy — How to Read a CAPA regulatoryacademy.com
Regulatory Academy — How Regulatory Affairs Works With R&D 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.