The Case for Keeping a Regulatory Decision Log

Six months after you decide a labeling change is minor enough not to trigger a new 510(k), someone will ask why. If the honest answer is that you don’t fully remember your reasoning at the time, a decision log is the difference between reconstructing your logic under pressure and just reading it back.

In brief

The records requirement in 21 CFR § 820.180 is about more than keeping the paperwork — a quality system record that shows only the outcome of a decision, not the reasoning behind it, is thinner evidence than it looks like.
A decision log isn’t the polished rationale memo you’d hand to an auditor. It’s the running, unpolished record you keep as you go, so that memo is easy to write later instead of reconstructed from memory.
The habit pays off most on the calls nobody else will remember you making — the small classification judgment, the “this is probably fine” that turns out to matter eighteen months later.
It also protects whoever holds the role after you. Institutional memory that lives only in one person’s head leaves the building the day that person does.

What belongs in the log, and what doesn’t

Not every action item earns an entry. The log is for judgment calls — the moments where you chose between two reasonable readings of a requirement, or decided something didn’t rise to a threshold: a change that probably isn’t significant enough to need a new submission, an event that probably isn’t reportable, a deviation that probably doesn’t need its own CAPA. For each one, a few lines is enough: the date, the question, what you considered, what you decided, and why. That is a different document from writing a regulatory rationale you can defend, which is the finished, polished artifact you produce for one specific decision that needs to hold up to scrutiny. The log is the raw material you would draw on to write ten of those a year without redoing the thinking each time.

Why this beats trusting your memory

A root cause investigation under 21 CFR § 820.100 often turns on what was known and decided at the time, not what makes sense in hindsight. A contemporaneous log beats a reconstructed timeline for the same reason a dated lab notebook beats a reconstructed one: it is evidence of what you actually thought when you thought it, not a story that has quietly reshaped itself to look more obviously correct than it felt in the moment. The same discipline is what makes a 483 response persuasive instead of merely plausible — “we always intended to do X” is a much stronger claim when there is a dated entry from months earlier that says so. A decision log is a different habit from building a regulatory intelligence habit, which tracks what is changing in the outside world; this is a record of the calls you made inside your own program.

Where people get stuck

Waiting to write it up “properly” later

Later rarely comes, and by the time it does, the reasoning has usually reshaped itself in memory to look cleaner and more obviously correct than it actually felt at the time you made the call.

Logging the outcome without the reasoning

“Decided the change was minor” with no note on why is barely better than nothing. The value of the log is entirely in the why, not the what.

Keeping it somewhere that leaves when you do

A personal notebook or a personal drive folder isn’t a substitute for whatever your quality system already treats as the record of record. Keep the log as your own working feed into that system, not a shadow system that replaces it.

None of this needs to be elaborate. A dated entry of a few sentences, written the day you made the call, is worth more than an eloquent reconstruction written six months later under pressure. The discipline is showing up consistently on the small decisions, not producing something impressive on the large ones.

Sources & further reading

21 CFR § 820.180 — Records, General Requirements ecfr.gov
21 CFR § 820.100 — Corrective and Preventive Action ecfr.gov
Regulatory Academy — How to Write a Regulatory Rationale You Can Defend regulatoryacademy.com
Regulatory Academy — How to Write an FDA 483 Response regulatoryacademy.com
Regulatory Academy — How to Build a Regulatory Intelligence Habit 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.