Build one register of everything with an expiry date, including your payment card, and check it in December. An expired card silently fails every automatic renewal at once.

Why they cluster

Things bought when a business started, or when a site was built, or when somebody did a tidy-up in January, all renew on their anniversary.

Since those events cluster at the start of a year, so do the renewals.

Which puts a group of expiry dates in the first quarter, arriving during the period when attention is lowest: people are away, the holiday backlog is being cleared, and nobody is reading renewal notices.

The result is that the least-watched weeks of the year contain the most expiries, which is a bad combination and an entirely predictable one.

The payment card is the sleeper

The item that turns several small renewals into one simultaneous failure, and it is almost never on anybody's list.

Business cards expire, usually at the end of a month, and a replacement arrives with a new number and a new expiry date.

Every automatic renewal charged to that card then fails at once, silently, over the following weeks: the domain, the certificate, the hosting, the mailing platform, and whatever else was set up years ago.

Some of those retry and email you. Some simply lapse.

Check your card's expiry date now, and if it falls in the next six months, list everything charged to it and update the card everywhere before it changes rather than afterwards.

What has an expiry date

The sixth is the one that costs most reputationally, since an expired accreditation displayed on a website is a claim you are no longer entitled to make.

One register, not several reminders

The structure that works, and it is deliberately simple.

A single list with four columns: what it is, when it expires, what it costs, and who is responsible.

Kept somewhere the business owns rather than in one person's calendar, since the person with the reminders is the person who will be away in January.

Reviewed once in December, when you can see the whole first quarter at once, rather than reacted to as notices arrive.

Individual reminders scattered across calendars and inboxes are what most businesses have, and they fail in exactly the way this article describes.

A worked example

A business had automatic renewal enabled on everything and considered the question settled.

Their company card was replaced in early February, as scheduled, and the new details were updated for the bank and the accounting software.

Over the following seven weeks four things failed quietly: a mailing platform that suspended the account, a monitoring service nobody noticed had stopped, a backup subscription, and a domain used for a secondary site.

The domain was the one that mattered, and it was recovered during its grace period after somebody happened to notice the site was down.

They built a register the following December, with the card expiry as the first line.

The owner's remark was that automatic renewal had felt like the solution and had actually been the reason nobody was watching.

Automatic renewal is not the answer on its own

Worth stating because it is the usual response to everything above.

Automatic renewal fails when the card expires, when the card is replaced after fraud, when the billing address changes, when a bank blocks an unfamiliar recurring charge, and when the account it bills to has been closed.

It also renews things you meant to cancel, which is the opposite failure and equally common.

Enable it, because it prevents the most likely lapse, and do not treat it as the whole system.

The register is what catches the cases automatic renewal cannot.

Certificates behave differently

A short note, because they are the most likely thing to fail and the least understood.

Many are now issued for short periods and renewed automatically by the host, which works well until the automation breaks and nobody has been checking.

A failure is immediately visible to every visitor as a warning, which is a considerably more damaging failure than most.

Put the expiry date in the register regardless of whether it renews automatically, and check the live site rather than the configuration.

Doing that in mid-December is sensible, because a certificate expiring over the holiday period is the version of this that costs the most.

Diarise the check, not the dates

A small distinction that makes the register survive.

Individual date reminders proliferate, get ignored, and stop being useful once there are twenty of them.

One recurring entry in early December, to review the register and the coming quarter, is a single habit rather than twenty interruptions.

Add a second in June for the same reason, which catches anything that moved.

Give it a named owner and note a deputy, since the whole failure mode described here is one person being unavailable in January.

The counter-case

This can become administration for its own sake.

A sole trader with a domain, a hosting plan, and a certificate that renews itself does not need a register, and building one is process replacing judgement.

The threshold is roughly whether you could list everything with an expiry date from memory. If you can, keep doing that.

There is also a risk in over-investing in the register while ignoring the thing it is meant to protect: a business with an immaculate list and no backups has the priorities inverted.

Build it when the list has outgrown memory, keep it to four columns, and spend the remaining attention on the things that would actually stop the business.

The December check

  1. Check your payment card's expiry date first.
  2. List everything charged to it.
  3. Build one register with four columns.
  4. Include insurance, memberships and accreditations.
  5. Look at the whole first quarter at once.
  6. Check the certificate on the live site.
  7. Diarise the review, not each individual date.

Step one takes ten seconds and is the single most likely cause of several things failing at the same time.

Notices going to an address nobody reads are covered in renewal notice to a dead address.

Frequently asked questions

Why do so many things expire in the first quarter?

Because they were bought when the business started or the site was built, and those events cluster at the start of a year. Renewals land when attention is lowest.

What is the most overlooked expiry?

The payment card. When it is replaced, every automatic renewal charged to it fails at once, silently, over the following weeks. Some retry and some simply lapse.

What should the register contain?

Four columns: what it is, when it expires, what it costs, and who is responsible. Kept somewhere the business owns rather than in one person's calendar.

Is automatic renewal enough?

No. It fails when a card expires or is replaced, when a bank blocks a charge, or when the billing account is closed. It also renews things you meant to cancel.

Why check certificates separately?

Because a failure is immediately visible to every visitor as a warning. Many renew automatically until the automation breaks, so check the live site rather than the configuration.

Do I need a register at all?

Only once the list has outgrown memory. A sole trader with a domain, hosting, and a self-renewing certificate does not need one.

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.

Everything on automatic renewal?

Check when your payment card expires. That one date decides whether several things fail at once in February.

Start a Conversation