GVP Module VII: PSUR Data Lock Point and Reporting Interval

Introduction

The data lock point (DLP) is one of the most important control dates in the PSUR process. It defines the end of the reporting interval for the periodic safety evaluation and provides the reference point from which the submission timeline is calculated.

A PSUR process can therefore fail even when the scientific writing is strong if the organisation uses the wrong reporting interval, misses a change to the applicable EURD schedule, incorrectly determines the DLP, or fails to control information around the DLP.

The DLP should consequently be treated as a controlled pharmacovigilance milestone rather than simply as the date printed on the cover page of the report.

1. What Is the Reporting Interval?

The reporting interval is the period covered by the PSUR safety evaluation.

It establishes the temporal boundary for the information that is principally evaluated in that report. The PSUR nevertheless places information arising during the interval into the context of cumulative knowledge, so the reporting interval should not be confused with the total historical safety experience of the product.

A simplified model is:

Previous cumulative knowledge
          +
Information arising during the reporting interval
          ↓
     Data lock point
          ↓
  Periodic evaluation
          ↓
        PSUR

The reporting interval should be defined before the data-collection and analysis activities begin.

2. What Is the Data Lock Point?

The DLP is the date through which data are included in the PSUR reporting period.

It is a controlled reference date for the safety evaluation. Once established, the organisation can determine which information belongs to the reporting period and can coordinate the subsequent data extraction, analysis, medical review, quality control and submission activities.

The DLP is therefore both a regulatory date and an operational control point.

3. DLP Is Not the Date the PSUR Is Submitted

The DLP and submission deadline are different dates.

For example, if a PSUR has a DLP of 30 June, the organisation does not normally submit the report on 30 June. The DLP closes the reporting period; the applicable regulatory submission period follows it.

This distinction is fundamental when designing the PSUR project plan.

Reporting interval
───────────────────────────────► DLP
                                 │
                                 │ preparation / review
                                 │
                                 ▼
                           submission deadline

Confusing these dates can result in incorrect project planning and late submission.

4. How Is the Applicable DLP Determined?

The applicable DLP should be established from the current regulatory framework and the applicable product or active-substance schedule.

For substances and combinations covered by the EU reference-date system, the EURD list provides the applicable frequency, DLP and submission date.

The EURD list is a living regulatory document and is updated regularly. An MAH should therefore not rely solely on a historical PSUR calendar, an old marketing-authorisation record or a previous PSUR cover page.

The current applicable entry must be verified.

5. The European Union Reference Date

The EURD framework harmonises periodic reporting for relevant active substances and combinations of active substances across the EU.

The European Union reference date is associated with the first or earliest known marketing authorisation in the EU for a medicinal product containing the relevant active substance or combination.

The EURD framework allows products containing the same active substance or combination to be assessed together even when they are covered by different marketing authorisations.

This is important because the PSUR schedule is not necessarily determined independently for every individual marketing authorisation.

6. Why the EURD List Must Be Monitored

The EURD list is not a static historical reference.

EMA states that it is updated monthly following the relevant regulatory adoption process, and changes generally become effective six months after publication. The MAH remains responsible for checking the applicable schedule and complying with the resulting requirements. citeturn0search0turn0search1

A controlled process should therefore record:

• the date on which the EURD list was checked;
• the relevant active-substance or combination entry;
• the applicable frequency;
• the DLP;
• the submission date;
• any relevant notes or exceptions;
• and the person or function responsible for the determination.

7. EURD Schedule Versus the Standard Legislative Cycle

The legislation establishes standard PSUR submission frequencies, but where an active substance or combination is covered by the applicable EURD list, the EURD schedule overrides the standard cycle and relevant marketing-authorisation conditions concerning frequency.

EMA currently describes the standard schedule as six-monthly, yearly and thereafter three-yearly where the EURD list does not establish another applicable frequency. citeturn0search0turn0search20

This is why a PSUR calendar based only on the generic legislative cycle can become incorrect.

8. When the Substance Is Not in the EURD List

Not every situation is governed by an EURD entry.

Where the active substance or combination is not included in the EURD list, the applicable submission requirements must be determined from the marketing authorisation conditions and the applicable legislative framework.

