This guide covers everything you need to know about quality control measurements in PMBOK 8. Quality control measurements are the documented results of inspections, tests, and reviews conducted to verify that project deliverables and processes meet the defined quality standards — they are the evidence base for quality assurance decisions.
What Are Quality Control Measurements?
Quality control measurements are the data and results collected during quality control activities — testing, inspection, auditing, and review — that quantify the quality characteristics of project outputs. They answer the question: “Do the deliverables actually meet the quality standards we defined?” and provide the objective evidence needed to accept, reject, or remediate project outputs.
Quality control measurements are different from the quality management plan (which defines what standards will be applied) and quality reports (which communicate quality status to stakeholders). Measurements are the raw data: test pass rates, defect counts, performance benchmarks, inspection results, and audit findings.
These measurements feed into acceptance decisions, corrective action planning, and continuous improvement. A project with consistently poor quality measurements needs process intervention; a project with consistently strong measurements can use that data to justify reduced inspection overhead in lower-risk areas.
Quality Control Measurements in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, quality control measurements belong to the Governance Performance Domain and are produced during the Manage Quality Assurance process. PMBOK 8 treats quality control measurements as an input to both quality reporting and continuous improvement — measurements that consistently deviate from standards indicate a systemic process problem, not just individual defects.
Quality control measurements feed into quality reports (communicating quality status to stakeholders) and can trigger change requests (when defects require rework) or corrective actions (when process adjustments are needed to prevent recurring defects).
Key Elements of Quality Control Measurements
Well-structured quality control measurements typically include:
- Measurement ID and Date — when the measurement was taken and by whom
- Deliverable or Process Measured — what was inspected or tested
- Quality Metric — the specific characteristic being measured (performance, defect count, compliance rate)
- Standard or Threshold — the acceptable target value or range
- Actual Measurement Result — the value measured during inspection or testing
- Conformance Status — whether the result meets, exceeds, or falls below the standard
- Action Required — corrective action, acceptance, or escalation as appropriate
Quality Control Measurements Example — Project Phoenix
Project Phoenix collected quality control measurements across three phases: design review, development testing, and pre-launch QA. During design review, BrightFrame’s mockups were measured against three criteria: brand guideline compliance (100% required, 100% achieved), mobile responsiveness across five device types (100% required, 100% achieved), and stakeholder approval score from Sarah Chen’s review (8/10 minimum, 9/10 achieved).
During QA testing by Maria Santos, 47 test cases were executed. Results: 44 passed on first run, 2 had minor defects (resolved within 48 hours), and 1 had a critical checkout flow bug requiring a code fix. The critical bug was assigned to Sam Lee, resolved in one day, and re-tested successfully. The final Google Lighthouse measurement for the homepage was 91 (performance), 97 (accessibility), 89 (best practices) — all above the 85 minimum threshold. These measurements were compiled into the QA Test Report and presented to Sarah Chen as the basis for her acceptance decision.
You can download the complete filled-in example below — it shows exactly how quality control measurements were collected and used in a real project.
Download Free Quality Control Measurements Template and Example
We have prepared two free resources to help you collect quality control measurements on your own projects:
- Download the Quality Control Measurements Template — PMBOK 8 (blank, ready to fill in)
- Download the Quality Control Measurements Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Quality Control Measurements — Best Practices and Common Mistakes
Define the quality metrics and thresholds before work begins, not during inspection. If the team does not know what “acceptable quality” means until they are being evaluated, they cannot design their work to meet the standard. Record all measurements — both passing and failing — to build a quality history that informs future project risk planning. Trend analysis of quality measurements over time is more valuable than any single measurement.
The quality control measurements process is most effective when measurements are objective, repeatable, and collected by someone independent of the work being measured. Teams that skip or rush this process often discover quality problems at client acceptance — the most expensive time to find them.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Quality Control Measurements Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management