Drawing of Stakeholder map

Change Management, How to Guides and Advice

  • Concise, focused guide that cuts through the clutter
  • Step-by-step instructions for creating a project plan in under a day
  • Master essential skills like work breakdowns and task sequencing
  • Real-world troubleshooting for 20 common scheduling challenges
  • Rapidly get up to speed if you're new to Microsoft Project
  • Includes glossary, support resources, and sample plans
The cover of the book 'Essential Microsoft Project: The 20% You Need to Know'

Free Change Impact Assessment Template for Excel

Identify who is affected, what changes for them and what support they need. Select the image to enlarge it.

“We are introducing a new system” tells people very little. What will they have to do differently on Monday morning?

Use this free change impact assessment template to turn a project announcement into practical actions. Record the teams affected, compare their current and future ways of working, rate the impact and assign the support they need.

The Excel workbook has space for 200 impact records, an automatic summary and a separate worked example. Choose the light or dark theme. Both contain the same features.

Download the change impact assessment template

Each download includes a blank assessment, summary, eight example entries, impact definitions and instructions. Excel .xlsx format. No macros.

Start on Summary, then add your records on Impact assessment. The worked example stays separate from your totals.

What is a change impact assessment?

A change impact assessment identifies how a proposed change will affect people and their work. It compares what happens now with what will happen next, then records the preparation and support each group needs.

One project can affect teams in different ways. A new service portal might mean a short demonstration for occasional users, new daily routines for the service desk and different approval responsibilities for managers.

Use the assessment when introducing software, changing a process, moving work between teams, updating a policy or relocating a service. Start while the change is being designed, then revisit it as the details become clearer.

Bring the affected people into the discussion. They can spot the small changes that a project plan misses: the report they rely on, the exception they handle every Friday or the colleague who provides cover.

What is in the workbook?

WorksheetWhat it does
SummaryShows impact records, high impacts, teams affected, overdue actions, open records and records with missing details. Includes breakdowns by impact level and action status.
Impact assessmentProvides 200 rows for your own assessment, with dropdowns for change area, impact level and action status. Automatic columns flag deadlines, missing details and duplicate IDs.
Worked exampleShows eight fictional impacts for a business introducing a service desk portal. Uses a fixed review date of 15 March 2027.
Instructions and resourcesExplains how to complete the workbook, defines the three impact levels and lists related stakeholdermap.com resources.

Light and dark template previews

These previews show the blank summary included in each download. The figures update as you enter your own impact records.

Light theme

The light summary shows six headline counts and breakdowns by impact level and action status. Select the image to enlarge it.

Dark theme

The dark version has the same fields, formulas and example as the light version. Select the image to enlarge it.

How to complete the change impact assessment

  1. Name the change and set a review date. Enter your project name on Summary. The review date uses today’s date automatically. Replace it with a fixed date when you want to review deadlines against a particular day.
  2. Identify the affected teams or groups. Start with your stakeholder analysis. Include people who use the service, support it, approve work or receive its outputs. Use the same name for a team throughout the register.
  3. Give each impact a separate row. Start in row 9. Enter a unique ID such as CI-001. A single team may need several rows if the change affects its processes, systems and responsibilities differently.
  4. Explain what changes for the people involved. Compare the current way of working with the new one. “Submit requests through the portal and track progress there” is useful. “Adopt the new operating model” leaves everyone guessing.
  5. Rate the impact and explain why. Select Low, Medium or High. Record the practical reason for your rating, such as daily use of a new tool, a new approval responsibility or a change to where work takes place.
  6. Assign the support. Add an action, owner, due date and status. The action might involve training, communication, practice sessions, access, revised instructions or additional help after launch.
  7. Review the results with the affected people. Check high impacts, blocked actions and overdue work. Fill in missing details and add evidence when an action is complete.

Make the change concrete

Too vague: Staff will use the new system.

Useful: Team managers will approve requests in the portal and nominate a deputy to cover their absence.

How to rate the impact

The template uses three descriptive levels. Choose the level that best describes the change for that group, then explain your choice in Why this rating?

LevelMeaningTypical support
HighA major change to daily work, responsibilities or service delivery.Substantial preparation, practice, training or hands-on support.
MediumA noticeable change to a familiar process or tool.Targeted guidance, training or an adjustment to working practices.
LowA small change with limited disruption.A brief explanation or simple update.

A beneficial change can still have a high impact. Removing a clumsy spreadsheet may be welcome, but people still need time to learn its replacement. Rate the scale of the adjustment, then plan the help.

Worked example: introducing a service desk

An extract from the workbook’s fictional service desk example. The full worksheet contains eight entries. Select the image to enlarge it.

A business is replacing a shared mailbox and spreadsheet with a service desk portal. The project has one launch, but the changes look different for each group.

GroupWhat changes?ImpactSupport
RequestersSubmit requests through the portal and check progress there.HighA short demonstration and quick-start guide.
Service deskTriage tickets in one queue using agreed categories.HighPractice sessions using common and urgent requests.
Team managersApprove requests in the portal and nominate a deputy.MediumGuidance on approvals and deputy arrangements.

The example also shows changes to knowledge searches, IT support, reporting, record retention and the Facilities team’s portal bookmark. It includes an action that is blocked, one that is complete and one marked Not required, with an explanation.

Notice how the support follows the impact. The service desk needs practice with its new daily routine. Managers need to understand approvals and cover. Sending both groups the same launch email would leave important work undone.

Turn the assessment into action

Support actions have named owners, due dates and statuses. Deadline flags use the example’s fixed review date. Select the image to enlarge it.

Keep the register open during planning meetings. Filter Impact level to High, Action status to Blocked or Deadline to Overdue to focus the discussion.

The Deadline column compares the action due date with the review date. It shows Overdue, Due today, Due in 7 days or On track. Records marked Complete or Not required show Closed. The Missing details column remains visible if a closed record still needs an owner, evidence or another required field.

  • Training needs: turn them into sessions and materials in your training plan.
  • Communication needs: add the audience, message and timing to your communications plan.
  • Unresolved problems: use your issue log when they need wider project attention.

When an action is complete, record what was delivered or agreed. A test result, accepted support guide or completed briefing gives the next reviewer something useful to check.

Frequently asked questions

Is this the same as a stakeholder analysis?

They work together. A stakeholder analysis identifies the people and groups involved and helps you plan engagement. This assessment records the specific changes each group faces and the support those changes require.

Is this a change request form?

No. Use a change request form when seeking approval to alter a project’s scope, cost, schedule or other agreed requirements. Use this workbook to assess how a planned change affects people and their work.

Can I use it for more than one team?

Yes. Enter each affected team or group in its own impact rows. The same team can appear several times. Keep its name consistent so the summary counts it once.

Do filters change the summary totals?

No. The summary includes all 200 prepared rows, even when you filter the register to show only one team or status.

How many records can I add?

The template is set up for 200 impact records in rows 9 to 208. Enter your records within that area so the formulas, dropdowns and summary cover them.

Can I overwrite the grey columns?

Enter your information in columns B to L and O. Leave M, N and P for the formulas. These calculate deadline flags, missing details and the team count.

Does it need macros or Power BI?

No. It is an Excel .xlsx workbook using worksheet formulas, dropdowns and conditional formatting. Power BI is not required.