Before the first participant is dosed, an emerging sponsor needs a working safety system: a safety database, a safety management plan, a medical reviewer available at all hours, clear reporting timelines, and agreed roles between the sponsor, the CRO, and any safety vendor. The first serious adverse event can arrive in the first week of dosing, and the regulatory clocks start the moment the sponsor or its delegate learns of it. A safety process that exists only on paper becomes visible very quickly.
What must be ready before the first participant is dosed?
At a minimum, sponsors should have:
A validated safety database and a process for case intake, coding, and medical review
A safety management plan that defines roles, timelines, and communication paths
A medical monitor or safety physician reachable around the clock for urgent questions
Current reference safety information, usually in the investigator brochure
Agreed procedures for emergency unblinding, if the study is blinded
A plan for reconciling serious adverse events between the safety database and the clinical database
Submission pathways to FDA and, where relevant, to other regulators and ethics committees
What are the reporting clocks?
Under FDA's IND safety reporting rule at 21 CFR 312.32, a sponsor must report a suspected adverse reaction that is both serious and unexpected within 15 calendar days of determining that it qualifies, and an unexpected fatal or life-threatening suspected adverse reaction within 7 calendar days. Investigators, in turn, must report serious adverse events to the sponsor immediately. Many other regulators, including those in the European Union, apply similar 7-day and 15-day timelines for suspected unexpected serious adverse reactions. Day zero typically begins when anyone acting for the sponsor first receives the minimum information for a valid case, so delays inside the sponsor or CRO consume the regulatory window.
Who should do the work?
Sponsors usually choose among three models: the full-service CRO manages safety, a specialist pharmacovigilance vendor manages it, or a small internal team does the work with outsourced support. Each can work well. Whatever the model, the sponsor remains accountable for safety reporting, and any transfer of obligations to a CRO must be documented in writing. The sponsor's own physician should review significant cases and should be involved in decisions about causality, expectedness, and changes to the safety profile.
Why does the reference safety information matter so much?
Expectedness is judged against the reference safety information, which is typically a section of the investigator brochure. If that section is vague or out of date, the safety team cannot decide consistently whether an event is expected, and reporting decisions become inconsistent across cases. Reviewing the reference safety information before the first dose, and agreeing how it will be updated, is one of the simplest ways to make reporting decisions defensible.
How do safety data and clinical data stay consistent?
Through planned reconciliation. Serious adverse events are recorded in both the safety database and the clinical database, and the two must match on key fields such as onset date, outcome, and seriousness. Reconciling monthly during the study, and fully before database lock, avoids the late scramble that can delay a topline readout.
How do you know the system works?
Run a mock case before first patient. Have a site send a simulated serious adverse event at an inconvenient hour and follow it from the investigator's report through intake, medical review, assessment, and a mock regulatory submission. In my experience, a two-hour drill like this reveals at least one gap, often a contact number that routes nowhere or a handoff no one owns, and it is far better to find it in rehearsal.
Keep reading: Medical Monitoring: What to Keep and What to Outsource
