ChangeGate by Tenax Imperium

Book a demo

BUSINESS CHANGE MANAGEMENT

Business change management, with every decision on record.

A new pricing model. A supplier swap. A policy rewrite. A restructure. The changes that shape an organisation rarely touch a server, so they rarely touch a system. They are agreed in a meeting, confirmed by email and hard to find at the next audit.


ChangeGate gives every business change the discipline IT gives its releases: a structured request, a scored risk assessment, a named approver, the cost and forecast benefit, and a record that shows what was decided and whether it paid off.

One system for business, operational and IT change. Live in days, not months.

What it means

What business change management means here.

“Change management” covers two different jobs. One is the people side: communication, training and adoption. The other is governance: deciding which changes go ahead, on what evidence and at what risk, and being able to prove it afterwards.


ChangeGate does the governance, and brings the people side in where it counts. Each change records who it affects and the training it needs, so readiness is part of the decision. For bigger changes, the Initiatives module adds a light layer of organisational change management: several changes run as one initiative, through readiness gates for the people they affect.

Business change

The changes that shape your organisation.

Each of these is a business change, and each one usually leaves something important unrecorded.

Launching a service, or withdrawing one

The business case, and whether it paid off.

Approving a new tool for staff, such as AI

Who approved it, and on what evidence.

Opening a new office, moving offices or leaving one

The plan, the cost, and whether it came in on budget.

A restructure, or a role moved between teams

Which functions and processes it touched.

A new pricing or billing model

Who agreed it, and what it was expected to earn.

Moving a service to a new supplier

The risks that were weighed, and who owns them now.

Creating a new policy or procedure

Why it was needed, what it solves, and who it affects.

In ChangeGate, every one of those answers is part of the change record.

One record per change: the request, the risk, the approval and the outcome.

How it works

How ChangeGate governs a business change.

01

Request

Say what is changing and why, which parts of the organisation and which sites it touches, what it will cost and what it should return.

02

Impact analysis

Score the risk on a 5x5 grid. Write each risk as a cause, an event and an impact, with a named owner and dated actions.

03

Approval

The change type sets the route, and whoever raised it cannot approve it. The person accountable for each area, such as finance, compliance or HR, approves the changes in it; larger ones go to a change advisory board.

04

Planning

Agree the plan, the pilot or test steps, the success measures and the rollback plan before anything moves.

05

Execution

The change goes live against the plan it was approved on. Freeze windows keep your busiest periods clear.

06

Hypercare

A set period after go-live to catch problems while they are small.

07

Post-implementation review

Did it work, what did it cost and what did it return, against what was promised?

08

Closure

Closed with a complete evidence pack: every approval, risk, decision and outcome in one export.

08

Closure

Closed with a complete evidence pack: every approval, risk, decision and outcome in one export.

Initiatives

Bigger changes, run as one initiative.

Some changes are really a dozen: a new operating model, an acquisition, a move to new systems. The Initiatives module groups them under one initiative with a sponsor and a lead, and takes the whole programme through five readiness gates.

Govern

Should we, and who is accountable? The purpose, the scope, the sponsor and the money, agreed before anything starts.

Align

Are the people affected with us? The impact understood, people told what, why and when, and their concerns answered.

Train

Can they do it on day one? Training delivered and confirmed area by area, procedures updated, support in place.

Execute

Are we ready to go? Every change approved with a plan, a rehearsal done, the timing cleared and the go decision signed.

Sustain

Will it hold, and did it pay? An owner for the new way of working, and the benefits reviewed after delivery.

Benefits

Prove the change paid off.

Most business cases are approved once and never checked. ChangeGate’s benefit analysis takes the person proposing a change through where the benefit comes from, and records the workings and the evidence behind each figure.


At the post-implementation review the actual cost and the realised benefit are recorded against what was promised, and the executive dashboard shows realised benefit beside the forecast. The next business case is judged on what the last one actually returned.

One system

Business, operational and IT change in one system.

Business changes rarely stay in one lane. A new billing model needs a system change; a new supplier changes a process. ChangeGate runs all three kinds through the same lifecycle, the same register and the same audit trail, and puts them on one calendar, so nobody is surprised by a change someone else approved.

Run a law firm or another professional services firm? See change governance for professional services.

Getting started

Start with one controller and one sponsor.

Most mid-sized organisations do not employ a change manager, which is why the discipline never starts. In ChangeGate the method is built in: one person to run it and one senior sponsor are enough to begin. Everyone else joins in the role they already have. People raise changes, the person accountable for each area approves the changes that touch it, and the leadership team reads the dashboard.


In your own words. Name your own business functions and sites, and mark which functions are critical. Every change says which it touches, so it reaches the right approvers.

Evidence

Evidence for the questions that always come.

Quality and security standards ask the same of any change: plan it, assess it, authorise it and keep the record. ISO 9001 covers it in clauses 6.3 and 8.5.6; ISO 27001 in clause 6.3 and Annex A 8.32; SOC 2 in criterion CC8.1. ChangeGate produces those records as a by-product of the work.

Who approved this, and what did they know?

Every approval is recorded with who gave it, when and why, on the same record as the risk assessment.

What risk did you weigh, and who owned it?

Each risk is scored, given an owner and dated actions, and stays on the change after it closes.

Did it deliver what was promised?

The post-implementation review records the outcome, the actual cost and the realised benefit against the plan.

ChangeGate is not a certification body and does not guarantee audit outcomes. It gives you the evidence your auditor asks for.

FAQ

Business change management: common questions.

What is the difference between business change management and IT change management?+

IT change management controls changes to systems and infrastructure. Business change management controls changes to how the organisation itself works: prices, policies, processes, suppliers, structure and services. The discipline is the same (request, assess, approve, deliver, review), and ChangeGate runs both in one place.

See a business change governed from request to review.

Book a demo