WorkflowRegulatory Affairs

510(k) eSTAR Submission

A 510(k) eSTAR built to clear FDA's technical screening the first time, every check green

An eSTAR that clears FDA's technical screening the first time, every check green.

See one case, screen by screen ↓
demo31checksin the preflight on the sample eSTAR — 30 green on the first run, line 22 fixed in 2 places
demo17rowsbeside the predicate: 11 the same, 6 different, every difference answered by a report
target0holdsat FDA's technical screening on the last 9 submissions
target3weeksto a ready eSTAR, down from 10
In short

What is 510(k) eSTAR Submission?

eSTAR is FDA's electronic submission template, and every 510(k) must now be sent as one unless it is exempt. It runs to some 20 sections, from device description and the predicate comparison to sterility, biocompatibility, labeling and performance testing. 510(k) eSTAR Submission drafts those sections from your design history file, test reports and labeling and checks the result before it goes.

How to choose AI solutions for life sciences →

Updated

The problem

Why one wrong answer can hold a 510(k) for half a year

Every 510(k) now goes to FDA as an eSTAR: some 20 sections, from device description and the predicate comparison to sterility, biocompatibility, labeling and performance testing. The regulatory specialist assembles it by hand from three sources that never agree perfectly — the design history file, a dozen test reports and the labeling. The same model number, shelf life or standard edition appears in five places, and each is copied across by hand.

Checking is reading. The template's own checks only test that a field is filled, not that the answer is right, that an attachment answers its question, or that the standard cited is the edition FDA recognises today. FDA screens each eSTAR within 15 days; an answer that contradicts the device, an unexplained “N/A” or an attachment that misses its question puts the submission on hold for up to 180 days until a complete replacement arrives. A weak predicate comparison costs an Additional Information request and another cycle.

typical15daysfor FDA to screen an eSTAR technically
typical180dayson hold, at most, after a failed screen — until a complete replacement eSTAR arrives
typical63–68%of 510(k)s got an Additional Information request on the first review cycle, FY2018–FY2022
Where an eSTAR's working days goestimated
By hand50 days
With the solution15 days
  • Drafting 22 sections from the design file, test reports and labeling20 → 6 d
  • Building the predicate comparison and finding the report for each difference8 → 2 d
  • Checking standard editions and declarations of conformity5 → 1 d
  • Reading it twice for facts that disagree and attachments that miss10 → 1 d
  • Approvals, cover letter and 510(k) Summary7 → 5 d

Estimated split for a Traditional 510(k) from the start of drafting to a ready eSTAR — about 10 weeks by hand, 3 with the solution.

How it works

How a submission comes together

Five specialist agents draft, compare, match and check every section; a regulatory director approves and signs.

What comes in
Sources in3 sources · design file, test reports, labeling
Agents at work
Section drafterevery claim cited
Predicate comparerrow by row
Then
Standards matcherFDA-recognised editions
Then
Preflight checker31 screening checks
Cover letter writer
A person decides
Regulatory directorapproves and signs
What comes out
eSTAR, every check green
Predicate table with proof
Submitted by a person
One case, step by step

One eSTAR, from drafted to signed

