Promotional submissions go through the same FDA Electronic Submissions Gateway as everything else — but the account setup, the test submission, and OPDP’s own structural review are three separate lead times that teams routinely discover in the wrong order.
The 2253 deadline is set by a commercial action, not a regulatory one — and it is the only major submission obligation in the portfolio whose clock somebody outside regulatory can start without telling you.
A grouped submission lets one promotional piece cover several applications at once. It is the biggest efficiency available in ad-promo publishing, and the easiest to get subtly wrong.
OPDP publishes the errors it sees most often in promotional eCTD submissions. Most are structural, most are silent, and several fail in ways that are not obvious from the rejection notice.
Where each piece of a Form FDA 2253 submission belongs in the eCTD — the form, the current labeling, and the promotional material itself — and why the placement is not obvious from the guidance alone.
One design rule makes AI defensible in regulated environments: AI output is always a draft until a human approves it into the record. Here is how that boundary works in practice.
A submissions grid that took 12 seconds to load was issuing one database query per row. The fix took the page to 0.7 seconds — and taught us why performance is an adoption and compliance issue.
Can regulated software fix itself? Yes — within a strict boundary. The rule we use to decide what heals automatically, what escalates to humans, and why every heal writes an audit record.
How do you regression-test software whose ultimate validator is a health authority? Harvest real published sequences, replay them, and diff the results. Inside our characterization harness.
We automated 50+ operational qualification scripts and learned that the hard part isn’t automation — it’s honesty. How to build OQ evidence a QA auditor can actually trust.
