• The table below outlines the IT change freeze periods driven by key UoP events throughout the year.  
  • Applying strict rules on how we apply changes to the IT environment during these periods minimises the risk of system failures and downtime that could impact the business’ ability to successfully run these critical, high-profile, events. 
  • The change freeze timetable is scheduled in advance, allowing teams to prepare and complete necessary changes beforehand whenever possible.

 

 
2026 Dates Freeze Period Name Freeze Type
12 January – 23 January  Assessments   For awareness of key UoP event only 
19 January  Mid-Year Intake - January Starters  For awareness of key UoP event only 
18 May - 12 June  Examinations   Heightened Level of Change Period 
22 June – 10 July  Board Weeks   For awareness of key UoP event only 
20 July - 30 July  Graduation  Change Freeze 

30 July - 21 August  

22 August - 28 August

Confirmation & Clearing (Live) 

Confirmation & Clearing (Post) 

Change Freeze 

At Risk 

August - September  Registration   For awareness of key UoP event only 

14 September 

21 September 

Induction Week 

Start of Teaching (Block 1) 

No new services 

Glossary

  • At Risk: Changes to all systems and services will have a heightened level of authorisation.
  • Change freeze: No changes apart from the pre-approved exemption list (see below) will be applied unless authorised by the Change Advisory Board and IS SLT.

Note: Change will only be authorised to ensure a business critical service stays operational or to provide essential functionality to support the Change Freeze event in question.

  • New Services: No new services should go live during a change freeze, during induction or the start of teaching (Block 1). Unless specifically authorised by the Change Advisory Board CAB).
  • Exemptions: CAB pre-approved, standard, minimal-risk changes are excluded from change freezes. These are published before each Change Freeze event.
  • Heightened Level of Change Period: If it is essential for a change to be made during a freeze, it will need to follow the Change Freeze Process which requires assessment of the risk of agreement to delay the implementation. This will need CAB and IS SLT approval.
  • Controlled Change Period: Changes can still proceed, if they are non–service affecting. All changes must be reviewed and approved by CAB before implementation.
  • Change Advisory Board (CAB): Responsible for evaluating and approving IT related changes within the University. The CAB includes representatives from affected business departments and IT to ensure any changes are assessed from multiple perspectives. The CAB assesses the potential impact, risks, and benefits of proposed changes. Makes informed decisions to approve, defer, or reject changes and ensures necessary communications. The CAB plays a crucial role in reducing disruption to business services whilst maintaining stability and continuity when enabling necessary improvements and updates.

Need Help?

Contact the Service Desk:

Enable University alerts

Turn on notifications for critical updates like closures, safety alerts, and urgent service disruptions.