Veltara Medical is filing a Traditional 510(k) for the VLT-Flow 80 Subcutaneous Infusion Set — six models, product code FPA, 21 CFR 880.5440, Class II — against the Halvern SoftPort 90, K231592. Target submission: 20 Oct. Here is what happens next, screen by screen, in the working solution.

  1. 0113 Oct, morning

    The whole submission, and what is left, on one screen

    Nadia Brennan · Regulatory affairs specialist, devices

    Nadia owns the VLT-Flow 80 eSTAR v6.1: 22 of 22 sections drafted, 46 attachments, target 20 Oct. The preflight last ran on 12 Oct and the draft has had 14 edits since, so its 31 checks sit grey in eight groups — from submission and administration to declarations — with one light at the end: Ready to submit.

    On the submission strip: “FDA screens it within 15 days · if it fails, up to 180 days on hold.”

  2. 02Predicate

    The device beside its predicate, row by row

    Predicate comparer

    The comparer read the predicate's 510(k) Summary and the design history file and laid out 17 rows: 11 the same, 6 different. Each difference carries the report that answers it. The FEP cannula against the predicate's PTFE is answered by biocompatibility testing of the finished device (TR-0412) and kink and joint-strength testing (TR-0418), and the sentence for Section 8 is already drafted.

    TR-0418: “0 of 60 FEP cannulae occluded after 72 h bent at 90°; acceptance: 0 of 60.”

  3. 036–9 Oct

    A shelf-life claim with no report behind it

    Nadia Brennan and the Predicate comparer

    The draft claimed 36 months, like the predicate. On 6 Oct the comparer flagged that 36 months had no report behind it: packaging integrity and accelerated aging report TR-0433 supports 24. Nadia chose to claim 24 months rather than wait for real-time data, and on 9 Oct the drafter changed it in the description, the labels, Section 12 and the Summary. The gap is closed.

    TR-0433: “Accelerated aging to ASTM F1980-21 supports a labeled shelf life of 24 months.”

  4. 04Sections

    Every sentence cites the design file, a report or the label

    Section drafter

    Each of the 22 sections was drafted from the design history file, 9 test reports and the labeling; 17 of 22 are approved. Section 11, Sterility, states the method — ethylene oxide, SAL 10⁻⁶, at Lakeview Sterilization Services — and the residuals and endotoxin results, each with its citation. Its validation sentence cites ISO 11135-1:2007.

    The drafter never writes a claim without a source and never answers “N/A” without the reason.

  5. 05One click

    “Run preflight” — 31 checks, the way FDA screens

    Preflight checker · Standards matcher · Predicate comparer

    The agents read 22 sections and 46 attachments in 1.4 s, cross-checked the facts that repeat — 6 model numbers, the product code, shelf life and indications across 31 documents — in 2.2 s, tied the 6 differences to their reports and matched 14 standards to FDA's recognised list. Each line turns green as it is checked.

    “Matched 14 standards to FDA's recognised list — ISO 11135 cited at a withdrawn edition.”

  6. 0630 of 31

    Line 22 stays red, with the fix ready

    Preflight checker

    Sterilization cites a withdrawn edition of ISO 11135: ISO 11135-1:2007 appears in Section 11, para 2 and Section 4, row 7, while FDA recognises ISO 11135:2014 + Amd 1:2018. The wrong edition came from the 2019 eSTAR of the VLT-Flow 60, reused as a starting point. The ready light reads “Not ready yet”.

    The fix: “Swap the citation in both places. The validation report does not change — only what the submission says about it.”

  7. 07The evidence

    The lab already tested to the right edition

    Dr. Aisha Okonkwo · Test lab lead

    One click opens TR-0430, the EO sterilization validation from Lakeview Sterilization Services, dated 21 Jul 2026 and signed, at the passage on page 3. The work was done to the current edition; only the submission's citation was wrong. The report names the sections that cite it and points back to line 22.

    TR-0430, p. 3: “This validation was performed in accordance with ISO 11135:2014 + A1:2018 … using the overkill half-cycle approach.”

  8. 08Standards

    Every standard against the edition FDA recognises today

    Standards matcher

    Fourteen standards cited, checked against FDA's recognised list refreshed on 12 Oct 2026: one at a withdrawn edition, ISO 11135, and one in a transition period — ISO 10993-1:2018, accepted until 1 Jul 2029 now that FDA partially recognises the 2025 edition. The VLT-Flow 80 can go with 2018; the next biological evaluation should plan for 2025.

    The matcher never changes which standard a lab tested to — only the citation.

  9. 09One click

    Swapped in 2 places, and the light turns green

    Nadia Brennan · Regulatory affairs specialist, devices

    Nadia presses “Swap the citation in 2 places”. Section 11, para 2 is swapped and checked again; Section 4, row 7 is swapped and its declaration re-attached; line 22 passes. 31 of 31 checks passed, and 5 sections wait for Marcus Feld's approval and signature.

    On the record: “Applied by Nadia Brennan · 13 Oct.”

  10. 10Signed

    He approves, signs — and a person submits

    Marcus Feld · Director, Regulatory Affairs

    Nadia sends Sections 4, 8, 9, 11 and 22 to Marcus with a note: preflight green, line 22 fixed, target 20 Oct. Marcus approves the five sections and signs the truthful and accurate statement. The eSTAR PDF is ready to download with its 46 attachments, and Nadia submits it herself through the CDRH Portal.

    “Ready to submit · 31 of 31 checks · 22 sections approved · statement signed by Marcus Feld, 13 Oct 14:12. Nadia submits through the CDRH Portal.”

