borghei/Claude-Skills / ra-qm-team/audit-prep/fda-qsr-audit-prep
fda-qsr-audit-prep
VerifiedFDA Quality System Regulation (21 CFR 820 / QMSR) audit-prep playbook for medical devices. Use when an FDA inspection is announced, when preparing for the new QMSR (2026), or when a 483 / Warning Letter response is needed.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.1 KB |
| references/483-warning-letter-prevention.md | markdown | 10.0 KB |
| references/fda-qsr-pre-inspection-checklist.md | markdown | 10.4 KB |
| scripts/dhf_completeness_checker.py | script | 9.9 KB |
| scripts/qsr_readiness_score.py | script | 9.8 KB |
references/483-warning-letter-prevention.md
View on GitHub# 483 / Warning Letter Prevention and Response
Reference for preventing FDA Form 483 observations and Warning Letters, and for responding when they occur. Covers common triggers, response templates, escalation paths, and the patterns that prevent recurrence.
---
## 483 vs Warning Letter — the difference
| Form 483 (FDA observations) | Warning Letter |
|------------------------------|----------------|
| Issued at end of inspection | Issued post-inspection after FDA review |
| Lists specific observations of non-conformance | Indicates regulatory deficiencies + potential enforcement |
| 15 business days to respond | 15 business days to respond |
| Not formal enforcement; signals risk | Formal enforcement; signals serious risk |
| Approximately 1,400+ issued per year | Approximately 100-200 issued per year |
| Public via FDA database | Public via FDA database (more visible than 483s) |
A 483 unaddressed becomes a Warning Letter. A Warning Letter unaddressed becomes consent decree, import detention, criminal charges.
---
## The top 10 most-cited 483 areas
Year over year, FDA inspection findings cluster:
1. **CAPA failures (820.100)** — root cause not addressed; ineffective action; no effectiveness verification
2. **Complaint handling (820.198)** — complaints not investigated; MDRs missed
3. **Design controls (820.30)** — DHF incomplete; V&V gaps; design review skipped
4. **Production / process controls (820.70)** — validation missing or stale
5. **Document controls (820.40)** — old docs in use; no approval before issue
6. **Supplier controls (820.50)** — supplier not qualified; agreements missing
7. **Management responsibility (820.20)** — no management review; objectives missing
8. **Equipment / facility (820.70 / 820.150)** — calibration overdue; maintenance skipped
9. **Records (820.180-198)** — DHR incomplete; missing data
10. **Acceptance activities (820.80-86)** — receiving / in-process not documented
Most companies that get cited are cited in CAPA + Design Controls.
---
## Prevention patterns
### Pattern 1: CAPA discipline
- All CAPAs tracked in a single log (no shadow systems)
- RCA mandatory (5-Why, Fishbone, FTA, FMEA — pick one and use)
- Corrective action plan with owner + due date
- Effectiveness verification mandatory (not just "we changed the procedure")
- Closure requires verification evidence
- Quarterly trend analysis of CAPAs (recurring issues = systemic)
### Pattern 2: Design controls hygiene
- Design plan up-front (no after-the-fact)
- Inputs traceable to outputs
- Reviews scheduled (not "when we get to it")
- V&V protocols approved before execution
- DHF index document maintained (so you can find evidence)
- Design changes through formal change control
### Pattern 3: Mock inspections
- Internal mock inspection quarterly
- External mock annually (use a consultant who's a former FDA investigator)
- Findings treated as if real 483
- Remediation closed within 30 days
- Builds inspection-day muscle memory
### Pattern 4: Walkthrough rehearsals
- Pick 3-5 control owners
- Have someone unfamiliar play "inspector"
- Walk through the control as if responding to inspector questions
- Identify gaps in evidence or explanation
- Rehearse 1 week before inspection
### Pattern 5: Front-room / back-room operation
- Single front-room lead (Quality Manager typically) handles all inspector interaction
- All requests funneled through front-room (no inspector-to-engineer direct asks)
- Back-room pulls evidence, prepares witnesses
- Daily debrief identifies next-day topics
---
## Response: Form 483
### Step 1: Internal team activation (Day 1)
- QA Lead reads 483 carefully
- Outside FDA counsel engaged
- CEO + GC briefed
- Cross-functional team assembled per observation (CAPA owner, design lead, supplier QA, etc.)
### Step 2: Per-observation analysis (Day 1-5)
For each observation:
- What does FDA assert?
- Is the assertion factually correct? (Don't argue facts that are wrong; do correct facts that are right)
- What's the root cause?
- What's the corrective action?
- What's the timeline?
- What evidence supports?
### Step 3: Draft response (Day 5-12)
Structure:
```
Re: Form 483 Observations dated [date]
Inspector: [name]
[Vendor] acknowledges receipt of the Form 483 issued on [date].
We are committed to addressing each observation and have taken
the following actions.
Observation 1: [verbatim from 483]
Our investigation: [findings]
Root cause: [identified cause]
Corrective action taken: [completed actions]
Corrective action planned: [planned with dates]
Effectiveness verification: [how + when]
Evidence: [attachments]
[Repeat per observation]
We are available for any clarification or follow-up.
[Signed by senior management with appropriate authority]
```
### Step 4: Submit response (Day 15)
- Submit to inspector + district office
- Maintain copy in regulatory archive
- Internal communication to leadership + team
### Step 5: Ongoing follow-up
- Track committed actions to closure
- Be prepared for follow-up inspection (re-inspection within 6-12 months common)
- Update SOPs per corrections
- Train staff on changes
---
## Response: Warning Letter
### Step 1: Immediate (Day 1)
- CEO + GC + QA Lead briefed
- Outside FDA counsel ENGAGED IMMEDIATELY (Warning Letter is serious)
- Board awareness if material
- All staff briefed (without disclosing specifics; legal advised)
- Halt practices that triggered WL (per legal advice)
### Step 2: Investigation (Day 1-10)
- Comprehensive RCA per cited issue
- Document gathering
- Witness interviews
- External counsel reviews findings
### Step 3: Comprehensive corrective action plan (Day 10-15)
Beyond 483 response:
- Full RCA per WL item
- Corrective actions completed where possible
- Plan for actions not yet completed (with dates)
- Systemic improvements (process changes, training)
- Effectiveness measurement
- Commitment to FDA dialogue
### Step 4: Response submission (Day 15)
Submit + maintain ongoing dialogue with FDA.
### Step 5: Follow-up
- FDA may schedule follow-up inspection
- Compliance officer engagement common
- Public WL on FDA website (reputational impact)
- Customer notification may be required (depending on issue)
---
## Escalation patterns
### Within company
```
Quality Manager (front-line) → Director of Quality → VP RA/QA → CEO
↓
GC (parallel)
↓
Board (if material)
```
### To outside resources
```
- Outside FDA counsel: within 24h of 483; immediately for WL
- Crisis communications / PR: when public visibility likely
- Insurance broker: review D&O coverage; potential claim
- Customer relations: customer-facing if devices in market
```
---
## Document retention for inspections
Retain per QSR requirements (typically lifetime of device + 2 years; specific subparts vary):
- QSR records: lifetime of device + 2 years (820.180)
- Design records: per design history file requirements
- Complaint records: 2 years minimum (820.198(g))
- MDR records: 2 years from event date
- Manufacturing records (DHR): 2 years from release
Inspector can request any record. Make findable.
---
## "Inspector says X" — common requests
| Inspector asks | Response pattern |
|----------------|-----------------|
| "Show me your CAPA log" | Print most recent log (all open + closed for inspection period) |
| "Show me CAPA #[N]" | Pull complete CAPA record: RCA, action, evidence, verification |
| "How do you handle complaints?" | Walk through complaint procedure; show recent complaint records |
| "Show me design controls for [device]" | Pull DHF for that device |
| "Show me validation for [process]" | Pull validation protocol + report |
| "Who is your management representative?" | Show appointment letter; describe role |
| "Walk me through [procedure]" | Procedure owner walks inspector through |
| "What's your training program?" | Show LMS records, training matrix |
| "Show me last management review" | Meeting minutes + action items |
| "What is your error rate for X?" | Provide actuals with date range |
Always: have the document; know where to find it; have someone who can walk through it credibly.
---
## What NOT to do during inspection
- Lie to inspector — federal crime
- Argue about FDA interpretation — note + move on
- Volunteer information beyond what's asked
- Have engineering / sales talk directly to inspector
- Show inspector documents that haven't been pre-reviewed for relevance
- Promise corrective action without clearance from QA + legal
- Take photos of inspector or hide your own documentation
- Hide documents (always findable; never destroyed inappropriately)
- Make the inspector feel rushed
- Deny access to records, areas, or witnesses without GC consultation
---
## What TO do during inspection
- Be professional, courteous, fact-based
- Acknowledge issues found
- Provide requested evidence promptly
- Note observations carefully
- Have a back-room running smoothly
- Have a daily debrief
- Keep CEO informed
- Track every interaction for the formal record
---
## Cheat sheet
| Question | Answer |
|----------|--------|
| When to engage outside counsel? | 483: within 24h. WL: immediately. |
| 483 response template available? | Yes; see step 3 above |
| What if I disagree with the observation? | State your position factually; remediate where remediation is the right call regardless |
| Who signs the response? | Senior management with quality system authority (often Site Head or COO) |
| Most-cited issue? | CAPA failures consistently #1 |
| Most-preventable issue? | CAPA failures (with discipline + verification) |
| What if FDA returns for follow-up? | Treat as new inspection; demonstrate progress on prior 483 |
| Public visibility of 483? | Yes, FDA database; subscribe + monitor |
| Public visibility of WL? | Yes; more prominent than 483; reputational impact |
| Recovery from a Warning Letter? | Possible with disciplined corrective action; typically 12-24 months to fully resolve |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |