Free Quality Management Plan Template — Word Download

01 — Template Sections

What's in the Template — All 7 Sections

The quality management plan covers the full quality lifecycle — from defining what quality means on this project through to how defects will be managed and who is responsible for each quality activity. It should be completed during planning and reviewed at each phase gate.

Quality Objectives

Three to five measurable quality objectives specific to this project. Each objective has a target metric so it can be tracked. Examples: defect rate below 2% at go-live; 100% of requirements covered by test cases; first-time acceptance rate above 90%.

Applicable Quality Standards

The external standards, regulatory requirements and internal policies that apply to this project's deliverables. Examples: ISO 9001 for process quality, ISO 27001 for information security, WCAG 2.1 for accessibility, GDPR for data protection, or organisation-specific coding standards. Being explicit about which standards apply prevents disputes over what "good enough" means.

Acceptance Criteria

A row-per-deliverable table: deliverable name, specific acceptance criteria, how it will be verified, who verifies it and who has authority to formally accept it. The most important section in the plan — see Section 02 below for how to write criteria that hold up.

Quality Assurance Activities

Proactive activities built into the process to prevent defects: process audits, peer reviews, methodology compliance checks, design walkthroughs, standards reviews and supplier quality audits. Scheduled activities with named owners and frequency.

Quality Control Methods

Reactive activities that inspect or test outputs to identify defects: unit testing, integration testing, user acceptance testing, code reviews, document inspections, security penetration testing. Specifies the test type, entry and exit criteria, and who executes each control activity.

Defect Management

How defects will be logged, categorised, prioritised, tracked and resolved. References the Issue Log as the defect tracking register. Defines severity levels (Critical, High, Medium, Low), response times and the escalation path for Critical defects found in testing.

Quality Roles and Responsibilities

Named individuals for key quality roles: Quality Manager or Lead, Test Manager, Acceptance Authority (who can formally accept deliverables), and any third-party quality auditors. Includes a brief summary of each role's responsibilities on this project.

02 — QA vs QC

Quality Assurance vs Quality Control — Understanding the Difference

QA and QC are not the same thing, though they are often conflated. Getting the distinction right determines whether your quality activities are preventing problems or just finding them — and prevention is always cheaper than detection.

Proactive — Section 4 of Template

Quality Assurance (QA)

Focus: The process used to create deliverables

Timing: Throughout the project, before outputs are produced

Goal: Prevent defects by ensuring the right methods are followed

Examples: Process audits, peer reviews at design stage, methodology compliance checks, supplier quality audits, standards walkthroughs

Reactive — Section 5 of Template

Quality Control (QC)

Focus: The outputs and deliverables produced

Timing: After outputs are produced, before delivery to customer

Goal: Detect defects before they reach the customer

Examples: Unit testing, integration testing, UAT, code reviews, document inspections, security scanning

Both are necessary. QA without QC means you may be following the right process but still producing defective outputs. QC without QA means you find defects late when fixing them is expensive. The most effective quality approach invests proportionally in both — more QA effort in high-complexity areas, more QC rigour at higher-risk delivery points.

💡

PMP exam: the cost of quality rule of thumb. Defects found and fixed during requirements cost 1x. Found during design: 3–6x. During development: 10x. During testing: 15–40x. After release: 40–1000x. This progression — sometimes called the Cost of Poor Quality (CoPQ) or the Rule of Ten — is why QA investment during planning and design pays back multiple times over. The PMBOK exam tests whether you understand that quality is cheaper to build in than to inspect out.

03 — Acceptance Criteria

Writing Acceptance Criteria That Hold Up

Acceptance criteria are the most practically important element of the quality management plan. Vague criteria lead to disputes at delivery. Specific, testable criteria prevent them entirely. Every criterion must be agreed by the customer or sponsor before work begins — not when the deliverable is presented.

Example Acceptance Criteria — System Deliverable

Deliverable	Acceptance Criterion	How Verified	Verified By
Invoice Processing Module	System processes 1,000 invoices per hour with zero data loss under peak load conditions	Load test with 1,000 concurrent transactions — verified by performance test report	Test Manager
Invoice Processing Module	Error rate below 0.1% across a test dataset of 10,000 representative invoices	Batch test run — error count verified against test log	Test Manager
User Interface	All critical user journeys completable by 95% of test participants without assistance in usability testing	Moderated usability test with 20 representative users	UX Lead
Data Migration	100% of 47,000 live records migrated with zero data corruption — verified by reconciliation report	Automated reconciliation — source vs target record count and spot-check audit	Data Lead + Client Sign-Off

