SOP-203

IRB Submissions, Approval and Continuing Oversight

Number
SOP-203
Category
Start-up and Regulatory
Edition
Reference Edition 1.3
Approx. pages
8

[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] obtains IRB approval before a study starts, keeps approval current without a lapse, submits changes and reports, uses only IRB-approved materials, and closes the study with the IRB. FDA regulations prohibit starting a clinical investigation subject to 21 CFR 56 until an IRB has approved it and the study remains subject to continuing review. ICH E6(R3) expects documented, dated IRB approval of the protocol, consent materials, recruitment procedures and other participant information before the trial begins.

2. Scope

This SOP applies to all human-subjects research conducted at or by [SITE NAME], at all locations, from the first IRB submission through study closure. It covers central (commercial) IRBs, which are the default for the site, and local or institutional IRBs and reliance arrangements where a sponsor, funder or affiliated institution requires them.

Reportable events (unanticipated problems, protocol deviations requiring IRB reporting, new safety information) are reported to the IRB under SOP-502 and SOP-308; this SOP covers only how the submission is made and recorded. Consent form content and process are in SOP-301; recruitment materials are in SOP-300. Where a sponsor, CRO or IRB requirement is stricter than this SOP, the site follows the stricter requirement. Each IRB's written policies (investigator manual, reporting policy) are part of the requirements the site follows.

3. Responsibilities

RoleResponsibilities
Principal Investigator (PI)Holds responsibility for IRB approval and compliance. Reviews and signs (or electronically approves) each site submission. Implements no change without IRB approval except to eliminate an apparent immediate hazard. Reports to the IRB as its policies require.
Regulatory CoordinatorPrepares and submits site submissions, tracks deadlines and approval expiration, distributes approved documents, retires superseded versions, and files all IRB records in the ISF.
Lead CRC / CRCUses only current IRB-approved consent forms and participant materials. Tells the Regulatory Coordinator about events or changes that may need IRB submission. Supplies enrollment and event data for continuing review reports.
Site DirectorConfirms the IRB of record for each study, approves use of a local IRB or reliance arrangement, and maintains any site-level IRB registration or account.
Quality LeadChecks IRB approval status and document versions during QC (SOP-700). Reviews any lapse or use of an unapproved document as a deviation and CAPA (SOP-703).

4. Definitions

TermDefinition
Institutional Review Board (IRB)A board, committee or other group formally designated to review, approve the initiation of and conduct periodic review of research involving human subjects (21 CFR 56.102(g)).
Central IRBAn IRB that serves as the IRB of record for multiple sites in a study; for independent sites usually a commercial IRB such as [CENTRAL IRB NAME].
IRB of recordThe IRB responsible for review and oversight of the study at [SITE NAME].
Reliance agreementA written agreement (IRB authorization agreement) under which one organization relies on another's IRB for review.
Initial reviewThe IRB's first review of the study and of the site's participation, ending in approval, approval with conditions (modifications required), deferral or disapproval.
Amendment (modification)Any change to the approved protocol, consent form, participant materials, investigators or site information that needs IRB review before use.
Continuing reviewPeriodic re-review of approved research. Required at least annually for FDA-regulated research (21 CFR 56.109(f)).
Check-in (status report)A periodic status report some IRBs require for research that no longer needs formal continuing review under the 2018 Common Rule.
Lapse in approvalThe period after IRB approval expires and before it is renewed.
Immediate hazardA situation in which a participant faces imminent risk of harm, justifying a change before IRB approval.
Common Rule45 CFR 46 Subpart A (2018 revision), which applies to research conducted or funded by HHS and other signatory federal agencies.

5. Procedure

5.1 Identify the IRB of record

5.1.1
During start-up the Regulatory Coordinator confirms with the sponsor which IRB will review the study and records it on F-205-01.
5.1.2
The default for [SITE NAME] is the central IRB chosen by the sponsor. The Site Director approves use of any other IRB.
5.1.3
A local or institutional IRB, or a reliance agreement, is needed in these cases:
  • the study is federally funded cooperative research under the Common Rule, which requires a single IRB (45 CFR 46.114); the site may need a Federalwide Assurance (FWA) and must sign the reliance agreement the single IRB requires
  • the investigator or a location is part of a hospital or health system that requires its own IRB review or acknowledgment before its patients, facilities or staff are used
  • a state law or sponsor requires local review
