SOP-502

Unanticipated Problems and Reportable New Information

Number
SOP-502
Category
Safety
Edition
Reference Edition 1.3
Approx. pages
7

[YELLOW] the site fills in. [DEFAULT: green] a value the site may keep or change.

On this page

1. Purpose

This SOP describes how [SITE NAME] identifies, assesses and reports to the IRB unanticipated problems involving risks to participants or others, and other information the IRB requires investigators to report promptly (commonly called reportable new information).

2. Scope

This SOP applies to all trials overseen by an IRB at [SITE NAME], whether a central IRB ([CENTRAL IRB NAME]) or another IRB of record. It covers events, findings and information from any source: site observations, monitoring, sponsor communications, audits, inspections, complaints and privacy incidents.

Out of scope: investigator-to-sponsor SAE reporting (SOP-501), routine IRB submissions such as amendments and continuing review (SOP-203), and detailed procedures for deviations (SOP-308), privacy incidents (SOP-400), audits and inspections (SOP-701, SOP-702), and misconduct (SOP-704). Those SOPs point here for the IRB report.

The IRB's own written policy defines what to report and when. Follow the IRB's policy, and the protocol or sponsor requirement, where it is stricter than or more specific than this SOP. Where this SOP and the IRB policy differ, the IRB policy governs IRB reporting.

3. Responsibilities

RoleResponsibilities
Principal Investigator (PI)Determines whether information meets the IRB's reporting criteria, signs the assessment, approves the IRB submission, and decides on actions to protect participants.
Sub-Investigator (Sub-I)Contributes medical assessment of events when delegated; acts for the PI on urgent participant protection when the PI is unavailable.
Regulatory CoordinatorKeeps the current IRB reportable-event policy on file, opens F-502-01, prepares and submits reports in the IRB system within the IRB window, files IRB determinations, and tracks requested actions.
Clinical Research Coordinator (CRC)Identifies potentially reportable information and brings it to the Regulatory Coordinator and PI the same day; supplies the facts for F-502-01.
Site DirectorIs informed of every report; arranges resources for corrective actions; notifies the business owner, insurer or counsel where the event has legal or business impact.
Quality LeadReviews F-502-01 trends, links reports to deviations and CAPA (SOP-703), and checks timeliness in QC.
All Research StaffReport possible problems, complaints and incidents to the CRC, Regulatory Coordinator or PI the same day they become aware.

4. Definitions

TermDefinition
Unanticipated problem involving risks to participants or others (UP)Any incident, experience or outcome that meets all three criteria: (1) unexpected in nature, severity or frequency, given the research procedures described in IRB-approved documents and the characteristics of the population studied; (2) related or possibly related to participation in the research; and (3) suggests that the research places participants or others at greater risk of harm (physical, psychological, economic or social) than was previously known or recognized (OHRP 2007 guidance). Seriousness is not one of the criteria.
Reportable new informationThe IRB's term for the categories of information that investigators must report promptly. Categories and timelines are set by each IRB's policy.
Adverse Event (AE)Any unfavorable medical occurrence in a trial participant administered the investigational product, whether or not related (see SOP-500).
Unanticipated Adverse Device Effect (UADE)As defined in 21 CFR 812.3(s); see SOP-501.
NoncomplianceFailure to follow the regulations, the protocol, GCP, IRB requirements or determinations, or this site's SOPs. Serious noncompliance and continuing noncompliance are as defined in the IRB's policy.
Protocol deviationAny change, divergence or departure from the study design or procedures in the protocol (see SOP-308).
Immediate hazardA situation in which a participant faces an immediate risk to life or health that requires a change in procedures before IRB approval can be obtained.
Breach of confidentialityUnauthorized acquisition, access, use or disclosure of participant information (see SOP-400).
IRB reporting windowThe time allowed by the IRB's policy between the investigator becoming aware of the information and submission to the IRB.

5. Procedure

5.1 Know the IRB's policy