Who it’s for

Built for everyone who puts their name on a 510(k).

The same submission, seen by the four people who carry it — what their weeks looked like, and what they look like now.

NB
Nadia BrennanRegulatory affairs specialist · owns the VLT-Flow 80 eSTAR
Regulatory affairs specialist, devices
Before
Assembles 22 sections and 46 attachments by hand and reads it twice. “I don't fear FDA's questions. I fear the hold before they ask any.”
Now
Opens a preflight that shows exactly what is left — one red line with its evidence and a fix — applies it, sends for approval and submits.
MF
Marcus FeldDirector, Regulatory Affairs · approves every section and signs
Director, Regulatory Affairs
Before
Approves section after section without one view of what is still open. “Show me what's left, not what's done.”
Now
Gets the sections to approve with a green preflight and a note, approves by name, time and meaning and signs the truthful and accurate statement.
AO
Dr. Aisha OkonkwoTest lab lead · bench, sterility and biocompatibility testing
Test lab lead
Before
Finds her reports cited at the wrong edition. “My report says 2014. Why does the submission say 2007?”
Now
Her signed reports are the evidence each claim and difference points to, opened at the passage; she co-approves sterility, biocompatibility and performance.
TL
Tomasz LindqvistDesign engineer · owns the design history file
Design engineer
Before
Owns the design history file and the device description. “The answer is in the DHF. Which version did you take it from?”
Now
Every sentence in the eSTAR cites its source — the DHF, a test report or the labeling — and one model-number list is used in every section.
Built on the engine

5 agents. Each with one job, and hard limits.

Five specialist agents draft, compare, match and check every section; a regulatory director approves and signs.

Section drafter

Drafts each eSTAR section in plain regulatory English from the design history file, the test reports and the labeling, citing the DHF, a test report or the labeling by page for every factual sentence, and using one model-number list throughout.

  • Never writes a claim without a source
  • Never answers “N/A” without the reason
  • Never changes a test report
Predicate comparer

Builds the substantial equivalence table from the predicate's 510(k) Summary and the design history file — indications, users, technology, materials, performance, sterility, shelf life — and ties each difference to the report that answers it, or opens a gap.

  • Never chooses the predicate — a person does
  • A difference is answered only by a report
Standards matcher

Compares every standard cited — edition and amendments — with FDA's recognised consensus standards, full or partial, refreshed weekly, and flags withdrawn editions and transition dates.

  • Never changes which standard a lab tested to — only the citation
  • Proposes; a person applies
Preflight checker

Runs 31 checks modelled on FDA's technical screening: facts that repeat across sections, attachments that answer their questions, no unexplained “N/A”, fee and forms, standard editions and predicate differences — each with its evidence, and a fix when one exists.

  • Never marks a check passed without the evidence
  • Never submits
Cover letter writer

Drafts the cover letter and the 510(k) Summary from the approved sections.

  • Never signs
  • Never sends to FDA
Regulatory affairs director

Approves every section and signs. The agents propose; a named person decides.

Ask in plain words

Ask about any section, check or standard

Ask about any section, check, standard or difference from the predicate — or say what to change. Every answer points to its source.

Why is line 22 red?

Sections 11 and 4 cite ISO 11135-1:2007 for the sterilization validation. That edition is withdrawn; FDA recognises ISO 11135:2014 + Amd 1:2018. The lab did the work to the right edition — TR-0430 says so on page 3 — so only the citation is wrong. It came from the 2019 eSTAR of the VLT-Flow 60. The fix is ready on line 22.

