Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics -> Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Checklist Plug-and-play starting point Audits & Inspection

Checklist: Self-Assessment Against Recurring 483 and Warning Letter Trend Categories

A plug-and-play self-assessment checklist built from the citation themes that recur across years and modalities in FDA 483s and warning letters, sectioned by theme with pass criteria and evidence to capture, for use ahead of a mock inspection or between formal internal audits, with a filled specimen.

Document type: Checklist

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This checklist does not come from a generic control framework. Every section below is a citation theme that recurs across years and modalities in published FDA 483s and warning letters: inadequate investigations, data integrity gaps, laboratory control failures, quality unit weaknesses, aseptic and contamination control, cross-contamination and cleaning validation, and CAPA system weaknesses. Walking your own operation against each theme, honestly, before an inspector does it for you, is the closest thing to reading the next inspection’s script in advance. Replace every <<FILL: ...>> placeholder, record Pass, Gap, or N/A for every line, and capture the evidence named. A section that does not apply to your modality (aseptic processing at a non-sterile oral solids site, for example) is marked N/A as a block with a one-line rationale, not silently skipped. A filled specimen follows.

Document control header

FieldEntry
Document titleSelf-Assessment Against Recurring 483 and Warning Letter Trend Categories
Document number<<FILL: CHK-ID, e.g. CHK-QA-052>>
Version<<FILL: version, e.g. 1.0>>
Effective date<<FILL: effective date>>
Document owner<<FILL: RI lead or QA>>
Applies to<<FILL: site / area in scope>>

How to use this checklist

  1. Run this at the site or process level, not the enterprise level; controls and evidence differ site to site.
  2. For every line, decide Pass, Gap, or N/A, and record where the evidence lives (procedure number, record reference, self-check reference). A Pass with no evidence reference is not a pass.
  3. Mark an entire section N/A only with a stated rationale (for example, “no sterile manufacturing at this site”), not by leaving it blank.
  4. Log every Gap in the gap summary with a risk rating and an owner. This checklist does not replace CAPA; it feeds it.
  5. Use this ahead of a mock inspection, between formal internal audit cycles, or whenever a theme in this checklist appears as rising in the Regulatory Intelligence Signal and Trend Log.

Scoring legend: Pass, control is in place and evidenced. Gap, control is missing, partial, or unevidenced; must be logged. N/A, theme does not apply to this site; state why.

Assessment context

FieldEntry
Site / area assessed<<FILL>>
Modality / process scope<<FILL>>
Assessor (name, date)<<FILL>>
Trigger for this assessment<<FILL: scheduled / rising theme in RI register / pre-mock-inspection>>

1. Inadequate investigations

#CheckPass criterionEvidence to captureResult
I1Root cause supported by evidenceOOS and deviation root causes are supported by documented investigation steps, not assertedSample of closed investigations, last 6 months<<FILL>>
I2”Analyst error” or “human error” is not a defaultWhere human error is cited, the record shows the specific mechanism and why other causes were ruled outSample investigations citing human error<<FILL>>
I3Laboratory-phase investigation precedes invalidationOOS results are not invalidated before the laboratory-phase investigation is completeSample OOS records, sequence of events<<FILL>>
I4Investigation scope includes other affected batchesA confirmed root cause triggers a documented check for other batches or lots that could share itSample investigation extended-impact sections<<FILL>>

See OOS Investigation Process and Human Error in Deviations.

2. Data integrity

#CheckPass criterionEvidence to captureResult
D1Audit trail review performed and documentedAudit trail review happens at the defined frequency with a documented, signed record, not just a stated procedureSample review records<<FILL>>
D2No shared or generic loginsEvery GxP system user has a unique, attributable loginUser account export<<FILL>>
D3Role-based access control enforcedAccess privileges match job function; no unassigned elevated accessAccess control matrix<<FILL>>
D4System clocks synchronized and protectedClocks are synchronized to a controlled source and cannot be altered by ordinary usersTime-sync configuration<<FILL>>
D5Trial, test, and aborted runs are visibleNo pattern of trial injections or aborted runs being excluded from the reported recordAudit trail sample for trial/aborted runs<<FILL>>

See Data Integrity Foundations, ALCOA+ in detail, and Operationalizing Audit Trail Review.

3. Laboratory controls

#CheckPass criterionEvidence to captureResult
L1Methods validated before routine useAnalytical methods in routine use have a completed validation or verification recordMethod validation index<<FILL>>
L2System suitability not manipulatedSystem suitability failures are investigated, not repeated until passing without documented causeSample sequences with SST failures<<FILL>>
L3No testing into complianceNo pattern of repeat testing until a passing result appears without a documented, justified reasonOOS / repeat testing log review<<FILL>>

4. Quality unit authority

#CheckPass criterionEvidence to captureResult
Q1Quality unit reviews and approves before releaseNo batch is released without documented quality unit review and dispositionSample batch disposition records<<FILL>>
Q2Quality unit has authority to stop releaseProcedure and practice both confirm the quality unit can hold or reject a batch without being overridden informallyInterview / procedure review<<FILL>>
Q3Procedures are followed, not just writtenSpot-check of actual practice against the written procedure for a sampled activity shows consistencyDirect observation or record sample<<FILL>>

5. Aseptic processing and contamination control

Mark this entire section N/A if the site runs no sterile manufacturing. State the rationale in the assessment context above.

