Most audit failures are not process failures — they are preparation failures. A 30-day preparation program, applied systematically, eliminates the majority of findings before the auditor arrives.
Thirty days is enough time to close the documentation gaps that most audits find, if you use the time correctly: week 1 for a documented gap analysis, week 2 for closing the highest-risk records gaps, week 3 for employee preparation and mock audits, and week 4 for a final floor walkthrough. Facilities that use this framework eliminate the majority of predictable findings before the auditor arrives — because most audit findings are predictable, and most preparation programs never look where the auditor will.
Most manufacturing quality teams approach an upcoming audit with a combination of anxiety and procrastination. The preparation feels overwhelming, and the apparent scope of what could go wrong makes it hard to know where to start. But most audit failures are not process failures — they are preparation failures. An auditor who finds a documented gap with a corrective action in progress treats the situation very differently from one who finds an undisclosed gap.
The 30-day framework works because it is scoped correctly. You are not trying to rebuild your quality management system in a month. You are trying to identify the gaps between what your QMS claims and what your operation actually does, close the gaps that can be closed in 30 days, and ensure your team can speak confidently about the gaps that cannot.
An auditor who finds a documented gap with a corrective action in progress treats the situation very differently from one who finds an undisclosed gap. Evidence that you know where your system falls short and are actively addressing it is evidence of a functioning quality management system, not a failing one.
The first week is spent understanding where you stand before spending any effort on fixes you may not need.
Day 1-2: Inventory your required documented information. Pull the relevant standard (ISO 9001:2015, AS9100 Rev D, IATF 16949, or FDA Part 820) and make a list of every required procedure, record, and documented process. Cross-reference this list against what you actually have. Mark gaps.
The exercise sounds basic. Most organizations have not done it recently — if ever. The list that emerges is your audit risk register for the next 30 days.
Day 3-4: Check revision currency. For every active procedure and work instruction, verify that the document reflects the current process. The fastest way to do this is a process walk: take a printout of each procedure to the workstation where the process is performed and watch an operator execute it. Every step that does not match the procedure is a documentation gap.
Do not skip this step because it is time-consuming. Procedures that do not reflect practice are the single most common major finding in manufacturing quality audits. If you are going to invest 30 days, this is where the investment pays.
Day 5: Check calibration records. Pull the equipment list for your production processes. Verify that every monitoring and measuring device has a current calibration record, that the calibration is traceable to a recognized standard, and that the calibration interval is documented and being observed. Lapsed calibration on in-use equipment is a finding that is both common and avoidable.
Day 6-7: Prioritize your gaps by audit risk. Not all gaps carry equal risk. Rate each gap by likelihood of detection (will the auditor look here?) and severity of finding (is this a major or minor?). Focus the remaining three weeks on the highest-risk items.
The second week focuses on records — the documented evidence that your processes are being performed as documented.
Corrective action records. Review your open corrective actions. Close any that are complete but have not been formally closed. For any open CAs that were supposed to be closed by now, document the current status and the revised completion date. An auditor who sees open corrective actions with no activity since the last audit will find that more concerning than an auditor who sees open corrective actions with documented progress and realistic timelines.
Training records. Verify that training records are current for all personnel in scope. This means current revision training — not just evidence that someone was trained on a procedure at some point, but that they were trained on the version currently in use. If your training records do not track revisions, this is a gap to document and plan to address.
Internal audit records. Your last complete internal audit cycle should be documented and its findings addressed through corrective action. If any findings from the last cycle are still open, close them or document a justified timeline for completion. An auditor will ask to see evidence that your internal audit program is functioning. "We haven't had time" is not an answer.
Supplier qualification records. Pull your approved supplier list and verify that qualification records are current for your top ten to fifteen suppliers by spend or risk. Key documentation: your initial qualification criteria and evidence, monitoring records, and any supplier corrective actions issued.
Management review records. Your last management review should have documented inputs (quality metrics, audit results, CAPA status, customer feedback) and outputs (decisions, action items with owners and timelines). If the record is sparse — an agenda with no documented decisions — clean it up before the audit.
The third week is about people, not paper. Auditors spend at least half their time observing processes and talking to operators. Your documentation can be perfect and your audit can still produce major findings if your team cannot speak to what they do and how it connects to your quality management system.
Brief every operator who will be on the floor during the audit. This does not mean coaching them to give specific answers — auditors are skilled at recognizing coached responses and it creates a credibility problem. It means ensuring every operator can answer three questions confidently:
Operators who can answer these questions naturally, from their actual daily experience, will perform well in an audit interaction. Operators who have never been asked these questions before will not.
Run a mock audit. Assign a QE or supervisor who is not responsible for the areas being audited to spend two hours walking the floor as an auditor would — following documented procedures at workstations, reviewing calibration labels, asking operators questions, checking that records match the process. The findings from a mock audit two weeks before the real thing give you time to address issues that would otherwise be discovered by the registrar.
Prepare your quality team for auditor questions. Auditors ask process questions that require understanding, not just recitation. Common challenging questions:
Practice answering these with your team. The goal is confident, specific answers drawn from actual system knowledge — not scripted responses.
The fourth week is for final verification and ensuring that the physical environment supports a clean audit.
Final documentation verification. Walk every active workstation and confirm: the correct procedure is posted at current revision, the calibration status of all in-use measurement equipment is current, and there are no obsolete procedures in visible use.
Prepare your document package. Organize the documents most likely to be requested: your quality manual (if applicable), quality objectives with current performance data, your last three corrective action packages, your last complete internal audit cycle, and your approved supplier list with qualification records. Have these ready to retrieve immediately — not searched for while the auditor waits.
Physical walkthrough for housekeeping. Auditors observe more than they formally score. A facility that looks well-organized, where material is clearly identified, where workstations are clean and procedures are visible and current, starts the audit with positive momentum. A cluttered facility with unlabeled material and procedures buried under tooling creates a negative impression that colors every subsequent finding.
Assign escorts. Each auditor should have a designated escort who knows the area being audited and can respond to requests quickly. The escort's job is not to answer for the auditee — it is to ensure the auditor has everything they need and that the quality team is informed of anything requiring attention.
The opening meeting sets the tone. Arrive prepared with: your quality policy (top management should be present to speak to it), your quality objectives with current data, your audit scope statement, and a brief description of your quality management system. Keep the opening presentation under 20 minutes.
During the audit: Answer questions directly. Do not volunteer information beyond what was asked. If you do not know the answer to a question, say so and commit to getting the information. Speculating or improvising answers to questions you do not know creates more audit risk than "I'll need to look that up."
If the auditor finds something: Do not argue. Take the note, thank them for identifying it, and ask clarifying questions to understand exactly what the finding is. You will have the opportunity to respond during the closing meeting and in writing afterward. Arguing a finding in the field does not resolve it and damages the relationship with the auditor.
During the closing meeting: Listen carefully to each finding. Clarify any factual errors in how the finding is characterized — this is your opportunity, not the field audit, to correct misunderstandings. For each finding, your response should cover: your understanding of the root cause, the immediate containment action you have taken, and your plan for systematic correction.
A finding is not a failure. Every quality management system has gaps. The distinction between a well-run system and a poorly-run one is not whether findings exist — it is whether findings generate genuine corrective action that prevents recurrence.
When a finding is issued, your corrective action response should:
A corrective action that only addresses the specific instance of the finding is a corrective action that will produce the same finding at the next audit. Root cause analysis that reaches the systemic level — the procedure was ambiguous, the training was not revision-specific, the review cycle was not defined — produces corrections that actually reduce audit risk.
Coplain's Auditor Review tool analyzes your work instruction library against the documentation requirements of AS9100, IATF 16949, and ISO 9001 — identifying gaps before your auditor does. Try it free at coplain.com.
Coplain turns any work instruction into a print-ready, audit-proof job aid in minutes.
Try Coplain free →AS9100 Rev D Documentation Checklist: 12 Items Auditors Check First
Most audit failures aren't about process gaps. They're about documentation that doesn't reflect reality. Here's the checklist we wish existed before our first Rev D audit.
6 min readCOMPLIANCEFDA 21 CFR Part 820 Documentation Requirements: What Trips Up Manufacturers
Warning letters. 483 observations. Consent decrees. Most FDA enforcement actions have one thing in common: inadequate documentation. Here's what the agency actually looks for.
10 min readCOMPLIANCEISO 9001:2015 Documentation Guide: What You Actually Need vs What You Think
The 2015 revision eliminated the quality manual requirement and six mandatory procedures. What it added is more demanding. Here's what actually changed — and what your registrar looks for during surveillance.
7 min readCOPLAIN PLATFORM
See every tool that turns complex work instructions into floor-ready documents.