The formal definition, unpacked
ISO 9000:2015 defines a management system as a set of interrelated or interacting elements to establish policies, objectives, and processes to achieve those objectives; a QMS is that system with regard to quality. Strip the vocabulary and it means: the way you decide what good looks like, the way you organize work to produce it, the way you check whether you did, and the way you fix it when you did not.
What a QMS is made of in practice
- Processes. The core value chain (sales, design, production or service delivery) plus supporting processes (purchasing, training, maintenance) with defined inputs, outputs, and owners.
- Direction. A quality policy stating intent and measurable objectives that make the intent concrete.
- People and resources. Competence requirements, training, equipment, and working environment matched to what the processes need.
- Feedback loops. Monitoring, customer feedback, internal audits, management reviews, and corrective actions that make the system self-correcting.
- Documented information. Enough documentation to run consistently, enough records to prove it.
What a QMS is not
It is not software (software can support one), not the quality department (they facilitate it, everyone operates it), and not the documentation (that describes it). The most damaging misunderstanding I meet as an auditor is the parallel-universe QMS: an impressive documented system that describes a company that does not exist, running alongside the real informal one that actually ships product. Audits expose the gap quickly, and closing it in the documentation's favor is almost always wrong; describe how you really work, then improve how you really work.
The one-sentence test
If you can answer "how do we know our customers get what they were promised, every time, and what happens when they do not" with named processes, current data, and recent examples, you have a functioning QMS whatever you call it.