ISO 9001 clause 6.2.2: plan how the quality objective will be achieved

What clause 6.2.2 requires in practice

Clause 6.2.2 is about the plan behind each objective. When planning how to achieve a quality objective, the organisation works out five things. First, what will be done. Second, what resources will be needed. Third, who will be responsible. Fourth, when the work will be completed. Fifth, how the results will be evaluated.

Each of those answers should be specific enough that someone could check progress against it. The clause does not require a particular planning tool, a project template or a dedicated document; a line in a process review or a project plan can serve if it answers the five questions. The plan should also be consistent with the wider planning for risks, opportunities and changes, so that resources promised to an objective actually exist. The output is a credible route from objective to result, with a named owner and a way to judge success.

Why planning how to reach objectives matters to the business

Many objectives fail without anyone deciding they should. The target is announced, the owner is unclear, the resources were never agreed and the review date passes unnoticed. A short, concrete plan changes this by making commitments visible: who will do what, with which people or tools, by when, and how success will be judged. That clarity saves management time, exposes resource conflicts before they become excuses, and gives teams something to be proud of when results arrive. It also lets auditors and customers see that quality direction becomes operational work.

How to implement clause 6.2.2

Keep each plan short and attached to the place where the work is already managed. One way Sterling's teams do this is to add the five planning questions as a standing section in existing project or process review notes, so no separate document is created. The standard requires that the five matters are determined; it does not require a plan template, and a short paragraph that answers them clearly serves the purpose.

1. Take each objective and describe the main actions needed to move the result.
2. List the resources, including people, time, equipment, information and any external help.
3. Name one accountable person for each action.
4. Set a completion point that matches the nature of the work, not an arbitrary date.
5. Decide the evaluation method: which measure, from which source and reviewed by whom.
6. Confirm resources with the managers who control them before publishing the plan.
7. Review progress at set times and adjust the plan when results or conditions change.

Evidence an auditor expects for clause 6.2.2

The auditor is looking for follow-through from an objective to its delivery. Typical evidence includes: The auditor tends to test one objective end to end, asking who owns it, what has been done, what resources arrived and what the measure shows now. Evidence is stronger when the owner can describe obstacles accurately, because that shows the plan is being used, not filed.

• plans, project records or review notes that answer the five planning questions
• records showing resources were allocated as planned
• interviews with the responsible persons about progress and obstacles
• results compared against the objective and the conclusions drawn
• adjustments made when the plan was not working

Choose actions that address the actual gap

Make resources and responsibility explicit

Resources can include people, competence, time, information, infrastructure or external support. Consider what is genuinely available and what must be obtained. A plan that assumes busy staff will absorb substantial new work without reprioritisation may not be credible.

Clarify who is responsible for the planned work and who can resolve obstacles. Responsibility should be understood by the person concerned, not assigned silently in a management spreadsheet. Where several owners contribute, establish how their actions fit together and how the overall objective will be evaluated.

Illustrative software example: reducing escaped defects

Illustrative construction example: timely approval information

A hypothetical contractor wants to reduce delays caused by late approval of required material information. The plan identifies the project stages at which information is needed and the interfaces between procurement, technical review and customer approval. It distinguishes the contractor's own controllable actions from decisions made by other parties.

Owners agree when submissions must be prepared, which resources support review and how unresolved items will be escalated. Evaluation compares the availability of approved information with the actual work sequence and examines recurring causes of delay. The example illustrates planning; it does not override contractual arrangements or establish a universal project approval period.

Choose timing that supports the outcome

The clause requires determining when the work will be completed. Consider sequencing and lead times, especially where one action depends on another. A single final date can hide the fact that an essential early decision has no owner or that training occurs after the changed process starts.

Use milestones where they help, but avoid confusing elaborate scheduling with a workable plan. For a small objective, a concise action arrangement may be sufficient. For a complex cross-site change, more detailed coordination may be needed. The standard does not prescribe project-management software or one planning template.

Plan evaluation before declaring success

Determine how results will be evaluated, using information that reflects the objective. Consider when there will be enough relevant evidence to judge the effect and what limitations may influence interpretation. A brief period with no reported defects may tell little if very little work occurred during that period.

Records in ordinary business plans and action systems can support the explanation. Clause 6.2.2 does not name a mandatory plan format. Common weaknesses include actions unrelated to the performance gap, resources assumed but unavailable, deadlines repeatedly moved without review and closure based only on activity completion.