Keeping renewals from lapsing
Almost every lost club domain was lost by accident. The renewal was nobody's job, the reminder went to a mailbox nobody opened, and the card on file had already expired.
* * *
A domain renewal is a small administrative task that arrives once a year, or once every few years, and belongs to nobody in particular. It is not big enough to appear on an agenda, not frequent enough to become a habit, and not visible enough to be missed until the site goes dark. That combination is why lapses cluster in volunteer organisations rather than in businesses, where somebody is paid to notice.
The task with no owner
In a club, the domain is usually renewed by whoever set it up. That person may be a former secretary, a member who used to do the website, or somebody's relative. The role that person occupied has been handed on several times since, but the renewal has not, because it never appeared in any description of the role. The first repair is therefore not technical: it is deciding, in a meeting, which office holds the domain, and writing that into the description of the office rather than the name of the person currently filling it.
The treasurer is the usual choice, because renewal is a payment and treasurers already track recurring payments. The secretary is a reasonable alternative where the treasurer changes more often. What matters less is which office, and more that the answer is recorded somewhere the next committee will find it, which is one reason a written handover list exists at all.
Cards expire faster than domains
The most common single cause of an unintended lapse is a payment card that no longer works. Cards are reissued every few years, treasurers change more often than that, and a card registered against an account belonging to a person who has left cannot be updated by anyone still in the club. Automatic renewal then fails silently: the registrar attempts the charge, the charge is declined, a notice goes to an address nobody reads, and the name enters the sequence described in what happens after a domain expires.
Paying from an account the organisation controls, whether that is a club debit card, a direct debit from the club account or a prepaid balance held at the registrar, removes the dependency on one person's bank. It also means the payment appears in the club's own records, where the next treasurer will see it.
Reminders that reach more than one person
Registrars are required to send renewal notices before expiry and again afterwards, and those notices go to the address on the account. If that address is one person's mailbox, the reminder system has a single point of failure. Two changes fix it: set the account contact to a shared address that at least two officers can open, and add the renewal date to whatever calendar the committee actually uses, with a reminder well before the date rather than on it.
A second reminder set a month earlier gives room to fix a failed payment before anything breaks. A note in the annual cycle of the club, next to insurance renewal and the affiliation fee, is better still, because it is reviewed by the whole committee rather than by one person.
Automatic renewal is a safety net, not a plan
Switching automatic renewal on is worth doing, and it is not sufficient on its own. It depends on a working payment method, an account nobody has locked themselves out of, and a registrar that can reach somebody if the charge fails. It also renews names the group no longer wants, which is a smaller problem but a real one. The sensible arrangement is automatic renewal switched on as a backstop, with a human check once a year that the payment method is current and the contact address still reaches a living person.
Registering for several years at once reduces the number of occasions on which the process can fail, and moves the risk rather than removing it: a name registered for a long period will come up for renewal under a committee that has never thought about it. Longer registration works best combined with a written record, so the future committee inherits a date rather than a surprise. The mechanics of the cycle itself are set out in renewals and expiry.
A renewal that depends on one person's card, one person's mailbox and one person's memory has three ways to fail. Removing any one of them is worth an evening's work.
The month after an officer resigns
Resignations are when domains are lost, because the departing officer's mailbox is closed, the card is cancelled and the login is forgotten in the same fortnight. A standing item in the handover, checking that the domain contact address and payment method have been changed, catches it. So does a simple annual audit: sign in to the registrar account, confirm the expiry date, confirm the payment method, confirm who has access, and note the answers in the minutes. Deciding in advance whose account it should be at all is covered in who should hold the account.