Small Institutions

Handing a Group Over to a New Leader: What to Transfer, and in What Order

Kingsdale Saturday School in Bradford teaches 132 pupils in six classes on a Saturday morning. When its administrator of nine years moved away in July 2025, the school kept every teacher and lost almost every record: the parent contact list was in her personal phone, the consent forms were in a box in her spare room, and the register was a spreadsheet on a laptop nobody else had ever opened. It took her successor 41 days to be able to answer a question the school had been able to answer instantly the week before, which was who is in Year 4 and how do I reach their parents.

Published 12 June 20267 min readSmall Institutions

TL;DR

A handover is a transfer of access, not a document. Move things in this order: the member roster with contacts and consents, then accounts and admin rights, then the calendar of dated obligations, then the money trail, then two shadowed sessions, then the announcement to members. Give the successor their own login rather than a copied file or a shared password, and set a date on which the outgoing leader's access ends. Keep the overlap short and bounded, because a leader who stays on indefinitely to help leaves the group with two leaders and no clear one. In Bitir the roster, records, attendance history and channels belong to the group, so handing over a role is a change of permissions rather than six weeks of reconstruction.

What actually goes missing when a group leader leaves?

Not the skill. The skill is usually replaceable, and often the successor has been in the room for years.

What goes missing is the private layer: the phone numbers, the two families who pay in instalments, the child whose asthma inhaler lives in the kit bag, the caretaker's mobile number for when the hall is locked, the fact that the Tuesday booking has to be re-confirmed with the council every January. None of it is secret. All of it lived in one head and one phone.

Groups notice this in a specific order. Contact details go first, within days. Consents and medical notes go next, usually the first time something happens that needs them. Dated obligations go last and hurt most, because a missed insurance renewal or a competition entry deadline is discovered after it has passed.

Leaders we speak to describe the same moment: "We didn't realise she was the system until she'd gone." That is the whole problem in one sentence. A group with 40 members and one leader who holds everything is a group that has quietly made itself fragile, and no amount of goodwill at the leaving do fixes it.

What should be transferred, and in what order?

Order matters, because handovers run out of time. Do these in sequence and a truncated handover still leaves the group functioning.

  1. The roster. Members, contact details, emergency contacts, consents, medical notes, and who is a junior. Do this before the leaving date is even agreed. Our guide to member records, contact details, medical notes and consent covers what belongs in the record and what does not.
  2. Access, not files. The successor gets their own account with admin rights on every system the group uses, and the outgoing leader's access is removed on a stated date. Copying a spreadsheet is not a handover; it is a second copy of a record that will immediately start to diverge.
  3. The calendar of obligations. Hall bookings and their renewal dates, competition or exam entry deadlines, insurance, safeguarding and first-aid certificate expiry, funder reporting dates, and anything already promised to members.
  4. The money trail. Who has paid, who has not, what the venue costs and when it is invoiced, and every informal concession. The quiet arrangement where one family pays half is the thing that most often gets lost and most embarrasses everyone when it does.
  5. Two shadowed sessions. The successor runs them; the outgoing leader stands at the back and answers questions when asked.
  6. The announcement. Named successor, effective date, what is not changing, who to contact about what.

One thing to leave out: a long written pack. A handover document that takes two evenings to write is read once, becomes wrong within a term, and gives everyone false confidence that the transfer has happened. Write a page of dates and contacts, then spend the rest of that time in the room together.

How long should the overlap be, and who is in charge during it?

Two sessions of shadowing, a named end date, and one person in charge from day one.

This is where we take a firmer line than most club constitutions. The comfortable arrangement, where the outgoing leader stays on for a few months to help while the new one finds their feet, is the one that reliably goes wrong. Members keep asking the old leader because that is who they know, the new leader ends up running a group they cannot actually change, and by the time the old leader really leaves the group has had two thin transitions instead of one clean one. Six weeks is a generous outer limit. Two sessions is usually enough.

Consider Nadia Okonkwo, who took over an after-school coding club of 22 children in Nottingham from its founder. They agreed a fortnight: Nadia led both sessions, the founder sat at the side with a notebook, and every question a parent brought to the founder was answered with "ask Nadia, she runs it now". By the third week the founder was not there and nobody rang her. Compare that with the same club's previous handover, which ran informally for a term and ended with a committee meeting about who was actually responsible for the risk assessment.