5.1.1
For each IRB the site uses, the Regulatory Coordinator files the IRB's current investigator manual or reportable-event policy in the regulatory binder and records on the study page of F-502-01:
  • the IRB's reportable categories
  • the reporting window and whether it counts calendar or business days
  • the submission route (IRB portal form name)
  • any events the IRB states it does not want reported
5.1.2
The Regulatory Coordinator checks the IRB policy at least [DEFAULT: annually and at each study start] and updates F-502-01 when it changes.
5.1.3
There is no general FDA or IRB rule that every SAE goes to the IRB within 24 hours. The site does not submit routine SAEs to the IRB unless the event meets the IRB's criteria (usually, it is a UP) or the IRB's policy requires it.

5.2 Regulatory basis

5.2.1
FDA regulations require the investigator to promptly report to the IRB all unanticipated problems involving risks to human subjects or others (21 CFR 312.66) and require IRBs to have written procedures for prompt reporting of such problems, serious or continuing noncompliance, and suspensions or terminations (21 CFR 56.108(b)).
5.2.2
Device investigators have specific reporting duties to the sponsor and IRB under 21 CFR 812.150(a):
  • UADE: to sponsor and IRB as soon as possible, no later than 10 working days after first learning of it ((a)(1))
  • emergency deviation from the investigational plan to protect the life or physical well-being of a participant: to sponsor and IRB as soon as possible, no later than 5 working days after the emergency ((a)(4))
  • use of a device without informed consent: to sponsor and IRB within 5 working days after the use ((a)(5))
  • withdrawal of IRB approval: to the sponsor within 5 working days ((a)(2))
5.2.3
For federally funded research, 45 CFR 46.108(a)(4) requires IRBs to have equivalent written procedures for prompt reporting, and the IRB's policy sets the investigator's duty. Most industry trials at [SITE NAME] are FDA-regulated only.
5.2.4
FDA's final guidance "Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices" (December 2025) replaced FDA's 2009 guidance on AE reporting to IRBs. It states the following for IND studies (FDA guidance Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices, December 2025, section VI):
  • IND safety reports received from the sponsor describe UPs, and the investigator must submit them to the IRB (21 CFR 312.66). Where the sponsor submits them to the IRB on the investigator's behalf and the investigator has confirmation that it did, FDA does not expect a duplicate; the arrangement is documented (SOP-501 5.10.4).
  • In IND-exempt BA/BE studies, any SAE is a UP that must be reported to the IRB.
  • Events that do not meet IND safety reporting criteria may still be UPs that must be reported. They may occur at the participant, site or study level, for example serious and unexpected AEs before IP administration, during a washout period or attributable to a screening procedure, medication errors (such as a wrong dose or contaminated study medication), breaches of privacy or confidentiality, and untimely destruction of study records.
  • The IRB's written procedures may require other events in addition.
5.2.5
Individual AEs at the site that are not the subject of an IND safety report are reported to the IRB only when the PI determines they meet the UP criteria (5.5) or the IRB's policy lists them. The IRB's written procedures govern format and timing. If an IRB's policy says it does not accept individual IND safety reports from investigators, the Regulatory Coordinator obtains the IRB's written instruction for the study and files it with F-502-01.

5.3 Categories of reportable new information

5.3.1
Central IRBs typically require prompt reporting of the categories below. The IRB's own list governs; the Regulatory Coordinator adapts this list on F-502-01 for each IRB.
  • information indicating a new or increased risk, or a UP, including AEs that are unexpected and related or possibly related and that suggest greater risk
  • IND safety reports, unless the sponsor submits them on the investigator's behalf (5.2.4), and other sponsor safety information (SUSAR line listings, DSMB reports) that requires a change to the protocol or consent form, or that the IRB policy otherwise requires
  • UADEs
  • protocol deviations that harmed a participant or placed a participant at increased risk of harm, including monitoring findings that materially affect participant safety
  • changes made without prior IRB approval to eliminate an apparent immediate hazard to a participant
  • allegations or findings of noncompliance that may be serious or continuing, and any other noncompliance the IRB's policy lists
  • audits, inspections or inquiries by a federal agency, and written reports from those agencies (for example, FDA Form 483)
  • breaches of confidentiality or loss of participant data
  • participant complaints that indicate unexpected risk or that the site cannot resolve
  • incarceration of a participant in a study not approved for prisoner involvement
  • premature suspension or termination of the study by the sponsor, investigator or site
  • state medical board or licensing actions against an investigator
  • any other information the sponsor or protocol requires to be reported promptly to the IRB

