The work you’re leaving doesn’t stop when you do. A regulatory handoff is the last artifact you produce in a role, and it gets read by someone who wasn’t in any of the meetings that made your undocumented decisions make sense.
What actually needs to be in it
Start with open items, because they’re what someone will need first: for every active submission, what’s outstanding, the next concrete action, who owns it now, and any deadline attached to it — an FDA response due date, a committed internal review date, a deficiency clock. Then add the reasoning behind decisions that aren’t obvious from the file alone: why a particular predicate was chosen and another rejected, why a position was taken in a pre-submission meeting and what the agency actually said in response, why an internal disagreement got resolved the way it did. If you’ve been keeping a running decision log, this section is mostly assembly rather than recall, which is the strongest argument for keeping one long before you need to leave. Round it out with the practical scaffolding a new person can’t reconstruct on their own: where files actually live, which submission tracking numbers map to which product, and who the working contacts are on both sides — the reviewer, the cross-functional counterparts, anyone external who’s used to hearing from you specifically.
Write it for someone who wasn’t in the room
The habit that ruins most handoffs is writing in shorthand that only makes sense to the person who already knows the context — “still waiting on the usual answer from CDRH” means nothing to someone who wasn’t there for the calls that made “the usual answer” a shared reference. Every entry should stand on its own: what the item is, what’s been done, what’s left, and why it matters, written as though the reader has the file open but not your memory. A useful test is to hand a draft to a colleague who isn’t involved in the work and watch where they get stuck — the questions they ask are exactly the gaps the next person will hit, except they’ll hit them without you in the room to answer.
Where this goes wrong
Writing a status report instead of a handoff
A status update summarizes progress for someone who’s already tracking the work. A handoff has to work for someone starting from zero, which is a different document with a different job.
Noting that something’s closed without saying why
An item marked resolved with no reasoning attached invites the next person to either reopen a question that was already settled, or miss the context that made the resolution the right call.
Treating it as a last-week task
A handoff assembled under deadline pressure in your final days is thinner than one built continuously, a few minutes at a time, alongside the decisions themselves.
None of this is really about the document. It’s about the fact that how you leave a role is remembered longer, in a field this small, than most of what came before it — and a handoff someone can actually use is the cheapest, most concrete way to leave well.
Sources & further reading
- Regulatory Academy — The case for keeping a regulatory decision log regulatoryacademy.com
- Regulatory Academy — How to change companies in regulatory affairs regulatoryacademy.com
- Regulatory Academy — How to read your FDA pre-submission meeting minutes 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.
