Not Every Serious Problem Is Life-Threatening. STeP Is for the Rest.
STeP strategy for devices that meaningfully improve safety below the Breakthrough threshold — the same interactive FDA engagement model, a different eligibility bar.
The Engagement Is the Same. The Door Is Different.
STeP was built for devices that improve the safety of treatments or diagnostics for conditions less serious than those Breakthrough addresses — and it hands you substantially the same access.
Life-threatening or irreversibly debilitating disease or conditions.
Conditions less serious than that — the tier the Breakthrough criteria exclude by design.
More effective treatment or diagnosis.
A significant safety improvement — reducing a known failure mode, a serious adverse event, or a use-related hazard.
Unchanged — 510(k), De Novo, or PMA on the ordinary standard.
Unchanged — identical statutory standard, identical evidence expectations.
The strategic read: teams routinely force a Breakthrough request their indication cannot support, get declined, and conclude expedited engagement is closed to them. STeP is frequently the request they should have filed — and it costs a fraction of the time to argue honestly.
“Safer” Is a Number, Not an Adjective.
STeP eligibility turns on a claim of significant safety improvement, and FDA reads that as comparative: safer than what, measured how, by how much. A request that says the device is well designed has said nothing.
This is where your risk management file earns its keep. The hazard analysis you already maintain under ISO 14971 usually contains the raw material for the STeP case. The request is often a translation exercise, not a new investigation.
The strongest STeP cases come from designs that eliminate a failure mode rather than warning about it — the top of the risk-control hierarchy.
Name the Hazard
The specific failure mode, use error, or adverse event your design addresses — drawn from the hazard analysis, not from marketing.
Quantify the Baseline
Its incidence in the current standard of care, from literature, MAUDE, or your own post-market data. No baseline, no improvement.
Show the Delta
Why your design removes or reduces it, with the evidence that supports the size of the claim — and honesty about what is not yet proven.
Six Disciplines That Carry a STeP Program.
From the tier decision to the interactions that make the designation worth having.
Program Selection
The Breakthrough-versus-STeP call made on your indication and your evidence — before a misaimed request burns a quarter and a relationship.
Safety-Improvement Case
The comparative claim built from real data: the hazard, its rate in current practice, and the quantified improvement your design delivers.
Risk File Translation
Your existing hazard analysis mined for the STeP argument — because the evidence is usually already in the quality system, unread by regulatory.
Designation Request Build
The submission FDA can act on: eligibility argued explicitly, evidence attached, and the ask stated plainly.
Interactive Review Management
The access converted into decisions — each interaction closing a question that would otherwise appear as a deficiency.
Submission Execution
The eventual 510(k), De Novo, or PMA built to move at the speed the designation offers — priority handling helps only a file that is ready.
Six Failure Modes We Are Brought In to Prevent.
Nearly all of them are the same error: safety asserted rather than demonstrated.
The forced Breakthrough request
An indication that plainly doesn’t meet the serious-condition bar, argued anyway — declined, when STeP was available all along.
“Safer” without a comparator
A safety claim with nothing on the other side of it. FDA cannot evaluate an improvement over an unnamed baseline.
The risk file left in quality
A hazard analysis that contains the whole argument, never read by the team writing the request.
Marginal improvements oversold
A small, real safety gain inflated into a transformative claim — and a reviewer who now discounts the parts that were true.
Access left unused
Designation won, interactions never requested — the program’s entire value forgone out of deference or inertia.
Designation confused with clearance
Commercial materials that present a STeP designation as a market authorization — a promotional problem with regulatory consequences.
STeP Leadership for Devices That Make Care Safer.
Our device leads have built safety-improvement cases from risk files and run the interactions that follow.
“Most STeP cases are already written — in the hazard analysis. The work is translating an engineering document into a regulatory argument.”
The discipline we bring to safety-improvement programs.
Is Your Device Genuinely Safer? Make the Case in Numbers.
A senior device lead can read your hazard analysis against the STeP criteria and tell you whether the argument is already in the file.
Senior-led. Embedded in your team. No junior hand-offs.