Day Zero in Pharmacovigilance: When Does the Reporting Clock Start?

Day Zero is the date from which an individual case safety report reporting timeline is counted. It sounds like a simple timestamp. Operationally, it is one of the most consequential dates in case processing because it determines whether a report was submitted on time.

The central rule is not “when did Pharmacovigilance receive the case?” and not “when was the case entered into the safety database?”. Under ICH E2D(R1), the reporting clock generally starts when any personnel of the marketing authorisation holder, including a third party acting on its behalf, obtains sufficient information to determine that the case meets the minimum criteria for reporting, unless regional or local requirements specify otherwise.

In the EU, current GVP Module VI expresses the same principle in operational terms: the clock starts when information containing the minimum criteria has been brought to the attention of the competent authority or any personnel of the MAH, including medical representatives and contractors. The date is Day Zero even when it falls on a weekend or public holiday, because reporting periods are counted in calendar days.

The difficult part is determining what “awareness” means for different sources. Literature searches, digital platforms, incomplete reports, vendors, business partners, follow-up information and reconciliation can each create different fact patterns. A robust pharmacovigilance system therefore needs a source-specific Day Zero framework rather than a single database rule.

Purpose and Scope

This article addresses post-authorisation ICSR Day Zero. It focuses on the reporting clock for suspected adverse reactions and other reportable ICSRs under the current ICH E2D(R1) and EU pharmacovigilance framework.

It does not address clinical-trial SUSAR reporting timelines, periodic-report data lock points or other regulatory clocks except where comparison is useful. Those processes have their own governing frameworks.

The article also distinguishes three related but different concepts:

1. source receipt — when information first reaches a person or system;
2. regulatory awareness — when sufficient information exists to meet the applicable reporting criteria;
3. database processing — when the case is entered, triaged, medically reviewed or submitted.

Those dates may be the same. They may also differ by several days.

The purpose of Day Zero governance is to ensure that internal processing never moves the regulatory clock forward artificially.

Regulatory Framework

The current framework has two layers that should be read together.

ICH E2D(R1)

ICH E2D(R1), implemented in the EU from 18 March 2026, provides the current harmonised post-approval framework. Its general rule is that the regulatory clock starts when any MAH personnel—including service providers and contractual partners acting on behalf of the MAH—obtain sufficient information to determine that the minimum criteria for reporting are met.

For expedited ICSRs, E2D(R1) states that submission should occur as soon as possible and no later than 15 calendar days after Day Zero, while recognising that regional or local requirements determine which cases are expedited and what other timelines apply.

E2D(R1) also introduces explicit source-specific rules for:

• scientific literature;
• digital platforms under MAH responsibility;
• planned review of external digital platforms;
• initially incomplete cases;
• medically relevant follow-up;
• and amendments made without new source information.

EU GVP Module VI

GVP Module VI remains the principal EU operational guidance for ICSR collection, management and submission while EMA integrates E2D(R1) into the module.

Current GVP Module VI states that:

• the clock starts when the minimum criteria are brought to the attention of any MAH personnel, including medical representatives and contractors;
• the date is Day Zero irrespective of weekends or public holidays;
• serious valid ICSRs are submitted within the applicable 15-day timeframe;
• EU non-serious valid ICSRs are subject to the applicable 90-day timeframe;
• and contractual arrangements must allow the MAH to meet these timelines.

EMA's E2D(R1) implementation strategy states that, where E2D(R1) refers to regional requirements, the current GVP Module VI should continue to be followed as applicable.

The practical model is therefore:

ICH E2D(R1) Day Zero principle → EU GVP source-specific and reporting requirements → company procedure and agreements → case-level date determination → submission deadline

The Minimum Criteria Come Before the Clock

The ordinary Day Zero principle depends on the existence of a report that meets the minimum criteria for ICSR reporting.

For a conventional adverse-event or adverse-reaction ICSR, these are:

• an identifiable patient;
• an identifiable reporter;
• at least one suspect or interacting medicinal product;
• and at least one adverse event/adverse reaction or other reportable observation, as applicable.

Regional rules may create specific exceptions for some observations, but the basic principle remains that an incomplete contact is not automatically a valid ICSR merely because it mentions a medicine and a possible problem.

This matters because a pharmacovigilance process often sees two dates:

Initial contact → minimum information missing → follow-up obtains missing criterion → case becomes reportable → Day Zero.

If a patient writes, “I had a terrible reaction to Product X” but provides no information that allows a real patient or reporter to be established, the contact may require follow-up but may not yet meet the minimum criteria.

If follow-up on 5 October provides sufficient information to establish the missing criterion, Day Zero is generally 5 October under the E2D(R1) framework, subject to the applicable regional rules.

The original contact must still be retained. The point is not to erase the earlier date; it is to distinguish first contact from first regulatory awareness of a reportable case.

Day Zero Is Not the Database Entry Date

A common operational error is to define Day Zero as the date on which the case was created in the safety database.

That approach reverses the regulatory logic.

The database should record the awareness date; it does not create it.

Consider:

Monday — Medical Information receives valid report
Tuesday — report forwarded to affiliate PV
Wednesday — case sent to global safety
Thursday — safety database case created

If the Medical Information function is part of the MAH and received enough information on Monday to meet the reporting criteria, Thursday is not the appropriate Day Zero merely because that is when data entry began.

The same principle applies when the first recipient is:

• a medical representative;
• a call centre;
• a product-quality function;
• a patient-support vendor;
• a literature vendor;
• a digital-platform moderator;
• or another contractor acting on behalf of the MAH.

A pharmacovigilance system therefore needs to control first awareness across the organisation, not only first receipt by the central PV department.

Day Zero Versus Case Intake Date

