---
ref_id: PR32
ref_type: Process
ref_name: "Validate Scope"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-05-03
related_artifacts:
  - A08
  - A17
file_path: "reference/processes/PR32-validate-scope.md"
---
# PR32 — Validate Scope

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR32 |
| **Process Name** | Validate Scope |
| **Process Group** | Monitoring and Controlling |
| **Knowledge Area** | Scope Management |
| **PMBOK Source** | Process Groups: A Practice Guide §7.3 |

---

## Purpose
Formalize acceptance of the completed project deliverables. Brings objectivity to the acceptance process and increases the probability of final product, service, or result acceptance by validating each deliverable.

---

## Inputs
| Input | Description |
|---|---|
| Project management plan | Scope management plan, requirements management plan, scope baseline |
| Project documents | Lessons learned register, quality reports, requirements documentation, requirements traceability matrix |
| Verified deliverables | Output of Control Quality — confirmed correct and complete |
| Work performance data | Raw data on deliverable completion status |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Inspection | Review/walkthrough of deliverable with customer or sponsor |
| Decision making | Voting on acceptance |

---

## Outputs
| Output | Description |
|---|---|
| Accepted deliverables | Deliverables formally signed off by customer or sponsor |
| Work performance information | Processed data indicating acceptance status |
| Change requests | If deliverables are not accepted, defect repair or re-work change requests |
| Project documents updates | Lessons learned register, requirements documentation, requirements traceability matrix |

---

## Key Concepts
- Concerned with **acceptance** of deliverables (customer/sponsor sign-off).
- Distinct from **Control Quality**, which is concerned with **correctness** of deliverables.
- Control Quality is generally performed **before** Validate Scope, though both may run in parallel.
- Performed periodically throughout the project, not only at project closure.

---

## PMBOK 8 Alignment
- Supported by the **Scope** performance domain (§2.2).
- Accepted deliverables feed directly into **Close Project or Phase** (PR40).

---

## Related Processes
- Depends on: PR37 (Control Quality) — verified deliverables
- Feeds into: PR40 (Close Project or Phase)
- Cross-links: PR31 (Perform Integrated Change Control) — for change requests on rejected deliverables

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A08 | Artifact | Primary artifact produced or updated by this process |
| A17 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-03 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Are acceptance criteria formally defined before validation begins?
2. Is stakeholder sign-off documented for each validated deliverable?
3. Are partially accepted deliverables and conditions of acceptance documented?
4. Is scope validation integrated with quality control activities?
5. Are validated deliverables formally linked to requirements traceability?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
