Put the freeze on the calendar

Every estate we work in freezes in December. Maybe it is announced in November with dates and an exceptions process. Maybe it just happens, the way it happened to a logistics client of ours two years back: nobody declared anything, everybody quietly stopped deploying, and the one team that did not stop shipped the incident that ate the 27th. We wrote up what an undeclared freeze does to a migration already. This note is the other half: declare it, then use it.

Declare it by October 31. Three lines: freeze starts this date, ends this date, here is who signs exceptions. Publishing in October costs nothing. Publishing mid-November, after three teams have promised year-end deliveries that need the deploy window you are about to close, costs three arguments and an escalation.

Then plan the freeze weeks like the asset they are. A freeze is the only fortnight of the year when production stands still, and a standing-still estate is the easiest thing in the world to measure. The work that fits:

1. Reconcile the inventory. Walk what actually runs against what the CMDB says runs. A quiet estate makes the diff honest, and the inventory always surprises.
2. Rehearse a runbook. Failover, restore from backup, cold start of the batch chain. Rehearsal needs a stable stage; you have one now.
3. Read the year's incident list once, end to end, with the leads in one room. Two hours. The themes assign your Q1 roadmap better than any offsite.
4. Let the on-call rest. A freeze that becomes surprise overtime for the people holding the pager is a freeze you will not get compliance with next year.

What does not fit: the migration cutover someone proposes for the week "because it is quiet." Quiet is the point. The freeze has a skeleton crew, half the approvers on leave, and vendors on holiday rotas. If the cutover goes wrong on January 3 you have a bad Tuesday. If it goes wrong on December 24 you have a story people tell for years, and we know because we are still telling ours. It was a payroll adjacent system. It was not fine. Estimate the staffing before believing any December date; our rule is that a change needing more than two named people to roll back does not enter the freeze window.

Book the thaw too. First week of January, in this order: expire the exceptions, deploy the backlog in dependency order rather than first-come, and hold the freeze retro while memory is fresh. Ten lines in a shared doc: what got through on exception, what broke, what the quiet fortnight measured.

Two dates and a name, published by Halloween. Everything else about December follows from whether you did that.