Ask any safety team what the expedited reporting deadline is and you will get the right answer. Ask why a submission was late and the reason is almost never that nobody knew the number. It is that Day 0 was taken from the wrong date, or a follow-up clock was treated as a continuation of the original, or a case had been sitting with an affiliate for four days before it reached the safety database.
This guide is therefore mostly about mechanics rather than numbers. The numbers are easy to look up and they change; the mechanics are where the compliance risk lives.
Read this before using any table below
Regulatory requirements change, and they change independently by jurisdiction. Nothing here is regulatory advice or a substitute for the current legislation and guidance applicable to you. Always confirm the specific obligation for your product, market, case type and role with the authority's current requirements and your own qualified PV personnel. Use this guide to understand how the clock behaves, not as a compliance reference.
Day 0 is generally the date on which the first person in your organisation received the minimum information constituting a valid case. Three words in that sentence do most of the damage in practice.
Not the safety department
Receipt by a sales representative, a medical information line, an affiliate, a distributor, or in many arrangements a partner under a safety data exchange agreement, generally starts the clock — not the date it reached the PV team.
Not opened, triaged or entered
The date the information arrived, not the date somebody looked at it. A report sitting unread in a monitored mailbox is consuming clock.
The four E2D criteria
Where an initial report is not a valid case, Day 0 is generally the date the missing criterion was received — so an invalid report becoming valid starts the clock then, not retrospectively.
The affiliate problem
In multi-country organisations the most common late-submission root cause is a case received by a local affiliate or distributor days before it reaches central PV. The clock started at the affiliate. Fix this with defined intake routes, contractual exchange timelines that are tighter than the regulatory clock, and reconciliation — not with reminders.
Expedited reporting is driven by a combination of attributes, not by seriousness alone. The combination differs by market and by whether the case is from a clinical trial or post-marketing use.
| Attribute | Why it matters |
|---|---|
| Seriousness | The primary gate. Death and life-threatening outcomes typically attract the shortest clocks |
| Expectedness / listedness | Whether the event is listed in the reference safety information in force. Unlisted plus serious is the classic expedited combination |
| Case source | Clinical trial versus post-marketing spontaneous — different frameworks, different obligations, and for trials the SUSAR concept applies |
| Market and authorisation status | Where the product is authorised, and where the case originated, determine which authorities are interested |
| Causality | For trial cases in particular, a suspected causal relationship is part of the SUSAR definition |
| Your role | MAH, sponsor, distributor or service provider — and what your safety data exchange agreement delegates |
Because this is a combinatorial problem rather than a lookup, it should be encoded in a configurable rules engine rather than held as knowledge. See the reporting rules engine for how attributes resolve into a destination, a format and a deadline.
The table below is an orientation to the shape of the obligations in each jurisdiction — the frameworks, the submission mechanisms, and the characteristic clocks. It is deliberately light on precise day counts, because those are exactly the details that change and that you must verify against current requirements.
| Jurisdiction | Framework shape | Electronic submission route |
|---|---|---|
| US (FDA) | Post-marketing expedited reporting for serious unexpected cases, plus periodic reporting; distinct requirements for investigational products | FAERS via the electronic submission gateway; MedWatch 3500A as the corresponding form |
| EU (EMA / national authorities) | GVP-based framework covering ICSR reporting and periodic benefit-risk reporting, with the shortest clocks for fatal and life-threatening cases | EudraVigilance, using E2B(R3) |
| UK (MHRA) | A framework broadly comparable in shape to the EU one following divergence, with its own submission arrangements | MHRA submission arrangements, using E2B |
| India | Domestic adverse event reporting and periodic reporting expectations, alongside the ADR monitoring programme, plus separate requirements for clinical trials | Domestic arrangements — confirm current mechanism and format requirements directly |
About PVgenix submission coverage specifically
This guide discusses regulatory obligations generally, which is not the same as a statement about our product. PVgenix documents submission support for FDA (FAERS via the ESG gateway), EMA (EudraVigilance) and MHRA, with E2B(R2)/E2B(R3) generation, CIOMS I and MedWatch 3500A form outputs, and a built-in AS2 gateway. Other destinations — including Indian domestic submission routes — are assessed and scoped per client agreement. If a specific authority is critical to you, ask us directly rather than inferring coverage from this table.
Expedited clocks are commonly counted in calendar days, which has a practical consequence teams routinely under-plan for: a case received on a Thursday before a long weekend has lost several days of working capacity by the time anyone is back.
- Plan internal targets well inside the regulatory deadline — a common approach is an internal target at roughly two-thirds of the external clock
- Set contractual exchange timelines with partners and affiliates tighter than the regulatory clock, so the submitting party inherits usable time rather than a deadline that has already passed
- Make sure alerting is based on time remaining rather than time elapsed, so a case received before a holiday escalates earlier
- Confirm whether any specific obligation is counted in business days rather than calendar days — do not assume either way
- Account for time zones where receipt and submission sit in different regions
Where follow-up brings significant new information — a non-serious case becoming serious, a change in outcome, a change in causality or expectedness, a new event — a fresh expedited obligation generally arises, counted from receipt of that information.
The mistake this causes
Teams reason that because the initial report was submitted on time, the follow-up is administrative. It is not. Significant new information typically starts a new clock, and the significance determination is a regulated judgement that should be recorded. This is one of the most frequently observed causes of late follow-up submissions. See ICSR follow-up and case versioning.
These are separate frameworks with separate obligations, and teams carrying both need to keep them distinct in configuration as well as in SOPs.
| Clinical trial cases | Post-marketing cases | |
|---|---|---|
| Core concept | SUSAR — serious, unexpected, suspected causal relationship | Serious and unexpected/unlisted cases, plus other reportable categories |
| Reference document | The investigator's brochure or equivalent reference safety information for the study | The authorised product information (CCDS/CCSI, SmPC, USPI) |
| Recipients | Authorities plus, typically, ethics committees and investigators | Authorities, and partners per agreement |
| Additional complexity | Blinding — assessment may require controlled unblinding | Multi-market obligations for the same case |
| Configuration implication | Rules per protocol, since obligations vary by study | Rules per product and market |
The practical goal is that no individual has to remember a deadline. That requires the clock to be a property of the case rather than an entry in someone's calendar.
| Capability | Why it matters |
|---|---|
| Automatic Day 0 determination per reporter region | Removes the most common source of error, and makes the basis auditable |
| Per-obligation deadlines, not one deadline per case | One case can create several obligations on different clocks to different authorities |
| Escalation on time remaining | Alerts before breach, weighted for weekends and holidays, rather than a report of what is already late |
| Re-derivation on new case versions | A follow-up with significant information recalculates obligations rather than inheriting the old ones |
| Clock continues through rejection | A rejected submission is not a submitted one; the deadline has not paused |
| Derived on-time submission metrics | Computed from submission records rather than compiled by hand, so the number is evidence |
PVgenix determines Day 0 automatically per reporter region, calculates expedited timelines, tracks each obligation's due date separately with late-submission alerts, re-resolves obligations on new case versions, and computes on-time submission metrics from the submission records themselves. See regulatory submission.
- Day 0 taken from case creation rather than first receipt anywhere in the organisation
- A case sitting with an affiliate, distributor or partner beyond the contractual exchange timeline
- An unmonitored intake route — a mailbox, form or phone line with no owner
- Significant follow-up information treated as administrative, so no new report was submitted
- A rejected submission recorded as submitted, with the clock treated as stopped
- An unacknowledged transmission nobody noticed, so the submission was never actually completed
- Seriousness upgraded late at medical review, by which point most of the clock had been spent on a routine track
- Reliance on a spreadsheet of deadlines maintained by one person
The short version
The deadline is the easy part. Get Day 0 right — from first receipt anywhere in your organisation, not from case creation. Treat significant follow-up as a fresh clock. Set partner and affiliate exchange timelines tighter than the regulatory clock. Alert on time remaining rather than time elapsed. And keep the clock as a property of the case, derived by rules, so compliance does not depend on anyone remembering.
Related: the reporting rules engine, ICSR triage and duplicate detection for how quickly the clock starts being consumed, and E2B(R3) implementation for the submission mechanics themselves.
Frequently asked questions
Common questions
Day 0 is generally the date on which the first person within your organisation received the minimum information constituting a valid case — which includes sales representatives, medical information lines, affiliates, distributors, and in many arrangements partners under a safety data exchange agreement. It is not the date the case reached the safety department, was triaged, or was entered into the database. Confirm the precise definition applicable to you against current requirements and with your qualified PV personnel.
Rarely because the deadline was unknown. The recurring causes are: Day 0 taken from case creation rather than first receipt anywhere in the organisation; a case sitting with an affiliate or partner beyond the contractual exchange timeline; an unmonitored intake route; significant follow-up information treated as administrative so no new report was submitted; a rejected submission recorded as submitted; an unacknowledged transmission nobody noticed; and seriousness being upgraded late at medical review after most of the clock was spent on a routine track.
Where the new information is significant — a non-serious case becoming serious, a change in outcome such as death, a change in causality or expectedness, or a new adverse event — a fresh expedited obligation generally arises, counted from receipt of that information rather than continuing the original clock. Assuming otherwise because the initial report was submitted on time is a frequently observed cause of late follow-up submissions. The significance determination is a regulated judgement and should be recorded.
Expedited clocks are commonly counted in calendar days, which means weekends and public holidays consume the deadline without providing working capacity — a case received before a long weekend can lose several usable days. Do not assume either basis for a specific obligation; confirm it against the applicable requirement. Operationally, set internal targets well inside the external deadline and alert on time remaining rather than time elapsed.
They are separate frameworks. Clinical trial reporting centres on the SUSAR concept — serious, unexpected, with a suspected causal relationship — assessed against the investigator's brochure or equivalent study reference safety information, with recipients typically including ethics committees and investigators as well as authorities, and blinding adding a controlled unblinding step. Post-marketing reporting is assessed against the authorised product information and often creates multi-market obligations for one case. Configuration differs accordingly: rules per protocol for trials, rules per product and market for post-marketing.
No. A rejected submission is not a submitted one, and the deadline continues to run while the rejection is investigated and the file corrected and retransmitted. This is why schema and business-rule validation should run in-house before transmission, and why an unacknowledged transmission is the most dangerous state — nothing failed visibly, but nothing completed either.