Principle: embed quality

The third principle in the PMBOK® Guide, Eighth Edition, from PMI®, asks project teams to embed quality: build it into the way work is planned, done and accepted, instead of hunting for defects at the end. For an owner, that changes the question from "did we inspect enough?" to "did we decide, early enough, what good looks like and how we will know?"

Learning outcomes

• Explain what the embed quality principle asks of a project team, in your own words.
• Distinguish prevention from inspection, and quality assurance from quality control, using the cost-of-quality categories.
• Turn an owner requirement into measurable acceptance criteria with hold points and records.
• Draft an owner-side inspection and test plan for a Northgate interface that the owner, not the contractor, carries the risk on.

The lesson

Where the principle sits

The Eighth Edition, published by PMI in November 2025, cuts the twelve principles of the Seventh Edition down to six: adopt a holistic view, focus on value, embed quality, be an accountable leader, integrate sustainability and build an empowered culture. Lesson 3 showed how those principles sit above the seven performance domains and five focus areas. Quality was already a principle in the Seventh Edition. What is different now is the verb. "Embed" says quality belongs inside the processes and the deliverables themselves, across the whole life cycle, not in a separate inspection stage tacked on at the end.

There is no quality performance domain in the Eighth Edition. The seven domains are governance, scope, schedule, finance, stakeholders, resources and risk. Quality shows up as a principle that runs through all of them, and in specific processes: published summaries of the 40 processes place a Manage Quality Assurance process in the governance domain and a Validate Scope process in the scope domain. That is a useful signal for owners. Quality is a governance matter, decided by the people who set the rules of the project, and it is a scope matter, settled when someone formally accepts a deliverable.

What "quality" means here

In PMI's usage, quality has two halves. A deliverable must meet its stated requirements, and it must meet the stakeholders' real needs and expectations. A slab that meets the specification but cannot take the racking the owner bought has passed the first test and failed the second. Embedding quality means closing that gap before work starts: the requirement is written so that meeting it also satisfies the need, and the acceptance criteria are written so that anyone can tell whether it was met.

The principle also warns against the opposite error. Quality is not "as good as possible". Gold-plating, adding features or finishes nobody asked for, costs money and time and adds no value, which ties back to lesson 7. The target is fit for purpose, agreed in advance.

Prevention beats inspection

The older idea underneath the principle is the cost of quality. Every project spends money on quality in one of four ways. Prevention costs are spent so defects never happen: design reviews, mock-ups, training, a clear specification. Appraisal costs are spent finding defects: inspections, tests, third-party reviews. Internal failure costs come from fixing defects before handover: rework, re-testing, delay. External failure costs come from defects found after handover: warranty calls, business interruption, damaged reputation. The first two are the cost of conformance; the last two are the cost of non-conformance.

The rule of thumb is that the later a defect is found, the more it costs to fix, because more work has been built on top of it and more people are affected. Figure 1 shows the pattern as an illustrative index. The numbers are not data from any study; they show the shape owners should expect.

View the data

Where caught	Cost-of-quality category	Illustrative index
Design review	Prevention	1
Submittal review	Prevention	3
First-work inspection	Appraisal	8
Testing	Appraisal	20
Commissioning	Internal failure	40
After handover	External failure	100

Assurance and control are different jobs

Quality assurance asks whether the process is sound: are the right people checking the right things, at the right time, with records? Quality control asks whether the product conforms: does this pour, this panel, this test result meet the criteria? Assurance is upstream and systemic; control is downstream and specific. Embedding quality needs both, but owners usually get more from assurance, because one fixed process prevents many defects.

On a CCDC 2-2020 stipulated price contract, the contractor controls the Work and is responsible for its quality control. The Consultant reviews the Work during construction for general conformity, and GC 2.4 deals with defective work: the Consultant can reject it and the contractor must correct it at its own cost. The owner's quality role is not to supervise trades. It is to set the requirements clearly, check that the contractor's quality system exists and is working, protect the interfaces the owner carries, and accept deliverables on evidence. An owner who starts directing how concrete is finished risks taking on responsibility the contract placed elsewhere.

From requirement to accepted deliverable

Figure 2 is the chain that turns "we need a good floor" into something that can be accepted or rejected. Each link is a place where quality is either built in or lost.

Two terms matter in step 4. A hold point is a stage the work cannot pass until a named person has inspected and released it, such as concrete placement before the reinforcing has been reviewed. A witness point is a test or inspection the owner or Consultant has the right to attend, with notice, but which proceeds if they do not come. Hold points cost schedule time, so use them only where getting it wrong would be expensive to undo.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan, Ontario, with a 9.75 m clear height and ESFR sprinklers, built by Halvorsen Builders Ltd. (fictional) under CCDC 2-2020, with Ridgeline Architects Inc. (fictional) as Consultant. The details are on the Northgate fact sheet.

The interface the owner carries

The slab-on-grade finishes at M4, Friday May 14, 2027. The owner's racking contractor, under a separate contract, starts at M10, Monday January 17, 2028, eight months later. If the slab is not flat and level enough for tall racking, Halvorsen may have met its contract and the owner still has a problem, because the racking contract is the owner's, not Halvorsen's. That is exactly the kind of interface lesson 6 warned about, and exactly where embedding quality pays.

