Put every expiring thing on one calendar
7 min read
By Lumina Software
- Reliability
- Operations
- Service business
- Small business
Most software outages at small businesses are not caused by bugs. They are caused by something that quietly ran out. A domain registration lapsed. A security certificate expired and every browser started showing a warning. A card on file was replaced, so the phone provider's invoice failed and the main line went dark. A password on a shared account hit its forced reset date and the scheduling sync stopped.
None of these are hard problems. Each one had a known date, often printed in an email months earlier. The trouble is that the dates live in a dozen different inboxes and dashboards, and nobody is looking at all of them at once.
This post covers how to put every expiring thing a business depends on into one calendar, with an owner and enough warning to act.
Why expiry failures hurt more than they should
A bug usually shows up while someone is working on the system. An expiry shows up on its own schedule, often on a weekend or a holiday, and often years after the person who set it up has moved on.
They also tend to fail all at once. When a domain lapses, the website goes down, but so does email on that domain, the links in every confirmation text, and any integration that calls back to a web address on it. When the card behind the phone service is declined, the phone agent, the call forwarding, and the text confirmations can all stop together.
And the fix is rarely instant. Renewing a domain after it lapses can take time to take effect. Updating a certificate may need someone with access to the hosting account. Restoring a suspended phone account may need a call to the vendor during business hours. A two minute renewal done a month early turns into a half day of scrambling when it is done a day late.
Make the list
Start by writing down everything with an end date or a renewal date. Most businesses are surprised by how long this list gets. Look in these places:
- Domains. Every domain the business owns, including old ones that still redirect, and who the registrar is.
- Certificates. The security certificates on the website, booking pages, and any custom portals. Many hosts renew these on their own, but only if the settings and payment behind them stay valid.
- Cards on file. Every vendor that charges a card automatically. When a card is replaced or expires, each of those charges can fail.
- Subscriptions and plans. Phone service, scheduling, the job system, the messaging provider, email, file storage, and any software with an annual term.
- Access keys and tokens. The keys that let one system talk to another. Some of these are set to expire after a fixed period, and the integration stops when they do.
- Contracts and trials. Free trials that convert to paid, annual contracts with auto renewal clauses, and promotional pricing that ends.
- Licenses and registrations. Business filings, trade licenses, and insurance policies that a vendor or customer might ask to see.
For each item, write down what it is, the date it ends, what breaks if it ends, who can renew it, and where the renewal happens. That last field matters more than it looks. "Renew at the registrar" is not useful if nobody remembers which registrar or whose login it uses.
Put it on one calendar, with warning
Once the list exists, every date goes on one shared calendar. Not a reminder in someone's personal phone and not a note in a spreadsheet nobody opens. A calendar the owner and office manager both see.
Each item gets more than one reminder. A good default is:
- Sixty days before for anything that needs a decision, like a contract renewal or a price change.
- Thirty days before for routine renewals, so there is time to fix a failed payment.
- Seven days before as a final check that the renewal actually went through.
The seven day check is the one people skip, and it is the one that catches problems. Auto renewal is supposed to handle things, but it fails for ordinary reasons: the card changed, the account owner left, the vendor changed its billing system. Checking that the new end date really moved forward takes a minute and avoids most surprises.
Give every item an owner
A calendar entry with no name on it is a reminder for nobody. Each item should name one person responsible for making sure it gets renewed or deliberately cancelled.
The owner does not have to be the person with the login. In a lot of small businesses, the owner holds the card and the office manager tracks the dates. That works fine as long as both names are written down and both people know which part is theirs.
When someone leaves the business or changes roles, their items get reassigned the same week. This is the moment expiries most often fall through. The person who set up the domain five years ago is gone, the renewal email goes to an inbox nobody reads, and the first sign of trouble is a customer saying the website is down.
It helps to move renewal notices to a shared address instead of a personal one. A mailbox like billing@ or admin@ that two people can read means a renewal warning still lands somewhere when one of them is out.
Watch for the ones that fail silently
Some expiries announce themselves loudly. A lapsed website is noticed within the hour. Others fail quietly and can go unnoticed for days.
An expired access key between the booking system and the job system may not show any error to the caller. The phone agent might still take the call and say goodbye politely, while the booking never reaches the schedule. A failed payment on the messaging provider might stop confirmation texts without stopping anything else.
For these, a calendar reminder is not enough on its own. Pair it with a simple check that the connection is still working. That can be as basic as a daily test booking that someone confirms landed, or an alert when no confirmation texts have gone out during business hours. If the system has stopped doing its job, someone should hear about it before a customer does.
Clean up what you no longer need
Making the list usually turns up things the business is still paying for and no longer uses. An old domain from a previous name. A trial that converted to paid two years ago. A second scheduling tool that was replaced but never cancelled.
Each of these is a small cost, but they are also small risks. An unused account still holds customer data, still has logins that could be misused, and still sends renewal emails that bury the ones that matter. When an item has no reason to exist, cancel it on purpose, write down that it was cancelled, and take it off the calendar.
Be careful with domains in particular. A domain that once received email or appeared in printed materials can still get traffic years later. Letting it lapse means someone else can register it. If it was ever used publicly, it is often worth keeping it and pointing it at the main site.
Review the list twice a year
Systems change. A new vendor gets added, a card gets replaced, a contract term changes. Set a recurring calendar entry every six months to walk through the whole list with the owner.
The review takes less than an hour. For each item, confirm the date is still right, the owner is still the right person, and the renewal path still works. Add anything new and remove anything that was cancelled. If a renewal has failed in the last six months, note why and fix the cause, whether that was an old card, a dead inbox, or a missing login.
The short version
Most outages that look like technical failures are really a date that nobody was watching. List everything the business depends on that expires or renews: domains, certificates, cards on file, subscriptions, access keys, contracts, and licenses. Write down what breaks, who renews it, and where. Put every date on one shared calendar with reminders at sixty, thirty, and seven days. Give each item a named owner and reassign it when people leave. Add a working check for the connections that fail quietly. Cancel what you no longer use, and review the whole list twice a year.
Written by Lumina Software. Have a question? Book a call