Fundamental principles and concepts of a quality management system
Domain 1 tests conceptual understanding: what a quality management system is, why ISO 9001:2015 is structured as it is, and what the standard does not require. Later domains assume this vocabulary.
A QMS is a management system, not a document set
ISO 9000:2015 defines a QMS as a set of interrelated or interacting elements of an organization used to establish policies and objectives, and processes to achieve them. The elements are processes, resources, responsibilities and decisions; documentation records the system but is not the system. The 2015 revision removed the six mandatory documented procedures of the 2008 edition and requires documented information only where a clause demands it or where the organization judges it necessary for effectiveness.
The seven quality management principles
Customer focus, leadership, engagement of people, process approach, improvement, evidence-based decision making, relationship management. Link each to its clause: leadership to clause 5, engagement of people to 7.2 and 7.3, relationship management to 8.4, evidence-based decisions to 9.1.
Process approach, PDCA and risk
A process turns inputs into outputs using resources and controls. The process approach manages the sequence and interaction of processes and the performance of the network, not each process in isolation. PDCA maps onto the clause structure: Plan (4, 5, 6), Do (7, 8), Check (9), Act (10). Risk-based thinking is embedded in 6.1 and threaded through other clauses; it is not a separate risk management requirement.
Worked example
An injection moulder receives a complaint about flash on a connector housing. A documentation reflex raises a corrective action against the operator. The process approach instead traces the output: the complaint enters via customer communication (8.2), the nonconforming output is handled under 8.7, and mould maintenance emerges as an uncontrolled input to 8.5.1. The gap is the undefined interaction between maintenance scheduling and production planning - a system issue, not a person issue.
Traps
- Treating "documented information" as "write a procedure for everything".
- Assuming 8.3 or 7.1.5 can be ignored because the organization dislikes them.
- Answering in quality control language when the question asks about the management system.