ISO 10005 provides guidance for quality plans that describe how quality arrangements apply to a specific case, such as a project, product or service. A useful plan connects requirements, responsibilities, controls and evidence to the actual work. It should add necessary specificity rather than duplicate the entire corporate QMS.
The Quality Management Standards Explained: ISO 9001, ISO 9004 and Related Frameworks places this topic in its wider QMS context. The public ISO record identifies ISO 10005:2018. Guidance is distinct from contractual requirements that may make a particular plan or approval necessary.
Define the decision and its boundary
A quality plan applies arrangements to a particular case. The case might be a project, product, service or contract with needs that are not fully explained by common corporate procedures. Identify the additional detail required for competent delivery and acceptance. The plan should clarify the work rather than repeat every existing document in a new format.
Use references to existing controlled arrangements where they are suitable. Repeat only the detail necessary to make the case-specific decision clear. Identify which party reviews or approves the plan under actual project arrangements, and control later revisions. A plan should help people perform and verify the work; approval of the document alone does not demonstrate that the planned controls operated or that the final output was acceptable.
Put the method into practice
Connect planning to sequence and interfaces. Identify who supplies inputs, who approves changes and when verification evidence must be available. Some evidence cannot be obtained reliably after work has moved on or become inaccessible. Plan those points before delivery begins. Use references to suitable controlled procedures and add case-specific criteria or responsibilities where they are genuinely needed.
-
Define the case, requirements and relevant existing QMS arrangements.
-
Identify specific responsibilities, controls, verification and records.
-
Approve and maintain the plan as requirements and work conditions change.
Worked example
A fictional contractor prepares a project quality plan referencing corporate document control while adding project-specific inspection timing and handover responsibilities.
The plan identifies evidence needed before work proceeds and a route for changed requirements. It remains connected to the project sequence instead of becoming a static submission document.
The contractor’s project plan is useful because it identifies timing and handovers that the corporate system does not describe in project-specific terms. Its value depends on people applying those arrangements. A signed plan can show approval of the intended approach, but it does not independently demonstrate that inspections occurred or that the resulting work was accepted under the relevant criteria.
Useful evidence and records
Keep the plan and its referenced information consistent. Staff should be able to identify the current version, relevant work package and applicable acceptance evidence. Where a contract requires review or approval, establish the actual authority and conditions. Preserve changes and their effect on completed or planned work so that a later handover does not rely on an outdated planning assumption.
| Comparison element | Distinct purpose |
|---|---|
| Scope | Case and applicable requirements |
| Responsibilities | Project-specific authority and interfaces |
| Verification | Criteria and timing of checks |
| Records | Evidence needed for acceptance and handover |
Check the result and avoid a common mistake
Copying a generic plan can conceal project-specific gaps. Test it against the real sequence, including changes and activities whose evidence cannot be recovered later.
Follow one work package through the plan and its referenced procedures. Confirm that responsibilities and acceptance evidence are available when needed.
Check the plan using representative work rather than a document review alone. Trace an activity through its inputs, controls, verification and handover. Look for conditions requiring a decision that the plan leaves implicit. Revise the arrangement where necessary and communicate the change. A polished plan with missing operational evidence should not be treated as proof of successful implementation.
Connect the next decision
Review case-specific requirements when scope, sequence or external provision changes. Keep the distinction between guidance and actual obligations clear: a contract may require a particular submission even though the guidance itself is not a universal mandate. Integrate the plan with existing QMS ownership and records so that it supports delivery rather than create a parallel set of instructions nobody maintains.
For a related comparison, see ISO 10007 Configuration Management Explained. The related guide to construction QMS interfaces explains the wider process dependency.
Practical question
Is a quality plan always mandatory for ISO 9001? A particular standalone plan is not universally required merely because ISO 10005 exists. Actual obligations may arise from the work, contract or other applicable requirements. Choose a suitable format and retain the evidence needed to show that the relevant arrangements were implemented.
Use the plan during change discussions rather than consult it only at submission and final handover. A revised sequence can move an inspection point or alter who supplies acceptance evidence. Evaluate those effects before the work proceeds. Keeping the plan connected to execution makes it a useful control rather than a historical account of what the project once intended to do.