Somewhere in every regulatory career is a meeting where a decision that felt obvious from the inside lands, out loud, as arbitrary. The engineer who wanted a faster labeling change, the executive who wanted to skip a test, hears “the regulation requires it” and does not experience that as an answer — because it usually is not one, on its own. Explaining a regulatory decision well is a distinct skill from making it correctly, and the gap between the two is where good decisions get re-argued for months.
Start with the consequence, not the rule
A citation is evidence for a claim, not the claim itself, but it is tempting to open with it anyway — it feels precise, and precision feels like authority. What a non-regulatory colleague actually needs first is the consequence: what happens if we ship this labeling as drafted, versus what happens if we change it, in terms they already track — timeline, cost, review risk, the thing that keeps them up at night. The citation belongs after that sentence, as support for it, not before it as a substitute for it. This is the same instinct behind explaining a submission’s status honestly rather than hiding behind jargon; see working with an FDA reviewer for the mirror version of this skill, aimed at the agency instead of a colleague.
Separate what the rule requires from what you are choosing
Some regulatory answers really are binary: a required field on a form, a mandatory testing standard. Many of the ones that generate the most friction are not. Whether a device change requires a new 510(k) submission, for example, is governed by 21 CFR 807.81(a)(3), which asks whether the change “could significantly affect the safety or effectiveness of the device” — a standard the manufacturer applies through its own documented risk-based assessment, not a lookup table with a fixed answer. Explaining that kind of decision as though it were mechanical invites a colleague to find the one case where it was not, and the explanation collapses. Explaining it as the judgment call it actually is — here is the standard, here is our assessment against it, here is why we landed here rather than the alternative — survives a good follow-up question instead of dreading one. Reading the regulation itself closely enough to make that distinction is its own skill; see how to read a regulation, not just the guidance.
- Write the consequence sentence first, in the language the audience already uses.
- Name the alternative you rejected and why, in one sentence, even if no one asks.
- Separate “the regulation requires this” from “we are choosing to be conservative here” — say which one it is.
- Bring the citation as support, after the point, not as the point itself.
- Be ready to say what new information would change your answer. If nothing would, say that too.
Two habits that turn a sound decision into a fight
Presenting a judgment call as a lookup answer
Borrowing the confidence of a mandatory rule for a decision that was actually a risk-based judgment call works until someone finds the edge case where the confident version breaks. The judgment call, explained honestly as one, does not have that failure mode.
Explaining the rule but not the next step
A colleague who understands why a decision was made but not what to do about it will ask again next week. Closing every explanation with the concrete action — what changes, by when, who owns it — is what actually ends the conversation.
Sources & further reading
- 21 CFR 807.81 — Circumstances under which a premarket notification submission is required, including the significant-change standard at 807.81(a)(3) ecfr.gov
- Regulatory Academy — Building the 510(k), a free lesson on documenting the file behind a decision regulatoryacademy.com
- Regulatory Academy — The 510(k) Pathway, a free five-lesson course 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.
