How to write a regulatory rationale you can defend

A predicate rationale or a risk-based justification isn’t finished when it reads well. It’s finished when it survives someone trying to take it apart.

Structure before prose

A rationale is an argument, and arguments read best in a fixed order: the claim, then the evidence, then the citation that ties them together. State the position first — this device is substantially equivalent to the predicate, this change is a letter-to-file and not a new 510(k), this risk is adequately controlled — before laying out why. A reviewer who has to reconstruct your conclusion from a pile of test data and a standards list has to do your job for you, and a reviewer doing your job for you is a reviewer with room to disagree. The 510(k) summary requirement is a useful worked example of this discipline: 21 CFR 807.92(a)(3) doesn’t just ask for a substantial equivalence claim, it requires a discussion comparing the device’s technological characteristics to the predicate’s — claim, then comparison, then the evidence supporting it. The what a 510(k) actually is lesson walks through that comparison in more detail, and choosing the predicate covers the decision the rest of the rationale has to defend.

Tie every piece of evidence explicitly to the specific requirement it’s answering, not just the general topic. A test report dropped into a rationale with no sentence connecting it to a citation is an artifact, not an argument — the reader has to guess why it’s there. Name the requirement, then show the evidence that satisfies it, one pair at a time.

Write the counterargument yourself

Every rationale worth writing has an obvious objection sitting somewhere in it, and the writer usually knows exactly what it is before anyone else reads the document. Write that objection down and answer it in the text, rather than leaving it for someone else to raise later — a peer reviewer working through a useful review of your draft, or an FDA reviewer during the actual submission. A rationale that pre-empts its own weakest point reads as more careful, not less confident, and it’s considerably cheaper to fix in a draft than in a deficiency response.

This is a different job from explaining a regulatory decision to a stakeholder after it’s been made. Explaining happens after the fact, to someone who wasn’t in the reasoning and mostly wants to know what it means for them. A rationale is written before anyone has signed off on anything, for a reader whose job is to find the hole in it. Write it for that reader, not for the easier one.