Cover photo: Paymo / Unsplash. Illustrative photograph, not a client project.

Start with a task somebody has to perform

A new system rarely changes every team’s work in the same way. One team stops entering data, another gains an exception queue, and a manager who used to approve everything now handles only unusual cases.

A change impact assessment records those differences before they get lost inside “communications and training”. Use one row for each meaningful role-and-process combination. Describe what happens now, what will happen next, the gap and the action needed to close it.

GovS 002, section 8.7 calls for assessment of target groups’ current state and continuing attention to readiness and sustainable changed practices. The worksheet here is a suggested way to work through that problem, not an official standard. UK public-sector guidance does not impose requirements on UAE organisations.

Keep the assessment separate from the contact list

Stakeholder mapping helps identify who is affected, who influences the change and how to involve them. This assessment asks what the affected people will do differently at work. A stakeholder can have high influence but little daily task change; a small operational team can have low formal influence and a very large workload impact.

Write observable changes. “More digital” is not one. “Intake staff check an automatically populated address and resolve a mismatch before submitting the case” is. Include a normal transaction and the exceptions, handoffs and approvals surrounding it.

Ask staff to show the current process. A procedure document may omit a shared spreadsheet, a phone call or a manual correction that keeps the service working. Those workarounds are evidence to investigate, not behaviour to dismiss automatically.

Work through a case-intake change

Consider a fictional organisation replacing email-based requests with a structured intake form. The numbers and roles below are illustrative, not client findings.

Role and task Current work Future work Gap to resolve
Intake: capture request Re-key email into case record Validate submitted fields Practice identifying incomplete or inconsistent data
Case officer: receive work Choose from shared mailbox Accept allocated cases in a queue Allocation rules, cover and escalation
Team lead: approve Review every case Review exceptions above agreed thresholds Clear delegation and evidence of decisions
Support: help applicant Explain email requirements Help with form errors and assisted route Accessible support instructions and escalation

The change lead should validate each row with the people doing the task and its accountable process owner. A future process that nobody has agreed is a proposal, not a training requirement.

Do not turn every gap into a course. A missing delegation decision needs an authorised decision. An inaccessible form needs a design change or workable assisted route. Training people to work around an unresolved policy conflict just distributes the conflict.

Check who gains work as well as who loses it

Suppose 300 cases arrive each week and re-keying currently takes four minutes per case. Removing that task releases 1,200 minutes, or 20 hours, in the illustrative week. Now assume 20% of submissions need a six-minute validation check: 60 cases create 360 minutes, or six hours, of work.

The net change across those two tasks is 14 hours released per week. It is not automatically a cash saving. The work may sit in different teams, arrive unevenly or require scarce skills. The example excludes other tasks, training time and any overlap while old and new processes run together.

Test the assumptions with observation or a pilot. If validation is needed on 40% of cases, it takes 12 hours and the net release falls to eight hours. Keep the definition of a case and the measurement period consistent. Ask whether demand or case complexity changed before attributing a result to the new process.

Use the benefits realisation plan for the eventual outcome measurement. This assessment is where you identify the work changes that could enable or prevent that outcome.

Assign actions and look for adoption evidence

Each material gap needs an action owner, due date and evidence that the action worked. Practice scenarios should reflect the role: the intake team resolves a mismatch; the lead explains an exception decision; support helps someone complete the assisted route.

Record readiness as observed, partially demonstrated, not demonstrated or not assessed, with a note explaining the result. These labels are a suggested convention, not a universal maturity scale. Keep evidence about groups and processes where possible; avoid turning the worksheet into an unnecessary store of personal performance data.

After implementation, check whether the intended behaviour continues. Are staff using the queue or forwarding work back into the old mailbox? Are exceptions being resolved or simply renamed? Agree a review date with the process owner and keep support available where the gap persists.

Adoption is something people do, not a message they receive. A communications campaign can explain the change. It cannot make an unworkable process work.

Practical questions

When should the assessment start?

Start while the future process can still be changed. Use provisional rows where design is uncertain, then validate them as decisions become clearer. Repeat the assessment when scope, roles or operating arrangements materially change.

How should we prioritise impacts?

Consider the consequence if the changed task fails, the size of the capability gap, the timing and the support available. Agree the criteria with process owners. Do not assume the largest headcount always represents the greatest operational risk.

What if a team disagrees with the future process?

Record the disputed task or decision and investigate the reason with its owner. It may reveal a genuine service, capacity or policy problem. Resolve or escalate the design question before treating disagreement as a communications failure.

Use the worksheet

Download the editable worksheet (CSV) ↓

Open the CSV in your spreadsheet application, replace the illustrative entries and add rows for your programme. It contains plain values, no formulas or macros. Keep evidence references in the sheet and sensitive supporting material in your own controlled systems. Nothing is submitted through this download.

Reviewed 8 November 2026. Examples, figures and working methods are illustrative editorial material, not measured client results, professional certification or a substitute for your organisation’s required approvals.

Related reading and support