Skip to content
Home » QMSR transition: audit checklist before your next inspection

QMSR transition: audit checklist before your next inspection

Quality manager reviewing a QMSR audit checklist and inspection records before an FDA medical device inspection

Your Quality Management System Regulation transition audit checklist should do more than confirm that procedures exist. It should prove that your quality system, records, training, controls, and inspection responses are aligned with the current United States Food and Drug Administration model and can stand up under live investigator review.

If your team is still preparing around the old Quality System Inspection Technique logic, the preparation is already behind the current inspection reality. This article gives you a practical pre-inspection checklist, explains what changed under the Quality Management System Regulation, and shows you how to close the gaps that tend to surface when investigators start connecting records across design, risk, production, complaints, corrective action, and management oversight.

What Is The QMSR Transition, And Why Does It Matter Before Your Next Inspection?

The Quality Management System Regulation, or QMSR, is now the operating rule for medical device quality system compliance under Title 21, Code of Federal Regulations, Part 820. The United States Food and Drug Administration aligned Part 820 with International Organization for Standardization 13485:2016, which means your inspection readiness now depends on how well your system performs inside that revised structure, not how well it mirrors the older Quality System Regulation language.

This matters because many companies completed document updates but never finished operational transition work. A revised quality manual, a polished procedure hierarchy, and a neat clause crosswalk do not protect you if your complaint files are hard to retrieve, your design change records do not connect back to risk files, or your labeling controls sit outside the same controlled record process as the rest of the system. Inspectors do not evaluate readiness by how polished your binder looks. They evaluate whether the system functions, whether records are controlled, and whether your people can produce evidence fast without contradiction.

The transition also matters because the inspection model changed with it. Teams that spent years training managers and subject matter experts to respond within the old subsystem rhythm now need a broader readiness model. Your organization has to answer questions that move across functions, records, and risk points without losing traceability. That requires more than compliance language. It requires operational discipline.

If your company sells devices in the United States and assumed this transition was mainly about harmonization language, that assumption needs correction. The practical issue is inspection execution. You now need a system that reflects International Organization for Standardization 13485:2016 expectations, supports Food and Drug Administration specific requirements still retained in Part 820, and performs under a risk-based inspection process that can expose weak links fast.

Do You Need International Organization For Standardization 13485 Certification To Comply With QMSR?

No, you do not need an International Organization for Standardization 13485 certificate to comply with the Quality Management System Regulation. This point causes repeated confusion, especially among smaller manufacturers, software-driven device companies, and teams entering the United States market for the first time. Compliance with the regulation is not the same as holding a certificate issued by a registrar.

That distinction matters during audit planning. If your team treats certification status as the main readiness marker, the inspection preparation can drift toward appearance rather than evidence. A company can hold certification and still fail to produce clean, current, linked records during a Food and Drug Administration inspection. A company can also operate without certification and still demonstrate an effective quality system if procedures are controlled, responsibilities are defined, records are complete, training is current, and management oversight is documented and active.

Your checklist should treat certification, if it exists, as supporting context rather than the center of the readiness effort. What investigators need to see is implementation. They want to see whether your design controls are active where applicable, whether suppliers are evaluated and monitored, whether nonconforming product decisions are documented, whether complaint handling is disciplined, whether corrective and preventive action records show real follow-through, and whether record control allows reliable retrieval.

This is where many transition programs lose sharpness. Teams focus on matching clause language but fail to prove that the system works in the day-to-day record stream. If your internal audit still uses phrases like “system appears compliant” without checking approvals, revision control, training effectiveness, linked records, and closure evidence, your audit program is too shallow for current inspection expectations.

What Changed In Food And Drug Administration Inspections Under QMSR?

The biggest operational change is that the Food and Drug Administration stopped using the Quality System Inspection Technique, often called QSIT, for device inspections and moved to an updated inspection process under Compliance Program 7382.850. That shift changes how you should run mock inspections, how you prepare subject matter experts, and how you structure retrieval drills before investigators arrive.

