# A29 — Change Readiness and Adoption Record

## Artifact metadata

| Field | Value |
|---|---|
| **Artifact ID** | A29 |
| **Artifact name** | Change Readiness and Adoption Record |
| **Artifact family** | Stakeholders, scope, communications |
| **Artifact type** | Change management and adoption artifact |
| **Source type** | synthesis |
| **Governance layer** | Project Governance |
| **Version** | 1.0.5 |
| **Status** | Active |

---

## Purpose

Assess organizational and stakeholder readiness for the change being delivered, plan adoption actions, track progress against readiness targets, and capture stakeholder feedback that informs delivery timing and benefit realization.

---

## When used

During planning when the project involves significant organizational change, process change, or system deployment affecting end users. Updated through execution and at key deployment milestones.

---

## PMI authority

| Field | Detail |
|---|---|
| **Primary PMI source** | PMBOK8; Managing Change in Organizations (MCO) |
| **Exact section** | Guide, Stakeholders Performance Domain 2.5; MCO — Change Readiness and Adoption chapters |
| **Purpose of citation** | Ground adoption planning in PMBOK 8 stakeholder performance guidance and supplement with PMI's dedicated change management practice guide. |

---

## Performance domains and focus areas

- **Performance domains:** Stakeholders, Delivery, Governance, Resources
- **Focus areas:** Planning, Executing, Monitoring and Controlling
- **Related processes:** Manage Stakeholder Engagement; Monitor Stakeholder Engagement; Manage Project Execution

---

## Inputs and outputs

### Inputs
- Stakeholder register and engagement strategy (A07)
- Scope and requirements decision record (A08)
- Risk record — people and adoption risks (A19)
- Communications and reporting record (A28)
- Business case — expected benefits dependent on adoption (A01)

### Outputs
- Readiness assessment baseline
- Adoption action plan with owners and milestones
- Stakeholder feedback summary
- Go/no-go readiness recommendation for deployment gates
- Input to benefits realization record (A02) when adoption affects value capture

---

## Core fields

| Field | Description |
|---|---|
| Change description | What is changing and for whom |
| Stakeholder group | Affected group or audience |
| Readiness dimension | Awareness, willingness, knowledge, ability, or reinforcement |
| Current readiness level | Assessed state (not ready, developing, ready) |
| Target readiness level | Required state before deployment or go-live |
| Adoption action | Specific intervention — training, communication, coaching, process update |
| Owner | Person responsible for the adoption action |
| Due date | Target date for action completion |
| Feedback summary | Key themes from stakeholder feedback on the change |
| Gate recommendation | Readiness status at each deployment or review gate |

---

## Governance

| Field | Detail |
|---|---|
| **Owner** | Change lead, project manager, and business owner jointly |
| **Approval authority** | Sponsor or business owner |
| **Escalation trigger** | Adoption risk threatens deployment timing, business readiness, or value capture |

---

## Tailoring guidance

- Use for projects with material organizational change impact; lightweight or technical projects with no user behavior change may omit this artifact.
- The ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) is a compatible readiness dimension framework but is not mandated.
- Integrate readiness gates with the project schedule and risk record rather than managing adoption separately.

---

## Waste test

Fail if an organizational change impact assessment, stakeholder feedback log, and adoption plan are maintained as separate documents with no single coordinating adoption record linked to deployment decisions.

---

## Notes

- Replaces and consolidates v1.0.2 Items 209 (Change Impact Readiness Assessment Sheet) and 210 (Stakeholder Feedback Harvesting Hub).
- Source type is synthesis: PMBOK 8 provides the stakeholder performance domain grounding; MCO provides the change management practice detail.