Floor flatness and levelness are usually measured as F-numbers (FF for flatness, FL for levelness) under ASTM E1155. ASTM itself notes that the method is meant for randomly trafficked floors and should not be used to enforce tolerances on floors for fixed-path vehicles, such as narrow-aisle warehouses. So the owner's first quality decision is a requirement question, made long before M4: will Northgate run narrow-aisle equipment, and if so, which floor tolerance system does the racking and truck supplier need? Get that wrong and the slab passes every test and still fails the need.

An owner-side inspection and test plan

Figure 3 is a short owner-side inspection and test plan for the slab. It does not replace Halvorsen's quality control plan. It lists the few points where the owner wants evidence before accepting the risk.

Notice the shape. One prevention item in design, one hold point before the first production pour (when changing the method is still cheap), Halvorsen's own quality control left with Halvorsen, one witness point on the measurement that matters, and one hold point at the owner-to-owner handoff. The plan costs the owner a few site visits and one early decision. A slab that has to be ground or patched after racking anchors are drilled costs far more, and it lands squarely on the owner's M10 date.

Assurance, not just control

The owner's representative also checks the system. At the pre-construction stage, they ask Halvorsen for its quality control plan for concrete flatwork, confirm who the testing agency is and who hires it, and confirm that the survey timing in the specification matches the curing schedule. Those are assurance questions. If they get good answers, the owner needs to inspect less, not more.

Owner's move

• Write acceptance criteria before tender. For each deliverable the owner will rely on, name the test method, the tolerance and who signs. A requirement you cannot measure is a dispute waiting to happen.
• List the owner's interfaces. Anything the owner's separate contractors, operations or equipment depend on (slab, power, sprinkler clearances, dock levellers) gets its own acceptance line.
• Use hold points sparingly. Put them where a defect is hard to undo, and plan them into the schedule as real activities.
• Audit the system early. Ask for the contractor's quality control plan and testing arrangements at pre-construction, not after the first failure.
• Feed lessons back. Record every significant non-conformance and the requirement that would have prevented it, so the next project's specification is better.

Common mistakes

1. Equating quality with more inspection. Inspection finds defects; it does not prevent them. A project that relies on it pays twice.
2. Vague acceptance criteria. "Floor to be level" or "to the owner's satisfaction" cannot be tested and invites argument at handover.
3. Owner directing means and methods. Telling trades how to do the work blurs responsibility the contract gave the contractor.
4. Gold-plating. Asking for better than fit for purpose spends value the owner could have used elsewhere.
5. Ignoring owner-to-owner handoffs. The contractor's tests prove the contract was met, not that the owner's next contractor can start.

Quick quiz

1. What does "embed" add to the quality principle in the Eighth Edition?

   1. Quality is checked by a separate team at the end
   2. Quality is built into processes and deliverables across the life cycle
   3. Quality becomes its own performance domain
   4. Quality is measured only by the sponsor

2. A design review that catches a missing tolerance is which cost-of-quality category?

   1. Prevention
   2. Appraisal
   3. Internal failure
   4. External failure

3. Which is a quality assurance activity rather than quality control?

   1. Surveying one pour for flatness
   2. Rejecting a cracked panel
   3. Confirming the contractor's testing agency and inspection schedule exist
   4. Measuring a sprinkler head's clearance

4. What is a hold point?

   1. An inspection the owner may attend if given notice
   2. A stage work cannot pass until a named person releases it
   3. A payment holdback
   4. A schedule buffer

5. Northgate's slab passes every specified test but the racking supplier rejects it. What failed?

   1. Quality control
   2. The testing agency
   3. The requirement: it did not capture the real need
   4. The racking supplier's survey

Show answers and explanations

1. B. The principle places quality inside the work across the life cycle. There is no quality domain in the Eighth Edition.
2. A. Money spent so the defect never reaches the field is prevention.
3. C. Assurance checks the process; the other three check a specific product.
4. B. A witness point proceeds without you; a hold point does not.
5. C. Meeting a requirement that does not reflect the stakeholder's need is the classic quality gap the principle tries to close.

Key terms

Embed quality

The PMBOK Guide 8 principle that quality is built into processes and deliverables throughout the life cycle, not inspected in at the end.

Cost of quality

All spending on quality, split into prevention, appraisal, internal failure and external failure.

Acceptance criteria

Measurable conditions, with a method and tolerance, that a deliverable must meet to be accepted.

Quality assurance

Checking that the processes that produce the work are sound and followed.

Quality control

Checking that a specific output conforms to its criteria.

Hold point

A stage that cannot proceed until a named person inspects and releases it.

Witness point

An inspection or test a party may attend with notice, which proceeds if they do not.

References

1. Project Management Institute, PMBOK® Guide, Eighth Edition (product page: six principles, seven performance domains, November 2025 publication).
2. PMExams, PMBOK 8: the full process map (third-party summary of the 40 processes by performance domain).
3. 4PMTI, What is the PMBOK 8th edition? Principles, domains, focus areas, and what changed.
4. The Rebel's Guide to Project Management, The principles of project management (PMBOK 8 Guide).
5. ASTM International, ASTM E1155: Standard test method for determining FF floor flatness and FL floor levelness numbers (scope note; current version E1155/E1155M-23).
6. Ontario General Contractors Association and Ontario Association of Architects, Recommended Supplementary Conditions for CCDC 2-2020 (revised March 15, 2024; amendments to GC 2.4 Defective Work).

Verified on November 6, 2026.

Next lesson in this trackPrinciple: be an accountable leader