Pre-production brief
| Field | Definition |
|---|---|
| Role | Founder, operations lead, or first RA/QA owner after clearance or before commercial distribution. |
| Scenario | The company knows FDA can inspect device establishments and needs a current evidence packet before inspection pressure arrives. |
| Concrete problem | The team may still be using QSIT-era assumptions and has not mapped QMSR-era evidence, MDR questions, or Form 483 response workflow. |
| Useful output | A QMSR evidence map, CP 7382.850 source ledger, gap list, Form 483 response-prep prompts, and MDR escalation questions. |
| TrueMedDevice role | Organize public sources and review artifacts without determining compliance, inspection readiness, reportability, or enforcement risk. |
Use the QMSR-era inspection frame
FDA's QMSR page says QSIT stopped on February 2, 2026 and the inspection process described in CP 7382.850 began. That means a current post-clearance article should not present the four QSIT subsystems as the current organizing model.
Legacy QSIT references may still help teams understand old internal habits, but the public readiness packet should lead with QMSR, ISO 13485 incorporation context, and the current compliance program.
Five days can organize evidence, not certify readiness
A short sprint can help a founder team collect documents, assign owners, and expose gaps. It cannot prove the QMS is compliant or inspection-ready.
The safer framing is a five-day evidence organization sprint: gather what exists, identify missing records, create a review index, and hand the packet to qualified RA/QA or regulatory counsel before making readiness claims.
| Day | Output |
|---|---|
| 1 | QMSR/CP 7382.850 source packet and owner list. |
| 2 | Procedure and record index for design, production, supplier, complaint, CAPA, training, and management-review evidence. |
| 3 | Complaint, MDR, recall, service, and field-signal review queue for qualified evaluation. |
| 4 | Gap log with evidence status, owner, due date, and escalation path. |
| 5 | Consultant-ready inspection-prep packet with source links, open questions, and no readiness conclusion. |
Treat inspection triggers as questions, not predictions
Public sources can explain FDA inspection authority, MDR obligations, Form 483 context, and compliance-program structure. They do not allow a founder blog to predict that a particular MAUDE pattern, complaint cluster, competitor finding, or internal gap will automatically trigger an inspection or observation.
The packet should therefore mark these as review questions: what complaint data exists, what MDR assessments were made, what CAPA evidence supports the decision, and what qualified reviewers need to check.
Prepare Form 483 response discipline before a Form 483 exists
FDA explains that a Form 483 lists observations made during an inspection and is not the same as a final agency determination. A response workflow should be prepared before the team is under deadline pressure.
The practical packet should identify response owners, evidence folders, correction/CAPA tracking, review signoff, and escalation to qualified regulatory counsel when needed. It should not promise that a response will prevent escalation.
What TrueMedDevice can prepare
TrueMedDevice can prepare a QMSR-era evidence organization packet: current-source ledger, CP 7382.850 map, QMS evidence index, complaint/MDR question log, Form 483 response-prep checklist, and qualified-review handoff memo.
Source ledger
What it can tell you
FDA's QMSR overview, effective-date context, and statement that FDA stopped using QSIT on February 2, 2026.
What it cannot decide
Whether a specific company is compliant or inspection-ready.
What it can tell you
FDA's FAQ discussion of QMSR implementation and the new inspection process.
What it cannot decide
A manufacturer's specific QMS gap list or compliance state.
What it can tell you
The current FDA compliance program manual for medical-device manufacturer inspections after QMSR implementation.
What it cannot decide
Which evidence an investigator will request in a specific inspection.
What it can tell you
The QMSR final-rule publication record and effective-date context.
What it cannot decide
A company's implementation completeness or audit result.
What it can tell you
The statutory inspection-authority text.
What it cannot decide
Whether a specific facility, timing, or inspection scope will apply.
What it can tell you
FDA's explanation of Form 483 observations and response context.
What it cannot decide
The right response strategy or legal posture for a specific observation.
What it can tell you
FDA's public overview of MDR requirements for manufacturers, importers, and device user facilities.
What it cannot decide
Whether a specific complaint or event is reportable.
Frequently asked questions
Does FDA still use QSIT for device inspections?
FDA's QMSR page says it stopped using QSIT on February 2, 2026 and began using the inspection process described in CP 7382.850.
Can a five-day sprint make us inspection-ready?
No. It can organize evidence and expose gaps for qualified review. Readiness is a professional judgment that this article does not make.
Does this decide whether a complaint is MDR reportable?
No. It helps collect complaint facts and source links so qualified reviewers can evaluate MDR questions.
Need a QMSR-era inspection evidence packet?
TrueMedDevice can organize current FDA QMSR, CP 7382.850, MDR, Form 483, and evidence-index questions before qualified RA/QA review.