Indications for use is not intended use

A 510(k) file that treats the indications for use statement on Form FDA 3881 as a plain-English restatement of the device's intended use has collapsed two terms FDA keeps genuinely separate. This blog has already covered how a predicate has to survive comparison on more than name recognition, and the comparison that decision actually runs on is indications for use — a narrower, submission-specific term sitting inside the wider intended-use standard defined at 21 CFR 801.4. They're related, but not interchangeable, and a submission that confuses the two usually doesn't find out until a reviewer asks why the indications statement says less, or more, than the rest of the labeling does.

801.4 asks a wider question than any one document answers

Intended use, as defined at 21 CFR 801.4, is the objective intent of the persons legally responsible for labeling a device — and that intent can be shown by the label itself, by other labeling, by advertising, by the device's own design or composition, or by the circumstances surrounding its distribution. FDA finalized a rewrite of that definition, alongside the parallel drug provision at 21 CFR 201.128, on August 2, 2021, effective that September, closing out a multi-year rulemaking history that had at one point proposed letting a manufacturer's mere knowledge that a product was being used off-label stand on its own as evidence of a new intended use. The final rule backed away from that: a manufacturer's mere knowledge of an unapproved use, standing alone, doesn't establish a new intended use, though FDA can still weigh it as one factor among the label, promotional material, and the product's own design and distribution. That's a standard built from the whole record around a device, not from any single statement a manufacturer files.

Indications for use is the term that lives inside one document

Indications for use has no equivalent standalone definition in Part 801 — it's the term FDA's own 510(k) forms and regulations use for a narrower, submission-specific statement: the disease or condition the device will diagnose, treat, prevent, cure, or mitigate, and the population or setting it's meant for. Every 510(k) carries one, filed on Form FDA 3881, and 21 CFR 807.92(a)(5) requires the 510(k) summary to state the device's intended use, including that disease or condition description, and — where the indication statements differ from the predicate's own — to explain why the difference isn't critical to the device's therapeutic, diagnostic, prosthetic, or surgical use and doesn't affect safety or effectiveness. That comparison is what actually carries the weight in a substantial equivalence argument: the indications for use of the new device have to be the same as, or narrower than, the predicate's own indications, not merely similar in spirit.

The two don't always move together

Because indications for use is one input into the broader intended-use determination rather than a synonym for it, the two don't always change together. This blog has already covered FDA's own decision tree for whether a device change needs a new 510(k), and a change to the population a device is intended for, or the specific disease it addresses, is exactly the kind of change that guidance says has to be evaluated on its own facts rather than assumed. A narrower or clarified indications statement doesn't automatically amount to a new intended use if the underlying objective intent, judged against the full 801.4 standard, hasn't actually shifted — and reading “the indications changed” and “the intended use changed” as the same finding skips the analysis the guidance actually asks a sponsor to run.

Where the mismatch actually costs something

A submission file that keeps one field labeled “intended use / indications for use” can't show a reviewer, or a later change-control decision, which standard a given labeling claim was actually checked against. The indications statement has to match verbatim across the 510(k) summary, the proposed labeling, and Form 3881; the intended-use analysis behind it has to survive comparison against the device's design, its promotional material, and the predicate's own indications, none of which show up on the form at all. Collapsing the two into one field means a labeling edit gets checked against whichever standard the drafter happened to be thinking about that day, not both.

Where this meets the file

A labeling-change tracker built around this split needs the indications for use statement as filed, kept separate from the broader intended-use rationale and its own supporting evidence — design, labeling, advertising, distribution — with a place to log which one moved on a given amendment. An indications-for-use worksheet built around 807.92(a)(5)'s own comparison requirement is previewed in the launch catalog. If your program tracks this distinction differently, the shelf takes that correction directly.