#CheckPass criterionEvidence to captureResult
A1EM excursions trigger investigationEvery environmental monitoring excursion above the defined limit has a documented investigation, not just a trend noteSample EM excursion records<<FILL>>
A2Media fill program current and passingMedia fills are performed at the required frequency, covering worst-case interventions, with no unresolved failuresMedia fill schedule and results<<FILL>>
A3Gowning qualification currentPersonnel gowning qualification is current for everyone with aseptic core accessGowning qualification records<<FILL>>

See Aseptic Processing and Media Fills and Annex 1 Contamination Control Strategy.

6. Cross-contamination and cleaning validation

#CheckPass criterionEvidence to captureResult
C1Cleaning validation covers the worst-case product/equipment combinationCleaning validation studies justify the worst-case grouping usedCleaning validation summary<<FILL>>
C2Shared-equipment risk assessedWhere equipment is shared across products, a documented cross-contamination risk assessment existsRisk assessment record<<FILL>>

See Cross-Contamination Control in Shared Facilities and Cleaning Validation Fundamentals.

7. CAPA system

#CheckPass criterionEvidence to captureResult
P1Effectiveness checks are performed, not assumedClosed CAPAs show a documented effectiveness check with a defined sampling basis, not just “implemented”Sample closed CAPAs<<FILL>>
P2Recurring root causes are flaggedA new deviation matching a prior root cause is identified as a repeat, not logged as an isolated fresh eventDeviation trend review<<FILL>>
P3CAPA fixes the system, not just the instanceSampled CAPAs show a systemic fix (procedure, training, configuration) where the root cause was systemic, not only correction of the single eventSample CAPA records<<FILL>>

See What Is a CAPA and CAPA Effectiveness Verification.

Gap summary

Gap refCheck #DescriptionRisk (H/M/L)OwnerRemediation / due dateStatus
<<FILL: G1>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>>

Overall result

FieldEntry
Sections assessed / N/A<<FILL>>
Lines assessed<<FILL: count>>
Pass<<FILL: count>>
Gap (open)<<FILL: count>>
Highest open risk<<FILL: H / M / L>>
Overall verdictPass / Conditional (gaps with plan) / Fail
Assessor (signature, date)<<FILL>>
QA review (signature, date)<<FILL>>

References

21 CFR Part 211, including 211.22, 211.42, 211.68, 211.100, 211.113, 211.160, 211.165, 211.192, 211.194. 21 CFR Part 11 (electronic records and signatures). FDA guidance, Data Integrity and Compliance With Drug CGMP: Questions and Answers (December 2018). ICH Q9(R1), Quality Risk Management.

Confirm the current version and clause numbers of each reference before issue. This checklist is an educational self-assessment aid, not a compliance guarantee.

Revision history

VersionDateAuthorSummary of change
<<FILL: 1.0>><<FILL: date>><<FILL: author>>Initial issue.

Filled specimen (excerpt)

Illustrative assessment for a single-site oral solids manufacturer, no sterile operations. Findings are illustrative.

Assessment context: Site A, oral solid dose, assessed by M. Osei, 14 Sep 2026, triggered by a rising DI/audit trail theme in the RI register.

Section 5 (Aseptic processing) marked N/A: no sterile manufacturing at this site.

Sample of completed lines:

#CheckResultEvidence / note
I2Analyst error not a defaultGapTwo of eight sampled investigations cited “analyst error” with no supporting root-cause evidence
D1Audit trail review performed and documentedPassWeekly review records complete for all 4 CDS instruments, last 6 months
L2System suitability not manipulatedPassNo pattern of repeated SST runs without documented cause in sampled sequences
P1Effectiveness checks performedGap3 of 10 sampled closed CAPAs show no effectiveness-check evidence beyond “implemented”

Gap summary:

Gap refCheck #DescriptionRiskOwnerRemediation / due dateStatus
G1I2Root cause assigned to analyst error without supporting evidence in 2 of 8 sampled investigationsMQC ManagerRetrain investigators on root-cause standard; re-open the 2 investigations; DEV-2026-0210Open
G2P13 closed CAPAs lack documented effectiveness-check evidenceHQAReopen the 3 CAPAs, define and execute effectiveness checks; CAPA-2026-0233Open

Overall verdict: Conditional. Two open gaps, both with a dispositioned remediation plan and an owner. The CAPA effectiveness gap (G2) is rated High because it undermines confidence in every other CAPA closed under the same practice, not just the three sampled, so the remediation plan includes a broader sample review beyond the three found here.

Common inspection findings this checklist prevents

  • A site can describe its controls in general terms but has never walked its own operation against the specific themes that recur in published enforcement actions.
  • “Analyst error” or “human error” used as a closing statement rather than a supported conclusion.
  • CAPAs closed on “implemented” with no effectiveness-check evidence, discovered only when an inspector samples the CAPA file directly.
  • A self-assessment that reports all Pass with no gaps, which itself signals the assessment did not look hard enough.

How to adapt this checklist

  1. Set your document number, owner, and effective date in the header.
  2. Mark sections N/A only where genuinely not applicable to the site’s modality, with the rationale stated in the assessment context.
  3. Add or adjust check lines to match your own operation’s specific process risks; the seven sections here are the recurring themes, not an exhaustive list.
  4. Feed every open gap into your real deviation or CAPA process, and track the gap summary to closure the same way any other finding is tracked.
  5. Pair this checklist with a mock inspection when the trigger is pre-inspection readiness rather than a routine periodic check.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.