Managing competing submission deadlines

Every regulatory calendar eventually produces a week where two products need you at once — an additional information response due the same day as a label supplement, a pre-submission package due the same week as a quality finding that needs a written response. Advice on estimating any single submission’s timeline doesn’t tell you what to do when two of them collide, and the instinct to treat every deadline as equally non-negotiable is usually what makes the collision worse.

Sort by consequence, not by order

When two deadlines land in the same week, the instinct is to work on whichever came first or whichever stakeholder is checking in most often. Neither question is the one that matters. The question is what actually happens if each deadline slips. A fixed regulatory clock with no real extension option — an additional information response window is the clearest example — carries a different consequence than an internally set target date that a cross-functional team picked because it sounded reasonable six months ago. Sorting the two kinds apart, honestly and early, is the entire first step. Everything after that is just protecting the one that can’t move.

Renegotiating one deadline on purpose

Sometimes both deadlines really are fixed, and something still has to give. The professional move is to surface that early and name which one should move and why, rather than letting the softer deadline die quietly while attention drifts toward whichever one feels more urgent that day, or splitting effort evenly across both and risking that neither gets done well. A deadline moved on purpose, with two weeks’ notice and a clear reason, reads as judgment. The same deadline missed without warning reads as a surprise, and surprises are what actually cost credibility — not the schedule change itself.

Building slack before you need it

The best defense against a collision is built long before the week it happens, in how a timeline gets estimated in the first place. Estimating a regulatory submission timeline well means building in slack deliberately, not as padding to pad around a lazy estimate, but as the realistic acknowledgment that another deadline will eventually land on top of this one. A submission finished two weeks early absorbs whatever comes next without anyone noticing there was a conflict at all. A submission finished exactly on time has no slack to give, and the first competing deadline that shows up turns into a crisis instead of a scheduling decision.

Running a submission readiness review, covered in how to run a submission readiness review, is one of the few points in a timeline where a looming collision is still visible early enough to do something about it other than simply absorb it.