Show only the differences from the predicate

Six rows differ from the Halvern SoftPort 90 (K231592): cannula material, tubing length, inserter, adhesive, hub material and shelf life. Five are answered by a test report — for example the FEP cannula by TR-0418 — and shelf life was closed on 9 Oct by claiming 24 months, which TR-0433 supports. None is open.

Which standards must change edition before 2029?

Two. ISO 11135 now: the submission cites the withdrawn 2007 edition. And ISO 10993-1: FDA partially recognised the 2025 edition on 25 May 2026 and accepts declarations to the 2018 edition only until 1 Jul 2029. VLT-Flow 80 can go with 2018; the next biological evaluation should plan for 2025.

Add a check: IFU revision matches the labeling section

Added as check 32: the IFU revision attached in Section 9 must be the one named in the device description and the 510(k) Summary. On today's draft it passes — IFU rev C everywhere. It runs on every submission from now on and is on the audit trail.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The preflightThe submission strip — device, predicate, product code, target date — and 31 technical screening checks in eight groups, with the Ready to submit light at the end.
Predicate side by side17 rows against the Halvern SoftPort 90: 11 the same, 6 different, each difference with the report that answers it and the sentence drafted for Section 8.
A gap closedShelf life: the 36-month claim had no report behind it; TR-0433 supports 24 months, and the claim changed in every place it appears.
eSTAR sections22 sections drafted from the design history file, 9 test reports and the labeling, with their status and a citation on every claim.
Agents at workSections and attachments read, repeated facts cross-checked, differences tied to reports and standards matched — each step timed.
The line left to fixWhat was found and where, the evidence from the validation report, where the wrong edition came from and the one-click fix.
The report at its passageTR-0430 opened at page 3, the sections that cite it and whether the submission matches it.
Standards cited14 standards against the edition FDA recognises today: where each is used, one withdrawn edition and one transition to 2029.
Every check green31 of 31 passed, the fix recorded in both places with who applied it, and the sections sent for approval.
Approved and signedReady to submit: sections approved, the truthful and accurate statement signed, the eSTAR ready to download — and a person submits.
Submission timelineFrom design freeze to FDA's Day 90 decision goal, what is left before it goes, and what a month late, an Additional Information request or a technical screening hold would cost.
Every submissionEach 510(k) built here, how technical screening went, whether FDA asked for additional information and the FDA days to a decision.
Your rulesThe preflight checks, approvers per section, who signs and submits, the recognised-standards refresh and the drafting rules.
Governance

Built for FDA's screening: cited, approved, signed by a person.

Every claim cites its sourceEvery sentence in a section cites the design history file, a test report or the labeling, and a citation opens the page and the passage. A sentence without a source is held back.
No check passes without evidenceEach of the 31 preflight lines shows what was checked, what was found and where — the section, the report, the standard — and a failed line comes with its fix.
Approved by name, time and meaningThe regulatory affairs director approves every section before it goes in the eSTAR, and the test lab lead co-approves sterility, biocompatibility and performance testing.
A person signs and a person submitsThe truthful and accurate statement is signed by a person, and a person submits through the CDRH Portal. Nothing goes to FDA from an agent.
Test reports stay as the lab signed themAgents never sign, never submit and never change a test report. A fix changes what the submission says about a report, never the report itself.
Every draft, check and fix on the audit trailEach draft, edit, preflight run, fix and approval is recorded with who, what and when — “applied by Nadia Brennan · 13 Oct”, “signed by Marcus Feld, 13 Oct 14:12”.
Configuration

Your screening checks and approvers, not ours

What the preflight checks, who approves and how standards are watched are settings for every submission.