The exception worth making is for a seasonal group. If a leader leaves in March and the club's main event is in June, the outgoing leader can reasonably stay as a named helper for that one event, with the scope written down.

Who owns the group's data when the leader is a volunteer?

The group does, even when the only copy is on a volunteer's personal phone.

This is not a technicality. Under UK data protection law the organisation deciding why and how member data is used is the controller, and the ICO's guidance for small organisations is clear that clubs, charities and small institutions carry those duties in the same way larger bodies do. If your only record of who is in the group sits in a personal account, the group cannot reliably correct it, delete it, or produce it when a parent asks what is held about their child. Registered charities have the parallel governance duty of keeping proper records, set out in the Charity Commission's guidance on what is involved in being a charity trustee.

Practically, that means one decision: hold member records in a system the group controls, and give leaders access to it. Then a change of leader is a permission change on a Tuesday evening, and a leaver who stops replying to messages is an inconvenience rather than an incident.

It also means being honest about the group WhatsApp. A chat created from a personal number is owned by that number, and the history of the group's decisions goes with it. Groups that keep their communication in a shared channel with owned roles avoid the awkward conversation where a departing leader is asked to hand over a chat they created.

How should you tell members that the leader is changing?

Once, in writing, on the channel they already use, before the last session rather than after it.

Include four things: the successor's name, the date it takes effect, what is not changing (the time, the venue, the fees), and who to contact about what afterwards. That last item does more work than people expect. A parent who does not know whether to ask about a payment or an absence is a parent who asks the person they already know, which is exactly the habit the announcement is trying to break.

Say something warm about the outgoing leader, and keep it to two lines. A long tribute in the same message dilutes the practical content, and the group will want its own way of marking the departure anyway.

If your group runs on a rota of volunteers rather than a single leader, the same principles apply per role rather than per person, which is the pattern described in our guide to volunteer rota management for community groups. Roles that are named and visible survive their holders; roles that exist only as "whoever does the kit" do not.

What does a handover look like when the group already runs in one place?

Short, and mostly clicking.

When the roster, attendance history, records, assignments and announcements already sit in the group's own space, the handover is: create the successor's account, give them the manager role, walk them through two sessions, remove the old access, post the announcement. The material transfer is minutes rather than weeks. In Bitir the capabilities behind that role are explicit, so a group can hand over the ability to run sessions and see member records without also handing over billing or the power to delete the channel, and our guide to roles in a coaching group sets out how leaders, helpers and members differ.

There is a second benefit that only shows up later. The successor inherits history, not just contacts: who attended what, which assignments were set, what was announced in March. A new leader who can read the last two terms rather than being told about them arrives with context, and members notice within about a fortnight.

Questions organisers ask

What should be handed over first when a group leader leaves?

The member roster: names, contact details, emergency contacts, consents and medical notes. Everything else in a handover can be rebuilt from public information or asked about later, but a contact list that lived in one person's phone leaves with that phone. Transfer it before the leaving date is agreed, not in the final week.

How long should a leadership handover overlap be?

Two full sessions of shadowing with a hard end date, not an open-ended period of the old leader helping out. Two sessions is long enough for the successor to hit the ordinary problems while the outgoing leader is still in the room, and short enough that members learn quickly who is actually in charge. Anything past about six weeks tends to leave the group with two leaders and no clear one.

Who owns a group's member data when the leader is a volunteer?

The group does, not the volunteer, even when the list only exists in the volunteer's personal phone. That arrangement is a problem for the group rather than for the leaver: the group has no reliable way to correct, delete or produce the data on request. Hold member records in a system the group controls and give leaders access to it, so a change of leader is a change of permissions rather than a data recovery exercise.

How do you announce a change of leader to members?

One message on the channel the group already uses, naming the successor, the date the change takes effect, what is not changing, and who to contact about what afterwards. Send it before the last session rather than after, so members can say goodbye and the new leader arrives to a group that already knows their name. Do not leave it to word of mouth at the door.

What usually goes wrong in a club or class handover?

The predictable failures are a roster that only ever existed on a personal device, consent forms in a box at the leaver's house, dated obligations nobody else knew about such as a competition entry or an insurance renewal, and a shared password that means access can never be cleanly removed. Each is avoided by holding records where the group controls them and by handing over accounts rather than copies.

Make the next handover a permission change

Keep the roster, records, attendance history and announcements in a space the group owns, give each leader their own role, and hand a group over in an evening instead of a term.

Set Up Your Group