What decides whether a device change needs a new 510(k)

An engineering change order that swaps a component supplier, tightens a tolerance, or revises a firmware routine rarely arrives labeled as a regulatory decision — it looks like ordinary change control until someone has to answer the question 21 CFR 807.81(a)(3) actually poses: does this change require a new 510(k), or does the existing clearance still cover it. The regulation states that trigger in two short prongs and leaves the harder work of applying them to FDA's guidance, Deciding When to Submit a 510(k) for a Change to an Existing Device, finalized in 2017. A change log that records what was modified and stops there, without running the modification through that test, has skipped the decision the regulation actually requires — and left no record of having made the call at all.

Two prongs, and neither one names a specific change

807.81(a)(3) requires a new premarket notification when a device already cleared under section 510(k) is to be significantly changed or modified in design, components, method of manufacture, or intended use, and it defines what counts on two separate tracks: a change or modification that could significantly affect the safety or effectiveness of the device, or a major change or modification in the device's intended use. Neither prong enumerates the changes it covers. That's a deliberate choice, not a gap — a fixed list would either miss changes the drafters didn't anticipate or catch trivial ones by accident, so the standard is written as a judgment a manufacturer has to apply fresh to its own change, not a table to look a part number up in.

Four flowcharts, sorted by what actually changed

FDA's guidance doesn't leave that judgment unstructured. It walks a manufacturer through one of four decision-making flowcharts depending on the category of change: Flowchart A for labeling changes, Flowchart B for technology, engineering, and performance changes to non-IVD devices, Flowchart C for materials changes to non-IVD devices, and Flowchart D, which combines technology, engineering, performance, and materials questions for in vitro diagnostic devices. The questions differ by category — a labeling change is tested against whether it alters indications, warnings, or directions in ways that could affect safe use, while a materials change is tested against biocompatibility and performance risk — but every flowchart in the guidance resolves back to the same two prongs 807.81(a)(3) sets, restated in terms specific enough to actually answer against a real change.

A “no” has to be earned, not assumed

The guidance frames the whole exercise as a risk-based assessment, and it's explicit that a conclusion of no new 510(k) needed isn't the end of the analysis — it has to be confirmed by successful, routine verification and validation activities before the decision is finalized. That confirmation step is where a change-control process either does real work or becomes a formality: a design team that runs the flowchart logic on paper, reaches a negative answer, and never checks that answer against the verification data the change actually produced hasn't confirmed anything, whatever the flowchart said. The engineering change itself still runs through the design-and-development-file process ISO 13485 Clause 7.3 governs; 807.81(a)(3) is a separate regulatory question layered on top of that process, not a substitute for it.

The record the guidance requires, even when nothing gets filed

Most changes run this analysis and conclude a new 510(k) isn't required — and the guidance's actual requirement in that case isn't silence, it's documentation. Manufacturers are expected to document the rationale behind the decision at each point in the flowchart, kept in the change record inside the quality system rather than sent to FDA, detailed enough that an investigator could reconstruct why the conclusion was reached. That's the same shape of obligation a correction-and-removal record carries under 21 CFR 806.20 when the risk test doesn't clear the reporting bar, and the same shape a complaint record carries under 21 CFR 820.35 when an investigation isn't repeated: the regulation doesn't just test whether the answer was yes or no, it requires the reasoning behind a no to exist on paper, checkable, before the next audit asks for it.

Where a “yes” hands off

When the analysis does land on yes, the new submission goes back through the same gate every 510(k) passes through first — FDA's acceptance review, checking the filing for completeness before anyone reads the science inside it. A change-evaluation record that can show its flowchart, its confirming verification data, and its documented rationale is also the fastest way to assemble that filing when the answer turns out to be yes instead of no.

A change-evaluation record built around this structure — the two-prong 807.81(a)(3) test, the flowchart matched to what changed, and the documented rationale a negative conclusion still requires — is previewed in the launch catalog. If your program applies the flowcharts differently, the shelf takes that correction directly.