Many companies still organize inspection prep around the familiar Quality System Inspection Technique flow because that is what their quality leaders, consultants, and long-time employees know best. That legacy muscle memory is understandable, but it creates blind spots. A team can become very good at walking through known subsystem patterns and still struggle when an investigator moves more directly through risk, records, and process linkages. Under the current model, your readiness has to be broader and faster.

Your audit checklist should reflect that change. It should test whether your personnel can connect the dots across the quality system instead of answering from a single silo. When an investigator starts with a complaint, can your team show the evaluation, risk impact, any design change review, associated corrective action, training updates, and resulting production or labeling controls without delay? When an investigator reviews a supplier issue, can your team connect supplier qualification, incoming controls, nonconformance records, product impact review, and management escalation?

The inspection shift also means your mock audit should feel less scripted. You need to pressure-test retrieval speed, role clarity, escalation paths, and consistency across documents. If the quality group knows where everything lives but operations, engineering, manufacturing, regulatory affairs, and service teams give uneven answers, the system is not inspection-ready. Readiness now depends on organizational control, not just document ownership.

What Should Be On A QMSR Audit Checklist Before An Inspection?

Your Quality Management System Regulation audit checklist should focus on evidence, control, and retrieval. The right checklist is not a generic internal audit template with a fresh title. It is a targeted inspection-readiness tool that checks whether your current system matches the revised Part 820 structure, covers retained Food and Drug Administration specific requirements, and produces records that investigators can follow from start to finish.

Start with your quality management system structure. Confirm that the scope of the quality management system is defined, current, and consistent across your quality manual, procedures, organizational responsibilities, and actual operations. Review the quality policy, measurable quality objectives, management review process, internal audit program, training control, document control, records control, supplier management, design and development controls where applicable, production controls, process validation where required, complaint handling, servicing where relevant, nonconforming product control, and corrective action process. The point is not to confirm that these topics exist on paper. The point is to verify that each one is implemented, current, and supported by records that tell a coherent story.

Then move into record control. This area deserves special attention because record weakness creates inspection trouble faster than almost anything else. Your team should verify that controlled records are identifiable, approved where required, retrievable, protected from unintended change, retained for the correct period, and clearly linked to the applicable process. If your system stores procedures in one platform, training in another, complaints in a third, and engineering change history in a fourth, your checklist must test retrieval across all of them. A fragmented architecture is not automatically noncompliant, but it does increase inspection friction if the linkages are weak or informal.

Labeling and packaging controls must also be reviewed with care. These are not side issues that can be delegated and forgotten. If your team treats labeling as a commercial artifact instead of a quality-controlled device record, you are creating unnecessary inspection risk. Verify approval workflows, revision history, release controls, reconciliation practices where applicable, obsolete version segregation, and consistency between approved labeling, device master records, and marketed product configurations.

Include a mapping review as part of the checklist. Your organization should maintain a working crosswalk that links legacy Title 21, Code of Federal Regulations, Part 820 concepts to the current Quality Management System Regulation and International Organization for Standardization 13485:2016 clauses. This is not just a training tool. It is a practical bridge for internal auditors, procedure owners, and inspection coordinators who still think in old citation patterns. A good mapping file reduces confusion, speeds response preparation, and helps you spot gaps where procedures were renamed but not truly aligned.

End the checklist with a retrieval drill. Select a complaint, a supplier issue, a design change, a training record, a corrective action, and a labeling revision. Require the team to produce the governing procedure, current approved record, approval history, linked risk rationale where relevant, training status, and closure evidence. Put a time limit on the exercise. If retrieval becomes a search party, your checklist has identified a real readiness problem before the investigator does.

A practical checklist should cover the following items:

  • Defined quality management system scope and applicability
  • Current quality policy and measurable quality objectives
  • Management review records with decisions, actions, owners, and follow-up
  • Internal audit schedule, findings, investigations, actions, and closure evidence
  • Document control and records control procedures aligned with current practice
  • Training records tied to job roles, procedure changes, and effectiveness where needed
  • Design and development controls with traceability across inputs, outputs, reviews, verification, validation, and risk control
  • Supplier qualification, monitoring, re-evaluation, and quality agreement controls
  • Production and process controls, including validation where required
  • Nonconforming product identification, segregation, disposition, and trend review
  • Complaint handling, medical device reporting support where applicable, and service record linkage
  • Corrective and preventive action records with root cause, action, verification of effectiveness, and closure
  • Labeling and packaging controls with approval and revision traceability
  • Inspection response roles, escalation paths, and document retrieval assignments
  • Crosswalk between old Part 820 references, current procedures, and evidence locations

What Are The Biggest Gaps Companies Find During The QMSR Transition?

The biggest gaps are usually not dramatic policy failures. They are connection failures. Companies often have most of the required procedures in place, but the procedures, records, and ownership model do not line up tightly enough to support a clean inspection response. The gap appears when an investigator asks for evidence that crosses functions and the company responds with fragments instead of a traceable chain.

Record mapping is one of the most common weak points. Legacy document structures were often built around older Part 820 expectations, paper-era habits, or department-specific repositories. During transition, teams rename procedures, refresh templates, and insert International Organization for Standardization language, yet leave the underlying record system scattered. The result is a quality management system that sounds current but behaves like an archive of disconnected files.

Another frequent gap sits in retained Food and Drug Administration specific requirements. Some organizations assume that if a process looks compliant under International Organization for Standardization 13485:2016, it must also be ready for the United States inspection environment. That assumption can miss important operational details, especially in records and labeling or packaging controls. Your internal audit should test those points directly instead of assuming that general conformity covers them.

Training drift is another recurring issue. During transition work, procedures change fast, roles shift, and document owners update language without fully resetting training matrices or verifying that affected personnel actually understand the new expectations. A signed training record alone does not solve that problem. If interview answers vary by department, or if employees still use old terminology and old routing habits, your transition remains incomplete no matter how current the procedure list looks.

Management review quality also exposes maturity issues. Some companies treat management review as a standing agenda with generic slides and routine acknowledgments. That will not help you much during an inspection if decisions, risk escalations, resource needs, and unresolved quality signals are not documented in a way that shows active oversight. Management review records should show that leadership monitors system performance, reacts to trends, assigns actions, and drives closure.

Internal audits often reveal another weak spot: audits written to satisfy a schedule rather than test the system. If the audit plan covers every process but the actual audit work is narrow, polite, and surface-level, the transition gaps stay hidden until the inspection. Your auditors should challenge retrieval, traceability, ownership, and effectiveness. Anything less gives you a false sense of security.

Can Investigators Review Internal Audits And Management Review Records Under QMSR?

You should prepare on the assumption that internal audits and management review records may come under close review and will matter during inspection activity. Planning any other way creates risk. If those records show weak issue handling, repeated missed actions, or vague leadership oversight, they can undermine the rest of your inspection narrative.

This is an area where companies sometimes move in the wrong direction. They hear concern about visibility into internal quality records and respond by making audits vague, watered down, or stripped of meaningful detail. That is not a sound control strategy. A weak internal audit record does not protect the organization. It signals that the company either does not see problems clearly or does not manage them with discipline.

Your internal audit files should show clear observations, evidence-based findings, risk-appropriate escalation, assigned ownership, due dates, and verified closure. If management review records contain only attendance, a standard metric list, and generic statements that quality remains adequate, they are not doing enough work for you. Management review should document what leadership saw, what decisions were made, what resources were assigned, and what follow-up is expected. Those records should read like real governance, not ceremonial compliance paperwork.

This also affects how you coach leaders before an inspection. Executives do not need a script packed with regulatory terms. They need command of the system. They should be able to explain quality objectives, major trends, recurring issues, escalation rules, resource decisions, and how the organization verifies that corrective actions actually work. When leadership answers with confidence and record support, the organization looks controlled. When leadership defers every question back to quality, investigators notice.

The strongest position is simple. Run internal audits and management review the way you would want them read by an outsider. That means clear evidence, honest issue reporting, disciplined follow-up, and no gap between what the record says and what the organization actually did.

How Should Small Medical Device Companies Get Inspection-Ready Under QMSR?

Small medical device companies should build for control, clarity, and retrieval speed. Size does not reduce the need for a functioning quality management system. It changes how efficiently you need to organize it. A lean system can perform well if ownership is explicit, documents are controlled, records are easy to retrieve, and leaders stay close to quality signals.

One common mistake in smaller companies is chasing document volume instead of operational discipline. Teams build layers of procedures to look mature, then struggle to follow them. That is a poor trade. A shorter, tighter system that your people actually use will serve you better than a large procedural library copied from a much bigger manufacturer. Your audit checklist should test whether every controlled document reflects real practice. If a procedure describes a workflow your team does not follow, revise it or implement it. Do not leave dead language in place.

Tool selection matters, but tool branding does not solve readiness on its own. Whether you use an electronic quality management system, a validated document platform, or a combination of controlled systems, your environment must support version control, approvals, access management, audit trail visibility, retention, training linkage, and reliable retrieval. If your company stores software history in one tool, quality procedures in another, and complaint files in email trails or loose folders, you need stronger control before inspection.

Role concentration is another small-company issue. One person may own quality, regulatory affairs, supplier oversight, document control, and training administration all at once. That is common, but it raises continuity risk. Your checklist should confirm that backup ownership exists, responsibilities are documented, and critical records remain retrievable even if a single key employee is unavailable. Investigators do not pause expectations because the company is lean.

Small companies also benefit from disciplined mock inspections. Keep them realistic. Require the same people who will face investigators to retrieve records, answer questions, and escalate issues. Use live documents, live systems, and live time pressure. If the organization depends on last-minute coaching from outside consultants to answer basic quality questions, the system needs more internal control.

How Do You Run A Pre-Inspection Mock Audit That Actually Finds Problems?

A useful mock audit does not exist to confirm that everyone can recite procedures. It exists to expose where your system breaks under pressure. That means your mock audit has to feel operational, not ceremonial. Use real records, real time limits, real interviews, and cross-functional questioning that moves from one record set to another without warning.

Start by selecting a set of high-value trails. Pull one complaint, one nonconformance, one supplier issue, one design change, one training update, and one labeling change. From each starting point, trace forward and backward. Check the governing procedure, approvals, linked risk files where relevant, training impact, resulting corrective actions, implementation evidence, and closure status. If any trail requires a subject matter expert to search multiple inboxes, local folders, or unofficial trackers, note that as a control weakness.

Interview people outside quality. Production supervisors, engineers, complaint handlers, service personnel, manufacturing leads, document coordinators, and senior managers should all be tested. Ask them what changed in the quality management system, where they access current procedures, how they know they are using current forms, what they do when records conflict, how issues escalate, and who approves critical changes. You are not looking for memorized regulatory language. You are checking whether the organization behaves like a controlled system.

Then evaluate response discipline. During inspection, delays and inconsistencies create their own risk. Your mock audit should measure retrieval time, completeness of responses, accuracy of document versions, and whether answers stay within the scope of the question. Teams often over-answer, produce drafts instead of approved records, or supply documents without checking revision status. Those habits need correction before they happen in front of an investigator.

Close the mock audit with a written readiness report that ranks issues by inspection impact. Separate cosmetic clean-up from true control failures. A typo in a template matters less than an unlinked complaint investigation, an obsolete labeling record still in circulation, or a corrective action marked closed without effectiveness evidence. If your mock audit does not force those distinctions, it is not preparing you for the real event.

What Should A QMSR Audit Checklist Include?

  • Current quality management system scope and procedures
  • Records control, training, complaints, corrective action, suppliers, labeling
  • Crosswalk to current Part 820 and International Organization for Standardization 13485:2016
  • Mock retrieval drill for inspection evidence

Walk Into The Next Inspection Ready To Prove Control

Your Quality Management System Regulation transition audit checklist should confirm one thing above all else: your system works when someone independent tests it under pressure. If your procedures are current, your records are linked, your people are trained, and your leaders can explain how quality issues move from detection to decision to closure, you are in a strong position. If those elements still live in separate silos, the transition is not finished, no matter how polished the documentation looks. Tighten the crosswalks, run retrieval drills, test real records, and correct weak ownership now. That work turns inspection prep from a paperwork exercise into a controlled operating discipline.


References