Many safety databases contain several dates, for example:

• initial receipt date;
• latest information date;
• date entered;
• date medically reviewed;
• transmission date.

These should not be treated as interchangeable.

A useful operating model is:

Where Day Zero differs from the original contact date, the reason should be reconstructable.

For example, the original contact may have lacked an identifiable reporter and the missing criterion may have been obtained later. The case record should preserve both dates and the evidence supporting the Day Zero decision.

Calendar Days Matter

EU GVP explicitly states that the first day of awareness is Day Zero even if it occurs on a weekend or public holiday. Submission periods are based on calendar days.

This has direct consequences for intake systems.

An MAH cannot design a process that effectively treats reports received on Saturday as becoming known to the company only on Monday.

If the report was available to MAH personnel or a contractor and contained sufficient information on Saturday, an internal business-hours convention does not move the regulatory awareness date to Monday.

This is why after-hours coverage, monitored channels and vendor transfer arrangements are part of compliance design.

EU Submission Timelines in Context

Current GVP Module VI describes the principal post-authorisation EU ICSR timelines as follows:

These are submission requirements, not definitions of Day Zero.

Day Zero answers when the clock starts. The reporting rule determines which clock applies.

The rest of the article therefore follows the information through the main source types where the awareness date becomes difficult to determine.

Direct Reports From Healthcare Professionals and Consumers

For a direct spontaneous report, Day Zero is usually straightforward once the minimum criteria are present.

If a healthcare professional telephones the MAH on 1 October and describes an identifiable patient, a suspect product and a suspected adverse reaction, with the caller identifiable as the reporter, the report is valid at that point. Day Zero is 1 October.

The date does not move because:

• the call is transcribed the next day;
• a medical reviewer confirms seriousness later;
• the case is entered into the safety database later;
• the affiliate forwards the case to global safety later;
• or a regulatory specialist determines the destination later.

Those are processing events after awareness.

Information Received Through a Non-PV Function

The same principle applies when the report enters through another company function.

Examples include:

• Medical Information;
• Quality or product-complaint teams;
• commercial field staff;
• market access;
• patient services;
• reception or general contact channels;
• and other employees who may foreseeably receive safety information.

The relevant question is whether the recipient forms part of the MAH and has received sufficient information, not whether the recipient is trained as a case processor.

Training should therefore help non-PV functions recognise and transfer potential safety information promptly. Training does not postpone Day Zero. Its purpose is to prevent information that already triggered the clock from remaining outside the PV system.

Contractors and Service Providers

ICH E2D(R1) expressly includes third parties such as service providers and contractual partners acting on behalf of the MAH in the general Day Zero rule.

Current EU GVP similarly includes contractors and requires explicit procedures and agreements for safety-information exchange.

Consider a homecare vendor operating an MAH-sponsored service:

If the vendor is acting on behalf of the MAH and the nurse had sufficient information on 2 October, the later transfer does not automatically move Day Zero to 4 or 5 October.

This is why contractual transfer timelines should be designed as internal operational limits shorter than the regulatory deadline.

A requirement such as “transfer within one business day” can be a useful control, but it should not be misunderstood as permission to start the regulatory clock one business day later.

Contractual Partners Are Not All the Same

The phrase “partner” can describe very different legal and operational relationships.

Examples include:

• a call-centre vendor acting directly for the MAH;
• a literature-screening vendor;
• a distributor receiving reports on behalf of the MAH;
• a co-promotion partner;
• a licensing partner with independent pharmacovigilance responsibilities;
• or another MAH exchanging safety data under a pharmacovigilance agreement.

For parties acting on behalf of the MAH, the E2D(R1) general rule is direct: their awareness can establish Day Zero for the MAH.

For arrangements between separate organisations that each have their own regulatory responsibilities, the position may be more complex. The applicable regional requirements and the pharmacovigilance agreement should define:

• which organisation receives what information;
• who performs case assessment;
• who submits;
• what exchange timelines apply;
• and how awareness dates are preserved.

A contract can organise responsibilities. It cannot legitimately erase an earlier awareness date once the MAH itself, or a party acting on its behalf, has sufficient reportable information.

Safety Data Exchange Agreements

A good pharmacovigilance agreement should preserve the regulatory chronology.

For Day Zero purposes, useful provisions include:

• definition of safety information;
• identification of channels covered;
• rules for initial and follow-up information;
• exchange timelines;
• treatment of weekends and holidays;
• treatment of incomplete reports;
• source documentation requirements;
• reconciliation;
• duplicate management;
• late-case escalation;
• and the date fields that must accompany each transfer.

The MAH receiving a partner case should be able to answer:

What was the earliest date on which the relevant organisation had sufficient information to meet the applicable reporting criteria?

If that cannot be reconstructed, the agreement may be operationally convenient but pharmacovigilance control is weak.

Incomplete Reports

Incomplete information requires careful distinction between potential safety information and a valid reportable ICSR.

Suppose a call centre receives:

“A customer became ill after taking Product X.”

If no specific patient can be identified and the reporter cannot provide qualifying information, the contact may not yet meet the minimum criteria.

The organisation should still:

• record the contact according to its procedures;
• attempt follow-up where appropriate;
• preserve the date and content of the original information;
• and document when the missing criterion was obtained.

If an identifiable patient is established on 6 October, the case may become valid on 6 October. Day Zero should then be based on that date under the applicable framework, not retrospectively assigned to the original incomplete contact merely because it occurred earlier.

This prevents two opposite errors:

1. starting the regulatory clock before a case is reportable, creating artificial lateness;
2. delaying Day Zero after the minimum criteria were already present, creating artificial timeliness.

Second-Hand Reports

