Put each renewal in the calendar twice: once thirty days before with what to check, and once on the day. The first entry is the one that does the work.

A date is not a warning

Most people who diarise renewals put a single entry on the expiry date itself.

That entry tells you something is happening today, at the point where the only available action is to pay whatever is asked.

A renewal you want to question, move, or cancel needs notice, and a card that needs updating needs it too.

So each renewal wants two entries, and the useful one is thirty days earlier.

What lead time each thing needs

The last is the one people get wrong. Moving a domain, a host, or an insurer takes weeks, and discovering on the renewal date that you wanted to move means paying for another year first.

Write what to check, not just what renews

Which is what makes the early entry useful rather than annoying.

An entry saying domain renewal, thirty days does nothing except create anxiety.

An entry saying check the card is current, confirm the contact address, and decide whether to keep the two spare domains is a task somebody can complete in ten minutes.

Write the checks into the calendar entry itself, at the moment you create it, while you still remember what they are.

Next year that entry is a working document rather than a reminder to think.

This is the difference between a diary that helps and one people dismiss.

Q1 is when they cluster

Which is worth knowing before January.

Businesses tend to have started things in January, so a disproportionate share of annual renewals land in the first quarter.

That means a single month can carry the domain, the hosting, the insurance, and three software subscriptions.

Knowing that in December lets you plan the cash rather than meeting it.

It also lets you spread things deliberately, since most renewals can be moved by renewing early for a partial period.

Two moved out of a crowded month is usually enough to make the quarter comfortable.

A cluster in one month is a cashflow problem you can largely solve with fifteen minutes of scheduling.

A worked example

A business listed everything renewing between January and March.

It came to eleven items, seven of them in February, totalling considerably more than they had expected in a single month.

They renewed two of the smaller ones early for eighteen months, which moved them permanently into August.

They also found the hosting renewal was on a card that expired in January, which would have failed.

The whole exercise took half an hour in the week before Christmas.

The card would have been discovered in February, after the site went down.

Do it before the break, not after

Which is the timing argument.

January is the busiest administrative month most small businesses have, and anything requiring calm attention loses to whatever is urgent.

The week before Christmas has slack in it, the information is all available, and nothing else is competing.

Half an hour now covers the whole quarter and means January contains no surprises at all from this category.

It is also the last moment before a supplier you might need to ask something goes away for two weeks.

Check the card and the address at the same time

Which is the pair of things that actually cause failures.

A renewal fails because a card expired or was replaced, and nobody hears about it because the notice goes to an address nobody reads.

Both are checkable in the same half hour you are listing the dates.

Confirm the card on file for each item, and confirm the notice address is one that more than a single person actually monitors.

Those two checks between them prevent almost every renewal failure there is.

Everything else on this page is scheduling and those two are the actual protection.

Put the list somewhere shared

Which is what makes it survive.

A renewal calendar in one person's account is a renewal calendar that stops working when that person is away or leaves.

Put the entries in a shared calendar and the list itself with the domain list and the supplier list.

Anybody covering should be able to see what is due, what to check, and who to contact.

That is the same argument as everything else this month and it applies most sharply here, since these have dates attached.

Note the price alongside the date

Which turns a reminder list into something you can make decisions from.

Writing what each renewal cost last year means that when the invoice arrives you can see immediately whether it has risen, which is the moment to question it rather than six months later.

Hosting, insurance, and software renewals in particular tend to rise quietly, and an increase of fifteen per cent on a routine item passes unnoticed unless there is a figure to compare against.

Total the column while you are there, since the annual cost of simply continuing to exist is a number most small businesses have never seen written down.

Next December that total tells you whether your fixed costs are growing faster than the business is.

The counter-case

Auto-renew handles most of this.

A business with everything on auto-renew and a current card will not miss anything, and the early entries mostly confirm that nothing needs doing.

Excessive diarising also produces entries people dismiss, which trains everybody to ignore the calendar.

And a business with three renewals does not need a system at all, only a note.

The threshold is somewhere around eight items, which is where remembering reliably stops working.

List everything due in Q1, add a thirty-day entry with the checks written in, confirm the cards and addresses, and put it somewhere shared.

The half hour

  1. List everything due in Q1.
  2. Note the amounts.
  3. Add an entry thirty days before.
  4. Write the checks in.
  5. Confirm every card.
  6. Confirm the notice addresses.
  7. Put it in a shared calendar.

Step four is what separates a calendar that works from one people dismiss, since an entry saying renewal in thirty days creates anxiety and one listing three checks creates a ten-minute task.

A prior version of this is at certificates and domains expiring in Q1.


Frequently asked questions

Why is a single calendar entry not enough?

Because an entry on the expiry date tells you something is happening today, when the only available action is to pay whatever is asked.

What lead times should I use?

Thirty days for domains and manual certificates, sixty for hosting and insurance, and ninety for anything you might want to move.

What should the entry say?

The checks, not just the fact of the renewal. Check the card is current, confirm the contact address, decide whether to keep the spares.

Why does Q1 cluster?

Because businesses tend to have started things in January, so a disproportionate share of annual renewals land in the first quarter, sometimes in one month.

Can I spread them out?

Yes. Most renewals can be moved by renewing early for a partial period, which turns a cashflow cluster into a scheduling decision.

Why do it before the break?

Because January is the busiest administrative month and anything requiring calm attention loses to whatever is urgent.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Renewals diarised on the day they fall?

Add a second entry thirty days earlier with the checks written into it. That is the one that works.

Start a Conversation