Year-end software renewals: the notice deadlines that land before Christmas

A contract that renews on 1 January does not get decided in January. By then it has already renewed. It gets decided on its cancellation deadline, the renewal date minus the notice period, and for a calendar-year contract that date falls somewhere between the start of October and the first week of December: the same weeks as budget season, year-end close and the run-up to the Christmas shutdown.

This guide gives the dates for 1 January 2027 renewals, explains the two ways a notice clause gets counted wrong, and sets out a short routine for the fourth quarter so that year-end renewals are decided rather than inherited.

The deadlines for a 1 January 2027 renewal

The cancellation deadline is the last day notice can be given, counted back from the renewal date by the notice period. For a contract that renews on Friday 1 January 2027:

• 30 days' notice: Wednesday 2 December 2026.
• 60 days' notice: Monday 2 November 2026.
• 90 days' notice: Saturday 3 October 2026.
• Three months' notice: Thursday 1 October 2026.

If the clause says 90 days or three months, this year's deadline has already passed. That does not always mean another full year of spend: what to do after a missed cancellation deadline sets out the options, and every one of them is easier to raise early in the new term than late in it.

Days and months are not the same deadline

A notice period written in days and one written in months look interchangeable, and they are not. Three calendar months before 1 January is 1 October; 90 days before it is 3 October. Count a months clause as if it were days and you arrive two days late, which is the direction that costs a year of contract.

The gap depends on the months in between. Before 1 January the quarter holds two 31-day months, so three months is 92 days. Before a 1 April 2027 renewal the quarter holds a 28-day February, so three months and 90 days happen to land on the same day; in a leap year they do not. Do not rely on the coincidence: count in whichever unit the contract uses, and if it uses months, count calendar months.

Why the fourth quarter is where renewals get missed

Nothing about the arithmetic is harder at year end. What changes is the calendar around it.

• The deadlines cluster. Every contract that runs to the calendar year has its notice window close in the same few weeks, so the renewals one person looks after arrive together rather than spread across the year.
• The decision needs a budget that is not set yet. Next year's budget is often still being agreed when the deadline passes, so the default becomes renewing everything and arguing about it later. Renewing is the outcome that needs nobody to act, which is why it wins.
• The people are away. The 30-day deadline lands in the first week of December, so the approval behind it has to happen in late November, with leave and the shutdown approaching. Who approves a software renewal is worth settling before then, not during.
• Quotes arrive late. A renewal quote that lands in mid December, with a renewal uplift built in, leaves very little time to push back before the date it applies from, and none at all if the notice deadline has already gone.

A Q4 routine for year-end renewals

1. 1In September, list every contract that renews between 1 January and 31 March. The January ones are urgent. The February and March ones are the next cluster: on a 90-day clause their deadlines start in early November.
2. 2For each one, read the notice clause itself: the period, the unit (days or months), whether notice must be received or merely sent, and the method. Write the deadline down as a date, not as a period.
3. 3Decide keep, renegotiate or cancel at least two weeks before the deadline, so there is time to get approval and serve notice. A decision left to the deadline day tends to become a renewal by default.
4. 4If you are renegotiating, ask for the renewal quote in writing well before the deadline. Your leverage is the option to cancel, and it lasts only until the deadline. How to negotiate a SaaS renewal covers what to ask for.
5. 5Serve any notice early, keep proof of delivery, and record the date it was sent against the contract.
6. 6Put next year's dates in the diary now. The same contracts will have the same deadlines next autumn unless something changes at this renewal.

Not every year-end renewal is on 1 January

Calendar-year contracts are the obvious cluster, not the only one. A business whose financial year starts on 1 April often has contracts aligned to it, and their notice deadlines land over the holidays instead. For a 1 April 2027 renewal the deadline is 2 March 2027 on 30 days' notice, 31 January on 60, and 1 January 2027 on either 90 days or three months. A 1 April renewal on a 90-day clause has to be cancelled by New Year's Day.

If several of your contracts renew on different dates through the first quarter, it may be worth co-terminating them at their next renewals, so the decisions arrive together on a date you choose rather than scattered across the holidays.

Seeing your year-end deadlines in StackTrackr

StackTrackr works out the cancellation deadline for every auto-renewing tool from its renewal date and notice period. In the software register, sort by the Cancel by column (if you saved your own column layout, add it from Columns first): the year-end deadlines rise to the top in the order you have to act on them. Reminders go out ahead of the cancellation deadline as well as the renewal itself, and again on the deadline day. Starter alerts at 30 and 7 days; Team and up use a cadence you set, 90, 60, 30 and 7 days by default.

The notice period is stored in days. For a clause written in months, enter the longest span those months can cover, 31 days for one month, 62 for two and 92 for three, so the deadline it works out errs a day or two early and is never late. Have a look at what it tracks, or start a free trial and put your January renewals in first.