Inspection Readiness: Being Ready Without a Fire Drill

Inspection readiness is the condition of being able to answer an inspector's question with the right document, quickly, without assembling anything.

Most organisations treat it as a project that starts when an inspection is announced. The ones that do well treat it as a property of how they already work, because the things an inspection exposes cannot be fixed in three weeks.

What is actually being tested

An inspector is checking whether your quality system operates as described. Two things reveal that faster than anything else:

How long it takes you to produce a document. A twenty-minute wait for a batch record says the record exists but the system around it does not.

Whether the people doing the work can explain it. A prepared answer from a manager carries less weight than the analyst who ran the method describing what they did.

The first hour

Expect to be asked for, and to produce immediately:

• The quality manual and the site organisation chart.
• The SOP index, with effective dates and version history.
• Training records for the people performing the operations under review.
• The deviation, CAPA and change control logs, with status.
• Complaint and, for devices, MDR logs.
• The internal audit schedule and evidence it was followed.
• Previous inspection findings and what you did about them.

That last one carries disproportionate weight. An inspector who finds a repeat of a prior observation has learned something about the system rather than about the observation.

The back room decides the outcome

During an inspection, requests go to a back room that retrieves documents, checks them, and hands them forward. Almost every inspection that goes badly goes badly there.

What makes it work:

• One named scribe recording every request, what was provided, and when. Without it you cannot reconstruct what the inspector saw, and you will need to when you write the 483 response.
• Someone reviewing documents before they go out, so an unrelated problem on page four does not open a new line of questioning.
• A single point of contact for the inspector. Multiple people volunteering information is how scope expands.

Where readiness actually fails

• Documents exist but are not retrievable. Being in a system nobody can search is functionally identical to not existing.
• The SOP and the practice have drifted. The procedure describes a step people stopped doing two years ago. An inspector asking someone to walk through the process finds this immediately.
• Open CAPAs past their due dates, with no documented justification. This is visible in your own log and is one of the easiest findings to make.
• Commitments from the last inspection that were completed late, or not at all, against dates you supplied.