How do I know if the quality system I already wrote will survive an audit?

A written procedure is not what gets audited. What gets audited is whether the records show it happening. Under NSF/ANSI 455-2, the standard a supplement plant is audited against when a retailer or a customer asks for GMP certification, an audit is eight activities and document review is one of them (NSF/ANSI 455-2, clause 5.5). The other seven read the same system through your people, through your production flow, and through a lot the auditor picks. A procedure that reads beautifully passes the one activity you can rehearse and gets found out by the rest.

So the honest test of a system you already wrote is not whether it is well written. It is whether your people, your records and one timed traceability exercise all say the same thing your procedure says.

Everything below is United States federal law and a certification scheme written against it. If neither your operation nor your product reaches the United States, none of it is aimed at you, and the equivalent question in your own market is a different one.

First, whether any of this reaches you

21 CFR Part 111 reaches you if you manufacture, package, label, or hold a dietary supplement (21 CFR 111.1(a)), including a supplement you manufacture that somebody else packages or labels (111.1(a)(1)) and one imported or offered for import (111.1(a)(2)). The holding requirements do not reach you if you hold supplements at a retail establishment for the sole purpose of direct retail sale to individual consumers, and the rule says plainly that a warehouse or other storage facility for a retailer is not a retail establishment (111.1(b)).

Four verbs, and one of them is enough. Answer for your own operation rather than for your supply chain:

• Do you manufacture a dietary supplement?
• Do you package one?
• Do you label one?
• Do you hold one, anywhere other than a retail establishment selling direct to individual consumers?

One yes and Part 111 reaches you. Four noes and it does not.

If you own a brand and your contract manufacturer does every one of those four, the federal rule is aimed at them, and so is the certification audit. Most brands do not get four noes. If your finished goods sit in a warehouse you contract, you are holding. If your manufacturer ships in bulk and a separate house applies the label, that house is labeling and you may still be holding what comes back. Work out which of the four verbs is yours before you decide this page is about somebody else.

The audit itself is a site audit. Its scope runs from incoming material procurement and receipt to finished goods holding and shipment, and it is specific to one site or campus operating under the same quality system, with product storage both on site and off site pulled into scope (NSF/ANSI 455-2, clause 5.3.4). The certificate that comes out of it details the scope of the audit and any limitations or exclusions from that scope (clause 5.8.1). The public certification listing is where the facility address and the facility type sit, alongside the same exclusions and limitations (clause 5.8.4). Neither document is your brand’s, and the exclusions are the part worth reading.

What is still yours either way is everything you wrote, everything you specified, and everything you told them to put on the label. Of the five self-tests below, two run on documents alone and are yours whether or not you own a building. The other three need a floor, people and a lot number. Where the floor is your contract manufacturer’s, those three become questions you put to them, and a refusal to answer is itself a result.

What is actually being tested

The standard asks for two things about your paperwork before it asks anything about your product. A document control program covering initiation, formatting, review, approval, distribution, storage, change control, retention and disposal (clause 4.4.32). And good documentation practices for both paper and electronic records (clause 4.4.33). It cites the same federal clause for both, (21 CFR 111.105).

What a record itself is expected to be is set out one clause further down (clause 4.4.33.3): kept as an original, a true copy or an electronic record; carrying the actual values and observations obtained during monitoring and, as appropriate, during verification; accurate, indelible and legible; created concurrently with the activity it documents; and detailed enough to give a history of the work, naming the plant, the date and where appropriate the time, the initials or signature of the person who did it, and where appropriate the product and its lot code.

Read the middle one again. Created concurrently. Federal law says the same thing ten separate times: ten clauses of Part 111 require documentation at the time of performance. The material review and disposition decision (111.113(c)). The quality control review (111.140(b)(2)). The manufacturing step itself (111.180(b)(3)(i)). Five separate parts of the batch record (111.260(j), 111.260(k), 111.260(l), 111.260(m), 111.260(n)). The laboratory (111.325(b)(2)(i)). The product complaint (111.570(b)(2)(i)).

A record assembled the week before an audit does not fail because somebody notices the handwriting. It fails because the clause that made it a record says when it had to be written.

