Operations
The notice deadline that expires while the office is shut
A contract that renews on the first of February with sixty days' notice has a deadline in the first week of December. One that renews mid-January can have a deadline between Christmas and New Year, when nobody is at a desk to act on it. December is the shortest working month of the year, and it is also the month with the densest cluster of act-by dates. Here is how to find the deadlines that fall inside the shutdown, before the shutdown starts.
Every notice deadline is really a working-day deadline. The contract says notice must arrive by 27 December; what that means in practice is that someone has to decide, draft and send it on a day when they are actually at work. For eleven months of the year the distinction barely matters. In December it is the whole story.
A contract that renews on 1 February with sixty days' notice has its act-by date in the first days of December, in the middle of budget wrap-up and before anyone is thinking about January. One that renews on 15 January with thirty days' notice has its deadline on 16 December, the week the office starts emptying. And a 1 February renewal with a thirty-day window lands on 2 January, which sounds safe until you remember the decision-maker is back at a desk on the 5th.
None of these deadlines is hidden. They are all sitting in plain sight in the contracts. What December does is quietly remove the working days you were counting on to meet them.
December has half the working days you think it does
On paper December has just over twenty working days. Subtract the public holidays, the near-universal shutdown between Christmas and New Year, the days lost to leave being used up before it expires, and the annual round of reviews and planning, and the month's real capacity for a considered vendor decision is closer to two usable weeks - the first two.
The people a renewal decision needs are the first to disappear. Signing authority goes on leave. The budget holder is locked in year-end. The person who actually uses the tool and can say whether it is worth keeping is out from the 18th. A notice letter that needs three people to agree can clear its deadline comfortably in October and miss the same deadline in December purely because the three diaries never intersect.
Vendors know this. It is not a conspiracy - it is just that a renewal falling due when the customer is out of the office is a renewal that goes through on the vendor's terms. The quietest weeks of your year are the strongest weeks of theirs.
The January renewal cluster puts its deadlines in the shutdown
January and February are often dense renewal months, because contracts get signed when budgets reset. Every one of those renewals counts its notice window backwards into December or the first days of January.
1 January renewal, 30 days' notice: act by 2 December. Early enough to be safe, if anyone is watching in November.
15 January renewal, 30 days' notice: act by 16 December. The office holiday lunch is that week.
31 January renewal, 60 days' notice: act by 2 December, again - long windows pull January deadlines forward into the year-end crush.
1 February renewal, 30 days' notice: act by 2 January. A date that exists on the calendar but not in anyone's working year.
The pattern is worth stating plainly: a longer notice window does not make a January renewal safer. It moves the deadline from a quiet week you would have been present for into the loudest month of the year.
What missing the window actually costs
Take an illustrative mid-size firm with a support platform renewing 15 January at $24,000 a year, carrying an 8 percent uplift in the renewal terms and a thirty-day notice clause. The team agreed in the autumn that the tool was on its way out - a migration was planned for the spring. The notice deadline of 16 December arrived in the week of handovers and out-of-office replies, and passed. The contract renewed at $25,920 for a tool the firm intended to leave, and the migration had to be pushed a year or run alongside a contract being paid for nothing.
Nothing about that outcome involved a bad decision. Every individual choice - taking leave, prioritising year-end close, deferring non-urgent email to January - was reasonable. The system failed because the one date that could not move was never separated from all the dates that could.
Run the December sweep in November
- List every contract renewing in January and February, not December. December's renewals had their deadlines in the autumn; it is the new year's renewals whose windows close during the shutdown.
- Compute the act-by date for each one: renewal date minus notice period. Do the arithmetic on paper or in a system, not in your head - sixty-day windows on end-of-January dates land earlier than intuition says.
- Flag every act-by date between 10 December and 10 January. Those are the ones the shutdown will eat. Treat their real deadline as 5 December.
- Make the keep-or-leave decision for the flagged contracts in November, while the people who use the tools are still at their desks. A decision made in November takes an hour; the same decision chased through December out-of-office replies takes three weeks it does not have.
- Send any notice before the holiday lunch, not after it. If the decision is to leave, nothing is gained by holding the letter until the deadline week - and a notice sent on 5 December cannot be undone by a flight delay or a flu.
Renewly does the arithmetic for you all year round. It reads each agreement, pulls out the renewal date and the notice period, calculates the last day you can act, and alerts you well before that day arrives - so a deadline that falls between Christmas and New Year surfaces in November, while there is still a working December in front of it.
