Initiation of a QMS implementation
Domain 2 covers the front end of an implementation project: the decision, the mandate, and the first structured look at the organization's current state. The exam tests sequencing - what must exist before planning starts - and the roles of top management and the project lead.
Start with the decision and the mandate
Top management must be able to state why the QMS exists: a customer requirement, a tender condition, the cost of poor quality, or a strategic goal. Clause 5.1 makes leadership non-delegable, so a system owned by a junior coordinator tends to fail at clause 5.1.1 during certification. ISO 9001:2015 does not require a management representative; that role was removed, and answers that reinstate it are wrong.
Establish the current state
Two activities frame everything else. First, context (4.1) and interested parties (4.2): which external and internal issues affect the ability to deliver conforming product, and which parties impose requirements. Second, a gap analysis against clauses 4 to 10, recording existing practice, available evidence and the size of each gap. Build a process inventory alongside it - each core, support and management process, its owner, inputs and outputs.
Plan the project
Produce a phased plan with milestones, owners, budget and a communication approach. Typical phases: initiation and gap analysis, planning, implementation, internal audit and management review, certification. Decide whether a consultant advises or owns - advising is defensible, ownership is not.
Worked example
A 120-person parts distributor seeks certification for a retail tender. The gap analysis finds no context analysis, calibration performed but not recorded, and corrective actions handled verbally. The plan sets three workstreams - process definition, measurement and records, and competence - over ten months, with monthly steering reviews and a buffer before the certification audit.
Traps
- Adopting the tender deadline as the plan, leaving no time for internal audit or management review.
- Letting a consultant write a system that staff cannot explain in interview.
- Skipping 4.1 and 4.2 as theoretical; both are audited.