EMA's current procedural advice explains that such PSURs are submitted through the PSUR Repository and that, where no other applicable frequency is specified, the standard submission schedule applies. Certain categories of products have specific exemptions or conditions. citeturn0search0

The operational lesson is simple: absence from the EURD list does not mean absence of PSUR obligations.

9. DLP Control in the MAH Quality System

The DLP should be recorded in the organisation's controlled regulatory calendar.

The control should link the DLP to:

• the active substance or product;
• applicable marketing authorisations;
• PSUR frequency;
• submission deadline;
• assigned PSUR team;
• data-extraction dates;
• review milestones;
• and submission responsibilities.

The calendar should be capable of showing why the organisation believes a particular DLP and submission date apply.

10. Practical Example: Incorrect Legacy Calendar

An MAH has historically prepared a PSUR every six months. A later EURD amendment changes the applicable frequency to annual reporting.

If the organisation continues using its old calendar without checking the current EURD entry, it may prepare reports on the wrong schedule.

The opposite can also occur: an organisation may fail to prepare a required report because its internal calendar has been changed to annual reporting while the applicable regulatory entry still requires a shorter interval.

The control is therefore not simply maintaining a calendar. It is maintaining a calendar that is traceable to the current regulatory source.

11. Practical Example: Multiple Marketing Authorisations

Several products containing the same active substance are authorised by different MAHs.

The EURD framework can establish a harmonised reporting schedule for the active substance, supporting EU-level assessment of the available safety information.

An individual MAH should therefore assess its own obligations against the applicable EURD entry rather than assuming that its product's historical reporting cycle remains independently applicable.

12. DLP and Data Extraction

The DLP should drive the data-extraction strategy.

The organisation should establish controlled cut-off rules for relevant datasets, including where appropriate:

• ICSR data;
• clinical-study information;
• literature information;
• signal-management records;
• exposure information;
• post-authorisation study findings;
• and regulatory information.

Different systems may have different technical extraction capabilities. The scientific assessment should nevertheless remain anchored to the defined reporting interval and DLP.

13. Information Received Near the DLP

Information may be received shortly before, on, or after the DLP.

The organisation should not use an informal rule such as "received after the DLP means it is excluded" without considering the applicable PSUR requirements and the significance of the information.

The DLP defines the reporting period, but important new safety information may require action through other processes regardless of whether it falls inside the periodic reporting interval.

The PSUR process therefore needs controlled rules for handling information around the cut-off while preserving the distinction between periodic reporting and immediate safety action.

14. Submission Timelines After the DLP

The DLP starts the controlled interval leading to PSUR submission. The applicable submission deadline must be established from the current regulatory schedule rather than calculated from an outdated internal assumption.

For PSURs covering intervals of up to 12 months, EMA's current procedural advice states that the PSUR should be submitted within 70 calendar days of the DLP. For PSURs covering intervals longer than 12 months, the period is 90 calendar days of the DLP. For an ad hoc PSUR requested by a competent authority, the request normally specifies the timeline; if it does not, EMA states that the PSUR should be submitted within 90 calendar days of the DLP. citeturn0search0

These are submission timelines, not the reporting interval itself.

15. Why the 70-Day and 90-Day Rules Matter

The distinction between the two timelines is operationally important.

A team that assumes that every PSUR has a 90-day preparation period can incorrectly plan a PSUR covering 12 months or less. Conversely, applying a 70-day assumption to a PSUR covering more than 12 months creates an unnecessarily short internal schedule.

The project plan should therefore derive the applicable submission period from the defined reporting interval and current regulatory requirements.

16. Submission Deadline in the EURD List

The EURD list provides the applicable submission date for covered active substances and combinations.

EMA states that the deadline published in the EURD list is legally binding and must be adhered to. The PSUR Repository permits submission before the deadline; the existence of a submission window does not remove the legal deadline. citeturn0search0

This distinction is useful in operational planning:

DLP
 ↓
Data extraction
 ↓
Analysis
 ↓
Drafting
 ↓
Medical / functional review
 ↓
Quality control
 ↓
Submission preparation
 ↓
Submission window
 ↓
LEGAL DEADLINE