A second-hand report can be incomplete if the person notifying the MAH does not have first-hand knowledge and the existence of the actual patient or reporter cannot yet be established.

ICH E2D(R1) recommends attempts, where permissible and feasible, to verify that an identifiable patient and reporter exist.

Day Zero should therefore follow the point at which the applicable reporting criteria are actually met.

This does not mean every second-hand report should be held indefinitely. Procedures should define:

• what constitutes sufficient identifiability;
• when follow-up should be attempted;
• how unsuccessful attempts are documented;
• and how regional requirements affect the reporting decision.

Reporter Anonymity

An anonymous reporter is not necessarily an unidentifiable reporter.

ICH E2D(R1) distinguishes between a reporter who wishes to remain anonymous and a situation in which there is insufficient evidence that a real reporter exists.

If the existence of a real person as the reporter is known and the other reporting criteria are met, the case can still qualify even if the person's identifying details are withheld.

The Day Zero assessment should therefore focus on identifiability as defined by the applicable framework, not on whether the database contains a full name.

Product Complaints and Medical Information

Product-quality complaints and Medical Information contacts illustrate why Day Zero governance must cross functional boundaries.

Product Complaint Example

A patient reports that a prefilled syringe leaked and also says they developed a severe rash after using it.

The Quality function may need to investigate the defect, while Pharmacovigilance assesses the adverse reaction.

The safety reporting clock is not suspended while the quality investigation determines the technical root cause.

If the minimum ICSR criteria were present when Quality received the complaint, that receipt can establish Day Zero.

Medical Information Example

A physician asks whether Product X can cause pancreatitis and then states that a named or otherwise identifiable patient developed pancreatitis after treatment.

The contact may contain both:

• a medical-information question;
• and a reportable safety case.

The Day Zero assessment concerns when the valid case information was obtained, not when the medical-information response was approved.

These interfaces will be addressed in dedicated QPPV.com articles, but the Day Zero principle is common: functional ownership does not override regulatory awareness.

Affiliates and Global Safety

Global organisations often use local affiliates as initial recipients and a central safety database for processing.

A typical flow is:

Local affiliate → regional hub → global case processing → regulatory submission.

The central database may be the authoritative case repository, but Day Zero can occur at the affiliate.

The organisation therefore needs:

• rapid transfer;
• reliable time-zone handling;
• preservation of the local receipt timestamp;
• controlled conversion to the database time standard;
• and reconciliation between affiliate logs and the central database.

A global team should not overwrite a local awareness date simply because the central system records a later receipt.

Time Zones

Time-zone differences can create hidden Day Zero errors.

Suppose a report is received in California late on 1 October local time but reaches a European safety hub on 2 October.

The source timestamp and time zone should be preserved.

The organisation's procedure should define how dates are normalised for database and compliance purposes without changing the underlying chronology.

The regulatory principle is more important than the technical convention: the system should be able to reconstruct when the relevant party first had the information, in the context in which it was received.

Organised Data Collection Systems

Reports generated through an organised data collection system are solicited, but solicitation does not remove the Day Zero requirement.

Examples include:

• patient support programmes;
• market research programmes;
• registries;
• non-interventional studies with primary data collection;
• and planned digital-data review.

For a solicited case, the additional causality assessment required by the E2D(R1) framework affects whether the case meets the applicable reporting conditions.

The workflow is therefore:

ODCS information received → minimum case criteria assessed → causality assessed as required → regional reporting criteria determined → Day Zero established according to the applicable source rule → submission clock applied.

The exact Day Zero mechanism can vary by source. Digital ODCS activities, in particular, have an explicit E2D(R1) rule and are considered separately later in this article.

A Practical Intake Decision

At first intake, the handler should be able to answer five questions:

1. When was the information first received or made available?
2. Who received it?
3. Was that person or organisation part of the MAH or acting on its behalf?
4. At what point were the minimum reporting criteria met?
5. Does a source-specific regional rule modify the general principle?

Only after these questions are answered should the Day Zero field be finalised.

This approach is more reliable than asking only, “What date did PV receive the case?”

Literature Day Zero

Literature is one of the clearest examples of why Day Zero cannot be defined by database entry.

ICH E2D(R1) states that the reporting clock for a literature ICSR starts when the MAH, or a third party acting on its behalf, identifies sufficient information to determine that the criteria for ICSR reporting are met. If follow-up is required to obtain missing minimum information, Day Zero is the date sufficient follow-up information is received.

The EU adds more specific operational rules through current GVP Module VI and EMA pharmacovigilance inspection guidance.

Weekly Global Reference-Database Searches

Current EU GVP expects systematic literature review of widely used reference databases no less frequently than once a week.

For valid ICSRs identified through that regular reference-database search, EMA's pharmacovigilance inspection Q&A states that Day Zero is the date on which the search was conducted.

This rule prevents a literature process from gaining extra time by delaying screening after search results have already been generated.

Consider:

If the abstract available from the Monday search already contained sufficient information for a valid ICSR, the current EU literature rule points to 5 October as Day Zero.

The organisation should therefore treat the search process, result delivery and review process as one controlled timeline.

Full Text Needed to Establish Validity

Sometimes the search result or abstract does not contain all minimum criteria.

The full article may be needed to establish:

• the patient;
• the suspect product;
• the adverse reaction;
• the reporter/source;
• or enough context to determine that the case is reportable.

Current GVP Module VI states that, for articles ordered as a result of literature search results, Day Zero is the date when the minimum information needed for a valid ICSR becomes available.

This creates an important distinction:

abstract already valid → search date can be Day Zero
abstract incomplete → later full text may establish Day Zero