5.1.4
Where a reliance agreement is used, the Site Director (or authorized signatory) signs it, and the Regulatory Coordinator records on F-205-01 which IRB is the IRB of record and what local requirements (for example an ancillary review, local context information) the site must still meet. The signed agreement is filed in the ISF.

5.2 Initial submission

5.2.1
For central IRB studies the sponsor usually submits the protocol, IB and master consent form, and the site submits a site-specific (investigator) submission. The Regulatory Coordinator confirms with the sponsor which documents each party submits so nothing is missed or submitted twice.
5.2.2
The Regulatory Coordinator assembles the site submission. Typical contents, per IRB requirements:
  • IRB investigator or site application form
  • PI CV and medical license; Sub-I information if the IRB requires it
  • Form FDA 1572 or investigator agreement, if the IRB requests it
  • site-specific consent form and HIPAA authorization (combined or separate) with site contact details and costs and injury language consistent with the CTA (SOP-201) and coverage analysis (SOP-202)
  • site recruitment materials and scripts (SOP-300)
  • participant-facing materials, translations and translation certificates
  • training documentation (human subjects protection, GCP) if requested
  • conflict of interest disclosures (SOP-104)
  • any local context information (state law on LAR, minors, age of majority from Appendix A)
5.2.3
The PI reviews and approves the submission before it is sent. If the IRB portal requires the PI's electronic signature, the PI signs it personally; staff do not use the PI's credentials.
5.2.4
The Regulatory Coordinator submits through the IRB portal, saves the submission confirmation, and logs the submission in [IRB TRACKER] with the submission date and contents.

5.3 IRB response and approval

5.3.1
When the IRB requests modifications or information, the Regulatory Coordinator coordinates the response with the PI and sponsor and submits it within the time the IRB sets, or within [DEFAULT: 5 business days] if the IRB sets none.
5.3.2
On approval, the Regulatory Coordinator checks the approval letter and approved documents for:
  • correct protocol number, version and date
  • correct PI and site address(es); every location where study procedures will occur is listed
  • approved consent form version(s) and languages, with IRB approval stamp or approval footer
  • approved recruitment materials
  • approval date and, where applicable, expiration date or next continuing review or check-in date
  • any conditions or restrictions
5.3.3
The Regulatory Coordinator reports errors to the IRB for correction before using the documents.
5.3.4
The Regulatory Coordinator files the approval and approved documents in the ISF (SOP-204), sends copies to the sponsor as required, records the approval on F-205-01 and enters the next review date in [IRB TRACKER].
5.3.5
No participant is consented or enrolled, and no study-specific procedure is done, before IRB approval and study activation (SOP-205). Pre-screening follows the single rule in SOP-300, section 5.10: record review for feasibility under the HIPAA preparatory-to-research provision may happen before activation, while contact with a candidate about the study and use of recruitment materials wait for IRB approval of those materials, and pre-screening logs (F-300-01) start on or after the IRB approval date. Use of a recruitment material before IRB approval is a deviation.

5.4 Using IRB-approved materials only

5.4.1
The Regulatory Coordinator distributes approved consent forms and participant materials to the study team and records the version and effective date on F-301-02.
5.4.2
The Regulatory Coordinator removes superseded versions from every place they could be used: clinic folders, shared drives, eConsent platforms and printed stock. Superseded versions are marked superseded and retained in the ISF.
5.4.3
Before each consent discussion the person obtaining consent checks that the form is the current approved version (SOP-301).
5.4.4
Staff do not alter IRB-approved documents, including formatting, logos or contact details, without IRB approval.

5.5 Amendments and other changes

