SOP-701

Sponsor and IRB Audits

Number
SOP-701
Category
Quality Assurance
Edition
Reference Edition 1.3
Approx. pages
6

[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] prepares for, hosts and follows up on audits of its studies by sponsors, contract research organizations (CROs) acting for sponsors, independent auditors engaged by sponsors, and IRBs.

2. Scope

This SOP applies to every audit of a study or process at [SITE NAME] performed by or for a sponsor or an IRB, whether on site, remote or a mix of both, routine or for-cause.

It does not cover:

  • routine monitoring visits (SOP-600 Sponsor Monitoring Visits)
  • FDA inspections and remote regulatory assessments (SOP-702 FDA Inspections and Remote Regulatory Assessments)
  • internal audits (SOP-700 Internal Quality Control and Quality Assurance Audits)

Where the protocol, the clinical trial agreement (CTA), the sponsor or the IRB sets a stricter requirement, follow the stricter requirement.

3. Responsibilities

RoleResponsibilities
Principal Investigator (PI)Permits audits (ICH E6(R3) Annex 1, 2.3.5). Makes time to attend the opening and closing meetings and to answer the auditor's questions. Approves and signs the written response.
Site DirectorConfirms the audit is authorized under the CTA, provides resources, and attends the closing meeting where possible.
Quality LeadCoordinates preparation, acts as audit liaison unless another person is named, leads the response and CAPA under SOP-703, and reports trends under SOP-700.
Regulatory CoordinatorPrepares the Investigator Site File (ISF) and regulatory records, and files audit correspondence.
Lead CRC / Clinical Research Coordinator (CRC)Retrieves participant records, arranges electronic system access, answers questions about their own work, and corrects findings.
Research Pharmacist or IP ManagerPresents IP storage, temperature and accountability records and answers IP questions.
All Research StaffAnswer auditor questions truthfully and only within their own knowledge.

4. Definitions

TermDefinition
AuditA systematic and independent examination of trial-related activities and records performed by the sponsor, service provider (including a CRO) or institution to determine whether the activities were conducted, and the data were recorded, analyzed and accurately reported, according to the protocol, applicable SOPs, GCP and applicable regulatory requirements (ICH E6(R3) Glossary).
MonitoringThe sponsor's ongoing oversight of trial conduct as the trial progresses, including on-site, remote and centralized activities. Monitoring is a quality control activity performed by the sponsor's study team (ICH E6(R3) Annex 1, 3.11.4).
Audit liaisonThe site staff member who is the auditor's single point of contact, manages requests and keeps the request log.
Audit certificateA declaration of confirmation by the auditor that an audit has taken place (ICH E6(R3) Glossary).
Direct accessPermission to examine, analyze and verify records important to the evaluation of a trial, on site or remotely, while protecting participant confidentiality and sponsor proprietary information (ICH E6(R3) Glossary).
Corrective and Preventive Action (CAPA)Actions taken to remove the cause of a finding and prevent it from recurring. See SOP-703.

5. Procedure

5.1 Audit versus monitoring

5.1.1
Staff treat an audit differently from a monitoring visit:
  • A monitoring visit is part of the sponsor's routine quality control of the study. The monitor is part of the study team, visits on a schedule, and works with the site to resolve issues as the study runs (SOP-600).
  • An audit is independent of the study team. The sponsor's quality assurance group or a contracted auditor examines whether the study and the site's processes meet the protocol, GCP and regulations. Audits are usually one-time events with a formal report and a required written response.
  • An IRB audit (sometimes called post-approval or compliance review) examines compliance with the IRB-approved protocol, consent process and IRB determinations. Central IRBs may audit routinely or for cause.
5.1.2
Audits may be routine or triggered. Common triggers include high or unusually low enrollment, an unusual safety reporting pattern, monitor-reported concerns, a study that is pivotal for a marketing application, and the expectation of an FDA inspection. An audit request does not by itself mean the sponsor has found a problem.

5.2 Notification and scheduling

5.2.1
Any staff member who receives an audit request forwards it the same business day to the PI, Quality Lead and Site Director.
5.2.2
The Quality Lead confirms with the requester, in writing:
  • auditor name(s), organization, and whom they represent (sponsor, CRO, IRB)
  • study, protocol number and the scope (study audit, process audit, specific concern)
  • proposed dates, expected duration and format (on site, remote, or both)
  • agenda, including meetings requested with the PI and staff
  • list of records to have ready, and electronic systems the auditor needs to access
  • whether the audit is routine or for cause, if the requester will say
