Regulators, inspections, and enforcement
Who watches and how: regulators set expectations and inspect; findings draw a response and CAPA; serious or unaddressed problems escalate to warning letters, import alerts, and beyond.
What a module is not
A module is a reading step, not training and not a qualification. Completing it evidences that you read it — SPEQ says exactly that on the credential — and the knowledge checks are a self-check, not an assessment.
Regulators check whether a company is really in control by following a thread through its records and people.
Inspections test control; findings (e.g. a Form 483) draw CAPA; enforcement escalates when problems are serious.
Inspection readiness is not a pre-visit project — it is what daily control looks like.
Who watches, and how
Regulators — the FDA in the United States, the EMA and national authorities in Europe, the MHRA in the UK, and many others — set expectations, review what companies are allowed to make, and verify compliance through inspection. International harmonisation bodies such as ICH reduce the differences between regions, but a company that sells in many markets answers to many regulators.
An inspection is the moment the state of control is tested by an outsider. Inspectors ask to see procedures, records, and evidence; they interview the people who did the work; and they follow a thread — often a deviation, a complaint, or a data trail — to judge whether the organisation is genuinely in control or only appears to be.
When control is found wanting
Inspection findings are usually documented on the spot — in the US, on a Form 483 listing observations. The company responds with corrections and CAPA. If problems are serious or unaddressed, enforcement escalates: warning letters, import alerts that block product at the border, consent decrees, and in the gravest cases, loss of the ability to supply a market.
The through-line of this whole series returns here. Everything — records, procedures, deviations, data integrity, qualified facilities — exists so that when an inspector pulls a thread, the evidence holds. Inspection readiness is not a special activity done before a visit; it is what a genuinely controlled operation looks like every day.
- 1Regulators set expectations, approve what may be made, and verify compliance through inspection.
- 2Harmonisation (e.g. ICH) narrows regional differences, but multi-market companies answer to many regulators.
- 3An inspection tests the state of control by following a thread through records, evidence, and people.
- 4Findings (e.g. a Form 483) draw a response and CAPA; serious or unaddressed problems escalate enforcement.
- 5Inspection readiness is not a pre-visit event — it is what genuine daily control looks like.
What does an inspection test?
- Whether an organisation is genuinely in control ✓
- The size of the facility
- The marketing budget
In the US, inspection observations are documented on a…
- Form 483 ✓
- purchase order
- press release
Why is a two-week pre-inspection "clean-up" the wrong idea?
- It is expensive
- Real control is a daily state, and clean-ups can create integrity problems ✓
- Inspectors never look at records
A company plans a "clean-up" of records in the two weeks before a scheduled inspection.
Why is treating inspection readiness as a pre-visit project the wrong idea?
If control only exists when an inspection is imminent, it does not exist — and a "clean-up" can itself create integrity problems. Inspectors follow real threads through daily evidence; readiness is the by-product of an operation that is actually in control every day, not a project run against a visit date.