Who should inherit the renewal calendar when the person who built it leaves the company?
Renewals tend to belong to whoever set them up years ago, not to a role. Here is how to move that responsibility before a departure turns into a lapsed domain or a suspended account.

Why renewals are the classic orphaned responsibility
In most small companies, renewals are owned by habit rather than by role. The person who registered the domain in the early days keeps getting the emails. The engineer who bought the certificate is the one the certificate authority knows. The office manager who signed up for the phone system is the billing contact. None of that is written down anywhere, and it works right up to the day one of those people resigns. Related: Never Lose a Domain Again: A Simple System
The departure itself is what breaks the chain. IT disables the mailbox on the last day, so vendor notices start bouncing. If the company forwards the old mailbox, the forward usually expires after a month or two, which is shorter than most annual renewal cycles. Worse, the payment method on file is sometimes a personal card that gets cancelled, or a corporate card issued to that person that is closed on exit. Nothing fails immediately. It fails eight months later, on a Saturday, with no obvious connection to the person who left.
Keep reading: The Hidden Cost of a Missed Renewal, Never Lose a Domain Again: A Simple System, SSL Certificate Expiry and How to Stay Ahead. See how LatePinger helps you expiry reminders for domains, ssl, and renewals.
Pick a role, not a hero
The new owner should be a function with a named primary and a named backup, rather than a single enthusiastic person. In a company under fifty people, finance operations or IT usually fits best. Finance already reconciles the card statements and can spot a renewal charge that did not post. IT already manages accounts and offboarding. The office manager is a reasonable third choice in a company with no IT function. Whoever it is needs payment authority or a direct path to it, and should be in the tools weekly rather than once a year. Related: How to Build a Single Calendar for All Your Expiries
Write the assignment down in an ownership register: one row per renewable item with the vendor, what it protects, the account email, the payment method, the expiry date, the primary owner, and the backup. This register is not the reminder system. It is the document that says who is responsible, so that when the reminder fires, nobody has to guess whose job it is. Review it whenever someone in the register changes roles, not just when they leave.
The handover checklist for the last two weeks
Start with an export of every account the departing person holds that has a renewal attached. Pull it from their password manager vault, their inbox search for words like renewal, invoice, and expires, and the last year of card statements. For each account, transfer ownership properly instead of sharing the password: most registrars, certificate authorities, and software vendors have an owner or admin transfer flow. Then rotate the password, move two-factor authentication to a method the team controls, and change the account email to the role address. Related: SSL Certificate Expiry and How to Stay Ahead
Next, move every payment method off cards tied to the individual and onto a company card that finance controls. Confirm at each vendor that the new email is receiving notices by triggering a test message or invoice copy. Keep the old mailbox as a forwarding alias to the role address for as long as company policy allows, ideally a full year, to catch anything the export missed. Finally, ask the departing person to write down the weird ones: the domain registered at a registrar nobody else uses, the trade show booth deposit, the annual data feed that is invoiced by a person rather than a portal.
Keeping it from happening again
The structural fix is to stop letting renewals live in inboxes. Every item in the ownership register should also live in a shared reminder system that notifies at least two people at each lead time. LatePinger was built for exactly this, but a shared calendar with multiple attendees is a fine starting point. The requirement is that no single mailbox is the only place a reminder lands.
Then make the handover automatic by adding a renewal ownership line to the offboarding checklist that HR or the manager runs for every departure. The line should point at the ownership register and require the manager to reassign every row before the last day. Twice a year, run the simple test: pick any person in the company, imagine they took a month off with no notice, and ask which renewal would be missed. If the answer is anything other than none, fix that row. Related: The Hidden Cost of a Missed Renewal
- Renewals usually belong to whoever set them up, and that ownership evaporates on their last day.
- Assign a function such as finance operations or IT, with a named primary and a named backup.
- Transfer account ownership, rotate credentials, move payment cards, and change contact emails before the person leaves.
- Put renewal ownership on the offboarding checklist and test it twice a year.
Never miss a renewal that matters
Expiry reminders for domains, SSL, and renewals. LatePinger is built to help you put this into practice.
Track a renewalMore from the LatePinger blog

The Hidden Cost of a Missed Renewal

Never Lose a Domain Again: A Simple System

SSL Certificate Expiry and How to Stay Ahead
Get the LatePinger playbook
Practical guides on expiry reminders, straight to your inbox as we publish them. No spam, unsubscribe any time.