The organisation should nevertheless obtain potentially relevant articles promptly. Delayed procurement cannot be used as a deliberate mechanism to postpone case validation.

Local Journals, Meeting Abstracts and Draft Manuscripts

EMA inspection guidance distinguishes the weekly global reference-database search from other mandatory literature-monitoring activities such as:

• local medical journals;
• relevant meeting abstracts;
• and draft manuscripts.

For these sources, the clock starts when the MAH identifies sufficient information to establish a valid report.

EMA also states that the information should be reviewed without delay and that Day Zero for valid ICSRs identified through these routes should not be later than seven calendar days after receipt of the information by the MAH.

That seven-day statement should not be misread as an automatic seven-day grace period.

If a valid case is identified earlier, Day Zero is earlier.

The purpose of the outer limit is to prevent a received publication from sitting unreviewed for an extended period.

Same Publication Arrives Through More Than One Route

A local journal article may later appear in the global reference database.

EMA's inspection Q&A states that the first received information should be considered when determining Day Zero.

If the article first reaches the MAH through the local monitoring process, the organisation should not wait for the next global database search to start the clock.

Conversely, if the publication is first identified in the systematic database search and sufficient information is already available there, the search date applies.

Literature Vendors

Outsourcing the search does not move Day Zero to the date the vendor sends the case to the MAH.

Current GVP Module VI Appendix 2 states that, when literature searching is contracted out, the clock begins with awareness of the minimum information by either the organisation or the contractual partner, whichever is earliest.

For a valid case visible in the search abstract:

vendor runs search Monday → vendor reviews Tuesday → vendor transmits Wednesday → MAH receives Thursday

The MAH should not automatically use Thursday.

This is why literature agreements need controls over:

• search schedule;
• result availability;
• review turnaround;
• full-text procurement;
• transfer timelines;
• and preservation of the original search and awareness dates.

Literature Follow-Up and Duplicates

A publication may provide:

• a new initial case;
• follow-up to an existing case;
• or a duplicate of information already received from another source.

If the publication contains new medically relevant information for an existing case, the follow-up rules apply and a new follow-up clock may begin.

If it is purely duplicative and adds no new reportable information, duplicate management should not create an artificial new Day Zero.

The case record should preserve the publication citation and document the duplicate assessment.

QPPV.com covers the broader literature process in GVP Module VI: Literature Monitoring and Literature ICSRs.

Digital Platforms Under MAH Responsibility

ICH E2D(R1) gives a particularly clear Day Zero rule for digital platforms owned, controlled or operated by, or on behalf of, the MAH.

The MAH should screen platforms under its responsibility frequently enough to identify and report cases within the applicable timeline.

For these platforms, the reporting clock starts when sufficient information to meet the minimum ICSR criteria was posted on the platform.

This is different from saying:

Day Zero is when the safety team first read the post.

Consider:

If the Saturday post already contained sufficient minimum information, the E2D(R1) source-specific rule points to 10 October.

The screening interval must therefore be designed so that reports can still be submitted on time from the posting date.

Moderated and Outsourced Platforms

If an agency or vendor moderates an MAH-responsible platform, outsourcing moderation does not change the underlying responsibility.

The contract should preserve:

• original posting date and time;
• content available at first posting;
• edits or deletions;
• moderation actions;
• date first reviewed;
• and transfer date to PV.

A screenshot or audit trail may be important evidence if platform content later changes.

External Digital Platforms

E2D(R1) states that MAHs are not generally expected to screen digital platforms that are not under their responsibility.

Two situations should then be separated.

Planned Review as an ODCS

If the MAH deliberately conducts a planned review of an external digital platform—for example, a defined social-listening activity—the activity can constitute an organised data collection system.

For such an external-platform ODCS, E2D(R1) states that Day Zero begins when the MAH or third party, during review of the accessed data, identifies an AE/ADR and has sufficient information to determine that the reporting criteria are met.

Importantly, Day Zero is not necessarily the date the dataset was accessed.

Consider:

Data collected 1 October → reviewer begins defined review 3 October → valid case identified 6 October

The source-specific E2D(R1) rule points to 6 October if that is when the reviewer identified the AE/ADR and had sufficient information.

This differs deliberately from the rule for an MAH-controlled platform, where a valid post can start the clock when it is posted.

Incidental Awareness Outside an ODCS

An MAH employee may encounter an adverse-event report on an external platform while performing another activity.

E2D(R1) does not allow the organisation to ignore information merely because the platform is external.

If the employee becomes aware of sufficient information and the case meets applicable regional reporting requirements, the general spontaneous-report framework applies.

The organisation should therefore distinguish:

no general duty to screen every external platform
from
a duty to manage qualifying safety information actually encountered

These are not contradictory.

Digital Identifiability Can Change the Clock

A social-media post may mention a medicine and an event but fail to establish a real patient or reporter.

ICH E2D(R1) states that a digital username or handle alone is insufficient to confirm that a real patient or reporter exists in the absence of qualifying identifiers.

Where permissible and feasible, follow-up can be attempted.

If the original post is incomplete and follow-up later establishes the missing criterion, the Day Zero analysis may move to the date the sufficient follow-up information was obtained.

The process should retain:

• original post;
• timestamp;
• platform;
• username/handle;
• reason the case was initially incomplete;
• follow-up attempts;
• and the information that subsequently established validity.

Messaging Apps, Chatbots and Automated Intake

Digital intake increasingly includes:

• web chat;
• messaging applications;
• automated forms;
• chatbots;
• and AI-supported front ends.

The Day Zero principle does not depend on whether a human immediately reads the message.

If the channel is under MAH responsibility and a valid case is posted or submitted, the E2D(R1) digital-platform rule must be considered.

This has system-design implications.

