Regulations and compliance · Practical guide

GVP day zero: when does the ICSR reporting clock start?

A contracted provider receives a report on Friday. Someone enters it in the safety database on Tuesday. Which date counts? Under GVP, Day Zero relates to when sufficient information became known to the relevant party. Distinguish receipt, completeness and database entry in the European pharmacovigilance process for human medicines.

Table of contents

At a glance

Which receipt date determines day zero for an ICSR?

Day zero is generally when personnel of the marketing authorisation holder, or a third party acting on its behalf, receive enough information to establish the minimum criteria. Later receipt by the PV department or entry into the database does not restart the clock. Check source-specific rules, including literature, and the regional reporting scope. Treat new relevant follow-up information differently from an internal correction without a new receipt.

  • Database record creation and the relevant knowledge time point are distinct events.
  • Weekends do not automatically shift Day Zero to the next working day.
  • Minimum criteria, reporting scope, and appropriate deadline must be jointly determined.

1. Separate determination of the start date and reporting obligation

This article addresses human medicinal products in the EU post-authorization context. First, it must be determined whether a valid and compliant ICSR, as required by applicable regulations, is available. Thereafter, the correct start date for the reporting period is derived. The terms "Day Zero" and "reporting obligation" do not substitute for one another.

GVP Module VI should be read in conjunction with ICH E2D(R1) and the EU Implementation Strategy. The additional transition period ended on 18 September 2026. Specific regional regulations remain decisive. The deadlines outlined herein must not be generally applied to clinical SUSARs, veterinary reports, or any worldwide received non-serious report.

Sources: [1] [2] [3]

2. Do not allow incomplete entries to disappear

For the routine suspected adverse reaction report, verify identifiable patient, identifiable reporter, suspected or interacting medicinal product, and suspected adverse reaction. While the current ICH guideline addresses special observations and refers to regional reporting requirements, a one-size-fits-all automation based on four arbitrarily filled database fields is therefore inappropriate.

If required information is missing initially, the entry is still documented and appropriately tracked. Record what was missing and when it was supplemented. The subsequent evaluation must not appear as though the original information had never existed. Conversely, a previously complete information set must not be retrospectively treated as incomplete merely because additional desirable details were absent.

Sources: [1] [2]

3. Clearly define key time points

Our own matrix helps distinguish different events in the data model and in the work instruction. It does not prescribe specific field names. However, the evidence should indicate which time point originates from a source and which arises from internal processing.

When employees use different time zones, a clear and traceable handling procedure shall be established. This document does not assert a universal regulatory requirement for UTC usage. What is essential is that deadline evaluation accurately reflects the actual receipt and is not distorted by format changes or forwarding actions.

Own timeline matrix for deadline assessment
EventSignificanceTypical error
First incomplete message Start of the documented procedure Message regarding missing information not to be recorded
Minimum information provided to the relevant recipient Basis for determination of Day Zero Use subsequent PV review as a new start point
Routing to the PV department Internal or contractual transfer Confuse transfer date with original knowledge
Database record maintenance Processing step Entry date to be issued retrospectively as a source event
New relevant information Determine when the follow-up reporting clock starts Override the original entry
Internal correction without new information Document the correction process Artificially Create New Day Zero

Sources: [1] [2]

4. Example: Friday fully completed, Tuesday entered

In this example, the report pertains to a serious suspected adverse reaction within the defined EU reporting scope. As of Thursday, 1 October 2026, the patient has not yet been identified. The designated partner receives this information on Friday, 2 October. The incident is only entered into the central database on Tuesday, 6 October.

On these assumptions, Day Zero is 2 October. The next day is Day 1 and 17 October is 15 calendar days after Day Zero. Submit as soon as possible. The deadline calculation is no reason to wait until the last day. Arrange weekend and deputy cover so the process can continue.

Example: filled expiration date axis
DateInformation or actionContext
October 1, 2026 First receipt; a required minimum criterion is missing Document and purposefully query
2. October 2026 Partner receives the missing information; case meets the prescribed criteria Day Zero
October 3, 2026 Saturday Day 1. The clock does not restart on Monday.
October 6, 2026 Central database data entry Day 4; deadline start remains 2 October
October 17, 2026 15 calendar days after Day Zero Absolute 15-day limit for the described serious incident case

Sources: [1] [2]

5. Partners and literature have their own validation gaps

For a third-party service provider acting on your behalf, the time of their knowledge must not be later than the dispatch of a consolidated report. Therefore, agree on the provision of receipt date and information status. The mere designation 'external partner' does not substitute the assessment of their actual function and the specific contractual agreement.

For literature, GVP VI contains specific EU regulations. When conducting a weekly search, the search date may be significant if the abstract already contains the minimum required information. If the information is missing and only becomes available upon full text access, the entry must be evaluated separately. Order relevant full texts promptly; delayed processing is not a valid means of postponing the clock.

Sources: [1] [2]

6. Follow-up and amendment timing are distinct

New medical information relevant to an already reported case may trigger a new follow-up deadline. A change in the severity classification—from non-serious to serious—due to new information may alter the reporting decision. The original case history remains intact; a new entry does not replace the previous one.

An internal correction without additional information does not establish a new Day Zero. Errors and corrections should be treated as separate events. The required reporting type depends on the content and significance. A system that automatically assigns a new entry date upon every change must therefore be evaluated for suitability to the intended process.

Sources: [1] [2]

7. Track expiry date until actual result is achieved

A suspended transmission schedule does not constitute successful submission. Link the alert inventory to Gateway evidence and processing response. Partially or fully rejected messages require further processing. In the case of a failure, the specific error path is decisive; a general automatic extension of deadlines cannot be inferred therefrom.