5.5.1
Changes to the protocol, consent form, participant materials, recruitment materials, PI, site locations, or other items the IRB requires to be reported are submitted for IRB approval before they are implemented.
5.5.2
The sponsor typically submits protocol amendments and master consent revisions to a central IRB; the Regulatory Coordinator submits site-specific changes (site consent revisions, new locations, new site advertising, PI change, Sub-I changes if the IRB requires them).
5.5.3
A change may be implemented before IRB approval only when necessary to eliminate an apparent immediate hazard to participants. The PI reports the change and its reason to the sponsor promptly and to the IRB within the time its policy requires, and the Regulatory Coordinator records the event under SOP-308.
5.5.4
Administrative or logistical changes (for example a new monitor or sponsor phone number) that the IRB does not require to be submitted are documented in the ISF with a note to file (F-306-01).
5.5.5
When an amendment is approved, the Regulatory Coordinator follows 5.3.2 to 5.3.4 and 5.4. The Lead CRC confirms the study team is trained on the change before it is implemented (SOP-103) and that participants are re-consented if the IRB requires it (SOP-301).
5.5.6
21 CFR 312.66 requires the investigator to report unanticipated problems to the IRB; FDA's December 2025 investigator safety reporting guidance (Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices, section VI) states FDA considers IND safety reports (21 CFR 312.32(c)) to be unanticipated problems, so the investigator submits them to the IRB. Where the sponsor submits them to the IRB on the investigator's behalf, the Regulatory Coordinator files the written arrangement and the sponsor's confirmation of each submission, and the site does not submit a duplicate. The IRB's procedures set the format and timing. Where the IRB states in writing that it will not accept them, the Regulatory Coordinator files that instruction (SOP-502, 5.2.5). Other new safety information from the sponsor (for example IB updates) is submitted when the IRB's policy requires it. The Regulatory Coordinator follows SOP-502 and files every safety report received in the ISF.

5.6 Continuing review, check-ins and avoiding a lapse

5.6.1
The Regulatory Coordinator tracks every study's next continuing review or check-in date in [IRB TRACKER] and sets reminders at [DEFAULT: 60 and 30 days] before the IRB's submission deadline.
5.6.2
The requirement depends on the regulations that apply:
  • FDA-regulated studies (21 CFR 56): continuing review at intervals appropriate to the degree of risk, not less than once per year. This applies even when the study is closed to enrollment or only in follow-up, until the study is closed with the IRB.
  • Studies subject only to the 2018 Common Rule: continuing review is not required for minimal-risk research approved by expedited review, or for research that has progressed to data analysis or to accessing follow-up clinical data from procedures that are part of clinical care, unless the IRB decides otherwise and documents why (45 CFR 46.109(f)). The IRB may require a periodic check-in instead.
  • Studies subject to both: the stricter FDA requirement applies.
5.6.3
For studies that do not need continuing review, the IRB may issue an approval with no expiration date and ask for periodic status reports instead. FDA-regulated studies always have a continuing review date. The Regulatory Coordinator follows the date and form the IRB sets for each study.
5.6.4
The Regulatory Coordinator prepares the continuing review or check-in submission with data from the Lead CRC, such as: number enrolled, withdrawn and completed; summary of AEs and unanticipated problems; deviations; complaints; relevant new information; consent issues; and any change in investigator financial interests. The PI reviews and approves it.
5.6.5
The Regulatory Coordinator submits early enough that the IRB can review before approval expires, per the IRB's published deadlines.
5.6.6
If approval lapses:
  • the Regulatory Coordinator tells the PI, Lead CRC, Site Director and sponsor the same day
  • enrollment and all research activities stop, including screening and consent of new participants
  • research interventions for enrolled participants continue only if the IRB determines it is in their best interests (for example to avoid harm from stopping treatment), and only as the IRB allows; the PI contacts the IRB immediately to request this determination
  • the Regulatory Coordinator submits for renewal at once
  • the Quality Lead records the lapse as a deviation (SOP-308) and opens a CAPA (SOP-703)
  • activities resume only after renewed approval is received and filed
5.6.7
For device studies, the PI submits progress reports to the sponsor, monitor and IRB at regular intervals and at least yearly (21 CFR 812.150(a)(3)). For drug studies, the PI provides progress reports to the sponsor (21 CFR 312.64(a)); the IRB continuing review submission is separate.

5.7 Reporting to the IRB during the study

5.7.1
The PI reports to the IRB, per its policy and the regulations, any:
  • unanticipated problems involving risks to participants or others (SOP-502)
  • deviations made to eliminate an immediate hazard, and other deviations the IRB requires to be reported (SOP-308)
  • changes significantly affecting the conduct of the trial or increasing risk
  • new information that may adversely affect participant safety or the conduct of the trial
  • suspension or termination by the sponsor, or by the PI without sponsor agreement, with an explanation
  • for device studies, IRB-required reports under 21 CFR 812.150(a)
5.7.2
The Regulatory Coordinator files each report, the confirmation of submission and the IRB acknowledgment or determination in the ISF and logs it in [IRB TRACKER].
5.7.3
If the IRB suspends or terminates approval, the PI tells the sponsor promptly (for device studies within 5 working days, 21 CFR 812.150(a)(2)), and the site follows the IRB's instructions for participants already enrolled.

