This page explains our release process and provides links to the full list of releases and detailed release schedules. Each release is either planned or emergency, and is classified as either market‑participant impacting or internal.
What is a release?
A release is a bundle of approved changes (such as new features, fixes, or configuration updates) deployed to the live DIP service at a specific point in time.
Releases are categorised as DIP System-only changes, which enhance user experience without major impact, and Material System changes, which may affect business operations, incur high costs, or have long-term implementation, governed by DIP Rules and advisory boards.
Different types of releases
Releases fall into two categories:
- Planned releases – deployed on a regular, scheduled timetable
- Emergency releases – deployed only when required
Each release is classified as Tier 1 or Tier 2, which determines the governance it must follow:
- Tier 1 (material-Market Participant impacting) – subject to DCAB consultation, requires industry testing, and must align withiIndustry code-freeze windows
- Tier 2 (internal-only/non-Tier 1) – tested by DIP Manager, requies CAB approval, and deployed without industry involvement
The DIP Manager, in consultation with the relevant industry governance body, will make the initial Tier 1 / Tier 2 assessment.
Communicating Releases to stakeholders
Forward Schedule of Change (FCS)
The Forward Schedule of Change (FCS) lists our upcoming releases and lets you see what is coming, when, and how it may affect you. It is updated monthly.
- View Foward Schedule of Change (awaiting this document)
Forward Schedule of System Change
The Forward Schedule of System Change provides an indicative view of planned DIP changes to support transparency and participant planning. It does not replace formal change notices or DCAB approvals.
Detailed release process
Full details of the release process are set out in the Release Strategy, which explains how releases are documented, how Release Notes are issued, and how stakeholders are kept informed and aligned to industry release windows