The record also has to carry the number rather than the verdict. The batch record must include the actual results obtained during any monitoring operation (111.260(g)). Conforms is not an actual result. And the batch record must accurately follow the master manufacturing record, with each step performed (111.255(c)), which makes the master record a promise the batch record either keeps or does not. Two documents you wrote, sitting on the same desk, disagreeing with each other. That is what a document review is looking for.

Run the audit’s own activities on yourself

The eight activities are the opening meeting, the facility tour and inspection, employee interviews, document review, the traceability challenge, the auditor’s review of the facility inspection, the auditor’s final review of the findings, and the closing meeting (clause 5.5). The first five gather the evidence. The last three are the auditor writing up, checking and presenting what those five turned over, and the sixth heading below explains how they work rather than asking you to rehearse them.

So five are yours to run this month, without a certification body and without a booking. You do not need the standard’s own text to run them: it is copyrighted and is not reproduced here, and what each clause requires is stated as you go. What each test gives you is a named gap or a clean answer on one thing. None of them gives you a grade, and anybody who tells you otherwise is guessing.

The opening meeting is already a test

Its stated purpose is to confirm the scope and process of the audit, with senior managers present who have the authority to make corrective action happen. Exclusions get captured, confidentiality is discussed, and the production schedule and safety precautions are reviewed. Then, in the same meeting, the auditor holds a discussion of the processes and metrics for quality management oversight and review, and the improvement activities and projects you have put in (clause 5.5.1).

Twenty minutes in, you have been asked what you measure and what you have improved. A clean answer is one you can give from the meeting minutes in the room. If it takes a week to assemble, you have learned something about your own system before anybody has opened a document.

Walk the flow, not the file

The tour follows production flow: raw material receiving, processing, packaging, warehousing, testing, release, shipping, with support functions such as the QC laboratory and maintenance taken in along the way. The site is inspected against the standard for premises, equipment, materials, production, finished products and the lab. The clause also gives the auditor a stop button. Where the site is clearly not ready for certification, the auditor ends the audit after consulting the certification body (clause 5.5.2).

Your own version costs an afternoon. Walk your plant in that order with the relevant procedure in your hand, and read each one standing at the place it is performed. Procedures fail out loud when you read them where the work happens.

Preparation has its own clause, and how it is graded is worth reading. The site is expected to be prepared, to have ready access to appropriate documentation and to provide appropriate staff; the one hard obligation in the clause is that the scope of certification has to be in operation during the audit (clause 5.4.3). Ready access is an expectation rather than something you fail on its own, and it still shapes the day. If your controlled copies live on one person’s laptop and that person is on leave, an auditor spends the morning waiting, and forms a view while waiting. And where a significant process runs seasonally or only occasionally, the same clause says the audit is either scheduled for that time or a separate audit assesses that process.

There is also a short list of what you send ahead. At least a week before the visit the site supplies the certification body with background information. What the certification body asks for is its own to set, and the clause gives a floor it is not limited to: organization chart, site plan, process flow diagram, the list of products and technologies in scope, shift patterns, the standard operating procedure index, the regulatory inspection history for the past five years, and the site registration. If a different certification body did your last audit, you hand over that report and its corrective action plans too (clause 5.4.5). Assemble that packet now. Whatever you cannot produce in a day is a gap in something other than paperwork.

Ask three people to explain their own job

Employees are selected at random from different parts of the operation and asked to explain their tasks. The purpose is to verify that they understand the duties they are assigned and the procedures and GMPs related to their function, and their names are recorded so training records can be checked against them (clause 5.5.3).

Federal law asks you to hold those training records, with the date, the type of training and the person trained (21 CFR 111.14(b)(2)). So three things have to agree: the procedure, the record, and the person. Pick three people yourself, at random, and ask them to talk you through the step. A clean answer is an operator describing the step the way the procedure describes it, with a training record showing they were trained on that procedure and on the date it says. Anything else is a gap, and you now know which of the three it sits in. This is where a procedure written by somebody who has never run it gets found out, and it is the cheapest test on this page.

Build the index before anybody asks for it

