Under QMSR, “We Have a Procedure” Isn’t Enough Anymore

What Is QMSR?

Every quality team has a procedure for field inventory. A document somewhere describes how consigned stock should be tracked, how loaner kits should be returned, how placed equipment should be accounted for during a transition, how expiring product should be handled. Under the old Quality System Regulation, having that document on file and being able to describe the process to an investigator was most of what mattered. That is no longer the standard.

The Quality Management System Regulation (QMSR) is FDA’s revised device quality rule, effective February 2, 2026, replacing the prior Quality System Regulation (QSR) and incorporating ISO 13485:2016 by reference. It shifts FDA’s inspection focus from whether a written procedure exists to whether that procedure demonstrably functions in practice.

What Actually Changed

QMSR incorporates ISO 13485:2016 by reference, and FDA retired its old Quality System Inspection Technique in favor of a new inspection process built around that standard. The shift is described by FDA and by the quality community as a move toward a more risk-based, process-effectiveness model. In practice, that means an investigator is now positioned to ask not just what your procedure says, but whether your records demonstrate the procedure actually functioned, consistently, over time.

That distinction sounds subtle. For field inventory, it is not. A written SOP for expiration management or consignment reconciliation is easy to produce. Evidence that the SOP was followed, every time, at every location, by every rep, for the last quarter, is a different kind of record entirely, and it is exactly the kind of record most field operations cannot currently produce.

Why Field Inventory Is the Weak Point

Manufacturing and design controls have had decades to build documentation discipline around QSR, and most companies can show an investigator a clean paper trail for what happens inside the plant. Field inventory rarely gets the same rigor, because the movement happens outside the building. It is a rep’s trunk stock, a loaner kit traveling between cases, a consigned tray at a hospital, a capital console placed at a customer site and handed off when a territory changes. A functioning control in that environment is not a matter of having a policy. It is a matter of the policy actually shaping what happens at the moment product moves, and having a record that proves it.

What a Functioning Control Actually Looks Like in the Field

Take expiration management as the example, since it is one of the more common QMSR-relevant gaps in field operations, and one that cuts across every device category. A written policy says something like: rotate stock so older product is used first, and confirm condition before a returned or placed item goes back into circulation. Under the old standard, having that sentence in a procedure was close to enough. Under QMSR’s process-effectiveness lens, the question becomes whether that rotation actually happens, and whether there is a record showing it.

A functioning version of that control has two parts, and both have to hold up under scrutiny, not just exist on paper. The first is sort discipline at restock: arranging every trunk case, loaner tray, or set of disposables staged at an account so the item expiring soonest sits in the position reached first. The second, and the part most procedures miss entirely, is replenishment insertion discipline: new stock has to go in relative to what is already there, not wherever there is open space, or the rotation breaks on the very next shipment. The same logic governs a tray of implants in a rep’s vehicle and a shelf of dated disposables sitting beside a placed unit at a hospital.

Neither of these is a system sending a reminder. They are gating steps in a physical workflow, and the difference matters under QMSR, because a reminder proves you were told something. A gating step, logged at restock and at replenishment, proves the control operated.

How an Unresolved Gap Becomes a 483 Observation

When a functioning control cannot be demonstrated, the result an investigator documents is a Form 483, the list of inspectional observations issued at the close of an inspection. The pattern is consistent and not hypothetical. A company keeps a sound written procedure for stock rotation and condition assessment, but cannot show that the control operated in the field: product is stored in a way that does not facilitate proper rotation, returned or placed items go back into circulation without a documented condition check, and the records needed to prove otherwise live in texts, spreadsheets, and memory. The observation writes itself, because the inspector is not evaluating the policy. They are evaluating the evidence that the policy functioned, and that evidence does not exist in a form that can be produced.

Findings like these rarely stay contained to a line on a form. An inventory-control observation that points to product condition or rotation can widen into questions about every lot that passed through the same uncontrolled process, and the cost shows up as write-offs of product that can no longer be trusted, holds on affected inventory, and the revenue lost while the gap is remediated. That is what happens when the distance between a written procedure and a functioning one goes unaddressed long enough for an inspector to find it.

What This Means for the Audit Trail

The practical test is simple to state and hard for most companies to pass today. If an investigator asked for 90 days of evidence that field inventory rotation actually happened, not that a policy exists describing it, could you produce it the same day, or would it take a multi-week reconstruction from memory, texts, and spreadsheets? A reconstructed record is itself a finding waiting to happen, because a record that has to be rebuilt after the fact is not the same as a record that was captured when the event occurred.

The uncomfortable reframe is this: field inventory is not adjacent to your quality system anymore. It is inside it.

In the next part of the series, we walk through exactly what happens when an auditor asks for ninety days of field history, and why manual reconstruction is both slow and quietly dangerous.

Frequently Asked Questions

• What is QMSR and when did it take effect?
  QMSR, the Quality Management System Regulation, took effect February 2, 2026, replacing FDA’s prior Quality System Regulation and incorporating ISO 13485:2016 by reference.
  
  

• Does QMSR apply to field inventory, not just manufacturing?
  Yes. QMSR’s process-effectiveness standard applies to any quality system record FDA reviews during inspection, including field inventory records such as consignment tracking, loaner kit returns, placed-equipment accountability, and expiration management, not only manufacturing floor documentation.
  
  

• What is the difference between QMSR and the old QSR?
  The QSR required a written quality system. QMSR, by incorporating ISO 13485 and changing FDA’s inspection technique, tests whether that system’s controls demonstrably function, evaluated through records showing consistent execution over time.
  
  

• What happens if a control exists on paper but isn’t consistently followed?
  It can surface as an FDA Form 483 observation during inspection, an inspectional finding that a condition appears to violate applicable requirements, which can escalate to a warning letter if the response is inadequate.
  
  

• What does QMSR’s incorporation of ISO 13485 mean for field inventory records specifically?
  By incorporating ISO 13485:2016, QMSR extends the standard’s requirements for identification, traceability, and record control to field inventory. Consigned stock, loaner kits, trunk inventory, and placed equipment are subject to the same record-keeping expectations as manufacturing floor documentation, not a separate, lower standard.