Most committees think about the website when they inherit one. The handover checklist covers what to ask for when you are the person arriving. This is the same problem from the other side: what to leave behind so the next secretary, treasurer or chair does not have to reconstruct it from guesswork.

What good handover looks like

A clear handover means the next person can find the domain, get into the registrar account, edit the site, and see who has access to what, without waiting on anyone's memory. It does not need to be elaborate. It needs to exist somewhere other than one person's head.

• The domain name and where it is registered
• The registrar login: username, password, and the email address the account is tied to
• Who currently has editing access to the site, and how
• Where the content lives (the platform or system it was built on)
• Any subscriptions or renewals tied to the site, and when they fall due

Why this is worth doing before you are asked

Committees change on their own schedule, often at an AGM, and the person who knows how the website works is rarely still in post by the time someone needs that knowledge again. Writing it down while you have it removes the guesswork for whoever comes next, and it means the site does not quietly stop being updated because nobody knew where to log in.

The same problem, seen from the point of view of someone arriving cold, is covered in what happens to a club website when the person who made it leaves. If your governing document says anything about who is responsible for the club's digital assets, that is worth checking too: see what your constitution or governing document probably says about digital assets.

A club's committee changes every year or two, but the website usually only gets attention when someone is already on their way out. By then the person who knows the registrar login is already distracted, and whoever takes over is starting from nothing. The problem repeats itself because nothing about the last handover was written down anywhere the next committee could find it.

Succession is the pattern behind most of this: officers change, but the digital side of the club rarely changes with them in any planned way. Treating it as a one-off task for whoever is leaving guarantees it gets done badly, if at all, because leaving is exactly when people have the least time and the least patience for writing things down.

Building it into the calendar

The fix is ordinary. Put website handover on the agenda every year, so it becomes a routine item.

• Add a standing item to the AGM agenda: who currently holds registrar and hosting access, and whether that needs to change.
• Check the governing document for any reference to digital assets, and update it if it says nothing about them.
• Ask the outgoing officer for the details set out in the handover checklist, before they stop being reachable.

None of this takes long once it is a fixed part of the year. It takes far longer to reconstruct after the fact, which is the state most committees find themselves in when they first look this up.

What your governing document probably says, or should say, about who holds these responsibilities is covered on its own: What your constitution or governing document probably says about digital assets. What to actually collect from a departing officer is set out in full at What to get from whoever is leaving, before they stop answering emails.