The site provides an index of the procedures in use, and they are reviewed for completeness and content. Then the standard names the supporting documents that have to be reviewed. The list is a floor and not a ceiling, and batch records are audited across your manufacturing technologies, chosen risk-based where you run several (clause 5.5.4). What it names, one line each so you can tick them:

• Incoming material records
• Pre-weigh and dispensing forms
• Manufacturing records and forms
• Packaging records
• Shipping and traceability records
• Quality control records, including test method procedures and specifications for ingredients, components, batches and finished products
• Deviations and out-of-specification records
• Change control records
• Maintenance records
• Cleaning records
• Sanitization records
• Training records, covering both skill and GMP training
• Complaint and recall program documents, including mock recall records
• The subcontracting program
• The pest control program

That is the checklist people go looking for, and it is sitting in the standard. Build your index against it. A clean line is one where you can name the document and the version, and hand it over in the same minute. A line with no document behind it is a gap you found before anyone else did. A line with a document nobody has opened in three years is usually the bigger one. Procedures and their forms are expected to be reviewed and revised as operations change, and at least every three years regardless (clause 4.4.33.1).

Run the traceability challenge and put a clock on it

The auditor traces raw and packaging materials through the production process by reading batch and production records, verifying the dietary ingredients, excipients and other components used. Then finished goods are traced through distribution, and a mock recall is reviewed to evaluate your material control system (clause 5.5.5). The standard sets the bar elsewhere: traceability and mock recall exercises at least once a year, forward and backward, recovering between 99.5 and 101.5 percent of the material within four hours, with any additional exercises finished inside 24 hours (clause 4.6.20).

Run one. Have somebody else pick the lot number so you cannot pick a kind one, and time it. It is the only test on this page that hands you a number you cannot argue with.

Know how a finding gets written before one gets written about you

The auditor raises each observation with the site host at the time it is made, verifies it, and runs further checks as needed. Findings have to be specific, naming specific procedures, practices and production lots (clause 5.5.6). Specific means your document number and your lot, not documentation weaknesses. That cuts in your favor too: a finding you can name yourself is a finding you can close yourself.

Severity is the auditor’s judgment on the day, sorted into critical, major and minor, and minor findings taken collectively can be raised to a major (clause 5.5.9). The technical reviewer at the certification body applies the same logic afterwards: where several findings sit inside one system element, such as training, the classification of that element is raised (clause 5.6.2).

That changes how you count your own results. Five small problems spread across five systems are five small problems. Five small problems all sitting in training are one big one. Group what you find by the system it belongs to before you decide how you are doing.

What a bad result costs is set out as well. Grades A, B and C all stay on a path to certification once the corrective action plans are approved, with a monitoring audit required at C. A grade of D means the site is not eligible and a new certification audit is required (clause 5.7.3). A certificate already held is withdrawn where the site no longer meets the GMP requirements, where corrective actions are not implemented within the timelines, or on evidence that records were falsified (clause 5.8.5).

What a downloaded checklist can and cannot do

Every requirement of the standard is audited during the certification audit visit (clause 5.1), so nothing on the list is a secret and a checklist that reproduces it is telling you the truth. What it cannot do is open your recall plan, hold it against the clause that asks for a written plan naming the steps and assigning responsibility for taking them (clause 4.6.19), and tell you the requirement is still unanswered. Having a document and having one that answers the requirement are different states, and they look identical from the outside.

The standard already asks you for the harder version. A self-assessment against the standard has to be conducted to prepare for the audit, and gaps found in it have to be addressed before the certification audit happens (clause 5.3.2). Separately, an internal audit program has to be established and conducted, and the standard notes for itself that there is no specific federal citation for internal audits because the expectation sits inside 21 CFR 111.105 (clause 4.6.22).

One thing to read for yourself before you bring anyone in. Clause 5.4.6 puts a duty to avoid conflicts of interest on the certification body, on the auditor and on the site, and it names two bars in particular: an auditor cannot have been employed by the audited company within the previous three years or hold a familial or financial relationship with it, and an auditor assigned for certification cannot have been involved in a gap analysis or provided consulting services to the same company within the previous two years (clause 5.4.6). The bar runs against the individual auditor rather than against the site, and a company that is not a certification body has no auditor to lose. Whether a particular arrangement clears the clause is between you and your certification body, and it is worth asking them before you sign anything, not after.

