FDA QSR / QMSR Audit Prep

May 27, 2026 · View on GitHub

Operational playbook for FDA inspection preparation under Quality System Regulation (21 CFR 820) and the transitioning Quality Management System Regulation (QMSR, fully effective 2026, harmonizing with ISO 13485:2016).

When to use this skill vs. fda-consultant-specialist:

  • This skill: FDA inspection imminent OR 483/Warning Letter received; need sprint
  • fda-consultant-specialist: building / maintaining QMS; multi-quarter

When to use this skill

SituationSkill applies
FDA inspection announced (or unannounced visit imminent)Yes — start immediately
Form 483 observation receivedYes — scripts/qsr_readiness_score.py to assess + plan response
Warning Letter receivedYes — plus engage outside FDA counsel
Annual readiness assessmentYes — periodic sprint
Building QMS from scratchUse ra-qm-team/fda-consultant-specialist
Medical device submission (510k / PMA)Use ra-qm-team/fda-consultant-specialist

The audit-prep sprint at a glance

2-week sprint (announced inspection, mature QMS)

Week 1: Inventory, walkthrough rehearsal, gap remediation
Week 2: Inspection week (front room + back room operation)

8-week sprint (gaps identified, scheduled inspection)

Weeks 1-2: Readiness assessment + 483 / WL prior issue review
Weeks 3-6: Gap remediation (DHF, CAPA, complaint records, etc.)
Weeks 7-8: Mock inspection + final remediation + inspection prep

Reactive: 483 / Warning Letter response

- 483: 15 business days to respond (then ongoing)
- Warning Letter: 15 business days to respond (then full corrective action plan)
- Approach: Acknowledge + investigate root cause + corrective action plan + commitment + evidence

QSR / QMSR key audit areas

21 CFR 820 SubpartTopicAudit focus
Subpart BQuality systemManagement responsibility, quality policy, planning
Subpart CDesign controlsDesign history file (DHF), design reviews, V&V
Subpart DDocument controlsDocument approval, change control, distribution
Subpart EPurchasing controlsSupplier qualification, agreements, evaluations
Subpart FIdentification and traceabilityProduct ID, lot/batch traceability
Subpart GProduction and process controlsProcess validation, environmental controls, equipment maintenance
Subpart HAcceptance activitiesReceiving, in-process, finished device acceptance
Subpart INonconforming productIdentification, segregation, disposition
Subpart JCorrective and preventive action (CAPA)CAPA process, root cause analysis, effectiveness verification
Subpart KLabeling and packagingLabel inspection, packaging validation
Subpart LHandling, storage, distributionProcedures, shelf-life, distribution records
Subpart MRecordsDevice Master Record (DMR), Device History Record (DHR), QSR records
Subpart NServicingServicing procedures, complaint review
Subpart OStatistical techniquesSampling, statistical methods

QMSR transition (effective Feb 2026): Harmonizes 21 CFR 820 with ISO 13485:2016. Adds requirements for risk management (ISO 14971), software lifecycle (IEC 62304), usability (IEC 62366).


Quick start

  1. Run readiness score: python3 scripts/qsr_readiness_score.py --config qsr-controls.yaml
  2. Check DHF completeness for in-scope devices: python3 scripts/dhf_completeness_checker.py --dhf device-dhf.yaml
  3. Pick sprint length based on score + known issues
  4. Execute sprint per references/fda-qsr-pre-inspection-checklist.md

Common FDA inspection findings (highest 483 / Warning Letter trigger)

  1. CAPA failures — root cause not addressed, ineffective corrective action
  2. Complaint handling — complaints not investigated, MDR (Medical Device Reporting) missed
  3. Design controls (Subpart C) — DHF incomplete, V&V gaps, no design reviews
  4. Process validation — processes not validated, validation stale
  5. Supplier controls — suppliers not qualified, agreements missing, evaluations skipped
  6. Document control — old procedures in use, no document approval evidence
  7. Management responsibility — no management review, no quality policy, no objectives
  8. Records (DHR) — incomplete records, missing lot traceability

See references/483-warning-letter-prevention.md for prevention patterns + response templates.


Inspection-week operations

Front room (where inspector works)

  • Designated front room (conference room, not someone's office)
  • Front-room lead (often Quality Manager) accompanies inspector all day
  • All requests routed through front-room lead
  • Inspector requests evidence; front-room asks back-room

Back room (where requests are fulfilled)

  • Cross-functional team available
  • Document retrieval, witness preparation, technical questions answered
  • Inspector requests evidence; back-room delivers (filtered through front-room lead)

Daily debrief

  • End of each inspection day: review what was inspected, observations, next-day topics
  • Prepare overnight any evidence needed for next day

After inspection

  • Form 483 review (if issued): consult with QA Lead + outside counsel
  • 15 business days to respond
  • Full corrective action plan
  • Ongoing engagement with FDA office

Tooling

ScriptPurpose
scripts/qsr_readiness_score.pyScore current QSR/QMSR state per subpart
scripts/dhf_completeness_checker.pyValidate Design History File completeness per device

References


  • ra-qm-team/fda-consultant-specialist — deep FDA program (510k, PMA, QMSR build)
  • ra-qm-team/quality-manager-qms-iso13485 — ISO 13485 QMS (QMSR harmonized)
  • ra-qm-team/risk-management-specialist — ISO 14971 (required for QMSR)
  • ra-qm-team/capa-officer — CAPA process specialist
  • ra-qm-team/qms-audit-expert — internal/external QMS audits
  • ra-qm-team/audit-prep/compliance-readiness — multi-framework readiness