A product lead pushes back on a launch date, and the honest answer is that FDA's review timeline isn’t up to regulatory affairs. That's true, and it's also not useful on its own — it tells the room what you don't control without saying what you do. The better move is to break the timeline into its actual pieces, name which one is the real constraint, and negotiate that piece specifically instead of the date as a whole.
Name which clock you're actually talking about
A device launch timeline usually runs on three different clocks, and only one of them is yours. There's the internal clock — when the file is actually ready to submit, which is a function of your own testing, documentation, and review cycles, and which is genuinely within the company's control. There's FDA's review clock, which for a 510(k) is governed by a MDUFA performance goal that FDA and industry renegotiate every few years — a target the agency works toward, not a statutory deadline, and the specific day count shifts between MDUFA cycles, so check the current agreement rather than a number from an old conversation. And there's the remediation clock: how long it takes to close a deficiency if FDA sends an additional information request, which restarts part of the review and is driven by how fast your team can produce a real answer, not a placeholder one.
When someone pushes on a date, the reflex is to say the whole thing isn't up to you. It's more accurate, and more useful, to say which piece isn't: “the review clock isn't ours to move, but the submission date is, and that's the lever we actually have.” That sentence gives the room something to plan around instead of a wall.
Give the room a choice, not a refusal
Instead of a flat no, put two honest paths on the table with their real trade-offs: submit a narrower set of indications sooner and expand the label later once more testing is in, or hold for the fuller package and accept the later date. Both are legitimate business decisions — but only if the option that looks faster is actually built on a file that's ready, not a shortcut through the parts of a submission a defensible rationale depends on. A trade-off that trades away the substance of the file isn't a faster path, it's a rejected one with extra steps.
Where this goes wrong
Saying no without naming the actual constraint
A flat refusal reads as obstruction. Naming which specific clock is fixed — and which is not — reads as someone who understands the schedule well enough to be trusted with it.
Promising a date that depends on FDA's review clock
The submission date is yours to commit to. The clearance date is a goal FDA works toward, not a company deliverable — promising it as one sets up a broken commitment that isn't actually within your control to keep.
Leaving the trade-off undocumented
Months later, the only record of a schedule conversation is often someone's memory that “regulatory said it would work.” A dated note of what was actually agreed and what it assumed is worth writing down before you need it.
Holding the line on a timeline is not the same skill as holding the line on a technical position in a live meeting — that's about defending a regulatory read under pressure; this is about the calendar math underneath it. Both end the same way, though: in a decision log, dated, so the trade-off you actually offered is the one anyone can check later.
Sources & further reading
- FDA — Premarket Notification 510(k): review process and MDUFA performance goals fda.gov
- FDA Guidance — FDA and Industry Actions on Premarket Notification (510(k)) Submissions: Effect on the FDA Review Clock fda.gov
- Regulatory Academy — Being the only regulatory voice in the room regulatoryacademy.com
- Regulatory Academy — How to run a submission readiness review regulatoryacademy.com
- Regulatory Academy — The case for keeping a regulatory decision log regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
