This page describes the standard operating rhythm for change delivery across data, reporting, and analytics services.
A predictable delivery cadence supports stable operations, clearer expectations, improved planning, and safer releases. Rather than operating through ad-hoc change activity, work is managed through a structured weekly cycle.
This approach helps balance delivery speed with service reliability.
Purpose
The Change & Release Calendar exists to provide:
- Clear release expectations
- Predictable planning cycles
- Safer production deployment windows
- Protected development time
- Regular stakeholder engagement points
- Dedicated time for documentation and knowledge management
Standard Weekly Cadence
| Day | Primary Focus |
|---|---|
| Monday | Production releases and controlled deployments |
| Tuesday | Backlog review, prioritisation, intake, planning |
| Wednesday | Development, build, enhancement delivery |
| Thursday | Testing, validation, readiness, handover |
| Friday | Documentation, release notes, knowledge updates, no structural change |
Daily Guidance
Monday — Release Day
The preferred day for planned production change activity.
Typical activities:
- Production deployments
- Controlled logic releases
- Approved structural amendments
- Post-release monitoring
- Communication of completed change
This provides a full working week to observe outcomes and respond if required.
Tuesday — Planning & Prioritisation
Focused on managing incoming demand and sequencing future work.
Typical activities:
- Review new requests
- Confirm priorities
- Assess risks and dependencies
- Classify change levels
- Confirm delivery candidates
Wednesday — Build & Development
Protected time for focused engineering delivery.
Typical activities:
- Data engineering development
- Report enhancements
- Model amendments
- Technical fixes
- Performance improvements
Thursday — Validation & Readiness
Used to prepare changes for controlled release.
Typical activities:
- User testing
- Peer review
- Validation checks
- Deployment readiness
- Stakeholder signoff where required
Friday — Documentation & Stability
Reserved for strengthening the service rather than introducing structural risk.
Typical activities:
- Release notes publication
- KnowHow updates
- Catalogue maintenance
- Technical documentation
- Backlog refinement
- Service review
Structural production changes should normally be avoided unless urgent and approved.
What Users Should Know
If Requesting Change
Submit requests early enough for planning and triage.
If Expecting Release
Planned production changes will normally target Monday.
If Testing Changes
Mid-week is typically the best period for validation activity.
If Requiring Stability
Friday is intentionally biased toward low-risk activity.
Exceptions
Urgent incidents, critical fixes, programme milestones, or business deadlines may require exceptions to the standard cadence.
Where exceptions occur, they should be visible, controlled, and communicated.
Governance Note
A standard rhythm improves consistency, but good judgement remains essential. Not every week will be identical, and priorities may shift based on operational need.
Related Guidance
See also:
- Recent Changes
- Breaking Changes Register
- How to Raise a Change
- Change Levels Matrix
- Safe Data Explained
Final Note
Reliable delivery is rarely accidental. Consistent operating rhythm creates confidence, protects focus, and improves outcomes over time.