What is a quality management system?

What it is

Your quality management system is how you make sure the thing you ship is the thing the customer ordered, every time, and how you know when it is not.

Every manufacturer already has one. It may be undocumented, it may live in the heads of three long-tenured people, and it may fall apart when one of them takes a week off, but it exists. The work of certification is rarely inventing a system. It is describing the one you have, closing the places where it is silent, and building the evidence that it runs.

A QMS under ISO 9001 covers your processes and how they connect, who is responsible for what and whether they are competent, the documents and records you keep, how you plan for what could go wrong, how you measure performance, and how you improve when something fails.

When you will hear it

In the standard itself, constantly. Clause 4.4 is titled "Quality management system and its processes" and is where the requirement to define your processes and their interactions lives.

In sales conversations, usually as a scope question. "What is in your QMS?" means which sites, which product lines, and which processes your certificate covers. Scope is a decision with cost consequences, because audit time is driven by the headcount inside it.

In software marketing, where QMS often means a document-control application. The application is not the system. It stores part of the evidence the system produces.

What the auditor expects to see

That you can describe your processes, show how they connect, and produce the records each one is supposed to generate.

Most auditors start at clause 4 and work outward: what is your scope, what processes are in it, who owns each one, what are the inputs and outputs, and how do you know each is working. A process map is not required by the standard, but a company that cannot answer those questions verbally usually cannot answer them with records either.

They will also test whether the system is used rather than possessed. Ask three people on the floor how a nonconforming part gets dispositioned. If you get three answers and the procedure gives a fourth, that is a finding regardless of how well the procedure reads.

Common mistakes

Building the system around the standard's clause numbers. Your processes are receiving, planning, fabrication, inspection, shipping. Organizing your documentation by clause instead of by process makes it unusable to the people who have to follow it, and the auditor will notice that nobody uses it.

Documenting everything. The 2015 edition requires far less documented information than people assume. Every extra procedure is something you must then keep current and be audited against.

Letting it belong to one person. A system that lives with the quality manager stops when they leave. The clauses that assign responsibility to top management exist for this reason.

Copying another company's system. Their processes are not yours, and the mismatch shows on the floor within minutes of an auditor asking a question.

FAQ

Do we need a quality manual?

Not as a named document. ISO 9001:2015 removed that requirement. Many companies keep one anyway because it is a useful orientation for new hires and for customers, but no auditor can write you up for its absence.

How long does it take to build one?

For a manufacturer that already runs disciplined production, the work is mostly description and evidence, and three to six months is typical with help. The floor is set by the roughly three months of records an auditor expects to sample before certification.

Can our ERP system be our QMS?

It can hold a lot of the evidence: traveler records, inspection results, nonconformance dispositions, training records. It will not cover management review, internal audit, or your process definitions.

Who should own it?

Someone with authority to stop shipment and access to top management. Title matters less than those two things.