The Keys, the Login and the Little Black Book: Auditing Your Network Before the Chair Goes

There’s a particular moment at a November committee meeting when someone says, “I’ll be standing down in March,” and the room goes quiet for half a second too long. Everyone nods. Everyone says the right things. And then everyone quietly hopes the chair has a spreadsheet somewhere with all the important bits on it.

Usually, they don’t. What they have is a head full of names, a phone with the group chat, a drawer with the bank paying-in book, and a vague memory of which council officer actually answers emails. That’s not a criticism. It’s how most local business networks survive — on one person’s goodwill and working knowledge. But it’s also how they disappear.

Succession planning sounds like something you’d find in a policy folder. In practice, it’s the difference between a forum that hands over the keys and one that changes the locks by accident. If your chair, treasurer or secretary is leaving in the spring, the work starts now — not at the AGM.

The network isn’t the meetings. It’s the memory.

Most members see the monthly breakfast, the occasional speaker, the Christmas drinks. What they don’t see is the invisible scaffolding: the venue booking that relies on a favour, the council contact who takes your call because they know the chair’s first name, the sponsor who renews because someone remembered to ask in September.

That scaffolding is the network’s memory. And memory is exactly what walks out of the door when a long-serving volunteer steps down.

A handover audit isn’t about creating bureaucracy. It’s about making the invisible visible while the person who knows it is still in the room. Think of it as a stocktake, not a resignation letter.

Start with the four keys

Every local network runs on four kinds of access. If you map these before March, you’ll catch most of the risk.

Relationships. Who does the chair actually talk to? Not the mailing list — the real people. The council’s economic development officer. The venue manager who waives the room hire deposit. The local journalist who runs the new business round-up. The bank manager. The sponsor who pays for the mince pies. Write the names down, with a note on what each relationship is for.

Logins. This is the boring bit that sinks networks. Who controls the email account? The website domain? The social media pages? The WhatsApp group admin? The online banking? The mailing list platform? If the answer is “the chair’s personal email,” you’ve found a problem. Get access transferred to a shared, role-based account before the leaving do, not after.

Money. Bank mandate signatories, the treasurer’s handover, the year-end accounts, any petty cash, the insurance renewal date, the room deposit held by the venue. A departing chair doesn’t need to be a finance expert, but they do need to show the next person where the numbers live.

Rhythm. What happens when? The AGM, the membership renewals, the summer social, the budget setting, the council consultation deadlines. A simple twelve-month calendar is worth more than a folder of old minutes.

The handover meeting that actually works

Don’t ask for a handover document. Build one together, in a room, with a laptop open and a deadline. Two sessions of ninety minutes will do more than six months of “we must sort that out.”

First session: the map. The chair talks, the successor types. Names, access, dates, quirks. Who returns calls. Which venue needs a deposit. Why the December meeting never gets a quorum. This is the unwritten rulebook — capture it while it’s still fresh.

Second session: the introductions. This is the part most handovers skip. A list of contacts is not a relationship. The chair should personally introduce the successor to the council officer, the venue manager, the bank contact and the main sponsor. A short email copied to both people is enough: “This is [name], who’s taking over from me in March. They’ll be your point of contact from now on.” That one sentence stops a lot of future silence.

Don’t forget the awkward bits

Handovers often stall on the things nobody wants to mention. The bank mandate needs paper signatures and time. The insurance policy needs the new committee names. The website domain renewal might be sitting in someone’s personal account. The WhatsApp group might have three admins, two of whom left years ago.

And then there’s data. If your network holds a membership list, you’ve got responsibilities under UK GDPR. The incoming committee needs to know where the list lives, who has access, and what the privacy notice says. That’s not red tape for its own sake — it’s the difference between a clean handover and a messy inbox full of subject access requests.

The one-page test

Here’s a simple check: could a new chair run next month’s meeting using only one side of A4? Not perfectly, but well enough to keep the lights on. If the answer is no, the audit isn’t finished.

The one-pager should list the current committee, the bank signatories, the key contacts, the login owner, the next three events, and the one thing that absolutely must happen before the AGM. Keep it somewhere shared, not in a drawer.

Succession is a favour to your future self

A departing chair often feels guilty about leaving. The best way to ease that guilt is not a lavish leaving gift — it’s a clean handover. Knowing the network won’t collapse in April is worth more than a engraved tankard.

And for the incoming chair, the audit is a gift too. They inherit a map instead of a mystery. They know which council officer to ring, which sponsor to thank, and which login belongs to the group rather than to a person who’s moved to Devon.

Local business networks are fragile things. They run on favours, memory and a bit of goodwill. A handover audit doesn’t make them corporate. It makes them last. And with AGM season coming into view, there’s no better time to ask the quiet question: who actually has the keys?