5.2.3
The Site Director or Finance / Contracts Lead checks the CTA for audit rights, notice periods, confidentiality and any audit fees. For an auditor from a company other than the sponsor, the Quality Lead confirms in writing that the sponsor authorized the audit and that the auditor is bound by confidentiality.
5.2.4
The Quality Lead agrees a date when the PI and key staff can attend. The site does not delay an audit to gain preparation time beyond a reasonable scheduling window.
5.2.5
The Quality Lead names the audit liaison and a backup and records them on F-702-01 Inspection Request and Document Log, which the site also uses for sponsor and IRB audits.
5.2.6
For a sponsor audit, the PI or Regulatory Coordinator notifies the IRB only if the IRB's policy requires it. For an IRB audit, the PI or Regulatory Coordinator notifies the sponsor or CRO promptly unless the CTA says otherwise.

5.3 Preparation

5.3.1
The Lead CRC and Regulatory Coordinator gather, for the study in scope:
  • ISF, using F-204-01 Investigator Site File Index
  • signed consent forms and F-301-01 Informed Consent Process Notes for all participants
  • source documents and access to the electronic health record (EHR) for study participants only
  • F-303-01 Screening and Enrollment Log and F-303-02 Eligibility Verification Checklists
  • F-304-01 Investigational Product Accountability Log, F-304-02 Temperature Monitoring Log and any F-304-03 Temperature Excursion Reports
  • F-302-01 Delegation of Authority Log, staff training records and CVs
  • safety records (F-500-01, F-501-01), F-308-01 Protocol Deviation Log, F-600-01 Monitoring Visit Log and follow-up letters
  • IRB and sponsor correspondence
5.3.2
The Quality Lead performs a focused pre-audit check (consent, eligibility, delegation, training, IP, safety reporting) using F-700-01 Internal QC Review Checklist.
5.3.3
Problems found during preparation are handled honestly:
  • Missing or incorrect entries are corrected following SOP-306 Source Documentation and Data Integrity (ALCOA+), with the current date and an explanation. Records are never backdated, re-created or altered to look contemporaneous.
  • An issue that cannot be corrected is documented on F-306-01 Note to File with the facts and the corrective action, and logged on F-308-01 if it is a deviation.
5.3.4
The Site Director or Quality Lead arranges:
  • a private room with workspace, internet access and a telephone
  • read-only EHR and system accounts, limited to study participants and time-limited to the audit, set up under SOP-401 Computerized Systems and Electronic Records
  • availability of the PI, Sub-Is, CRCs, IP Manager and Regulatory Coordinator at agreed times
5.3.5
The Quality Lead briefs staff on the agenda and these rules:
  • Answer the question asked, truthfully, and only from your own knowledge.
  • If you don't know, say so and offer to find the person who does. Don't guess or speculate.
  • Use the records to answer where possible.
  • Report any concern raised by the auditor to the liaison right away.

5.4 Conduct of the audit

5.4.1
The liaison greets the auditor, confirms identity against the confirmed auditor name, records the visit on F-702-01, and arranges any site sign-in and confidentiality requirements.
5.4.2
At the opening meeting, the PI or Quality Lead gives a short overview of the site and study team, and the auditor confirms scope and schedule.
5.4.3
The liaison logs on F-702-01 each record request, the time requested, the time provided, the person providing it, and any copies given. The liaison checks that requests stay within the agreed scope and raises scope changes with the Quality Lead.
5.4.4
Copies are provided only as requested. The liaison:
  • keeps a duplicate of every copy given, filed with the audit records
  • marks copies of site proprietary material "Confidential"
  • provides copies of participant records redacted and checked under the single redaction rule in SOP-400 5.4.1; direct review of identified records on site or through read-only access is permitted under the consent and authorization (SOP-400 Participant Privacy and HIPAA in Research)
