# Change Impact Assessment Template: People, Process, Technology and Control

> A practical IMPACT-6 change impact assessment template for mapping consequences, owners, readiness evidence, controls and release decisions.

- Canonical page: https://mtfinstitute.com/insights/change-impact-assessment-template/
- Content type: Article
- Editorial category: Guides & Frameworks
- Publisher: MTF Institute of Management, Technology and Finance
- Author: MTF Institute Editorial Team- Published: 2026-08-21
- Updated: 2026-08-21
- Language: English
- Topics: Risk Management, Change Management, Transformation, Templates

## Change Impact Assessment Template: People, Process, Technology and Control

## What a change impact assessment should do

A change impact assessment should turn a proposed change into a controlled list of consequences for specific people, tasks, processes, systems, controls and measures. Its purpose is not to produce a generic red-amber-green slide. It should show what will be different, who must act differently, what could fail and what evidence will prove readiness.

The template below can be used for technology implementation, operating-model redesign, policy change, merger integration, service transformation or the introduction of AI into a workflow.

## Why “communication and training” is too late

Teams often discuss change management after a solution has been selected. The implementation plan is already fixed, and the remaining work is described as communication, training and resistance management.

That sequence hides design defects. A new tool may change approval authority. A centralized process may remove local knowledge. Automation may create a new exception queue. A policy may require evidence that the current system cannot retain.

The UK Government Project Delivery Function’s [guidance on organizational and societal change](https://projectdelivery.gov.uk/teal-book/home/part-f-solution-delivery/chapter-35-management-of-organisational-and-societal-change/) states that change should be considered while work and solutions are being planned. It describes impact assessment, readiness, ownership, stakeholder engagement, validation and transition as connected management activities.

That is the right operating principle: assess the change while the solution can still be changed.

## The IMPACT-6 template

Use one row for one material change affecting one group or operating unit. Do not put “all employees” into a single row if teams face different workflows or risks.

| Field | Question | Example |
|---|---|---|
| **I — Intended outcome** | What measurable outcome should this change enable? | Reduce contract intake time without weakening review |
| **M — Modified work** | Which task, decision, handoff, system or control changes? | Business users submit structured requests through a portal |
| **P — Population affected** | Which role, team, customer, supplier or location is affected? | Sales managers in three regions |
| **A — Adoption burden** | What must people stop, start, learn or decide differently? | Stop emailing free-text requests; classify deal type and risk |
| **C — Control and continuity risk** | What could fail during transition or normal operation? | Urgent deals bypass intake; incomplete data delays legal review |
| **T — Test, owner and evidence** | Who owns readiness, and what evidence permits release? | Regional sales operations owner; 90% complete fields in pilot |

The six fields create a minimum decision record. Add timing, severity, dependency and status columns when the programme is complex.

## Copyable assessment table

| Change ID | Intended outcome | Modified work | Affected population | Adoption burden | Control or continuity risk | Severity (1-5) | Frequency (1-5) | Readiness evidence | Owner | Release decision |
|---|---|---|---|---|---|---:|---:|---|---|---|
| CHG-01 |  |  |  |  |  |  |  |  |  |  |
| CHG-02 |  |  |  |  |  |  |  |  |  |  |
| CHG-03 |  |  |  |  |  |  |  |  |  |  |

For a spreadsheet, calculate **impact exposure = severity × frequency**. Treat the score as a sorting aid, not an automatic approval rule. A rare failure involving safety, legal obligation, customer harm or irreversible data loss may require a hard gate even when the arithmetic score is moderate.

## Step 1: define the current and future state

Write one observable sentence for each state.

- Weak: “The procurement process becomes digital.”
- Better current state: “Buyers email unstructured requests to procurement, which manually asks for missing information.”
- Better future state: “Buyers submit a structured intake form; requests missing mandatory risk data cannot enter sourcing review.”

The contrast reveals the real impact: a new input standard, a changed handoff, an automated control and a different source of delay.

## Step 2: segment the affected population

Segment by the way work changes, not by the organization chart alone.

Useful dimensions include:

- role and decision authority;
- location, shift or market;
- frequency of using the process;
- customer-facing versus control responsibilities;
- current capability and access;
- degree of discretion lost or gained.

Two people with the same title may need different treatment. A frequent user needs workflow practice; an occasional approver may need a concise decision guide.

## Step 3: record the adoption burden

For each population, identify four types of burden:

1. **Stop:** routines, workarounds or approvals that must end.
2. **Start:** new tasks, evidence or decisions.
3. **Learn:** knowledge or practice required before go-live.
4. **Sustain:** reinforcement, monitoring or coaching required after launch.

This is more useful than assigning every group a generic training session.

## Step 4: separate adoption risk from solution risk

Adoption risk asks whether people will use the change as intended. Solution risk asks whether the future process, technology or policy works safely and reliably.

Consider a new AI-supported customer-service workflow:

- adoption risk: agents ignore the tool because explanations are unclear;
- solution risk: the tool produces unsupported answers;
- control risk: supervisors cannot reconstruct which source informed an answer;
- continuity risk: the fallback process cannot handle demand when the tool is unavailable.

Each risk needs a different response. Communication cannot fix an invalid model, and technical testing cannot establish whether supervisors understand escalation authority.

## Step 5: define readiness as evidence

Avoid readiness statements such as “the team is comfortable” or “training is complete”. Define observable evidence.

| Readiness question | Weak evidence | Decision-ready evidence |
|---|---|---|
| Can users perform the new task? | Training attendance | Successful completion of representative scenarios |
| Does the process work? | Process document approved | Pilot transactions meet time, quality and control thresholds |
| Are exceptions manageable? | Escalation mailbox exists | Named owner, response target and tested exception cases |
| Can leaders see adoption? | Dashboard planned | Baseline, target, data owner and review cadence confirmed |
| Is continuity protected? | Backup mentioned | Fallback steps tested with capacity and recovery owners |

## Step 6: make a release decision

Use one of four decisions for each high-impact row:

- **Ready:** evidence satisfies the release threshold.
- **Ready with conditions:** bounded gaps have owners, dates and compensating controls.
- **Pilot only:** uncertainty is too high for broad release but can be tested safely.
- **Not ready:** a critical capability, control or continuity condition is missing.

The decision should identify who has authority to accept residual exposure. The project team should not silently accept a business or control risk simply because a launch date exists.

## Worked example: introducing AI contract review

| IMPACT-6 field | Assessment |
|---|---|
| Intended outcome | Reduce first-pass review time for standard low-risk clauses |
| Modified work | AI proposes clause classifications; lawyers confirm or correct them |
| Population affected | Commercial lawyers, contract managers and sales requesters |
| Adoption burden | Reviewers must distinguish recommendation from approval and record overrides |
| Control and continuity risk | False low-risk classification; missing audit trail; over-reliance; unavailable service |
| Test, owner and evidence | Legal operations owns pilot; 200 historical clauses tested; error thresholds and fallback approved |

This row exposes a design question: if the system cannot retain reviewer overrides, the problem is not “user resistance”. The solution lacks evidence required for accountable use.

## Common failure modes

- **One row per department:** hides different tasks and risks inside the same team.
- **Impact equals sentiment:** treats positive attitudes as proof of operational readiness.
- **Training as the default response:** ignores process, system, policy and control defects.
- **No current-state baseline:** makes benefits and regression impossible to measure.
- **No named owner:** turns every issue into a collective concern and nobody’s decision.
- **No expiry for temporary controls:** allows transition workarounds to become permanent operations.

## A 30-minute review agenda

1. Confirm the intended outcome and baseline.
2. Review only high-exposure and hard-gate impacts.
3. Challenge whether affected populations are sufficiently segmented.
4. Check that each readiness statement has observable evidence.
5. Assign owners and deadlines for conditions.
6. Record Ready, Ready with conditions, Pilot only or Not ready.

The assessment then becomes a governance tool rather than a workshop artifact.

For a broader management system covering capability, people analytics, change and human-AI work, see [Strategic HR and Organizational Leadership as a Business System](https://mtfinstitute.com/insights/strategic-hr-organizational-leadership-system/).

## Source

- [UK Government Project Delivery Function, Chapter 35: Management of organisational and societal change](https://projectdelivery.gov.uk/teal-book/home/part-f-solution-delivery/chapter-35-management-of-organisational-and-societal-change/)


## Citation

When citing or summarizing this material, link to the canonical HTML page: https://mtfinstitute.com/insights/change-impact-assessment-template/