SettingDefaultChoose from
Preflight checks31 onEach check on or off · add your own check in plain words
Every section approved byMarcus Feld · RA directorAny named approver, by name, time and meaning
Sterility, biocompatibility, performance co-approved byDr. Aisha Okonkwo · test lab leadA named co-approver, or not required
Truthful and accurate statementSigned by Marcus FeldSigned by a person; agents cannot sign
Who submits to FDANadia BrennanA person, through the CDRH Portal
Refresh FDA's recognised standardsWeekly · last 12 Oct 2026Daily, weekly or monthly
Warn before a transition ends24 months6 to 48 months, in steps of 6
Cite every claim · one model-number listOn · VF-0660 to VF-0910On or off
Connections

Works with the records a 510(k) is built from

Design history filedevice description, models and the revision each answer came from
Test reportsbench, sterility, biocompatibility, packaging and human factors reports
Labelinginstructions for use, pouch and carton labels, Form FDA 3881
Predicate 510(k) Summariesthe predicate's indications, technology, materials and performance
FDA recognised consensus standardseditions, partial recognition and transition dates, refreshed weekly
The eSTAR templatesections filled in the eSTAR PDF with every attachment embedded
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0holds
at FDA's technical screening on the last 9 submissions
9 of 9 cleared first time
2 holds in 6 before
estimated
$1.2Ma month
of sales kept on plan, not lost to a hold of up to 180 days
On holdup to $7.2M late
Cleared first timeon plan
target
3weeks
to a ready eSTAR, down from 10
By hand10 weeks
With agents3 weeks

“demo” = seen in the working solution, on its sample submission · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (FDA eSTAR program and 510(k) electronic submission guidance — technical screening within 15 days, hold up to 180 days; FDA MDUFA V performance report — Additional Information requests on the first cycle for 63–68% of 510(k)s, FY2018–FY2022). People, companies, devices, K numbers and submission numbers named on this page are fictional — characters and sample data in the working solution.

Questions

What device regulatory teams ask us.

What is a 510(k) eSTAR?

eSTAR is FDA's electronic submission template, and every 510(k) must now be sent as one unless it is exempt. It runs to some 20 sections, from device description and the predicate comparison to sterility, biocompatibility, labeling and performance testing. 510(k) eSTAR Submission drafts those sections from your design history file, test reports and labeling and checks the result before it goes.

How does the preflight relate to FDA's technical screening?

FDA screens each eSTAR within 15 days, and a failed screen puts it on hold for up to 180 days until a complete replacement arrives. The preflight runs 31 checks modelled on that screening — answers that contradict each other, attachments that don't answer their question, “N/A” where a question applies, standards at an edition FDA no longer recognises, and every predicate difference tied to a test report.

Does it replace the Refuse to Accept checklist?

eSTAR submissions are not reviewed under the Refuse to Accept checklist; FDA screens them technically instead. The preflight is built for that technical screening, and you can add your own checks in plain words.

How does it build the substantial equivalence comparison?

The predicate comparer reads the predicate's 510(k) Summary and your design history file and lays the device beside it row by row. Each difference is tied to the test report that answers it, or opened as a gap. A person chooses the predicate; the comparer never does.

Does it check that our standards are at the edition FDA recognises?

Yes. The standards matcher compares every citation — edition and amendments — with FDA's recognised consensus standards, refreshed weekly, and flags withdrawn editions and transitions such as ISO 10993-1:2018, accepted until 1 Jul 2029. It changes only the citation, never what the lab tested to, and a person applies the fix.

Do people stay in control of the submission?

Yes. The agents draft, compare and check. The regulatory affairs director approves every section by name, time and meaning, the test lab lead co-approves test sections, a person signs the truthful and accurate statement and a person submits through the CDRH Portal. Agents never sign, submit or change a test report.

Can we set our own checks and approvers?

Yes. Each of the 31 preflight checks can be switched on or off, new checks are added in plain words, and the approver for every section, the co-approver for test sections, who signs, who submits, the standards refresh and the transition warning are all settings.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your SOPs, a design history file, test reports and a past eSTAR — and it goes live once every quality gate has passed. We will walk you through it on one of your own devices first.

See it on
your next 510(k).

We'll run 510(k) eSTAR Submission on the design file, test reports and labeling of one of your own devices.