This register provides advance notice of approved changes that may materially affect users, reports, integrations, or operating processes.
A breaking change is any change that may require user action, report amendment, process review, or technical adjustment in order to maintain continuity of service.
The purpose of this page is to provide early visibility, clear ownership, and sufficient time for preparation.
Purpose
The Breaking Changes Register supports controlled delivery by providing:
- Early warning of impactful change
- Clear deadlines and effective dates
- Visibility of affected assets or services
- Defined user actions where required
- Reduced disruption at release point
- Transparent communication across stakeholders
What Is a Breaking Change
A breaking change may include:
- Field renamed or removed
- Existing logic retired or replaced
- Dataset withdrawn
- Semantic model amended incompatibly
- API contract changed
- Security or access model updated
- Required migration to replacement asset
- Platform or environment cutover
- Structural change affecting dependencies
Not all significant changes are breaking changes, but all breaking changes should be communicated here.
Standard Operating Use
Users, analysts, and support teams should review this register when:
- maintaining reports or dashboards
- managing integrations or extracts
- preparing monthly or period-end activity
- planning releases or deployments
- validating future dependencies
- assessing readiness for programme milestones
Project and service leads should use this page during planning cycles.
Register of Upcoming Breaking Changes
The current list of approved and scheduled breaking changes is shown below.
[breaking_changes]
(Replace with your WordPress shortcode, Pods list, or custom feed.)
Recommended Entry Standard
Each entry should contain:
- Planned effective date
- Change title
- Summary of change
- Assets affected
- Impact description
- Required user action
- Replacement route (if applicable)
- Owner / accountable team
- Current status (Planned / Confirmed / Complete / Deferred)
Example Entry Format
| Effective Date | Change | Impact | Action Required | Replacement | Status |
|---|---|---|---|---|---|
| 01 Oct 2026 | Legacy ERP dataset retired | Existing reports may fail refresh | Repoint to Cloud dataset | ERP Cloud Reporting Model | Planned |
Change Status Definitions
- Planned – Approved in principle, subject to final scheduling
- Confirmed – Delivery date agreed
- Deferred – Postponed pending review
- Complete – Implemented
- Withdrawn – No longer proceeding
Governance Note
Changes not listed here should not normally be treated as formally notified breaking changes unless communicated through another approved route.
Where urgent action is required, direct communication may supplement this register.
Related Guidance
See also:
- Recent Changes
- Change Levels Matrix
- Release Calendar
- How to Raise a Change
- Emergency Change Route
Final Note
Well-managed change avoids surprises. Early notice allows users to prepare, adapt, and maintain continuity with confidence.