Notice what every criterion has: a specific number, a defined test method, a data volume or sample size, and a named verifier. None of them use words like "acceptable", "adequate", "reasonable" or "good performance" — every criterion can be passed or failed objectively.

📌

Agree criteria before work begins — not at delivery. The most common source of acceptance disputes is criteria that were only defined when the deliverable was presented. At that point, the customer will inevitably find the criteria they wish they had specified. Criteria agreed before delivery begins create shared understanding of what "done" means. Criteria agreed at delivery create arguments about what "good enough" means. Always use the Sign-Off Form template alongside this plan to formally record acceptance.

04 — Cost of Quality

Cost of Quality — Four Categories to Budget For

Quality activities cost money. The quality management plan should include at least a rough estimate of quality-related costs so they can be budgeted for in the project plan. The four standard categories cover all quality spend — from prevention through to the cost of external failures.

Prevention Costs

Stopping defects before they happen

Investment in QA activities, training, process design, standards development, supplier qualification and quality planning itself.

Examples: peer review sessions, QA process audits, standards documentation, supplier audits, staff training on quality procedures.

Appraisal Costs

Detecting defects through inspection

QC activities including testing, inspections, reviews and audits that identify defects after outputs have been produced.

Examples: test planning and execution, code reviews, document inspections, UAT facilitation, performance and security testing.

Internal Failure Costs

Fixing defects found before delivery

The cost of rework, retesting and re-inspection when defects are found during QC activities before the customer sees them.

Examples: bug fixing, rework effort, regression testing after fixes, scrap or wasted design work.

External Failure Costs

Fixing defects found after delivery

The highest-cost category: defects that reach the customer cause rework, warranty claims, reputation damage and relationship risk.

Examples: post-release patches, customer-reported defects, service credits, incident response, reputational impact.

The investment target: most quality practitioners recommend spending 10–15% of project budget on prevention and appraisal combined. Projects that under-invest in prevention and appraisal consistently incur higher internal and external failure costs that far exceed the prevention savings. A £10K investment in QA that prevents a £100K post-release defect is not a cost — it is a return.

05 — FAQ

Quality Management Plan — 4 Common Questions

A quality management plan defines how the project will achieve and verify the quality required by stakeholders. It identifies applicable quality standards, sets measurable acceptance criteria for deliverables, defines quality assurance activities (proactive checks built into the process), specifies quality control methods (reactive checks on outputs), and assigns quality roles. In PMBOK, it is a subsidiary plan of the project management plan, produced during the Plan Quality Management process as part of Planning.

Quality assurance (QA) is proactive — it focuses on the processes used to create deliverables to prevent defects. QA activities include process audits, methodology reviews and standards compliance checks. Quality control (QC) is reactive — it inspects outputs to identify defects after they have been produced. QC activities include testing, inspections, peer reviews and acceptance testing. Both are needed: QA prevents defects from occurring; QC detects them before they reach the customer. On the PMP exam, QA is associated with the Manage Quality process and QC with the Control Quality process.

Acceptance criteria define the specific, measurable conditions a deliverable must meet to be formally accepted. Good criteria are unambiguous, testable and agreed before work begins. They should specify: what must be delivered (functional requirements or performance), to what measurable standard (specific numbers, not vague descriptors), how it will be verified (test method, sample size, data volume), and who has authority to accept it. Criteria agreed after delivery almost always lead to disputes — agree them at the start and reference them in the Sign-Off Form at delivery.

In PMBOK, the quality management plan is a subsidiary plan of the project management plan — alongside the scope, schedule and cost management plans. It is referenced when setting acceptance criteria in the scope statement, when scheduling QA and QC activities in the project schedule, and when budgeting quality costs. On the PMP exam, quality is tested across three processes: Plan Quality Management (planning), Manage Quality (QA during execution) and Control Quality (QC during monitoring and control). Understanding which tools and techniques belong to each process is a key exam topic.

Free Quality Management Plan Template Word Download