The organisation should build internal milestones before the legal deadline rather than treating the legal deadline as the target drafting date.

17. Early Submission

A PSUR may be submitted before the applicable deadline where the submission system and procedure permit it.

Early submission can provide contingency time for technical or administrative issues, but it should not be confused with changing the DLP or reporting interval.

The DLP remains the DLP even when the completed PSUR is submitted earlier than the deadline.

18. Missed Submission Deadlines

Missing a PSUR deadline is a compliance issue, not simply a project-management inconvenience.

EMA's current procedural advice states that the MAH is responsible for ensuring submission by the deadline in the EURD list. Where a technical problem with the PSUR Repository causes a missed deadline, the MAH should contact EMA promptly using the applicable process; late submissions cannot necessarily be accepted once the procedure has started. citeturn0search0

An organisation should therefore have an escalation procedure for approaching a potential missed deadline before the deadline is reached.

19. Building the PSUR Project Backwards From the Deadline

A robust PSUR project plan is usually easier to control when built backwards from the regulatory deadline.

For example:

Legal submission deadline
          ↑
Submission readiness
          ↑
Final QC / approval
          ↑
Medical and cross-functional review
          ↑
Scientific assessment complete
          ↑
Data analysis complete
          ↑
Validated data extraction
          ↑
DLP

The exact internal milestones depend on the product, complexity, number of contributors, data systems and governance arrangements.

The important principle is that the regulatory deadline should drive the controlled internal plan.

20. DLP-to-Submission Risk Buffer

A mature process should not consume the entire regulatory period with planned work.

The organisation should establish contingency time for foreseeable problems such as:

• incomplete data extraction;
• reconciliation issues;
• late scientific input;
• quality-control findings;
• regulatory-calendar discrepancies;
• technical submission problems;
• unexpected safety findings;
• and approval delays.

The buffer is an operational control, not an additional regulatory period.

21. Changes to the EURD Schedule

A change to the EURD frequency or DLP can have significant downstream consequences.

EMA states that amendments to the EURD list generally become effective six months after publication. Exceptional situations can require a submission before a new frequency would ordinarily take effect, and the applicable EURD entry should be checked for such instructions. citeturn0search0

The MAH therefore needs a process for assessing every relevant EURD change for impact on:

• open PSUR projects;
• planned PSURs;
• DLPs;
• submission dates;
• staffing;
• contracts;
• and governance calendars.

22. New Marketing Authorisation and First PSUR

The first PSUR following a new marketing authorisation may require additional regulatory-calendar assessment.

EMA's current procedural advice explains that where a substance is not already appropriately represented in the EURD list, the first submission date may be established using the European Birth Date or International Birth Date framework and a new EURD entry may be required. Where the substance is already listed, the applicability of the existing entry must be assessed. citeturn0search0

This is an example of why the PSUR calendar should be linked to regulatory intelligence rather than created once and left unchanged.

23. Fixed-Dose Combinations

Fixed-dose combinations can require specific consideration because the relevant reporting obligation may relate to the combination rather than simply to the individual component substances.

GVP Module VII provides specific provisions for PSUR submission for fixed-dose combinations. The applicable EURD entry and current regulatory requirements should therefore be checked rather than assuming that the schedule of an individual component automatically applies to the combination.

24. Multiple Products and Different Authorisation Holders

A single active substance can be present in multiple medicinal products and be associated with multiple MAHs.

The EU reference-date system is designed to support harmonised periodic reporting and assessment in such circumstances.

For an individual MAH, this means that internal PSUR planning should identify the relevant active-substance entry and understand how its product fits into the applicable EU assessment framework.

25. Nationally Authorised Products

PSUR obligations are not limited to centrally authorised products.

EMA's current guidance states that PSURs for active substances not subject to EU-level EURD assessment still use the PSUR Repository, while the applicable frequency may arise from national requirements or the marketing authorisation where no EURD entry applies. citeturn0search0

The distinction between centralised and nationally authorised products should therefore not be reduced to different submission technology or different internal calendars. The applicable regulatory pathway must be established for each product situation.

26. Regulatory Calendar Reconciliation

The PSUR calendar should periodically be reconciled against authoritative regulatory sources.