5.4.5
The liaison or a knowledgeable staff member accompanies the auditor during facility tours (IP storage, laboratory, archive) and staff interviews.
5.4.6
The liaison asks the auditor at the end of each day for any preliminary concerns and next-day requests, and holds a short internal debrief with the PI and Quality Lead. Clear errors may be corrected during the audit under SOP-306 and the correction noted on F-702-01.

5.5 Closeout meeting

5.5.1
The PI attends the closeout meeting, with the Quality Lead, Lead CRC and Site Director where possible.
5.5.2
The liaison takes notes of each finding as presented, including its classification and the requirement cited.
5.5.3
The PI or Quality Lead asks clarifying questions and corrects factual errors with evidence at the meeting. Staff do not argue findings. Disagreements are noted and addressed in the written response.
5.5.4
The Quality Lead asks the auditor when the written report or findings letter will be issued, the response deadline, and whether an audit certificate or confirmation of audit will be provided.

5.6 Written response and CAPA

5.6.1
On receipt of written findings, the Quality Lead assesses each finding against the CAPA triggers in SOP-703 5.1.2. Findings that meet a trigger (for example, any finding graded major or critical) are logged on F-703-01 CAPA Record with an owner. Minor findings that do not meet a trigger are corrected and answered in the response with a one-line cause.
5.6.2
The response is due by the auditor's deadline. If none is given, the site responds within [DEFAULT: 30 calendar days of receipt of written findings]. If the site cannot meet a deadline, the Quality Lead asks for an extension in writing before the due date.
5.6.3
For each finding the response states:
  • the correction already made, with the date
  • the root cause, scaled to the severity of the finding (SOP-703)
  • the corrective and preventive actions, owners and target dates
  • how the site will check the actions worked
5.6.4
The Quality Lead drafts the response, the PI reviews and signs it, and the Regulatory Coordinator sends it to the auditor (and to the sponsor contact if different). The response is factual and does not promise actions the site cannot complete.
5.6.5
The PI assesses whether any finding is reportable to the IRB or sponsor (for example, serious or continuing noncompliance, or a deviation that affected participant safety) and reports it under SOP-308 Protocol Deviations and Noncompliance and SOP-502 Unanticipated Problems and Reportable New Information.
5.6.6
The Quality Lead tracks the CAPAs to closure and effectiveness check under SOP-703 and sends any promised follow-up evidence to the auditor.

5.7 Records

5.7.1
The Regulatory Coordinator files in the ISF: the audit notification, audit certificate or confirmation letter, findings letter or report (if provided), the site's response and any closure letter.
5.7.2
The Quality Lead keeps in the quality file: F-702-01, the duplicate set of copies provided, meeting notes, and CAPA records.
5.7.3
The Quality Lead includes audit findings in the quarterly metrics and management review under SOP-700.
  • F-702-01 Inspection Request and Document Log (used for audits)
  • F-703-01 CAPA Record
  • F-700-01 Internal QC Review Checklist
  • F-204-01 Investigator Site File Index
  • F-306-01 Note to File
  • F-308-01 Protocol Deviation Log
  • SOP-306 Source Documentation and Data Integrity (ALCOA+)
  • SOP-308 Protocol Deviations and Noncompliance
  • SOP-400 Participant Privacy and HIPAA in Research
  • SOP-401 Computerized Systems and Electronic Records
  • SOP-502 Unanticipated Problems and Reportable New Information
  • SOP-600 Sponsor Monitoring Visits
  • SOP-700 Internal Quality Control and Quality Assurance Audits
  • SOP-702 FDA Inspections and Remote Regulatory Assessments
  • SOP-703 Corrective and Preventive Action (CAPA)
  • 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 312.62Investigator recordkeeping and record retention
21 CFR 812.140Records (devices)
21 CFR 56Institutional Review Boards
45 CFR 164.508Uses and disclosures for which an authorization is required (HIPAA)
ICH E6(R3) Annex 1, 2.3.5Investigator permits monitoring, auditing and IRB review
ICH E6(R3) Annex 1, 2.12.14Direct access to trial records on request
ICH E6(R3) Annex 1, 3.11.2Audit (sponsor)
ICH E6(R3) Appendix CEssential Records (audit certificate; noncompliance and CAPA records)
ICH E6(R3) GlossaryAudit, Audit Certificate, Direct Access
ISO 14155 (current edition)Clinical investigation of medical devices for human subjects: Good clinical practice (device studies)

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.