QMSR Mock Inspection: Rehearse the Evidence Across CP 7382.850’s Six QMS Areas

A QMSR mock inspection is a controlled rehearsal of how your team retrieves records, explains decisions and connects evidence across its quality system. It is not a scripted performance, a certification audit or a prediction of FDA's inspection classification.

FDA's Quality Management System Regulation became effective February 2, 2026. FDA now uses CP 7382.850 for medical-device inspections rather than the former QSIT approach. The practical preparation question is no longer “Have we memorized an inspection checklist?” It is “Can we demonstrate that our processes work using authentic, current records?”

Use the six QMS areas as an evidence map

CP 7382.850 organizes inspection coverage around six QMS areas. They help teams plan a connected rehearsal, but they do not promise a fixed agenda or equal attention to every area during a real inspection.

Start with the six QMS areas guide for broader context. A single sample can cross several areas: a field complaint may lead to a software change, outsourced testing and a management decision. Rehearsing these handoffs reveals more than six independent document searches.

Build an accountable inspection team

Assign a primary and backup host, record coordinator, technical subject-matter experts and quality/regulatory lead. Make clear who receives requests, who retrieves records, who checks the applicable revision and who answers questions. Avoid having several people send different versions of the same evidence.

Choose a mock investigator sufficiently independent of the processes being reviewed. Internal colleagues may conduct the exercise where appropriate, but process familiarity can hide assumptions. Define scope, confidentiality and escalation rules. Do not use unnecessary patient information or transfer confidential records into a general coordination tool.

The Cahir MedTech CP 7382.850 Mock Inspection Kit starts with Request Log; it does not contain a separate Universal Baseline tab. Use War-Room Roster, Retrieval Tracker, Request Log, Interview Guide and the applicable category overlay to coordinate the exercise. Confirm the exact tab instructions in the Mock Inspection companion manual.

Map records before testing retrieval speed

Record document identifiers, approved revisions, owners and controlled locations. Select one current product or software version and follow its evidence from requirements through risk controls, verification/validation, release and postmarket feedback. Include a real deviation or open investigation rather than choosing only the cleanest files.

There is no universal FDA retrieval-time target prescribed by this article. Set an internal rehearsal target suited to the request and record system; do not confuse it with a legal deadline. Measure accuracy and explanation quality alongside speed. A quickly retrieved obsolete procedure is not a successful result.

If access depends on one employee's personal folder, fix the record-control weakness instead of simply coaching that employee to be available.

Run the request drill and interview rehearsal

Have the mock investigator issue requests through the host. Log the wording, owner, times, evidence delivered and any clarification. Use the Retrieval Tracker for controlled record locations, reviewer checks and pre-staged status; keep additional tasks and findings in controlled drill notes. Distinguish records provided from evidence still under review; preserve a record of mismatches and follow-up questions.

Interview process owners using open questions: “Show how this requirement reached the released version,” or “Explain why this complaint did or did not trigger additional action.” Staff should explain their actual process and identify records that support it. They should not memorize a compliant-sounding answer or guess when uncertain.

Test the handoffs between functions. For a SaMD change, ask engineering to identify the build, quality to show review/approval, and regulatory to explain the marketing-authorization assessment. A submission assessment and technical release approval are separate decisions. An authorized PCCP applies only within its applicable scope and controls. Our design-controls guide provides a useful starting point for the evidence chain.

Add the device-specific questions that matter

Select the SaMD, IVD, implantable, capital-equipment or consumable overlay according to actual products and operations. For SaMD, review configuration control, anomalies, cybersecurity-relevant changes and validation. For IVD, connect reagent/control/instrument combinations and performance evidence. For implants, assess material, packaging and sterility records where applicable—not an assumed requirement for every product.

For capital equipment, trace installed configurations and service history. For consumables, sample supplier lots, process controls and packaging or shelf-life changes. Document why a prompt does not apply. Category overlays do not replace device-specific regulations, authorizations or qualified applicability review.

Debrief into improvement, not a rehearsal score

• Every request has a recorded outcome and owner for open work.
• Wrong revisions, missing approvals and unexplained decisions are identified.
• Each finding has an assessment of significance and affected scope.
• Corrections and CAPA decisions follow the company's procedures.
• Appropriate reporting assessments are made without waiting for the next drill.
• Effectiveness checks and a focused repeat rehearsal have accountable owners.

Avoid treating all findings as administrative filing issues. A missing link may be a retrieval defect, or it may reveal that required work was never completed. Assess the facts before deciding. A practice drill must never become a reason to create retrospective evidence that misrepresents what happened.

Use the workbook and workspace together

The CP 7382.850 Mock Inspection Kit costs $299 USD one-time; applicable taxes may apply. It includes the workbook and branded companion guide. Read the online manual and download its PDF to orient the team, then purchase with a work-email account to access the paid workbook.

Workspace checklists, notes and activity help coordinate responsibilities; controlled QMS records remain the source of detailed evidence and approvals. The workspace does not modify the downloaded workbook or perform an FDA inspection. Discuss an evidence-review workflow with Cahir MedTech Copilot if your team needs help framing questions; software support does not replace qualified judgment.

Does ISO 13485 certification exempt us from FDA inspection? No. Certification does not remove FDA's inspection authority or prove that all FDA-specific requirements have been met. Review Part 820 together with other applicable device requirements.

Does a successful drill guarantee no Form 483 observations? No. A mock inspection uses a limited internal sample. FDA determines the actual scope, findings and follow-up based on its inspection and applicable requirements.

Primary sources and applicability

• FDA CP 7382.850 — inspection coverage, QMS areas and follow-up.
• FDA QMSR overview — effective date, inspection transition and certification limitations.
• 21 CFR Part 820 — QMSR and FDA-specific provisions.
• 21 CFR Part 803, Part 806 and Part 821 — separate reporting, corrections/removals and applicable tracking requirements.

This article is educational guidance, not an FDA inspection script or certification service. Use an authorized copy of ISO 13485:2016, current primary sources and your actual device scope. Publication date: October 20, 2026; editorial/source review: October 29, 2026.