5.4 Identifying potentially reportable information

5.4.1
Any staff member who becomes aware of information that may fall into section 5.3 informs the Regulatory Coordinator and the PI the same day. The awareness date is the date any member of the research staff first received the information.
5.4.2
Sources to watch include AE and SAE assessments (SOP-500, SOP-501), sponsor safety reports (SOP-501 section 5.10), deviation logs (SOP-308), monitoring follow-up letters (SOP-600), audit and inspection outcomes (SOP-701, SOP-702), privacy incident reports (SOP-400), and participant complaints.
5.4.3
The Regulatory Coordinator opens F-502-01 and records the awareness date, description and source of the information.

5.5 Assessment and PI determination

5.5.1
The PI (or a delegated Sub-I for medical events) assesses the information against the IRB's categories on F-502-01. For events that could be UPs, the PI answers and documents each question:
  • Is it unexpected, given the IRB-approved protocol, consent form, IB and the characteristics of the population?
  • Is it related or possibly related to participation in the research (IP or study procedures)?
  • Does it suggest that participants or others are at greater risk of harm than previously known?
5.5.2
If all three answers are yes, the event is a UP and is reported. If any answer is no, the PI records the rationale and the event is not reported as a UP (it may still fall into another reportable category).
5.5.3
The PI may consult the sponsor's medical monitor. If the sponsor has concluded that an event is a UP, or that safety information requires a protocol or consent change, the PI treats it as reportable.
5.5.4
The PI signs and dates F-502-01 with the determination: reportable (category stated) or not reportable (rationale stated). The PI makes this determination early enough to submit within the IRB window.

5.6 Immediate protective actions

5.6.1
Where participants face an immediate hazard, the PI acts first and reports afterwards. The PI may change procedures without prior IRB approval only to eliminate an apparent immediate hazard (21 CFR 312.66; ICH E6(R3) Annex 1, 2.5.4).
5.6.2
The PI informs the sponsor promptly of any change made to eliminate an immediate hazard and reports the hazard, the change and any proposed amendment to the IRB (ICH E6(R3) Annex 1, 2.5.4 and 2.5.5).
5.6.3
The PI decides with the sponsor whether to pause enrollment or dosing, add safety assessments, or contact enrolled participants. Medically necessary treatment is decided in the participant's best interest, regardless of protocol limits.

5.7 Sponsor coordination

5.7.1
The Regulatory Coordinator informs the sponsor (or CRO) of any reportable event before or at the time of IRB submission, unless the event concerns the sponsor's own conduct and the PI decides otherwise.
5.7.2
Where the sponsor submits certain categories to a central IRB on behalf of all sites, the Regulatory Coordinator obtains written confirmation of what the sponsor will submit and files it. The site remains responsible for site-specific events (site deviations, site privacy incidents, complaints, site inspections).
5.7.3
The site does not wait for sponsor agreement to report a site-specific event within the IRB window. Where the sponsor and PI disagree on reportability, the PI's determination governs the site's IRB report and the disagreement is recorded on F-502-01.

5.8 Submission to the IRB

5.8.1
The Regulatory Coordinator prepares the IRB submission on the IRB's form, including:
  • a factual description of the event or information and the date of awareness
  • the PI's assessment and the basis for it
  • actions taken or planned (including any change to protocol, consent or procedures, and whether participants need to be told)
  • whether the sponsor has been informed
5.8.2
The submission uses participant IDs, not names or other direct identifiers, unless the IRB asks otherwise.
5.8.3
The PI reviews and approves the submission (signature in the IRB system or on F-502-01). The Regulatory Coordinator submits within the IRB window and records the submission date on F-502-01.
5.8.4
If a submission is late, the report includes the reason for delay. The late report is also recorded as a deviation (SOP-308).
5.8.5
If information is incomplete at the deadline, the Regulatory Coordinator submits what is known and follows up as information becomes available.

5.9 After submission

5.9.1
The Regulatory Coordinator files the submission, IRB acknowledgment and IRB determination in the ISF (SOP-204), and sends a copy of the determination to the sponsor where the sponsor requests it.
5.9.2
The Regulatory Coordinator tracks every IRB-required action (for example, reconsent, consent revision, additional training, corrective action plan) on F-502-01 until closed. Consent revisions follow SOP-301 and SOP-203.
5.9.3
Where the IRB finds serious or continuing noncompliance, or suspends or terminates approval, the PI informs the sponsor promptly (ICH E6(R3) Annex 1, 2.6.4), and for device studies within 5 working days of withdrawal of approval (21 CFR 812.150(a)(2)). The Site Director and Quality Lead open a CAPA (SOP-703).
5.9.4
The Quality Lead reviews F-502-01 for trends, timeliness and open actions as part of the quarterly metrics review in SOP-700 5.7.1.
  • F-502-01 Reportable New Information Assessment
  • F-308-01 Protocol Deviation Log
  • F-400-01 Privacy Incident Report
  • F-703-01 CAPA Record
  • SOP-203 IRB Submissions, Approval and Continuing Oversight
  • SOP-204 Essential Documents and the Investigator Site File
  • SOP-301 Informed Consent Process and Documentation
  • SOP-308 Protocol Deviations and Noncompliance
  • SOP-400 Participant Privacy and HIPAA in Research
  • SOP-500 Adverse Event Identification, Assessment and Recording
  • SOP-501 Serious Adverse Event and Expedited Safety Reporting
  • SOP-600 Sponsor Monitoring Visits
  • SOP-701 Sponsor and IRB Audits
  • SOP-702 FDA Inspections and Remote Regulatory Assessments
  • SOP-703 Corrective and Preventive Action (CAPA)
  • SOP-704 Research Misconduct and Fraud Reporting
  • SOP-903 Network Oversight of Member Sites (Metrics, Central QA, Escalation) (Model N only)
  • SOP-905 Network Data, Systems, Privacy and Records Across Sites (Model N only)
  • Appendix B Central and Site Responsibility Matrix (Model N only)

7. References

ReferenceTitle
21 CFR 56.108(b)IRB Functions and Operations: Prompt Reporting
21 CFR 312.66Assurance of IRB Review
21 CFR 812.3(s)Definition: Unanticipated Adverse Device Effect
21 CFR 812.150(a)Investigator Reports
45 CFR 46.108(a)(4)IRB Functions and Operations (federally funded research)
ICH E6(R3) Annex 1, 2.4.6Communication with IRB/IEC: Changes Affecting Conduct or Increasing Risk
ICH E6(R3) Annex 1, 2.5.4, 2.5.5Compliance with Protocol: Immediate Hazards
ICH E6(R3) Annex 1, 2.6Premature Termination or Suspension of a Trial
FDA Guidance (December 2025)Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices
OHRP Guidance (2007)Reviewing and Reporting Unanticipated Problems Involving Risks to Subjects or Others and Adverse Events
[CENTRAL IRB NAME]Investigator Manual / Reportable New Information Policy (current version)

Independent Site SOP Library. Licensed CC BY-NC 4.0 by the American Institute for Medical Research (AIMR), with added permission for any site's internal use (license terms). Not legal advice: each adopting site confirms state law, IRB and sponsor requirements with its own counsel and owns every step it approves.