Every 510(k) has to end with one of two things attached, and most submitters never consciously choose between them. Under 21 CFR § 807.87(h), the submission must include either a 510(k) summary of the safety and effectiveness information or a statement that the information will be made available on request — and the two options commit you to very different things after clearance, not before it.
What the statement actually obligates you to
Choosing § 807.93 doesn’t avoid disclosure — it moves the timing and the audience. Instead of writing a public-facing comparison document as part of the submission, you are committing that if anyone — a competitor doing diligence, opposing counsel, a journalist — sends a written request, you have 30 days to produce the underlying safety and effectiveness information. Submitters who pick the statement route sometimes treat it as the quiet option. It is closer to the opposite: a standing, open-ended obligation with a hard clock, triggered by someone else’s request rather than your own publication choice.
Why almost everyone defaults to the summary
Writing the summary up front means you control the framing, build it once inside the submission timeline, and never have to field a cold request on a short deadline. A statement can look attractive when a full comparison would surface competitively sensitive detail, but then you are wagering that no one ever asks formally — and if someone does, you are assembling the document under a 30-day clock instead of during the unhurried work of building the file. The comparison itself follows the same logic either way: see how to read a 510(k) summary for what a reviewer and a competitor both look for in that document, and building the 510(k) file for where this choice sits in the overall submission.
How to tell which one your 510(k) used
If you weren’t on the team that filed the original 510(k), the choice is easy to check without asking anyone. FDA’s device database links out to the cleared summary when one was filed; a device cleared under a statement shows the certification instead, with no comparison document attached. The listing itself doesn’t spell out which option was chosen in so many words, but the presence or absence of a posted summary tells you immediately which path the submission took.
Where this goes wrong
Treating the statement as a way to avoid disclosure
It only changes when disclosure happens and who has to ask for it, not whether the information ever becomes available.
Not knowing which option your own company chose
It is a matter of public record — pull the cleared 510(k) from FDA’s database and check before you assume.
Waiting for a request to arrive before preparing to answer it
The 30-day clock starts at the written request, not when your team gets around to assembling the file — § 807.93 gives the requester 30 days, not you extra time to build from scratch.
The choice sits downstream of an earlier one: whatever you compare your device against has to hold up as a defensible predicate before the summary-or-statement question even matters, since a weak comparison reads the same way regardless of which document carries it.
Sources & further reading
- eCFR — 21 CFR § 807.92, Content and format of a 510(k) summary ecfr.gov
- eCFR — 21 CFR § 807.93, Content and format of a 510(k) statement ecfr.gov
- Regulatory Academy — How to Read a 510(k) Summary regulatoryacademy.com
- Regulatory Academy — Building the 510(k): eSTAR, Screening, and the Testing Burden 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.