Strategy & Leadership

Passing Audits Takes More Than Software

Most certified manufacturers have solved the documentation problem. The audit findings that keep showing up are behavioral, and the software can't fix those.

6 min read

Most manufacturers managing a quality certification already know the documentation problem is solved. The audit findings that keep showing up are behavioral, not documentary.

What Quality Management Software Actually Solves

Before integrated QMS platforms existed, a manufacturer managing ISO 9001, AS9100, or IATF 16949 compliance typically meant running a separate QMS, a separate document control system, and a paper trail for non-conformances, corrective actions, and inspection records. Keeping all of that synchronized took time and many manual steps. Audit prep meant spending two weeks pulling records from four different places.

Modern QMS platforms consolidated that. Systems like 1Factory, QT9, and ProShop bring document control, revision tracking, NCR management, inspection records, and work instructions into a single system. For manufacturers pursuing ISO 9001 certification for the first time, these platforms satisfy a significant portion of the requirements by design if used correctly. They don't write your quality manual, but the structure is there.

ProShop goes further than most for aerospace and defense manufacturers. It integrates the QMS directly into the job, connecting FAI records, inspection plans, and work instructions to specific work orders in the same system. For a manufacturer running AS9100, that level of integration changes what audit readiness looks like on a daily basis.

The documentation problem is largely solved across all of these platforms. The behavioral problem is what auditors are still finding.

Where Audit Findings Still Show Up

The findings that show up across certified manufacturers almost never involve missing documentation. The software is too good at capturing records for that to be the problem. What auditors find instead are records that don't match what the floor actually did.

An in-process inspection was required at a specific routing step. The job moved to the next operation without the inspection being completed. Someone entered the record after the fact, or the step was marked complete without the data being populated. The part shipped. The record says it passed. The auditor asks an operator what the inspection process looks like and gets an answer that doesn't match the documented procedure. That's a finding, and the software didn't cause it.

NCR management is the second failure pattern. Every major QMS platform makes it easy to open a non-conformance report. None of them make anyone close it. Industry data from the IATF consistently shows corrective action closure as the top source of major non-conformities across certified manufacturers, and the pattern is identical in ISO 9001 and AS9100 audits. In a busy operation, NCRs get opened when something goes wrong and then sit in the system for weeks or months without a root cause documented or a corrective action verified. For manufacturers running ISO 9001, this typically shows up around supplier non-conformances and incoming material inspection records — a supplier ships nonconforming material, an NCR gets opened, and nobody closes it before the next audit cycle. An auditor reviewing open NCRs and finding twenty with no closure dates isn't going to accept "we've been busy" as a response.

Skipped approvals are the third pattern. Every major QMS platform has approval workflows built in. Under schedule pressure, those workflows get bypassed. A job gets released to the floor before the engineering review is complete. A purchase order goes out before the supplier qualification is confirmed. The system has a record of the bypass. Auditors know how to look for it.

The Gap Between the System and the Floor

A QMS platform is a recording system. It captures what people tell it. If the floor isn't following the documented process and nobody is checking, the software will faithfully record that the process was followed because that's what was entered. It can't observe behavior. It can only record inputs.

Three things close that gap, and all three are behavioral.

The first is ownership. Someone has to be responsible for the QMS as an operational function, not just as an audit prep exercise. In most manufacturing operations that size, that's a quality manager or a senior operator with quality responsibilities. Their job is to make sure the process is being followed before the record is created, not to fill out records after the fact.

The second is a regular internal audit cadence. In an operation of 20 to 80 people, a practical cadence is one internal audit per quarter, rotating across departments. Not a full system audit every time. A focused review of the area most likely to have drifted. The person running the internal audit writes up findings, assigns owners, and verifies closure before the next cycle begins. If you're waiting for an external auditor to find your problems, you're already behind.

The third is management behavior. When the quality manager writes up a finding and the production manager treats it as an interruption rather than useful information, the QMS stops working. Operations that stay compliant between audits have leadership that treats quality findings the same way they treat late deliveries: as a signal something needs to be fixed, not a bureaucratic inconvenience.

A Note on High-Compliance Work in Aerospace and Defense

For manufacturers doing AS9100 or ITAR-registered work, the stakes attached to audit findings are higher than they are for general ISO 9001 certification, and worth understanding specifically.

A corrective action request from a Tier 1 aerospace customer starts a clock. You have a defined window to respond with a root cause, a corrective action plan, and evidence the fix is in place. If you can't close it to their satisfaction, you risk losing your approved supplier status. For a business whose revenue runs through two or three major aerospace customers, that's not a compliance problem. It's an existential one.

DCSA findings carry different consequences but the same stakes. A finding tied to ITAR controls or CUI handling can affect your facility clearance. A pattern of findings puts you under more intensive oversight, which adds cost and friction to everything you do and signals to customers that you're a risk they may not want to carry.

The AS9100 standard is also in transition. The IAQG is updating and rebranding it as IA9100, with changes expected in 2026 that raise the bar on information security, supplier controls, and counterfeit parts management. Manufacturers currently certified under AS9100 will need to plan for a transition audit, and the behavioral gaps that produce findings today will produce findings under the updated standard as well.

What This Looks Like in Practice

The manufacturers that clear the bar consistently aren't doing anything exotic. They've built the discipline to use their software correctly every day, not just when an auditor is scheduled.

A $30M contract manufacturer serving defense and commercial customers was running at 60% on-time delivery and struggling with quality escapes when we started working together. After building the operational foundation, on-time delivery reached 90% within the engagement. The quality improvement came from the same place the delivery improvement came from: ownership, cadence, and management behavior. The process improvements were in place long before the next audit arrived.

Reach out at veritops.com/meet if you'd like to talk through what this means for your business.

More Insights

Ready to run a leaner, more profitable shop?

Let's Talk