A useful control compares:

The objective is not merely to confirm that two dates look similar. The organisation should be able to demonstrate the source from which each controlled date was derived.

27. What Happens When the Internal Calendar Is Wrong?

Suppose an internal system says that a PSUR is due on 30 September, while the current EURD list specifies 31 August.

The regulatory source takes precedence.

The organisation should investigate why the internal record was wrong, determine whether other products or substances may have the same problem, correct the calendar and assess whether the discrepancy created a compliance risk.

This is a quality-system issue as well as a PSUR scheduling issue.

28. Inspection Scenario: The Calendar Has No Source

An inspector asks an MAH why the PSUR DLP is 31 March.

The organisation produces a spreadsheet showing the date but cannot identify the regulatory source from which the date was obtained.

Even if the date happens to be correct, the control is weak because the organisation cannot demonstrate how it established the requirement.

A stronger system can show:

Product / substance
        ↓
Current regulatory source
        ↓
Applicable EURD entry / requirement
        ↓
DLP + frequency + deadline
        ↓
Controlled internal calendar

29. Inspection Scenario: EURD Change Not Assessed

An EURD amendment changes the reporting frequency for an active substance.

The MAH's regulatory intelligence function receives the updated list, but no documented impact assessment is performed. The PV team continues working to the old schedule.

The issue is not simply that one calendar entry was stale. It indicates a broken interface between regulatory intelligence and pharmacovigilance operations.

An effective process should define who reviews the change, who assesses impact, who updates controlled records and how completion is evidenced.

30. Inspection Scenario: DLP Correct, Submission Late

An MAH correctly identifies the DLP but completes internal review only after the submission deadline.

The DLP determination itself may be correct, but the overall PSUR process is not compliant if the legally applicable deadline is missed.

The investigation should therefore consider the complete chain:

• DLP determination;
• project planning;
• resource allocation;
• data availability;
• review capacity;
• approval;
• submission preparation;
• technical submission;
• and escalation.

31. Key Operational Principle

The DLP should be treated as the beginning of a controlled countdown, not the end of a data-collection exercise.

Once the DLP is confirmed, every remaining activity should have a defined owner, expected completion point and escalation route sufficient to protect the regulatory deadline.

32. Governance of PSUR Timelines

Responsibility for PSUR timelines should be explicit.

The organisation should define who is responsible for:

• monitoring regulatory sources;
• determining the applicable reporting schedule;
• maintaining the controlled calendar;
• confirming the DLP;
• initiating the PSUR project;
• monitoring progress;
• escalating schedule risk;
• approving the final report;
• and completing the submission.

These responsibilities may be distributed across Regulatory Affairs, Pharmacovigilance and other functions, but the interfaces must be controlled.

A common failure is to assume that because Regulatory Affairs monitors regulatory dates, Pharmacovigilance does not need independent awareness of a changed PSUR schedule. Conversely, a PV team should not silently maintain its own calendar without reconciliation against the authoritative regulatory source.

33. QPPV Oversight

The QPPV should have sufficient oversight of the PSUR process to understand whether the organisation can meet its regulatory obligations and whether significant schedule risks are being appropriately escalated.

This does not mean that the QPPV must personally maintain every PSUR calendar entry.

The relevant question is whether the PV system provides reliable governance, visibility and escalation.

Evidence can include:

• governance dashboards;
• regulatory-calendar reconciliation;
• escalation records;
• PSUR status reports;
• overdue-action monitoring;
• and documented decisions concerning significant timeline risks.

34. Vendor and Partner Interfaces

PSUR preparation frequently depends on external parties.

Examples include:

• co-development partners;
• licensors;
• distributors;
• contract research organisations;
• literature-monitoring providers;
• safety-data vendors;
• and external medical writers.

A vendor contract does not transfer the MAH's regulatory responsibility for timely PSUR submission.

The MAH should therefore establish timelines that allow sufficient time for receipt, reconciliation and review of partner information before the final submission deadline.

35. Reconciliation With Other Regulatory Activities

The PSUR calendar should be considered alongside other regulatory activities that may affect the safety evaluation.

Potential interfaces include:

• variations;
• referrals;
• safety-related regulatory procedures;
• risk-management commitments;
• PASS milestones;
• product-information changes;
• and regulatory requests for additional information.

A change in one regulatory process can create important information for another. The organisation should therefore have mechanisms for communicating significant developments across the relevant functions.

36. When the DLP Falls Near a Major Regulatory Event

A PSUR DLP can coincide with or occur shortly after another important event, such as:

• a major variation;
• a new indication;
• a regulatory referral;
• a signal-related regulatory action;
• or a significant risk-minimisation change.

The PSUR team should not treat the DLP as an artificial boundary that prevents consideration of important context.

The applicable Module VII requirements should determine how the information is represented in the PSUR, while urgent regulatory or safety processes continue independently where necessary.

37. Post-DLP Information

Information becoming available after the DLP requires controlled handling.

The correct approach is not simply to add every post-DLP observation to the PSUR or to exclude every post-DLP observation automatically.

The organisation should determine:

1. whether the information belongs to the reporting interval;
2. whether it is relevant cumulative information;
3. whether it represents an important new safety issue;
4. whether another immediate process is required;
5. and how it should be documented in the PSUR and associated records.

This assessment should be consistent with current Module VII requirements and controlled procedures.

38. Ad Hoc PSURs

A competent authority may request a PSUR outside the routine schedule.

An ad hoc PSUR should be treated as a specific regulatory request rather than simply inserted into the ordinary PSUR calendar.

EMA's current procedural advice states that the submission timeline will normally be specified in the request; where it is not specified, the PSUR should be submitted within 90 calendar days of the DLP. citeturn0search0

The organisation should capture the request, scope, DLP, deadline, responsible functions and escalation arrangements as controlled records.

39. Submission Through the PSUR Repository

The submission route is itself part of the controlled timeline.

EMA states that use of the PSUR Repository is mandatory for PSUR submissions and that MAHs submit directly to the repository through the eSubmission Gateway. The current technical requirements should be checked against the applicable EMA user guidance. citeturn0search0

A report that is scientifically complete but cannot be submitted correctly because technical preparation was left until the last day is still a process failure.

40. Internal Milestones Should Be Earlier Than the Regulatory Deadline

A defensible timeline should contain internal deadlines that precede the legal submission deadline.

For example:

DLP
 ↓
Data extraction complete
 ↓
Data reconciliation complete
 ↓
Scientific assessment complete
 ↓
Draft complete
 ↓
Medical / functional review
 ↓
QA / QC
 ↓
Final approval
 ↓
Technical submission readiness
 ↓
Contingency window
 ↓
Regulatory deadline

The number and duration of these milestones should be risk-based and appropriate to the complexity of the PSUR.

41. Timeline Metrics

Useful process metrics can include:

• percentage of PSURs submitted by the regulatory deadline;
• percentage submitted with the planned internal buffer;
• number of calendar discrepancies detected;
• number of EURD changes assessed within the required internal period;
• number of timeline escalations;
• number of late partner inputs affecting the critical path;
• and number of technical submission failures.

Metrics should be used to identify systemic weaknesses rather than simply to demonstrate that reports were eventually submitted.

42. Common Timeline Failures

Failure 1: Using the previous PSUR as the calendar source

The previous report is used to populate the next DLP and deadline without checking the current EURD entry.

Control: reconcile every applicable PSUR schedule against the current authoritative source.

Failure 2: Treating the DLP as the submission date

The team schedules completion on the DLP itself.

Control: establish a separate submission timeline beginning from the DLP.

Failure 3: Applying 90 days to every PSUR

The team does not distinguish reporting intervals of up to 12 months from longer intervals.

Control: derive the applicable submission period from the reporting interval and current guidance.

Failure 4: No contingency

The final approval or technical submission is scheduled on the legal deadline.

Control: establish an internal buffer and escalation threshold.

Failure 5: Regulatory change not communicated

Regulatory Affairs identifies an EURD change but the PSUR team continues with the old schedule.

Control: formal regulatory-intelligence-to-PV interface and documented impact assessment.

Failure 6: Vendor deadline equals regulatory deadline

An external contributor is contractually expected to deliver information on the same day the PSUR is due.