A chatbot that stores messages overnight but sends them to PV only during office hours does not necessarily postpone regulatory awareness to the next business day.

Before deploying such channels, the organisation should define:

• whether the platform is under MAH responsibility;
• what is timestamped;
• how messages are preserved;
• how potential safety information is identified;
• screening frequency;
• escalation during weekends and holidays;
• and how the original source date is transferred to the safety database.

Source-Specific Rules Must Override Generic SOP Shortcuts

A single generic rule such as “Day Zero equals the date PV first receives the case” is not adequate for modern pharmacovigilance.

The source may impose a more specific rule:

A defensible procedure begins with the general rule and then documents these source-specific exceptions and refinements.

Follow-Up Information Starts a New Clock When It Matters

A submitted case does not have only one possible regulatory clock.

When new medically relevant information is received for a previously reported case, ICH E2D(R1) states that the reporting time clock begins again for submission of the follow-up report. Day Zero for that follow-up is the date the MAH receives the new information.

Examples can include:

• a new diagnosis;
• a change in outcome;
• additional treatment details;
• new laboratory or imaging results;
• new information relevant to causality;
• a new seriousness criterion;
• or information that changes whether the case qualifies for expedited reporting.

The original Day Zero remains part of the case history. The follow-up creates a new clock for the new information.

Non-Serious Case Becomes Serious

Suppose a non-serious case is initially received on 1 October.

On 10 October, follow-up reveals that the patient was hospitalised because of the event.

The new information changes the seriousness classification.

Under E2D(R1), the follow-up Day Zero is 10 October. The case now qualifies for the applicable expedited reporting timeline from that new Day Zero.

The safety database should preserve both:

• initial case Day Zero: 1 October;
• serious follow-up Day Zero: 10 October.

A system that keeps only one mutable “receipt date” can obscure this chronology.

Serious Case Becomes Non-Serious

The reverse situation also needs controlled handling.

Current EU GVP states that when a case initially submitted as serious becomes non-serious based on new follow-up information, that follow-up should still be submitted within the 15-day timeframe. Subsequent follow-up reports can then follow the non-serious reporting timeframe as applicable.

This is an EU operational nuance and should not be replaced by a generic rule that every downgrade immediately changes the current reporting clock to 90 days.

Significant Versus Non-Significant Follow-Up

Current EU GVP distinguishes significant follow-up from information that does not materially affect case assessment or management.

Examples of potentially significant follow-up include:

• new medical information;
• new administrative information that affects case management;
• a change in seriousness;
• information affecting expectedness or causality;
• or other details relevant to regulatory processing.

Examples of non-significant information can include:

• correction of a typographical error;
• revised internal comments;
• or other purely administrative corrections that add no new source information.

The distinction matters because not every change to an ICSR should create a new Day Zero.

The clock is driven by receipt of new relevant information, not by every edit made inside the safety database.

Amendments Without New Source Information

ICH E2D(R1) is explicit that an amendment based only on internal quality review, with no receipt of additional information, should not be assigned a new Day Zero.

Examples include:

• correcting an incorrectly coded MedDRA term;
• correcting a data-entry error;
• revising an internal causality field after medical review;
• attaching a document that had already been available internally;
• or correcting formatting.

These changes may still require an amendment submission under regional rules, but the organisation should not manufacture a new awareness date merely because the database record changed.

The case history should distinguish:

new source information → potential new follow-up Day Zero
from
internal correction → no new Day Zero

Reconciliation Does Not Automatically Create Day Zero

Reconciliation is a control for finding discrepancies between systems or organisations. It is not itself a universal Day Zero rule.

Consider a reconciliation between a patient-support vendor and the MAH.

The reconciliation finds a valid case that the vendor received on 1 September but failed to transfer. The MAH discovers the omission on 20 September.

If the vendor was acting on behalf of the MAH, using 20 September as Day Zero merely because that is when the MAH's PV team discovered the case would erase the earlier regulatory awareness.

The correct response may include:

• preserving the original vendor receipt date;
• assessing the case as late if applicable;
• submitting promptly;
• documenting the reconciliation discovery date separately;
• investigating the failed transfer;
• and implementing corrective and preventive action where warranted.

Reconciliation should reveal lateness, not redefine it away.

Reconciliation With an Independent Partner

A different analysis may apply where the other organisation is an independent MAH or partner that is not acting on behalf of the receiving MAH.

The pharmacovigilance agreement and applicable regional requirements should establish:

• which organisation had the regulatory responsibility;
• when the receiving MAH became aware;
• what information had to be exchanged;
• and whether a missed contractual transfer created a compliance issue.

The key point is to avoid a mechanical rule such as:

Reconciliation date always equals Day Zero.

The relationship between the parties matters.

Duplicate Cases

Duplicate identification can also create confusion about Day Zero.

Suppose two cases are entered separately and later found to describe the same patient and event.

The duplicate-management process should preserve the original source chronology.

Merging or linking duplicates does not ordinarily create a new Day Zero merely because the duplicate was discovered.

However, if one version contains medically relevant information that was not previously known to the MAH, that new information may create a follow-up clock.

The case processor should therefore ask:

1. Is this truly the same case?
2. Does the newly identified source contain new medically relevant information?
3. When was that information first available to the MAH or party acting on its behalf?
4. Does the information require a follow-up submission?

Duplicate management and Day Zero assessment are connected, but they are not the same process.

Case Transfers Between Databases

Mergers, acquisitions, licence transfers and safety-database migrations can result in cases moving between systems.

Migration itself should not reset Day Zero.

If a case was valid and reportable before migration, the regulatory history should survive the transfer.

Key dates that should remain traceable include:

• original receipt date;
• original Day Zero;
• follow-up receipt dates;
• submission dates;
• and dates of later amendments.

If historical metadata are lost during migration, the organisation may be unable to reconstruct whether a case was submitted on time.

That is a data-integrity problem, not merely a technical migration issue.

When a Case Becomes Reportable Only After Medical Assessment

Some situations require careful distinction between minimum validity and regional reportability.

For spontaneous reports, suspicion of a causal relationship is generally implied for reporting purposes.

For solicited reports, E2D(R1) requires an appropriate causality assessment and indicates that a solicited report should be submitted when a causal relationship is at least a reasonable possibility as assessed by either the reporter or MAH, subject to regional requirements.

The organisation should avoid using routine internal medical-review scheduling to postpone Day Zero artificially.

If all information needed to determine reportability is already available, a later administrative approval step should not become the awareness date merely because a physician signs the case then.

Conversely, if the report genuinely cannot meet the applicable reporting conditions until additional information is received or the required source-specific assessment can be completed, the chronology and rationale should be documented.

Other Observations

ICH E2D(R1) also addresses observations such as:

• lack of efficacy;
• overdose;
• abuse;
• misuse;
• medication error;
• occupational exposure;
• pregnancy or breastfeeding exposure;
• and off-label use.

Where such information is reportable as an ICSR under regional or local requirements, the Day Zero framework applies to the point at which the applicable reporting criteria are met.

The organisation should therefore avoid assuming that “no adverse event” means “no regulatory clock”.

The first question is whether the observation is reportable in the jurisdiction and circumstances. The second is when the information became sufficient for that reporting obligation.

Nullification

A previously submitted ICSR may later be found to be completely erroneous or otherwise meet the criteria for nullification under the applicable E2B framework.

Nullification is not a mechanism for rewriting the original Day Zero.

The case history should preserve:

• why the original case was created;
• when it was reported;
• what new information led to nullification;
• and when that information was received.

If new source information caused the nullification decision, that information should be recorded with its own receipt chronology. The technical nullification transaction should not be used to obscure the original reporting history.

Scenario: Medical Representative Receives a Case Late on Friday

At 18:30 on Friday, a physician tells a medical representative about a patient who developed a serious adverse reaction to the company's medicine. The minimum criteria are present.

The representative sends an email to PV on Monday morning.

Day Zero: Friday.

Why: current EU GVP includes medical representatives among MAH personnel and uses calendar days. Monday is an internal transfer date.

Control

The organisation should have weekend escalation or transfer arrangements that recognise the Friday clock.

Scenario: Vendor Receives an Incomplete Case

A patient-support vendor receives a report on Monday but the reporter does not provide enough information to establish an identifiable patient.

The vendor obtains sufficient patient information on Thursday.

Potential Day Zero: Thursday, subject to the applicable reporting requirements.

Why: the Monday contact was incomplete; the missing minimum criterion was first obtained Thursday.

Control

The case record should retain Monday as the original contact date and document why the reporting criteria were not met until Thursday.

Scenario: Reconciliation Finds a Missed Vendor Case

A vendor acting on behalf of the MAH received a valid serious case on 1 August but failed to transfer it. Monthly reconciliation on 1 September detects the omission.

Day Zero: the analysis should preserve 1 August as the relevant awareness date if the vendor's receipt triggered MAH awareness under the applicable framework.

Why: reconciliation detected the failure; it did not create the original awareness.

Control

Submit promptly, record the late discovery, investigate the process failure and assess CAPA as appropriate.

Scenario: Follow-Up Changes Seriousness

A non-serious report is received on 1 October. On 12 October the reporter provides hospitalisation details.

Initial Day Zero: 1 October.
Follow-up Day Zero: 12 October.

Why: the new medically relevant information changes seriousness and starts a new follow-up clock.

Scenario: Internal Coding Correction

An already submitted case is reviewed during quality control and a MedDRA term is corrected. No new source information has been received.

New Day Zero: none.

Why: this is an internal amendment, not new follow-up information.

Scenario: Full Literature Article Adds New Information

An abstract yielded a valid literature case and Day Zero was assigned according to the applicable literature rule. The full article is obtained later and adds a previously unknown hospitalisation.

Initial Day Zero: remains unchanged.
Follow-up Day Zero: date the new medically relevant information from the full article becomes available to the MAH or its literature provider, as applicable.

The article does not retrospectively move the original Day Zero. It can create a new follow-up clock.

The Evidence Chain

A well-controlled case should allow a reviewer to reconstruct:

source information → first availability → recipient → validity assessment → source-specific rule → Day Zero → applicable deadline → submission → subsequent follow-up clocks.

If any link is missing, the organisation may still have submitted on time, but it may not be able to demonstrate that fact reliably.

Building a Controlled Day Zero Process

Day Zero should be treated as a controlled pharmacovigilance decision supported by evidence, not as a clerical field populated at the end of case entry.

A practical control model has six layers.

1. Source Inventory

Identify every channel through which safety information can enter the organisation.

This should include:

• spontaneous-report channels;
• Medical Information;
• product complaints;
• field personnel;
• affiliates;
• partners;
• patient-support programmes;
• market research;
• non-interventional studies;
• literature;
• MAH-controlled websites and applications;
• social-listening activities;
• and other vendors or service providers.

For each source, define whether the general Day Zero rule applies or whether a source-specific rule modifies it.

2. Date Capture at the First Point of Contact

The first recipient should preserve:

• date;
• time where relevant;
• time zone where relevant;
• original source;
• original information;
• and evidence of when the information was available.

The process should avoid replacing the original source timestamp with the later date on which information entered the central PV workflow.

3. Validity and Reportability Assessment

