Release freezes that respect teaching calendars
A freeze that blocks every change from week three to week thirteen is as harmful as shipping mid-exam. Learning platforms need a freeze language that names protected windows and still allows urgent security patches.
Name the protected windows
- Census and late-enrolment processing
- Major exam periods and results release
- Known vendor maintenance nights that already steal change capacity
Allow listed exceptions
Security patches and broken gradebook fixes should have a documented path through the freeze. Release readiness reviews work best when that path already exists — otherwise “hold” recommendations arrive with nowhere to escalate.
Write the freeze rules where product, engineering, and academic governance can all find them. Verbal understandings evaporate when staff rotate between terms.