During an inspection

During a GMP inspection

An inspection follows a broadly predictable shape. What varies is depth, and depth is driven by what turns up early. An inspector who doubts your document control will look harder at everything downstream of it, which is why retrieval speed and consistency matter more than most sites expect.

On this page

The inspection is a sampling exercise: what the inspector finds early determines how deep they go, so the first hours carry disproportionate weight.

01 · During an inspection

How inspections work

The structure is broadly consistent across EU and PIC/S inspectorates, whether the inspection is routine, pre-authorisation, for-cause or unannounced.

  • Opening meetingScope, duration, the areas to be covered and the logistics. This is where you learn what the inspection is actually about — listen more than you present.
  • Facility tourOften early. Qualification status versus what is installed, cleaning and status labelling, segregation, and anything visibly out of place.
  • Document requestsFlowing continuously through the back room. Each request is logged, retrieved, checked and provided; timing is itself being observed.
  • Interviews with the people who do the workNot only managers. Operators are asked why a step exists, which tests whether training conveyed understanding or just attendance.
  • Daily wash-upEmerging findings are usually flagged as the inspection proceeds. This is the opportunity to provide evidence that resolves a misunderstanding — take it the same day.
  • Closing meetingDeficiencies presented and classified as critical, major or other. Clarify anything you do not understand here, not afterwards.
02 · During an inspection

What inspectors may ask

The questions are rarely obscure. They tend to test whether the system works as described, and whether the people running it understand why.

  • Show me the training record for this operator on this batchA retrieval test as much as a records test. Slow retrieval reads as weak document control.
  • Why does this step exist?Asked of an operator. Answers like 'because the SOP says so' indicate training that produced a record rather than understanding.
  • What was the root cause, and how do you know?The second half is the real question. 'Human error' without an explanation of why the process permitted it will not survive.
  • How did you verify this CAPA was effective?Expect follow-ups on when the criterion was set and what data was compared against it.
  • Who reviews the audit trail, and what did they find?A precise question with a precise answer, or a finding.
  • Show me the oldest open deviationAnd why it is still open. Ageing is visible in your own registers.
  • What did management review decide, and was it funded?Tests whether management responsibility is real or documentary.
  • Has this happened before?The recurrence question. Answer it accurately — the trend data is usually in the records they already have.
03 · During an inspection

How employees should respond

The behavioural rules are simple to state and hard to hold under pressure. They should be rehearsed, because an inspection is not the moment to learn them.

  • Answer the question asked, completely, and stopVolunteering additional context is the single most common way a new line of enquiry opens. Helpfulness and brevity are not in conflict here.
  • Say you do not know, then find out'I don't know, but I can find out who does' is a perfectly good answer. Guessing is not, and an inaccurate answer will be checked against records.
  • Never speculateIf asked what might have caused something, distinguish clearly between what you know and what you are hypothesising.
  • Do not contradict a colleague in the roomIf you believe an answer was wrong, correct it through the inspection lead rather than in the moment.
  • Never alter or create a record during an inspectionBackdating or completing a record retrospectively converts a documentation finding into a data integrity finding, which is a different order of seriousness.
  • Provide what was asked for, not moreDocuments go through the back room so they are checked and logged. Handing over an unrequested file is how unrelated issues surface.

A subject-matter expert trying to be helpful is the most common source of self-inflicted findings. Coaching SMEs on answering only what is asked is a half-day exercise with a disproportionate return.

04 · During an inspection

Common organisational mistakes

These are failures of preparation and structure rather than of compliance, and they are the ones that convert a routine inspection into a difficult one.

  • No functioning back roomRequests handled ad hoc, nothing logged, documents provided unchecked, and no record of what the inspector has already seen.
  • Departments telling different storiesProduction, QA and engineering describing the same process differently suggests the written procedure is not what happens.
  • Senior management absentReads as management disengagement from the quality system, which is itself a Chapter 1 expectation.
  • Arguing with a finding in the roomClarify facts, certainly. Disputing classification during the inspection rarely helps; the written response is the place for that.
  • Producing documents nobody has reviewedHanding over a file with an obvious gap because there was no time to check it first.
  • Treating an unannounced inspection as unfairIt removes the preparation window by design. Readiness becomes whatever state you were already in, which is the point.
Rehearse it

A mock inspection tests this rather than assuming it

Timed retrieval, back-room simulation, SME questioning and narrative consistency, run at inspection pace. Most sites discover the gap in a rehearsal, which is the cheap place to find it.