Most device changes never touch FDA’s desk. A manufacturer changes a supplier, a dimension, a software routine, a label — and decides, on its own, whether that change needs a new 510(k) or can be handled with a written rationale kept on file. That written rationale is the letter-to-file, and reading one closely is a different skill from just knowing the rule exists.
What the analysis actually has to show
The regulation names specific things a change can affect that push it over the new-submission line — intended use, energy source or type, design, materials, and performance specifications — plus a general test above all of them for whether the change could significantly affect safety or effectiveness. A letter-to-file that’s doing its job walks each element the actual change touches: it quotes the current specification and the changed one, describes what testing or analysis supports the conclusion that the difference doesn’t cross into any of those categories, and says so in enough detail that someone reading it two years later, with no memory of the discussion, could reconstruct why the decision was reasonable at the time.
Why it’s worth reading closely, not just confirming it exists
The failure mode that shows up at inspection isn’t a missing letter-to-file — most files have one for every change that plausibly needed one. It’s a rationale that states its conclusion without showing its work: “this change does not significantly affect safety or effectiveness,” with no discussion of what was actually compared or which of 807.81(a)(3)’s categories the reasoning was checked against. The other pattern worth watching for is drift across several small, individually reasonable changes — a material substitution here, a tolerance widened there — each judged not to cross the line on its own, without anyone stepping back to ask whether the device three changes later is still the device the original 510(k) cleared. That’s the same discipline behind reading a risk management file for whether a residual-risk conclusion still holds after a design has moved, not just whether the form was filled in.
Where this goes wrong
Writing the conclusion and skipping the analysis
“This change does not significantly affect safety or effectiveness” is a conclusion, not a rationale — a reader two years later needs to see what was actually compared.
Evaluating each change in isolation
A string of individually minor letter-to-file decisions can add up to a device that no longer matches what the original 510(k) cleared.
Filing it and forgetting it
A letter-to-file that isn’t cross-referenced to the device master record and design history file is hard to find exactly when an inspector or a due-diligence reviewer asks for it.
A letter-to-file only protects the company that wrote it if the reasoning inside it would still hold up read cold, by someone who wasn’t in the room when the change was made — and that’s a higher bar than most rationales are written to.
Sources & further reading
- 21 CFR § 807.81(a)(3) — When a premarket notification submission is required ecfr.gov
- Regulatory Academy — How to Write a Regulatory Rationale regulatoryacademy.com
- Regulatory Academy — How to Read a Risk Management File regulatoryacademy.com
- Regulatory Academy — The Case for a Regulatory Decision Log 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.