Domains held by clubs and charities

A club is a strange kind of owner. It outlives every individual in it, yet it acts through people who serve for a few years and then step back. Anything the club holds has to survive that turnover, and most of the things it holds already do: the bank mandate is changed at the annual meeting, the keys to the clubhouse are passed on, the insurance is renewed in the organisation's name. The domain is the exception. It tends to sit in a personal account belonging to whoever set it up, invisible until the moment it fails.

Fixing that is less about technology than about arrangement. The name has to be registered to the organisation rather than to a member. The account that controls it needs more than one route back in, so that a forgotten password or an unreachable mailbox does not become a crisis. The renewal has to be a recurring item that a treasurer inherits along with the accounts, not a card detail known to one person. And somebody has to write down, in a form a successor can read, where the name lives and who to contact about it.

The pages here take those questions one at a time. They begin at the start of the story, with choosing a name a village foundation can spell over the phone, print on a shirt and read aloud at a meeting without ambiguity. They cover what .org actually signals, and what a charity or foundation should hold in its own right rather than leaving with a supplier. They then move to the running of it: shared access without a password on a sticky note, renewals that survive a change of officers, and the consequences of putting the account in the hands of the chair, the webmaster or the agency.

Everything here assumes the mechanics are already roughly understood. Groups coming to this cold will find the vocabulary explained in the basics section, and the question of who the registrar actually listens to in who owns a domain. The checklists in the notes section condense the practical steps into something that can be printed and taken to a meeting.