The process should determine:

• when the minimum criteria became available;
• whether regional reporting criteria are met;
• whether the source is spontaneous or solicited;
• whether causality assessment is required;
• and whether a special source-specific rule applies.

Where the case is initially incomplete, the reason should be visible in the record.

4. Automated Deadline Calculation

Once Day Zero and the applicable reporting category are established, the system can calculate the submission deadline.

Automation is useful only if the input date is correct.

A perfectly configured 15-day calculator cannot compensate for a Day Zero that was moved three days forward during internal transfer.

5. Independent Quality Controls

Quality checks can target:

• difference between source receipt and Day Zero;
• difference between Day Zero and database entry;
• weekend or holiday receipts;
• vendor transfer intervals;
• literature search-to-review intervals;
• digital posting-to-screening intervals;
• follow-up dates;
• and late cases discovered by reconciliation.

The objective is to identify systematic drift, not simply individual data-entry mistakes.

6. Governance and Escalation

Repeated Day Zero problems usually indicate a process-design issue.

Examples include:

• an unmonitored mailbox;
• a vendor that batches cases weekly;
• a local affiliate that waits for medical review before transfer;
• a literature vendor that records delivery date instead of search date;
• or a digital platform screened too infrequently.

These require process correction rather than repeated case-by-case explanations.

Day Zero Metrics

Metrics can help identify weak interfaces, but they should measure the real process.

Useful examples include:

A low average transfer time can still hide individual serious late cases. Distribution, outliers and source-specific trends are therefore more useful than one organisation-wide mean.

Quality Review of the Day Zero Field

A reviewer assessing Day Zero should not ask only whether the entered date “looks reasonable”.

The review should trace the evidence.

Useful questions include:

• What is the earliest source document?
• When was it received or posted?
• Who had access to it?
• Were all minimum criteria present?
• If not, what was missing?
• When was the missing information obtained?
• Was the recipient an MAH employee or acting on behalf of the MAH?
• Does literature or digital guidance provide a more specific rule?
• Is this initial or follow-up information?
• Is the update new source information or an internal correction?

This evidence-based approach reduces retrospective date selection based on the desired compliance outcome.

Inspection Perspective

An inspector evaluating Day Zero is likely to be interested in the complete information flow rather than the database field alone.

Potential inspection questions include:

• How does the organisation define Day Zero?
• How is the definition aligned with current E2D(R1) and GVP?
• Which non-PV functions can receive safety information?
• How are weekends and public holidays handled?
• Which vendors can trigger awareness?
• How are partner agreements structured?
• How is literature Day Zero determined?
• How are MAH-controlled digital platforms screened?
• How are initially incomplete cases documented?
• How are significant follow-up and amendments distinguished?
• What happens when reconciliation identifies a missed case?
• Can the organisation reconstruct Day Zero from source evidence?
• How are late cases investigated and trended?
• Does QPPV or PV governance receive visibility of material compliance issues?

The strongest response is an auditable case chronology supported by contemporaneous evidence.

Illustrative Failure Modes

The following examples are hypothetical failure modes, not descriptions of actual inspection findings.

Central PV Receipt Is Used for Every Case

A procedure defines Day Zero as “date received by Global Safety”.

Why it fails: valid safety information may already have been received by an affiliate, employee, contractor or other function acting for the MAH.

Business Days Replace Calendar Days

A weekend report is assigned Monday as Day Zero.

Why it fails: current EU GVP uses calendar days and states that weekends and public holidays do not postpone Day Zero.

Vendor SLA Is Mistaken for Regulatory Awareness

A vendor has two business days to transfer a case, and the MAH starts Day Zero on receipt from the vendor.

Why it fails: an internal transfer allowance does not necessarily change the earlier awareness date.

Literature Delivery Date Replaces Search Date

A valid case was already visible in the abstract generated by the weekly search, but Day Zero is set to the date the vendor sent the case form.

Why it fails: current EU literature guidance can tie Day Zero to the search date when the search output already contains sufficient information.

Digital Screening Date Replaces Posting Date

A valid case is posted to an MAH-controlled platform on Saturday but screened Monday.

Why it fails: E2D(R1) starts the clock from when sufficient information was posted on an MAH-responsible platform.

Every Follow-Up Creates a New Day Zero

A spelling correction triggers a new reporting clock.

Why it fails: internal amendments without newly received information do not receive a new Day Zero under E2D(R1).

Reconciliation Hides a Late Case

A missed vendor case is assigned the reconciliation date as Day Zero.

Why it fails: reconciliation may reveal earlier awareness rather than create it.

The Earliest Date Is Always Used, Even When the Case Was Invalid

An incomplete initial contact is automatically assigned as Day Zero despite missing minimum information.

Why it fails: the general clock depends on sufficient information to meet the applicable reporting criteria. Earlier incomplete contacts should be preserved but not mechanically converted into Day Zero.

Practical Decision Framework

A case processor can use the following sequence:

1. Identify the source.
2. Find the earliest available source evidence.
3. Determine who first received or could access the information.
4. Determine whether that recipient was the MAH or acting on its behalf.
5. Assess when the minimum criteria were first met.
6. Check for a source-specific literature or digital rule.
7. Determine whether regional reportability conditions are met.
8. Record Day Zero and the rationale.
9. Calculate the applicable submission deadline.
10. For later information, distinguish follow-up from internal amendment.
11. Preserve all earlier dates rather than overwriting the chronology.

This sequence should be implemented consistently across central PV, affiliates and vendors.

Day Zero Checklist

Before finalising the awareness date, verify:

• [ ] Source identified.
• [ ] Original receipt/posting/search date retained.
• [ ] Recipient identified.
• [ ] Relationship of recipient to MAH understood.
• [ ] Minimum ICSR criteria assessed.
• [ ] Missing criteria and follow-up documented where applicable.
• [ ] Literature-specific rule checked.
• [ ] Digital-platform-specific rule checked.
• [ ] Weekend/public-holiday handling is correct.
• [ ] Initial versus follow-up version distinguished.
• [ ] New source information distinguished from internal correction.
• [ ] Partner/vendor transfer date not substituted automatically for earlier awareness.
• [ ] Reconciliation discovery date not substituted automatically for earlier awareness.
• [ ] Time zone documented where it could change the calendar date.
• [ ] Submission deadline calculated from the correct Day Zero.
• [ ] Rationale reconstructable from source evidence.

Relationship With Other QPPV.com Articles

Day Zero is one part of the broader ICSR framework.

The underlying E2D(R1) source and report taxonomy is explained in ICH E2D(R1): What Changed in Post-Approval Pharmacovigilance.

Literature-specific operational requirements are covered in GVP Module VI: Literature Monitoring and Literature ICSRs.

Initial intake, validity and triage are addressed in GVP Module VI: Case Intake, Triage and Initial Assessment.

Broader follow-up and reconciliation controls are addressed in GVP Module VI: ICSR Data Quality, Follow-Up and Reconciliation.

These topics overlap operationally, but the present article focuses on one question: which date starts the regulatory reporting clock?

Key Takeaways

• Day Zero is a regulatory awareness date, not simply the safety-database entry date.
• Under ICH E2D(R1), the general clock starts when MAH personnel or a third party acting on its behalf obtain sufficient information to meet the applicable minimum reporting criteria, unless regional requirements specify otherwise.
• Current EU GVP includes medical representatives and contractors and counts reporting periods in calendar days, including weekends and public holidays.
• An initially incomplete contact should be retained, but Day Zero generally arises when the missing information needed for reporting is obtained.
• A vendor or service provider acting on behalf of the MAH can trigger the clock before the central PV team receives the case.
• Current EU literature rules can make the weekly reference-database search date Day Zero when the available search record already contains sufficient information.
• For other mandatory literature sources, valid cases should be identified without delay; current EMA inspection guidance states that Day Zero should not extend beyond seven calendar days from receipt merely because review was delayed.
• On an MAH-responsible digital platform, E2D(R1) ties Day Zero to when sufficient information was posted, not when PV later screened the platform.
• During a planned ODCS review of an external digital platform, Day Zero is when the reviewer identifies the AE/ADR and has sufficient information; it is not necessarily the date the dataset was accessed.
• Medically relevant follow-up can start a new reporting clock.
• Internal amendments without newly received information should not be assigned a new Day Zero.
• Reconciliation can reveal an earlier missed Day Zero; it should not be used automatically to redefine the clock.
• A defensible Day Zero can be reconstructed from source evidence, recipient, validity assessment and the applicable source-specific rule.

References

1. International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use. ICH E2D(R1): Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports. Final Step 4 guideline, adopted 15 September 2025.
   https://database.ich.org/sites/default/files/ICH_E2D%28R1%29_Step4_FinalGuideline_2025_0819.pdf

2. European Medicines Agency. ICH E2D(R1) Guideline on post-approval safety data: definitions and standards for management and reporting of individual case safety reports — Step 5. EMA/CHMP/ICH/59123/2024. Legal effective date: 18 March 2026.
   https://www.ema.europa.eu/en/ich-e2d-post-approval-safety-data-management-scientific-guideline

3. European Medicines Agency. EU implementation strategy of ICH E2D(R1) Guideline — Post-approval safety data: Definitions and standards for management and reporting of individual case safety reports. EMA/11141/2026.
   https://www.ema.europa.eu/en/documents/scientific-guideline/eu-implementation-strategy-ich-e2dr1-guideline-post-approval-safety-data-definitions-standards-management-reporting-individual-case-safety-reports_en.pdf

4. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module VI — Collection, management and submission of reports of suspected adverse reactions to medicinal products, Rev. 2. EMA/873138/2011 Rev. 2.
   https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/guideline-good-pharmacovigilance-practices-gvp-module-vi-collection-management-submission-reports-suspected-adverse-reactions-medicinal-products-rev-2_en.pdf

5. European Medicines Agency. Coordination of pharmacovigilance inspections — Questions and answers: What is the day zero for ICSRs described in the medical literature? Current EMA inspection guidance.
   https://www.ema.europa.eu/en/coordination-pharmacovigilance-inspections-0

6. European Parliament and Council. Directive 2001/83/EC on the Community code relating to medicinal products for human use, as amended, including Article 107 pharmacovigilance reporting requirements.
   https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02001L0083

7. European Medicines Agency. EU Individual Case Safety Report (ICSR) Implementation Guide. Current EudraVigilance implementation guidance.
   https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/european-union-individual-case-safety-report-icsr-implementation-guide_en.pdf

Regulatory Note

This article explains post-authorisation pharmacovigilance Day Zero as reviewed on 1 October 2026.

ICH E2D(R1) provides harmonised guidance but repeatedly defers to regional or local reporting requirements. In the EU, the current GVP Module VI and applicable legislation must therefore be read together with E2D(R1). EMA has stated that GVP Module VI is being revised to integrate E2D(R1); source-specific procedures should be checked against the current EMA version before operational changes are implemented.

The 15-day and 90-day EU timelines described in this article refer to the current post-authorisation ICSR framework. They should not be applied automatically to clinical-trial SUSARs, periodic reports or other regulatory processes governed by different rules.

The scenarios and failure modes are illustrative. They are not presented as actual inspection findings unless a specific regulatory source is identified.