5.8 Communications and correspondence

5.8.1
All IRB correspondence, including emails that record decisions or instructions, is filed in the ISF. The Regulatory Coordinator sends the sponsor copies of IRB approvals and other correspondence the CTA or sponsor requires.
5.8.2
Phone calls with the IRB that affect the study are documented in a note to file (F-306-01) with date, IRB contact, topic and outcome.

5.9 Study closure with the IRB

5.9.1
The Regulatory Coordinator submits a closure report or final report to the IRB after the site's last participant activity, completion of data collection for the site, resolution of outstanding queries that require participant contact, and the sponsor's close-out visit or confirmation that the site may close, per IRB policy and SOP-601.
5.9.2
The study stays open with the IRB while any participant follow-up, data collection with identifiable data, or participant contact continues.
5.9.3
For device studies, the PI submits the final report to the sponsor and IRB within 3 months after termination or completion of the investigation or the investigator's part of it (21 CFR 812.150(a)(6)).
5.9.4
The Regulatory Coordinator files the closure submission and IRB acknowledgment in the ISF and records closure on F-601-01.

5.10 Records

5.10.1
The ISF holds, for each study: all submissions, approvals, approved and superseded documents, IRB rosters or the IRB's statement of compliance (or a pointer to where they are maintained), correspondence, reports and acknowledgments, and the reliance agreement where applicable. Retention follows SOP-402.
5.10.2
Records may be kept in the IRB portal if the site has a complete export or certified copy in the ISF at study closure, because portal access may end. See SOP-204 and SOP-401.
  • F-205-01 Study Activation Checklist
  • F-300-01 Pre-Screening Log
  • F-301-02 Consent Form Version Control Log
  • F-306-01 Note to File
  • F-601-01 Study Closeout Checklist
  • Appendix A State Law Worksheet
  • Appendix B Central and Site Responsibility Matrix (Model N only)
  • SOP-103 Staff Qualification, Training and Training Records
  • SOP-104 Conflict of Interest and Financial Disclosure
  • SOP-201 Confidentiality Agreements, Clinical Trial Agreements and Budgets
  • SOP-202 Medicare Coverage Analysis and Research Billing Compliance
  • SOP-204 Essential Documents and the Investigator Site File
  • SOP-205 Site Qualification, Initiation and Study Activation
  • SOP-300 Participant Recruitment, Pre-Screening and Advertising
  • SOP-301 Informed Consent Process and Documentation
  • SOP-308 Protocol Deviations and Noncompliance
  • SOP-401 Computerized Systems and Electronic Records
  • SOP-402 Record Retention, Archiving and Destruction
  • SOP-502 Unanticipated Problems and Reportable New Information
  • SOP-601 Study Closeout
  • SOP-700 Internal Quality Control and Quality Assurance Audits
  • SOP-703 Corrective and Preventive Action (CAPA)
  • SOP-903 Network Oversight of Member Sites (Metrics, Central QA, Escalation) (Model N only)

7. References

ReferenceTitle
21 CFR 56Institutional Review Boards
21 CFR 56.103Circumstances in Which IRB Review Is Required
21 CFR 56.108IRB Functions and Operations
21 CFR 56.109IRB Review of Research
21 CFR 312.66Assurance of IRB Review
21 CFR 312.64Investigator Reports
21 CFR 812.150Reports (devices)
45 CFR 46.103, 46.109, 46.114Assurance; IRB Review of Research; Cooperative Research (Common Rule, 2018)
ICH E6(R3) Annex 1, 1Institutional Review Board/Independent Ethics Committee
ICH E6(R3) Annex 1, 2.4Communication with IRB/IEC
ICH E6(R3) Annex 1, 2.5Compliance with Protocol
ICH E6(R3) Annex 1, 2.6Premature Termination or Suspension of a Trial
ICH E6(R3) Annex 1, 2.13Reports
FDA Guidance (2012)IRB Continuing Review after Clinical Investigation Approval
FDA Guidance (2006)Using a Centralized IRB Review Process in Multicenter Clinical Trials
FDA Guidance (December 2025)Investigator Responsibilities: Safety Reporting for Investigational Drugs and Devices (replaced the 2009 guidance Adverse Event Reporting to IRBs)

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.