Published on 22/12/2025
Why Missing SUSAR Documentation Remains a Critical Audit Finding
Introduction: The Role of SUSAR Documentation in Clinical Trials
Suspected Unexpected Serious Adverse Reactions (SUSARs) represent one of the most significant aspects of clinical trial safety oversight. Regulatory agencies such as the FDA, EMA, and MHRA require timely reporting and complete documentation of all SUSARs as part of pharmacovigilance systems. Missing SUSAR documentation during audits signals serious compliance failures and raises concerns about both patient safety and sponsor oversight.
When auditors identify missing SUSAR reports, incomplete narratives, or undocumented follow-up actions, they classify them as major or critical findings. These deficiencies undermine the sponsor’s ability to demonstrate regulatory compliance and can result in inspection findings, warning letters, or even clinical hold decisions. For example, in one FDA inspection, failure to submit five fatal SUSARs within the expected timeframe led to a Form 483 observation and subsequent sponsor remediation plan.
Regulatory Expectations for SUSAR Documentation
Agencies emphasize strict adherence to timelines and comprehensive documentation. Key expectations include:
- ✔️ SUSARs must be reported within 7 days (fatal/life-threatening) or 15 days (non-fatal serious).
- ✔️ Complete case narratives must accompany all SUSAR submissions.
- ✔️ Sponsors remain fully accountable, even if CROs are contracted
The table below illustrates sample regulatory requirements:
| Requirement | Timeline | Responsible Party |
|---|---|---|
| Fatal/Life-Threatening SUSAR | 7 calendar days | Sponsor |
| Serious Non-Fatal SUSAR | 15 calendar days | Sponsor |
| SUSAR Narrative | Submitted with SUSAR | Sponsor/CRO |
| DSUR (annual cumulative safety report) | Yearly | Sponsor |
Common Audit Findings Related to SUSAR Documentation
1. Missing Narratives
One of the most frequent findings is incomplete or absent SUSAR narratives. Regulators expect full medical details, chronological sequence of events, and follow-up actions. Missing narratives suggest poor quality control within pharmacovigilance systems.
2. Delayed Documentation
Even if SUSARs are reported within the regulatory timeframe, delays in preparing and filing documentation are often flagged. In some audits, follow-up laboratory results or autopsy findings were never incorporated into SUSAR reports.
3. Discrepancies Across Systems
Regulators frequently identify inconsistencies between EDC entries, case report forms (CRFs), and safety databases. Such discrepancies indicate inadequate reconciliation, leading to incomplete or missing SUSAR records.
4. CRO Oversight Failures
When pharmacovigilance responsibilities are outsourced, sponsors sometimes fail to monitor CRO performance. Missing SUSARs often reflect oversight gaps where CROs failed to process or report cases adequately, and sponsors did not audit or monitor them.
Case Study: EMA Audit Finding on Missing SUSARs
In an inspection of a European Phase II oncology trial, EMA auditors found that 12 SUSARs were absent from the TMF (Trial Master File) and safety database. These included three life-threatening cases. The EMA classified this as a critical finding, requiring immediate CAPA and enhanced sponsor oversight. Detailed observations were published in the EMA’s annual GCP inspection findings report.
Root Causes Behind Missing SUSAR Documentation
Root cause analysis of missing SUSARs typically identifies systemic and operational weaknesses such as:
- ➤ Lack of SOP alignment with current ICH E2A and E2D pharmacovigilance requirements.
- ➤ Over-reliance on manual tracking instead of automated safety database systems.
- ➤ Inadequate communication between investigators, CROs, and sponsor safety teams.
- ➤ Insufficient reconciliation practices across multiple reporting systems.
- ➤ Resource constraints within sponsor pharmacovigilance departments.
Corrective and Preventive Actions (CAPA)
Corrective Actions
- ✔️ Perform retrospective reconciliation of SUSARs across CRFs, safety databases, and TMFs.
- ✔️ Submit corrective SUSAR narratives with missing details to regulatory authorities.
- ✔️ Conduct internal audits of CRO pharmacovigilance operations.
Preventive Actions
- ✔️ Implement automated SUSAR case tracking and alerts within pharmacovigilance systems.
- ✔️ Update SOPs to include reconciliation timelines and escalation pathways.
- ✔️ Define performance metrics for CRO pharmacovigilance functions.
- ✔️ Provide regular training to investigators and PV staff on SUSAR reporting requirements.
Best Practices for Ensuring Complete SUSAR Documentation
- Integrate Systems: Ensure seamless data exchange between EDC, safety, and clinical databases.
- Perform Regular Reconciliation: Conduct quarterly reconciliations of SUSAR reports across systems.
- Maintain Robust TMF Practices: Ensure all SUSAR records are included in the Trial Master File.
- Oversight of CROs: Sponsors should audit CRO pharmacovigilance teams regularly.
- Mock Regulatory Audits: Test readiness by simulating inspections focused on SUSAR documentation.
Audit Readiness Checklist for SUSAR Documentation
The following checklist can be used by sponsors and CROs:
- ✔️ All SUSARs reported within regulatory timelines.
- ✔️ Complete narratives filed and available for inspection.
- ✔️ Documentation reconciled across all databases and CRFs.
- ✔️ Contracts with CROs define SUSAR responsibilities clearly.
- ✔️ DSURs include cumulative SUSAR reporting with full accuracy.
Conclusion: Avoiding Critical Audit Findings
Missing SUSAR documentation is not simply a clerical issue—it represents a significant risk to patient safety and regulatory compliance. Sponsors remain ultimately accountable, and regulators treat missing or incomplete SUSAR records as critical findings. By implementing robust oversight systems, performing timely reconciliations, and enforcing accountability across all partners, organizations can avoid repeat findings and strengthen safety management in clinical development.
For ongoing reference, sponsors may consult the Australian New Zealand Clinical Trials Registry which publishes safety-related compliance expectations in trial listings and supports transparency in safety reporting.