SOP: GCP Inspection Management and Readiness (BIMO and EMA/National)

This is a ready-to-use SOP for managing a GCP regulatory inspection, whether an FDA Bioresearch Monitoring (BIMO) inspection or an EMA or national competent authority GCP inspection. Replace every <<FILL: ...>> placeholder, set your document numbers, and route it through document control. Readiness is a standing state your audit program maintains, not a sprint before the inspector arrives. A worked filled specimen follows. This is general guidance to adapt and verify, not legal advice.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> maintains readiness for and manages a GCP regulatory inspection so the inspection is a confirmation of a working quality system, records are produced accurately and completely, staff answer truthfully and within scope, and any observation is responded to on time and drives real corrective and preventive action.

2. Scope

This procedure applies to GCP inspections of the sponsor and its systems, and to sponsor support of inspections at investigator sites and vendors within the sponsor’s trials. It covers announced and unannounced inspections, pre-approval and routine surveillance inspections, and for-cause inspections. It does not cover the audit program, governed by <<FILL: SOP-ID for GCP audit program>>, though the audit program is what keeps the organization inspection-ready.

3. Responsibilities

4. Definitions

• BIMO: FDA’s Bioresearch Monitoring program, the inspection arm for clinical trials, run under Compliance Program Guidance Manuals (7348.811 clinical investigators, 7348.810 sponsors/monitors/CROs, 7348.809 IRBs).
• Form FDA 483: the list of inspectional observations an FDA investigator may issue at the close of an inspection. It is observations, not a final agency determination.
• Storyboard: a concise narrative of a trial’s design, key amendments, major deviations, safety profile, and data flow, prepared for inspection.

5. Procedure

5.1 Maintain standing readiness

Between inspections, keep the following in a state that does not require a scramble:

1. TMF current, complete, and retrievable. Inspectors increasingly start at the TMF, and a thin or late TMF predicts deeper problems.
2. Essential documents in order at inspected sites, with sites briefed on inspection conduct.
3. Key staff identified and available, including the medical monitor, PV lead, and data management lead.
4. A storyboard per registration trial, kept current.
5. Audit and CAPA history organized, with CAPAs closed where possible. Open CAPAs that show a working system are acceptable; abandoned CAPAs are a problem.
6. A mock inspection run on each registration program before the real one, so the back-room muscle memory holds up. See <<FILL: SOP-ID for mock inspection>>.

5.2 On notification (or arrival)

1. Notify the inspection lead, QA, and senior management immediately. For an unannounced inspection, the receptionist procedure routes the inspector to a holding area and calls the inspection lead.
2. Verify the inspector’s credentials and record them; for FDA, note the Form FDA 482 (Notice of Inspection).
3. Establish the front room (inspector, host, SMEs) and the back room (retrieval, review, SME staging). Keep them physically separate.
4. Brief the team on scope, roles, and conduct.

5.3 Run the inspection

1. Opening meeting. Confirm scope, the inspector’s plan, logistics, and daily timing.
2. Manage every request through the back room. Each request is logged with a time and an owner; the runner retrieves the correct version; the back room quality-checks it for completeness and flags any risk; the host delivers it and answers only what was asked.
3. Stage SMEs. Brief each SME before they enter the front room; debrief after.
4. Daily debrief. Review the day’s requests, answers, and any emerging concerns; prepare for the next day.

5.4 How to answer an inspector

1. Answer the question asked, accurately, then stop. Do not volunteer scope.
2. If you do not know, say you will find out, then have the back room find out.
3. Never guess, never speculate, never argue, and never hide a document the inspector is entitled to see.
4. Tell the truth. A false statement to an inspector is a separate and far more serious problem than the underlying finding.
5. Every document shown is logged by the scribe.

5.5 Document control during the inspection

1. Only correct, current, complete versions go to the front room, checked by the back room first.
2. Keep a copy of everything shown, matched to the scribe log.
3. Do not create, alter, or backdate any record during an inspection. If a record is found to be wrong, do not fix it mid-inspection; note it for the response.

5.6 Closing meeting and observations

1. Attend the closing meeting with QA and management. Listen; clarify factual misunderstandings; do not argue classifications.
2. For FDA, receive any Form FDA 483 and read each observation back to confirm understanding.
3. For EMA or national inspections, receive the inspection report classifying findings (critical, major, minor).

5.7 Respond to observations

1. Respond in writing within the required window (for an FDA 483, normally within 15 business days to have the response considered before any Warning Letter; for an EMA/national report, per the stated timeline).
2. For each observation: acknowledge it, state the immediate correction, give the real root cause, lay out systemic corrective and preventive action with owners and dates, and commit to an effectiveness check.
3. Where true, show that the audit program already identified and is fixing the issue, with the audit date, which demonstrates a functioning quality system.
4. Track the response actions to closure through the CAPA system.

6. Acceptance criteria

Inspection management is acceptable when: readiness elements in 5.1 are maintained and evidenced; front and back rooms operate as defined with a complete scribe log and document log; only correct, complete records were provided; answers were truthful and within scope; and any observation received a written response within the required window with real CAPA tracked to closure.

7. References

FDA BIMO Compliance Program Guidance Manuals 7348.811, 7348.810, 7348.809; Form FDA 482 and Form FDA 483. 21 CFR Part 312 (312.58, FDA access to records), Parts 50, 54, 56. ICH E6 Good Clinical Practice (inspection definition and sponsor responsibilities; confirm R3 locations). Regulation (EU) No 536/2014 and EMA GCP inspection procedures.

Confirm the current version of each reference before issue.

8. Records generated

Inspection notification record; credential and Form 482 record; scribe log; document request and disclosure log; daily debrief notes; storyboards; observations received (483 or report); written response; CAPA records.

9. Revision history

10. Approvals

Filled specimen

The following shows a 483 observation and the response skeleton completed for an illustrative inspection. The details are illustrative; replace them with your own.

483 Observation: “Informed consent was not obtained prior to the conduct of study procedures for one of twenty subjects whose records were reviewed (Subject 014).”

Response:

1. Acknowledgement: the observation is accepted as stated.
2. Immediate correction: Subject 014 was re-consented; the protocol deviation was reported to the IRB; the medical monitor confirmed no safety impact; the data were flagged in the deviation listing.
3. Root cause: the site used a paper consent log with no procedural check that consent preceded any trial procedure; the coordinator scheduled labs from the screening worklist without confirming consent status.
4. Corrective and preventive action: site SOP updated to require a consent-status check before any procedure; a pre-procedure checklist added to the visit workflow; all study staff retrained (records retained); the CRA will verify consent timing on the next three enrollments. Owner: site PI, sponsor CRA. Target date: 30 days.
5. Effectiveness check: audit of the next five enrollments at 90 days; success is 5 of 5 consented before any procedure.
6. Quality-system context: this issue was identified and CAPA’d through the sponsor audit AUD-2026-014 dated 16 September 2026, before the inspection.

That last point is the payoff of the whole program: when you can show the inspector you already found the issue, classified it, and fixed it through your own audit and CAPA system, a 483 observation becomes evidence the quality system works rather than evidence it failed.

Common inspection findings this SOP prevents

• Documents provided to the inspector that are the wrong version, incomplete, or not what was asked for.
• Staff volunteering scope, speculating, or arguing with the inspector.
• Records altered or backdated during an inspection (a far more serious problem than the original finding).
• No scribe or document log, so the organization cannot reconstruct what was asked and shown.
• A 483 or inspection report response that misses the required window or lacks real root cause and effectiveness checks.

How to adapt this SOP

1. Set your document number, owner, and effective date in the header.
2. Point the cross-references to your real mock-inspection, audit-program, and CAPA procedures.
3. Tailor the readiness elements in 5.1 to your portfolio (number of registration trials, decentralized elements, key vendors).
4. Confirm the BIMO CPGM numbers, the FDA form numbers, and the EU procedure references against current sources before issue.
5. Confirm the ICH E6 version in force and update citation locations for R3.