What the regulator’s own record shows

Eleven clauses of Part 111 ask for one thing and nothing else: that you establish and follow written procedures. Here is how often FDA has written a supplement facility up under one of them.

FDA inspection observations cited under 21 CFR Part 111, fiscal years 2009 through 2026, most recent inspection ending 9 July 2026. Read 20 August 2026.

What was counted	Observations	Facilities
All observations cited under 21 CFR Part 111	23,440	2,507
Cited under one of the eleven written-procedure clauses (111.8, 111.16, 111.25, 111.103, 111.153, 111.303, 111.353, 111.403, 111.453, 111.503, 111.553), or one of their lettered subparagraphs	3,760	1,363
Of those, the observation opens you did not establish	3,212	1,193
Of those, the observation opens you did not follow	505	349

Read what that does and does not evidence. The 3,212 are absence. Each one says a named procedure was not there, and they say nothing whatever about whether a system that does exist is sound. Only the 505 are the failure this article is about, where a written procedure existed and the record did not show it being followed. Nothing in the record explains the gap between the two numbers, and it should not be read as a measure of how often written systems fail. A count of citations is also not a count of firms or of systems, since one inspection produces several. The remaining 43 observations in the set carry text truncated in the published record, so they are left in neither row.

The useful part is what it says about where a certification audit starts. FDA’s record is dominated by absence, and if that is where you are, the five tests above are not your problem. A system that does not exist does not need examining; it needs writing, and the tests will only tell you what you already know. The certification audit does not stop at absence, because every requirement gets audited whether or not you have a document for it (clause 5.1), and the traceability challenge and the employee interviews test the procedures you do have against what actually happened.

Where the standard asks more than federal law, and one place federal law asks less

The standard exists to audit compliance with 21 CFR Part 111 and to add retailer requirements on top of it (clause 1.2), so some of what an auditor writes you up for was never a federal requirement in the first place. The recall plan is the clearest example. The standard asks for procedures defining recall and a written recall plan describing the steps and assigning responsibility, and it cites (21 CFR 117.139) for it. But subparts C and G of Part 117 do not apply to a facility with regard to the manufacturing, processing, packaging or holding of a dietary supplement that is in compliance with Part 111 and section 761 of the Federal Food, Drug, and Cosmetic Act (21 CFR 117.5(e)), and 117.139 sits in subpart C. Neither the word recall nor the word mock appears anywhere in Part 111.

So a plant FDA has been satisfied with for a decade can walk into this audit with no recall plan, no mock recall on record, and no internal audit program, and fail three clauses of this standard without having broken the Part 117 recall rule, which does not reach it. If you are testing a system that was built to Part 111, those are the places to look first, because nothing in your regulatory history would have flagged them.

What to do with what you find

Fix the procedure before you rewrite a year of records to match it. A record cannot be made true retrospectively, and the clauses above are the reason: the batch record had to be written at the time of performance, and the retention clock runs one year past the shelf life date where shelf life dating is used, and otherwise two years beyond the distribution of the last batch the records belong to (21 CFR 111.605(a)), with everything readily available for inspection and copying throughout (111.610(a)). What you can fix now is the next lot.

Where a gap is real and cannot be closed before the date, write it down anyway, with a date against it and a name beside it. After the audit you get ten business days from the final report to submit a corrective action plan with implementation dates against every nonconformance (clause 5.7.1). A gap you found yourself, with a plan already written, is a very different conversation from one an auditor finds for you.

Then read your own result before you decide anything else. If the five tests turned up nothing, you have evidence about five activities out of eight and none about the other three. That is a good position and it is not a grade. If they turned up gaps inside one system, fix that system rather than counting the findings. If a document does not exist at all, you are writing rather than examining, and none of this is your next job. And if your documents exist but your records do not carry what they promise, that is the case this page describes, and the next move is to read every requirement in the standard against every document you hold rather than five of them.

A related question, worked the same way: whether a cleaning validation survives an inspection, and where the hole usually is.