An inspection finding or critical observation
The deadline is external, the scope was defined by someone else, and the most damaging error available to you is promising more than the site can deliver.
A response letter is a set of commitments to a regulator on a fixed timetable — its credibility matters as much as its content.
Roughly the first working day
- Understand the finding before answering itIf the wording is ambiguous, seek clarification rather than guessing. Answering a different question than the one asked reads as evasion or misunderstanding.
- Establish the response deadline and who owns itName a single owner for the response with the authority to commit resource, and confirm the date the authority expects.
- Consider interim controlsWhere the permanent fix will take months, decide what protects product in the meantime. A long timeline with no interim control invites escalation.
- Check whether the finding is a repeatSearch your own records before responding. A recurrence you failed to identify is considerably worse discovered by the inspectorate.
- Assess scope beyond the example citedA finding is a sample. Responding only to the specific instance invites the follow-up asking what else shares the cause.
What must not be lost while people react
- The inspector's wording, verbatim, including any classification given.
- Records referenced during the inspection, retained in the state they were provided.
- Notes from the closing meeting, including anything clarified verbally.
- The back-room log of what was provided and when.
What shapes the investigation
- 01What exactly was observed, and does our understanding match the wording?
- 02Is this a first occurrence, or has something similar been raised before?
- 03How wide is the scope — one batch, one system, one site, or an estate?
- 04What can we genuinely deliver, on what dates, with the people we actually have?
- 05What protects product between now and the permanent fix?
Things to consider, not conclusions to adopt
- Response timelines are set by the authority; confirm the expected date rather than assuming a standard period.
- Commitments made in a response become obligations. A missed remediation commitment may be treated more seriously than the original finding.
- Where a finding suggests product already released may be affected, consider whether complaint, recall or notification obligations are engaged — take advice on your specific situation.
- Classification of the finding affects the response expected; if the classification is unclear, seek clarification.
What sites commonly get wrong
- Committing to an ambitious plan to appear responsive, then missing the dates.
- Addressing only the cited example rather than the wider cause.
- Closing the response internally without evidence attached to each commitment.
- Omitting the effectiveness check, which is what the follow-up inspection will look for.
Ten steps, in this order
- 01
Contain
Stop the situation getting worse. Quarantine affected material, halt the process step if continuing would compound the problem, and secure the area or system involved.
- 02
Assess
Establish what is known versus assumed. What happened, when, to what, and who observed it. Resist the pull to conclude a cause in the first hour.
- 03
Escalate
Notify according to your own procedure. Getting the right people informed early costs little; discovering later that QA or the QP was not told is itself a finding.
- 04
Investigate
Establish the cause with evidence rather than plausibility. Depth should be proportionate to risk, but the standard for a confirmed cause does not move.
- 05
Document
Record contemporaneously as you go. Reconstructing a record afterwards converts a quality problem into a data integrity problem, which is a different order of seriousness.
- 06
Determine impact
Assess product impact beyond the batch in front of you — other batches sharing equipment, materials, personnel or time window, and material already released.
- 07
Correct
Fix the immediate instance, and separately address the cause. Conflating correction with corrective action is the most common weakness in a response.
- 08
Prevent recurrence
Address why the process permitted the event. Where the design invites the error, training a person not to make it is a delay rather than a correction.
- 09
Verify effectiveness
Check against a criterion defined before implementation. This is the step most often skipped, and the one that decides whether the event returns as a repeat finding.
- 10
Close and monitor
Close with evidence attached, and keep the indicator under review long enough to know the fix held rather than merely completed.
This is quality guidance, not legal advice
This is practical quality guidance, not legal or regulatory advice. Whether a specific event triggers a particular regulatory obligation depends on the product, the market, the marketing authorisation and the facts. Assess against your own procedures, and take qualified advice where the situation may involve notification, recall or a deliberate act.
A date you did not choose
If there is a response deadline or an investigation that has to hold up under scrutiny, a short call is the fastest route to a view on what to do first.