Writing an indications for use statement you can defend

The indications for use statement is a few sentences on a form, and it quietly sets the outer boundary of everything your 510(k) can claim. Get it wrong and you find out at the worst possible time — after clearance, not before it.

Write the narrower statement first, then check whether you can broaden it

Start from what your data actually demonstrates — the specific condition, the patient population, the part of the body, the use environment, whether it’s prescription or over-the-counter — and write the indications for use statement to match that, not the other way around. Widen it only when you have a specific, documented basis for the wider scope: a predicate cleared for that broader use, and your own testing that supports it. The predicate you choose and the indications for use statement you write are the same decision seen from two angles — change one and you probably need to revisit the other.

This is where a working file of predicate devices earns its keep. Before matching your statement to a predicate’s, check what that predicate is actually cleared for — its 510(k) summary, not its marketing copy — the same habit covered in building a working file of predicate devices. Marketing language drifts from what a clearance letter actually says more often than it should.

It’s the spine of your SE argument, not a footnote on the form

Under 21 CFR 807.87, the indications for use on FDA’s Form 3881 is part of the submission’s administrative identity, and the substantial equivalence finding depends on your device having the same intended use as the predicate. If the labeling elsewhere in your file describes a use broader than what’s on that form, a reviewer isn’t going to treat it as a rounding error — it’s a mismatch between what you’re claiming and what your file actually supports, and it’s the kind of thing that shows up as a question in an interactive review cycle.

Once cleared, the statement becomes a public document, and it becomes the boundary you live inside until you submit again. A meaningful expansion of the indications for use — a new population, a new condition, a new claim — is generally a new submission, not something you can fold into a labeling revision after the fact.

The indications for use statement reads like paperwork right up until the moment it isn’t — when a reviewer asks why your labeling says more than your form does, or when a use case you didn’t write in shows up in the field. Write the narrower, defensible version first. Broadening it later, on purpose and on the record, is a much better problem to have than narrowing it after someone else notices the gap.