This area defines how changes to data, reporting, and analytics services are requested, assessed, delivered, and communicated.
Effective change management protects trusted outputs while enabling continuous improvement. It ensures low-risk improvements can move efficiently, while higher-risk changes receive the appropriate level of review, validation, and visibility.
The objective is simple: deliver change with confidence, clarity, and control.
Purpose
The Change Management framework exists to:
- Protect trust in data and reporting outputs
- Provide a clear route for requesting improvements
- Apply proportionate governance based on risk
- Communicate delivered and upcoming changes
- Reduce avoidable disruption
- Support reliable service delivery
- Maintain transparency across stakeholders
Core Principles
Fast Where Safe
Low-risk improvements should move efficiently.
Controlled Where Risky
Changes affecting logic, structure, security, or key outputs require stronger review.
Transparent Always
Users should be able to understand what has changed, what is planned, and what may affect them.
Continuous Improvement
Change is a normal part of service maturity and should be managed constructively.
Change Lifecycle
The standard lifecycle for managed change is:
- Request raised
- Initial review and classification
- Prioritisation and planning
- Development and validation
- Controlled release
- Communication and documentation
- Operational review
Governance Model
Changes are assessed according to their likely impact.
| Level | Description |
|---|---|
| Level 0 | Cosmetic / Safe |
| Level 1 | Controlled Safe |
| Level 2 | Business Logic |
| Level 3 | Structural / Sensitive |
| Level 4 | Strategic / Platform |
Further detail is provided within the Change Levels Matrix.
Standard Operating Rhythm
The weekly delivery model normally follows a structured cadence:
| Day | Primary Focus |
|---|---|
| Monday | Production releases |
| Tuesday | Backlog review and planning |
| Wednesday | Development and build |
| Thursday | Validation and readiness |
| Friday | Documentation and service improvement |
This rhythm supports predictable delivery and stable operations.
Communication Channels
Change activity is communicated through:
- Recent Changes register
- Breaking Changes register
- Release notes
- KnowHow guidance articles
- Direct stakeholder communication where required
Roles and Responsibilities
Requestors
Provide clear business need, expected outcome, and timing.
Delivery Teams
Assess, prioritise, design, validate, and implement change safely.
Stakeholders
Support prioritisation, testing, and adoption where required.
Service Owners
Maintain governance, standards, and service confidence.
What Good Looks Like
A well-managed service demonstrates:
- Clear intake of demand
- Consistent prioritisation
- Safe and regular releases
- Strong documentation
- Early warning of impactful change
- Continuous improvement without unnecessary friction
Supporting Guidance
This framework is supported by the following guidance:
- Safe Data Explained
- Change Levels Matrix
- How to Raise a Change
- Recent Changes
- Breaking Changes Register
- Change & Release Calendar
- Emergency Change Route
Final Statement
Good change management does not slow progress. It enables progress to happen reliably, visibly, and with trust maintained throughout.