Summary or statement: the 510(k) choice that sticks

Every Traditional, Special, or Abbreviated 510(k) has to close with one of two specific documents, and the choice is easy to treat as a formatting decision because FDA's own acceptance checklist lists them as interchangeable line items: a 510(k) summary under 21 CFR 807.92, or a 510(k) statement under 21 CFR 807.93. They aren't interchangeable in effect. The summary becomes part of the public record FDA posts once the device clears; the statement doesn't — it commits the submitter instead to a standing promise to hand safety and effectiveness information over later, to anyone who asks. A submission that picks one of the two without weighing what each one actually commits to is making a disclosure decision by default, not by choice.

Two ways to close the filing, built to do different jobs

21 CFR 807.92 sets out what a 510(k) summary has to contain: the submitter's name, address and a contact; the device's trade name, common name and classification name; identification of the predicate device the submission claims equivalence to; a description of the device and its intended use; a comparison of technological characteristics against the predicate; and, where substantial equivalence rests on performance data, a summary of the nonclinical and clinical testing behind it. The section requires all of it in sufficient detail to let a reader understand the basis for the substantial-equivalence determination — not a marketing abstract, a technical one. Once the device clears, FDA posts this document in its public 510(k) database, where it stays retrievable indefinitely.

The statement is a promise, not a disclosure

21 CFR 807.93 takes a structurally different approach: instead of summarizing the submission's content, the statement certifies that the submitter will make all the safety and effectiveness information in the 510(k) available to any requester within 30 days, if the device is found substantially equivalent. What gets released under that promise is a duplicate of the submission itself, with patient identifiers and trade-secret or confidential commercial information withheld under 21 CFR 20.61 — but nothing gets posted proactively. The statement has to be signed by the certifier, sit on its own page, and be clearly labeled — the same formatting discipline 807.92 requires of the summary, applied to a document that promises future access instead of providing it now.

What the choice actually turns on

A summary detailed enough to satisfy 807.92 can put a fair amount of a device's technological comparison and test rationale into a document a competitor can read the day clearance posts. A statement keeps that same information out of the public database, at the cost of an open-ended obligation to track and respond to requests for the underlying submission for as long as anyone might ask — and a request, when it comes, still surfaces most of the same content the summary would have, minus the trade-secret redactions. Neither option avoids disclosure entirely; they trade an automatic, immediate posting against a request-triggered, redacted one, and the right answer depends on how much comparison and test detail a sponsor is comfortable seeing published the moment the device clears, versus how reliably the organization can guarantee it'll still be able to respond to a request years later.

Where the acceptance checklist stops looking

The Refuse-to-Accept checklist requires one of the two documents to be present — a summary or a statement, either satisfies the same checklist row — and, as with every other item on that checklist, presence is all it's built to confirm. eSTAR's guided template carries the same requirement forward as a required field in its own structure, and the branch it opens depends only on which document type the submitter selects, not on whether that selection actually serves the sponsor's own disclosure preference. Nothing downstream of that field checks whether the choice was made deliberately, which makes it one place in the filing where the decision has to be made correctly the first time, on paper, before the template moves on.

A 510(k) closing-document worksheet that walks through this choice explicitly — what a summary discloses immediately against what a statement defers — is previewed in the launch catalog. If your program weighs the choice on different grounds, the shelf takes that correction directly.