Auditable change management means every change to an IT environment is recorded before it happens: what will change, what it affects, what could go wrong, how to undo it, and who approved it. During a deployment, this discipline is the difference between a controlled rollout and a series of surprises. This page shows how the workflow runs in KPODATA.
The change record
Each change is a structured record with eight fields:
- Request: what is being changed and why
- Type: standard, normal or emergency
- Impact: which sites, systems and users are affected
- Risk: what could go wrong, rated low, medium or high
- Rollback plan: how the change is undone if it fails
- Approver: the named person who signs it off
- Status: from request through approval to implementation and closure
- Outcome: what actually happened, recorded at closure
A change without a rollback plan does not reach approval.
Why auditable matters during deployments
Deployments compress dozens of changes into weeks: network builds, server migrations, device rollouts, access grants. Without a record per change, nobody can answer basic questions afterwards: what was changed on that site, who approved the downtime, why was this server reconfigured. With one, the deployment carries its own evidence, which is exactly what later reviews and MAS TRM assessments ask to see.
Emergency changes
Emergencies get a faster path, not a free pass. An emergency change is still recorded with impact, risk and rollback, and is reviewed after the fact. The record exists before the change, even if approval follows the fix.
Who runs it
KPODATA is built and operated by Global ITN. Change management like this runs inside every deployment delivered by Global ITN’s system integration team, and continues into ongoing managed support after handover.
Common questions
Does this slow deployments down?
Recording a change takes minutes. Recovering from an unrecorded one takes days.
Who can approve changes?
You decide. Approvers are named per environment, often one on each side.
What happens to the records after go-live?
They stay. The change history becomes part of the environment’s evidence set.