The team should be able to clearly identify which cases are due soon, already sent, not yet confirmed, or rejected. A single "completed" status column alone cannot adequately reflect these distinctions. Therefore, define a closure rule that takes into account deadline compliance and actual recipient response, without equating medical quality assessment with technical success.

Sources: [4] [1]

8. Checklist for a Robust Day-Zero Evidence

The following internal checklist is applicable to a specific case and for test data during a process change. Pay particular attention to transitions: initially incomplete, later complete; data entry at the partner; processing following a weekend; new information provided for an older case.

In the example, the subsequent entry on 6 October is correctly documentable and may not override the relevant receipt date of 2 October. Whether a delay in processing requires additional actions will be assessed separately. Correct date representation alone does not address underlying organizational causes.

  • What is the scope and the required minimum information?
  • First entrance and later additions?
  • Does the receiving partner's role consider?
  • Is Day Zero not derived from the entry date?
  • Does the calendar date and representation consideration apply?
  • Were literature guidelines reviewed in applicable cases?
  • Follow-up and internal corrections conducted at separate times?
  • Shipped errors and missing responses to be tracked further?

Sources: [1] [2] [4]

Project experience and collaboration

Trace the first relevant receipt through to reporting

With your team, we simulate a report received outside Pharmacovigilance, such as by a contracted provider. We examine when the minimum information becomes available, how that time is preserved and who monitors forwarding. One central channel may need different controls from multiple sites and partners. We align training, ownership and exception handling accordingly. Internal screening or later entry into the system does not restart the same reporting clock.

Frequently asked questions about GVP Day Zero

Is Day Zero always the date in the Safety System?

Only if this field accurately reflects the professionally relevant knowledge date. The automatic entry date may be later. Verify the source, receiving party, and information status, and record the internal capture as a separate event.

Sources: [1] [2]

Does an incoming batch occur on weekends?

Generally yes. Module VI defines Day Zero independently of whether the information is received on a weekend or holiday. Deadlines are based on calendar days. Therefore, the first regular business day is not automatically the start date.

Sources: [1]

Does the deadline begin only when a PV specialist reviews the case?

No. For the described EU reporting process, the time period begins as soon as any employee of the marketing authorisation holder, including field personnel and contractors, receives the required minimum information (GVP VI.B.7; ICH E2D(R1) 5.2). A subsequent review by the pharmacovigilance department does not reset the clock. Therefore, training and onward transmission must also include personnel who first receive a report outside the specialist department.

Sources: [1] [2]

What occurs when minimum specifications are not provided?

Document the receipt and make reasonable efforts to obtain missing information. Determine when sufficient information is available. Incomplete reports must not simply disappear from the PV process, even if a complete ICSR is not yet available.

Sources: [1] [2]

Should a period of 15 days always be applied?

No. The deadline depends on the report and its scope of application. Module VI specifies 15 days for relevant serious cases and 90 days for relevant non-serious EU cases. This classification must not be unreviewedly transferred to clinical or other regional reporting procedures.

Sources: [1]

Does the publication or search date of the literature count?

This cannot be determined solely from the publication date. Check the EU literature guidelines and assess when the required information became available. For a weekly search with sufficient abstracts, the search date as specified in Appendix 2 is relevant; a later consolidated report does not automatically shift this date.

Sources: [1] [2]

Does new follow-up information trigger a new deadline?

When additional relevant information is received, the follow-up deadline start date shall be determined separately. The original case and its initial entry remain unchanged. Document which information was new and explain why it influenced the corresponding reporting decision.

Sources: [1] [2]

Does an Amendment receive a new Day Zero?

Not when correction is made internally and no additional information is obtained. ICH E2D(R1) explicitly excludes this scenario. Detection of error, internal decision, and correction remain nonetheless traceable events in the audit trail.

Sources: [2]

Does a system failure automatically extend the deadline?

No. For incidents, root cause and relevant procedures must be investigated. The EU-ICSR Guideline distinguishes various sender and receiver failures. An internal incident must not be treated without further evidence, such as a confirmed EudraVigilance interruption.

Sources: [4]

How do we assess the date logic effectively?

Use cases involving weekend calls, partner forwarding, initial missing information, and subsequent follow-up. Calculate expected data independently. Additionally, verify that the software does not inadvertently correlate entry date and source event.

Sources: [1] [2]

Sources and review date

Source date: 7 October 2026. GVP VI Rev. 2, ICH E2D(R1), and EU Implementation Strategy 2026. Regional reporting criteria remain decisive. The timeline in the example does not recommend processing until the last allowable day.

  1. EMA: GVP Module VI – Collection, Processing, and Reporting of Suspected CasesRev. 2, dated 28.07.2017; applicable from 22.11.2017; VI.B.2, VI.B.7–7.1; VI.C.3–4; Appendix 2.7/2.9, pages 14–16, 21–22, 40–42, 97
  2. EMA/ICH: E2D(R1) – Post-approval safety dataStep 5, 18.09.2025; EU Efficacy 18.03.2026; §§ 2.2, 4.2, 5.2, S. 7, 10–11, 18
  3. EMA: EU Implementation Strategy for ICH E2D(R1)EMA/11141/2026, 26.02.2026; PRAC 20.02.2026; § 2, S. 2
  4. EMA: EU ICSR Implementation GuideEMA/51938/2013 Rev. 2, March 2021; I.C.2.1.6–.8, p. 17–21

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Trace the start date and processing status reliably and consistently.

We support you with incoming pathways, date logic, and conclusive test cases for partner transfers and safety systems.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →