Last updated: November 19, 2026
If an FDA investigator asked for your last management review, would you hand it over? You’d better be able to. A QMSR gap analysis checks your quality system, clause by clause, against ISO 13485:2016, which FDA’s amended Part 820 has incorporated by reference since February 2, 2026. Start with risk management, management review, internal audit, and supplier records, and give each gap an owner. KORE1 contractors stay a median 116 days (n=1,887 assignments, November 2026).
By Dave Manchester, Scientific Recruiting, KORE1
A word before the clauses. I recruit contract scientific and quality staff for KORE1’s medical device staffing work, so a long gap list isn’t bad news for my desk. It’s also no reason to buy anything. You can run this whole analysis with your own people, and the sections below are written so you can. QMSR, by the way, is short for Quality Management System Regulation, the name FDA gave Part 820 when it rewrote it.

What Changed for Device Makers When QMSR Took Effect on February 2, 2026?
The Quality Management System Regulation is the amended 21 CFR Part 820, FDA’s rulebook for how device makers design, build, and service a finished device. Since February 2, 2026 it has told you to document a quality management system that meets ISO 13485:2016, the international standard for medical device quality systems, plus a short list of requirements FDA kept for itself.
That date comes from FDA’s final rule, published in the Federal Register on February 2, 2024, which says “This rule is effective February 2, 2026.” Read 21 CFR 820.10 first. Paragraph (a) is the incorporation of ISO 13485, and paragraph (b) is where FDA ties specific clauses to rules outside Part 820, such as unique device identification (UDI), traceability, and the reporting criteria in Part 803. Both paragraphs matter.
FDA’s own additions are few. Section 820.35 spells out what complaint, servicing, and UDI records must contain, and section 820.45 sets labeling and packaging controls that go beyond the standard. If your procedures only follow ISO 13485, you’ve missed those two. Easy to do.
Three changes get lost in the summaries.
The audit exemption is gone. More on that in a moment.
A certificate doesn’t count. The final rule says FDA “does not intend to require medical device manufacturers to obtain ISO 13485 certification” and that a certificate “will not be considered or accepted as a substitute” for an inspection. Plain enough.
And the inspection itself changed. FDA’s QMSR page says that on February 2, 2026 the agency stopped using the Quality System Inspection Technique, the old QSIT guide investigators worked from, and began using the process in Compliance Program 7382.850, Inspection of Medical Device Manufacturers. Compliance Programs 7382.845 and 7383.001 were retired the same day. If your mock audit script still follows QSIT, it’s a script for a test that no longer exists. Retire it.
The wider background on QMSR and software assurance is covered in our piece on how QMSR and CSA change regulated tech hiring, so I won’t restate it here.
How Do You Run a QMSR Gap Analysis, Step by Step?
Six steps, in this order. Skip around and you’ll score the same gap twice.
- Set the scope. Name the sites, the device classes, and the processes you outsource. Scope first. Part 820 reaches contract manufacturers, relabelers, and sterilizers too, so a supplier can be in scope as well.
- Map every procedure to ISO 13485:2016 clauses 4 through 8, then add FDA’s extra requirements from 820.10(b), 820.35, and 820.45. One spreadsheet. One row per procedure.
- Score each gap one of three ways. Missing means no procedure exists. Written but not practiced means the procedure sits on the shelf while the floor does something else. Practiced but not recorded means the work happens and nobody can prove it, which is the sneaky one.
- Rank by patient risk and inspection exposure. A gap that could hurt a patient goes first, even if an investigator would never see it. Patients before paperwork.
- Give every gap an owner, a date, and the evidence that will close it. Evidence means a record or a revised procedure, not “discussed in meeting.” Vague closes nothing.
- Confirm closure with an internal audit run by someone who didn’t fix the gap. Fresh eyes.
I haven’t put a duration or an hours figure on any of those steps, and I won’t, because it depends on how many procedures you have and nobody honest can guess that from outside your building.
Which ISO 13485 Clauses Should You Walk First?
The clause numbers below match the ISO 13485:2016 numbering that FDA’s rule, FDA’s software guidance, and the public transition checklists all use, though the standard itself is sold by ISO, so check each clause against your own licensed copy.
Clauses 4.1 and 4.2, the quality system itself. FDA’s QMSR page says the incorporation “now specifically requires risk management,” and clause 4.1 expects your quality processes to be risk-based. Open your procedure index and ask which ones say how risk decided their rigor. Most won’t.
Clause 4.1.6 covers software used in the quality system. The complaint database, the electronic quality management system (eQMS), the spreadsheet that trends your CAPA backlog. CAPA, short for corrective and preventive action, is the process for fixing a cause rather than a symptom. All of it needs validation before first use, and again after changes, as appropriate. Every piece.
Clause 4.2.3 is the medical device file. It replaces the old device master record, and the final rule says it must contain or reference “the procedures and specifications that are current on the manufacturing floor.” Pull one device and try to find everything in one place. Try it on a Friday afternoon, for the sport of it.
Document and record control, 4.2.4 and 4.2.5, is the clause people call boring right up until a procedure still cites a Part 820 section that no longer exists. Boring matters.
Clause 5.6, management review. Does a dated record exist for each review, showing the inputs in 5.6.2 and the outputs in 5.6.3? Is there a name next to every decision? I’d walk this one early, because it’s now fair game for an investigator.
6.2 is competence, and competence isn’t the same thing as a training log. A signature proves a person sat through a class. Competence is the evidence they can do the work, and the clause asks you to judge how well the training worked, in proportion to the risk of the task. Contractors and temps count, which I get to below.
Clause 7.1 is where risk management is supposed to run through the whole product life, not stop when design freezes, and a common shape for this gap is a risk file updated at design review that then sits untouched while complaints pile up. Sound familiar?
Design and development gets two checks. Clause 7.3.10 is the design and development file, the successor to the design history file, and the final rule says it must “contain or reference all the records necessary to establish compliance with design and development requirements.” Clause 7.3.8, design transfer, is the handoff from the people who drew the device to the people who build it. Gaps cluster there. A device that was designed to one set of tolerances and built to another is a story every quality engineer has at least one of.
Purchasing, clause 7.4, expects supplier controls that scale with risk. A supplier who makes the sterile barrier shouldn’t get the same evaluation as one who sells you shipping tape. If every approved supplier got the same questionnaire, that’s the gap. Tape isn’t a sterile barrier.
Clause 7.5.6 covers validation of production processes, including software that runs or monitors them. You’ll see how FDA wants software validation handled in a minute.
Clauses 8.2.2 and 8.2.3, complaint handling and reporting to regulators. Section 820.35(a) adds what a complaint record has to contain, and 820.10(b)(3) says complaints meeting the reporting criteria of Part 803 go to FDA. Check that your complaint procedure really asks the reportability question every time, and writes down the answer.

Clause 8.2.4 is the internal audit. Does the audit program cover every clause on a schedule you can defend, and are the auditors independent of what they audit? Programs usually skip whatever the auditors find tedious. Human nature.
Clause 8.5 is CAPA, the improvement clause. Two things fail here. Backlogs, and effectiveness checks that declare success before enough time has passed to know.
Which Records Can an FDA Investigator Now Ask to See?
Under the old Quality System Regulation (QSR), section 820.180(c) carved out management review reports, quality audit reports, and supplier audit reports from what FDA could require you to hand over. The QMSR has no such carve-out. Gone.
FDA saw the objection coming. In the final rule, commenters asked it to keep the exception, and the agency answered that it “disagrees that it should maintain the exceptions set forth at Sec. 820.180(c).” The reasoning was harmonization. Other regulators and auditing organizations under the Medical Device Single Audit Program (MDSAP) already see these records, and FDA wrote that such records “are maintained in the regular course of business and should be readily available.”
So three records are on the table. What an inspection-ready version looks like is my read of the standard, not FDA text, so have your regulatory lead check it.
- Management review. A dated record, the attendee list, evidence that each input in 5.6.2 was addressed, and every output in 5.6.3 with an owner and a due date. Top management signs it. Dates too.
- Internal audit reports need scope, criteria, the auditor’s name, the findings, and follow-up on each. The auditor signs, and the manager of the audited area acknowledges.
- For a supplier audit report, I’d want the reason that supplier was audited, tied to the risk the purchasing procedure assigned, then the findings, then what happened to the supplier’s approved status. Quality signs. Short, dated, signed.
I’m not going to give you a count of inspections, warning letters, or Form 483 observations (the list an investigator hands you at the end of an inspection) here. I haven’t pulled those from FDA’s data dashboard, and a number I haven’t checked isn’t a number I’ll print. Not today.
How Does Computer Software Assurance Change Validation of Quality System Software?
Computer software assurance, or CSA, is FDA’s risk-based way to build confidence that production and quality system software works for its intended use, and it replaces the habit of testing every function against a long written script with effort that follows risk.
The document to cite is FDA’s final guidance Computer Software Assurance for Production and Quality Management System Software, issued February 3, 2026, docket FDA-2022-D-0795. It supersedes the version titled “Computer Software Assurance for Production and Quality System Software” that FDA issued September 24, 2025, so if a procedure of yours cites the September title, update it.
The guidance describes assurance as a risk-based approach and says high process risk functions may call for more rigor, such as scripted testing, while functions that aren’t high process risk can use unscripted methods like scenario testing, error-guessing, or exploratory testing. It also says manufacturers may use validation work done by suppliers and cloud service providers. Its footnotes tie the topic to subclauses 4.1.6, 7.5.6, and 7.6 of ISO 13485. It’s nonbinding, so your own validation procedure is what an investigator holds you to.
The staffing consequence is plain. A validation engineer who has worked a CSA program, and can explain why the complaint database got exploratory testing while the sterilizer controller got scripts, is a common contract seat. The skill is judgment about risk. Typing speed isn’t it.
Software validation background for regulated teams sits on our regulated industry tech staffing page.

Who Closes Each Gap, and What Stays With Your Team?
Where are you being asked to increase productivity without adding headcount? That’s the question Devin Hornick, a KORE1 partner, asks in his emails, and a gap list is a good place to ask it. Ask it early. Closing gaps is a project. It has an end date, and permanent headcount rarely does.
The table pairs each gap area with the contract seat that usually closes it and the part that should stay inside your company. The typical gaps are illustrative, not measured. They describe a pattern, and your own analysis will tell you which ones you actually have.
| ISO 13485 clause area | Typical gap (illustrative) | Contract seat | Keep internal |
|---|---|---|---|
| 4.2 documents and medical device file | Procedures still keyed to old QSR sections | Document control specialist or technical writer | Procedure approval |
| 5.6 management review | Inputs and outputs not kept as an inspectable record | Quality systems specialist who assembles inputs | The review and its decisions |
| 6.2 competence | Training logs without competence evidence | Training coordinator | Competence criteria |
| 7.1 risk management | Risk work stops at design | Quality engineer (medical device) | Risk acceptability |
| 7.3 design and development files | File gaps against 7.3.10 | Design file remediation quality engineer | Design review sign-off |
| 7.4 purchasing | Supplier evaluation not risk based | Supplier quality engineer | Approved supplier decisions |
| 4.1.6 and 7.5.6 validation | Script-heavy or missing software and process validation | Validation engineer (CSA) | Validation approval |
| 8.2.2 and 8.2.3 complaints and reporting | Complaints not trended or assessed for reporting | Complaint specialist | Reportability decisions |
| 8.2.4 internal audit | Audit program misses clauses | Contract internal auditor | Audit program ownership |
| 8.5 CAPA | Backlog and weak effectiveness checks | CAPA specialist | CAPA approval and effectiveness sign-off |
Notice the last column. Every decision that carries your company’s name stays with your company. A contractor can assemble the management review inputs, but the review and its decisions are yours, and a contractor who signs a reportability decision for you has been handed something that was never theirs to carry.
Get a bill rate quote for the seats on your gap list. Send me the table rows that apply and the bill rate quote form is where a real number comes from. There’s no dollar figure in this post on purpose. KORE1’s current rate index doesn’t carry a quality engineer line, so I won’t invent one, and seat-level detail lives on our quality engineering staffing page.
Here’s how a contract staffing engagement works, so there are no surprises. Contractors are KORE1’s W2 employees, billed to you hourly and paid weekly on Fridays. Across KORE1 placements, ended assignments ran a median 116 days (n=1,887), and the median offer-to-start was 3 days (n=1,997). Both figures cover all roles, as of November 2026. The data isn’t specific to device quality.
A contractor who has learned your quality system can often become your employee. In Devin’s words, “If this person completes 1,040 hours, then they are eligible to convert over to full time with that particular company at no additional charge from KORE1.” Fair warning on the other side. On contract there is no replacement guarantee. The commitments are that contractors show up on time and get paid on Fridays.
Last, the competence records. Clause 6.2 applies to anyone whose work affects product quality, and that includes contractors. The drug-side rules differ from yours, but the habit of proving training carries across, and I laid out what an investigator asks about temps in training records for contract staff. After a Form 483 lands, the FDA 483 remediation staffing page is the better first read.
What Device Quality Leaders Ask About a QMSR Gap Analysis
Is an ISO 13485 certificate enough under QMSR?
No. FDA does not require ISO 13485 certification and will not accept a certificate in place of an inspection, so a certificate never replaces your own gap analysis against Part 820.
Part 820 adds requirements the standard doesn’t carry, such as the record content in 820.35, and FDA has said it can’t be sure independent ISO 13485 audits cover Parts 803, 806, 821, or 830. A certificate can still matter for other markets. It just isn’t your FDA answer.
Is QMSR just the old QSR with new numbering?
No. QMSR replaces FDA’s own requirement list with ISO 13485:2016 by reference, keeps a few FDA-specific rules, and drops the old exemption for management review, audit, and supplier audit reports.
A lot maps across. The old design history file becomes the design and development file in clause 7.3.10, and much of the old device history record now lives in the medical device file or batch record. Mapping isn’t the same as done, though. Wording, scope, and proof all moved.
Do contract staff need competence records?
Yes. Clause 6.2 expects competence to be established and recorded for personnel whose work affects product quality, and a contractor doing that work is one of those people.
Keep the same evidence you keep for employees. Education and experience on file, training on your procedures, and some proof the training worked. The staffing firm can supply history. The competence call is yours.
Did QMSR change Medical Device Reporting under Part 803?
No. The final rule amended only 21 CFR Parts 4 and 820, so Part 803 stands as written, and 820.10(b)(3) ties complaint reporting under clause 8.2.3 to Part 803’s criteria.
So a complaint that meets the Part 803 criteria still goes to FDA. What QMSR changed is where the duty lives in your procedures. Complaint handling, 8.2.2, and reporting, 8.2.3, have to talk to each other.
Send Me Your Gap List
If your analysis has turned up gaps and your team is already full, send me the list. Tell me the clauses, the seats you think you need, and when the audit is. I’d rather read a messy list than a polished one. Messy is fine.
Let’s Connect. You can also find me on LinkedIn. Expert in finding you the right talent, right away.

