SOP: Management of Health Authority Inspections (Front Room and Back Room)

This is a ready-to-use SOP for managing a health authority inspection from arrival to close. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it.

Document control header

1. Purpose

This procedure defines how <<FILL: COMPANY NAME>> receives, hosts, and manages a health authority inspection (for example FDA, EMA, MHRA, or a competent authority) so that the inspection is conducted in a controlled, accurate, and cooperative manner, the company presents its true state of control, and every request, commitment, and observation is recorded. It applies whether the inspection is announced, unannounced, routine, pre-approval, or for-cause.

2. Scope

This procedure covers all health authority inspections of the sites in the header, from first notification or arrival through the closing meeting and the handover of any written observations. It does not cover the written response to observations, which is governed by <<FILL: SOP-ID for 483 / observation response>>, or customer and partner audits, governed by <<FILL: SOP-ID for external audits>>.

3. Responsibilities

4. Definitions

• Front room: the room where the investigator works and where interviews, document review, and system demonstrations happen.
• Back room: the controlled support area that reviews requested records first, manages the request log, escalates emerging issues, and prepares the response.
• Commitment: any statement to the investigator that the company will do or provide something by a time; every commitment is logged and tracked to closure.
• Form FDA 482 / 483 / 484: Notice of Inspection, Inspectional Observations, and Receipt for Samples respectively (US FDA). Equivalent instruments exist for other authorities.

5. Procedure

5.1 Notification and arrival

1. On arrival or notification, the reception or the person contacted notifies QA immediately per the internal call tree.
2. QA activates the inspection team and opens the front room and back room.
3. The coordinator receives the investigator, confirms credentials, and records the authority, the investigator name(s) and district, the inspection type, and the stated scope. For FDA, log the Form 482.
4. If the arrival is unannounced, do not delay entry; a delay, denial, or limitation of an inspection can itself carry regulatory consequence. Escort the investigator to the front room while the team assembles.

5.2 Opening meeting

1. The site head or quality head gives a short site overview if the investigator wants one.
2. Confirm the scope and the expected duration, and agree logistics (hours, breaks, a demonstration protocol for computerized systems).
3. The scribe records the stated scope verbatim.

5.3 Handling document requests

1. Every request is spoken back by the coordinator to confirm exact scope, and logged by the scribe on the document request log (<<FILL: form ID for the request log>>).
2. The runner retrieves the record from a controlled source. The back room reviews the retrieved copy before it crosses the table.
3. Provide exactly what was asked, nothing extra. Prepare two clean copies, one for the investigator and one held in the back room so reviewers see what the investigator sees.
4. If a record cannot be produced promptly, the coordinator gives a specific time commitment and the scribe logs it. If a record does not exist, say so plainly. Do not create or backfill a record during the inspection.
5. For a live system view, a qualified user drives the system while the investigator watches and directs; the investigator is not given administrative or unattended access to a validated system.

5.4 SME interviews

1. Bring in the SME for the topic under discussion and excuse them when it is done.
2. The SME answers the specific question asked, in plain language, supported by a record where one exists, and does not volunteer topics outside the question.
3. “I do not know, I will find out” is an acceptable answer; the SME does not speculate.

5.5 Back room operations

1. The back room maintains the document request log and matches every provided record with a back room review entry.
2. As records are pulled, qualified reviewers assess them for anything the company should be ready to discuss, and prepare the point before the investigator raises it.
3. Emerging significant observations are escalated to the site head and quality head the same day.

5.6 Daily wrap-up and briefing

1. Where the investigator holds a daily wrap-up, the coordinator and a scribe attend, clarify factual misunderstandings, and note the next day’s likely focus.
2. The team holds a short internal briefing for the site head and quality head: requests received, records provided, open commitments, and emerging issues.

5.7 Closing meeting

1. The investigator presents observations. The team listens and takes them down verbatim.
2. Correct clear factual errors at this meeting (for example a system that was retired on a stated date). Do not argue conclusions.
3. For FDA, receive any Form 483 and log it. Record every observation and every commitment made.
4. Do not make new substantive commitments at the close without the quality head’s agreement.

5.8 Immediately after

1. Reconcile the document request log and the commitment log; confirm every commitment has an owner and a due date.
2. Preserve the scribe records, the request log, and copies of everything provided as the inspection file.
3. Initiate the observation response per <<FILL: SOP-ID for observation response>>.

6. Acceptance criteria

A well-managed inspection meets all of the following:

• Every request, commitment, and verbal observation is captured contemporaneously in the scribe log and the request log.
• Every record provided was reviewed by the back room first, and matches exactly what was requested.
• No record was created, altered, or backfilled during the inspection.
• No unattended administrative access to a validated system was given.
• Leadership was briefed daily and was not surprised by any observation at the close.
• The inspection file is complete and preserved for the response.

7. References

21 CFR Part 211 (CGMP for finished pharmaceuticals); Part 600 series (biologics); Part 11 (electronic records). FD&C Act Section 704 (inspection authority), Section 501(j) (adulteration on delay, denial, limitation, or refusal of inspection). FDA Compliance Program 7356.002 (drug inspection program, systems-based model). EU GMP and the relevant competent-authority inspection procedures for EU/EEA inspections.

Confirm the current version and applicability of each reference before issue.

8. Records generated

• Document request log (<<FILL: form ID>>)
• Scribe interaction log
• Commitment tracking log
• Inspection file (copies of records provided, notes, any 482/483/484)

9. Revision history

10. Approvals

Filled specimen

The following shows the opening-day record for an illustrative unannounced routine CGMP inspection. Company, names, and numbers are illustrative; replace them with your own.

Opening-day flow that an inspector would recognize as controlled: the investigator requested the CDS audit trail configuration for one HPLC and the last three OOS for one product. The coordinator spoke each request back, the scribe logged them, the runner exported the records, the back room reviewed both before hand-off and flagged that one OOS was still open, and the SME was ready to show its current status when asked. No system access was handed over; a qualified analyst drove the CDS while the investigator watched. Every request had a matching back room review row by the end of the day.

Common inspection findings this SOP prevents

• Records were created or backfilled during the inspection to satisfy a request, converting a documentation gap into a data integrity violation.
• The investigator was given administrative access to a validated system and made or could have made changes to records.
• Commitments made verbally to the investigator were not tracked and not met, surfacing at the next inspection.
• Leadership learned of a significant observation for the first time at the closing meeting.
• No contemporaneous record of what was requested or provided, so the response could not reconstruct the inspection.

How to adapt this SOP

1. Set your document number, owner, and effective date, and align the call tree in 5.1 with your real notification path.
2. Point the cross-references in sections 2 and 5.8 to your real observation-response and external-audit procedures.
3. Name your document request log and commitment log forms and attach them.
4. Adjust the references for the authorities that actually inspect your sites.
5. Confirm every regulation in section 7 against the current published version before issue.