Control: contractual and operational milestones must precede the MAH's internal review and submission deadlines.

43. Inspection-Ready Evidence

A mature PSUR timeline should allow an inspector to trace the process from the regulatory source to the submitted report.

A useful evidence chain is:

Current regulatory requirement
          ↓
EURD / applicable schedule
          ↓
Controlled DLP and deadline
          ↓
PSUR project plan
          ↓
Data and review milestones
          ↓
Escalations / deviations
          ↓
Final approval
          ↓
Submission evidence

The objective is not to create documentation for its own sake. Each record should answer a meaningful control question.

44. Practical Case: The Seven-Day Problem

Imagine that an MAH's internal process reserves the final seven days before submission for approval.

A major review issue is identified during that period, requiring substantial revision.

If no contingency exists, the organisation may be forced to choose between inadequate review and a late submission.

A better design places meaningful review and approval milestones sufficiently before the regulatory deadline to permit correction of foreseeable problems.

45. Practical Case: A Change Published During Preparation

An EURD amendment is published while a PSUR is already being prepared.

The team should not assume automatically that the new schedule applies immediately. EMA states that EURD amendments generally become effective six months after publication, although exceptional circumstances may be specified in the applicable entry. citeturn0search0

The change should therefore undergo a documented impact assessment against the effective date and any specific instructions.

46. Practical Case: A Late Safety Finding

A clinically important safety finding is identified shortly before the planned submission.

The organisation should determine whether the finding requires immediate action independently of the PSUR and how it should be incorporated into the periodic assessment.

The correct response is not to delay urgent action until the PSUR is finalised merely because the report is already in drafting.

47. Final Decision Framework

For every PSUR, the organisation should be able to answer six questions:

1. What is the applicable reporting interval?
2. What is the authoritative DLP?
3. What is the legally applicable submission deadline?
4. How was each date established and reconciled?
5. What internal milestones protect the regulatory deadline?
6. What escalation occurs if the critical path is threatened?

If these questions cannot be answered from controlled records, the timeline process is not sufficiently robust.

Key Takeaways

• The DLP defines the end of the PSUR reporting interval; it is not the submission deadline.
• The current EURD list should be used where applicable to determine frequency, DLP and submission date.
• EURD changes generally become effective six months after publication, subject to applicable exceptions.
• PSURs covering intervals up to 12 months have a 70-calendar-day submission period from the DLP; intervals exceeding 12 months have a 90-calendar-day period under current EMA procedural guidance. citeturn0search0
• The EURD deadline is legally binding even though the repository permits earlier submission.
• Missing a deadline is a compliance issue requiring escalation and investigation.
• Internal milestones should precede the legal deadline and include contingency.
• Regulatory-intelligence, PV, Regulatory Affairs, vendors and partners require controlled interfaces.
• The MAH remains responsible for timely submission even when external parties contribute to PSUR preparation.
• Inspection readiness means being able to trace the submitted PSUR back to the authoritative regulatory schedule and controlled project plan.

References

1. European Medicines Agency. Periodic safety update reports (PSURs). Current EMA webpage, including submission requirements, EURD list information and post-authorisation procedural advice.
2. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module VII — Periodic safety update report.
3. European Medicines Agency. List of European Union reference dates (EURD) and frequency of submission of PSURs, current revision.
4. European Medicines Agency. Introductory cover note to the List of European Union reference dates and frequency of submission of PSURs, current revision.
5. European Medicines Agency. European Medicines Agency post-authorisation procedural advice for users of the centralised procedure, current revision.
6. European Commission. Commission Implementing Regulation (EU) No 520/2012, as amended.
7. European Parliament and Council. Directive 2001/83/EC, as amended.
8. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article is an educational explanation of PSUR reporting intervals, data lock points and submission timelines. It does not replace current GVP Module VII, applicable EU legislation, the current EURD list, EMA procedural guidance, PSUR Repository requirements or an organisation's approved procedures.

Regulatory schedules and technical submission requirements can change. Before preparing or submitting a PSUR, the current applicable regulatory sources and effective dates should be verified.

The timeline examples are illustrative. They do not establish regulatory deadlines independently of the applicable current regulatory source.