Inspection readiness, tested rather than assumed
Most sites do not fail an inspection on compliance. They fail on retrieval speed, on inconsistent accounts of the same process, and on answering questions nobody asked.
Structured the way we scope the work: what is wrong, what it risks, what waiting costs, and what we would actually do.
- 01The problem
- 02What it puts at risk
- 03What waiting costs
- 04How we assess it
- 05What we do
What is actually going wrong
Ask a quality team whether they are inspection-ready and you will usually get a considered yes. Ask them to produce the training record for a named operator on a named batch within fifteen minutes, and the answer changes. The gap between those two answers is where inspections are actually lost.
The pattern repeats: the underlying compliance is sound, but the site cannot demonstrate it at inspection pace. Documents take too long to surface. Two departments describe the same process differently. A subject-matter expert, trying to be helpful, opens a topic the inspector had not asked about and a new line of questioning begins.
- Slow retrieval reads as poor document control, and an inspector who doubts your control will look harder at everything else.
- Inconsistent accounts across departments suggest the written procedure is not what actually happens.
- Unclosed commitments from a previous inspection are the fastest route to a repeat finding, which is treated far more seriously than a first one.
- An unannounced inspection removes the preparation window entirely, and readiness becomes whatever state you were already in.
The cost of deferring this
Preparation deferred until an inspection is announced competes directly with the day job, at exactly the moment the day job cannot absorb it. The work is the same work; only the pressure and the cost of getting it wrong have changed. Sites that prepare continuously spend less in total than sites that prepare in a three-week sprint, and they sleep better.
Put a figure on itWe run a timed retrieval exercise and a short set of process interviews across departments before proposing anything. Those two exercises reliably predict how the first day of an inspection will go, and they take less than a day to perform.
The work itself
- Mock inspections at inspection paceincluding opening meeting, facility tour, document requests and closing summary.
- Back-room simulationbecause the room that supplies documents is usually the part nobody has practised.
- SME coachingon answering the question asked, completely and no further.
- Commitment closure reviewof every action from your last inspection or client audit, with evidence attached.
- Narrative consistency checksso production, QA and engineering describe the same process the same way.
The state you are left in
A site that could host an unannounced inspection this week without a scramble, and a quality team that has already had the difficult conversation in a rehearsal rather than in front of a regulator.
Fifteen minutes, no proposal attached
Bring the specific version of this problem that you have, and we will tell you what we would do about it, or that you do not need us.