Owning your first submission end to end

There is a specific moment in a regulatory career when the work changes shape. Up to that point you have supported someone else’s submission — drafted a section, chased down a reference, answered a reviewer’s question they handed you. Then, for the first time, a submission has your name on it as the person who owns it end to end. Nothing about the regulation changed. What changed is that every open question now has to land somewhere, and that somewhere is you.

The job becomes coordination, not production

Most of the actual labor in owning a submission is pulling inputs from people who don’t report to you and making sure what they hand over doesn’t quietly conflict with what someone else handed over. An indications-for-use statement that doesn’t match the testing scope, a labeling claim the clinical data doesn’t fully support — these are the errors a first-time owner catches late, because catching them early means reading the whole file as one argument rather than a set of sections. The same discipline behind keeping a working file of predicate devices current scales up to the whole submission once you’re the one who owns it. And the review that follows runs on a clock laid out in detail in the 510(k) review, from submission to the SE letter — but owning the file means you’re the one translating that clock into deadlines for everyone else who touches it.

What to hand off, and how

Ownership that only exists in your head is a liability the moment you’re out sick during an Additional Information deadline, or the project moves to someone else because you changed teams. The same record that makes a submission handoff someone else can use is the record that makes you less of a single point of failure while you’re still the owner — open items, who owes what, and the reasoning behind decisions that aren’t obvious from the file alone. Writing it down as you go costs less than reconstructing it under deadline pressure later, and it’s the difference between ownership that transfers cleanly and ownership that has to be re-earned by whoever inherits the file.

The first submission you own end to end rarely tests what you know about the pathway. It tests whether you can hold a file that several other people are contributing to without losing track of what still has to agree with what. That’s the job, and it’s a different one than the work that came before it.