Club Sports Officer Transition & Handoff

Every club sports officer eventually graduates, studies abroad, or just decides not to run again, and every club sports team has, at some point, lost something in that handoff: an admin password nobody wrote down, a contact list that lived in one person's phone, a login that stopped working the semester after the person who set it up left.

Money gets its own guide. See club sports treasurer responsibilities for that handoff specifically. This is about everything else: who has access, who's actually in charge, and what a clean transition for a president, captain, or any other officer role actually requires.

Decide the role, then grant exactly that

The instinct in a rushed handoff is to give the incoming officer "whatever the old one had." Resist it. Decide what the role actually needs (full staff access, or something narrower) and grant that, not a copy of whatever accumulated permissions the outgoing person happened to have picked up over two years.

There are two different situations here, and they call for different actions:

Someone brand new to the club, stepping into a leadership role, a sophomore who just got voted in and was never on the roster in an officer capacity, needs an invite with the right role attached from day one.

Someone already on the roster, getting promoted, last year's officer becoming this year's president, doesn't need a new invite at all. Their existing account should just have its role changed. Don't create a second account for someone who already has one; it fragments their history and usually confuses the export six months later when there are two rows for the same person.

Ownership is the one role worth being deliberate about

Most role changes are reversible: you can demote an officer back to player if it doesn't work out. Ownership is different, because a handful of genuinely irreversible actions are usually restricted to the owner specifically, not to "any staff member": revoking a pending invite, changing several people's roles at once, and viewing the team's own audit history are typical examples.

There is usually no single "transfer ownership" button, and that's not an oversight; it reflects a real fact about how the handoff actually goes. The functional equivalent is: the current owner promotes the incoming person to owner as well. For a period, the team genuinely has two owners. The outgoing owner then steps back to a lower role, or leaves the team entirely, once they're confident the new owner is set up correctly. This is safer than a single instantaneous swap: it gives you a window where either person can fix a mistake, instead of a hard cutover with no fallback.

One safety rail worth knowing about in advance: a sole owner is often blocked from deleting their own account until they've promoted someone else first. If you're a graduating senior and the sole owner of your club's account, that's the moment this becomes relevant: do it during the handoff, not as a surprise the week you're trying to leave.

What stays with the team when a person leaves

The reassuring part of a well-built handoff: the team's actual history doesn't belong to any one officer's account. Attendance records, the roster, chat history, financial records: all of it is attached to the team, not to whoever happened to be logged in when it was created. An officer graduating and losing access doesn't mean any of that goes with them.

What does change when someone is removed from the roster entirely (not just stepping down from a role, but actually leaving the team) is access. Removing someone from the roster typically also removes them from the team's private chat rooms, immediately. What it should not do is delete anything they said while they were a member: the messages themselves stay part of the team's record, visible to everyone who's still there, even though the person who sent them can no longer read the thread. That distinction is worth explaining to an outgoing officer directly: leaving the roster ends their access, not the team's memory of the season.

The actual pre-handoff checklist

In rough order, in the weeks before you leave:

1. Decide the incoming officer's role, and grant it directly: invite if they're new, a role change if they're already on the roster.
2. If you're the sole owner, promote a co-owner before you do anything else on this list. Everything downstream of this is easier with two owners in the room.
3. Export the roster. A real export gives the incoming officer a snapshot of who's actually on the team, not just who they remember from the season.
4. Export the finances, if you're also handing off money: see the treasurer guide for what that should include.
5. Write down the one thing that would otherwise leave with you: the recurring booking that's easy to forget, the contact at the venue, the thing that went wrong this year that you'd want to warn your successor about. This is the step every transition guide agrees gets skipped, and it's the one that actually matters most.
6. Don't hand over your personal login. Every officer should have their own account under their own role. A shared password is how access outlives the person who's supposed to have it, including, eventually, you, long after you've graduated and stopped checking that inbox.

How TeamBasin handles this

TeamBasin ties a team's history to the team, not to whichever officer's account happened to create it, which is what makes a handoff a role change instead of a data migration.

• Role changes without new accounts. Promoting someone already on the roster is a role change on their existing account, not a new invite; their history stays attached to one identity.
• A deliberate path for ownership, rather than an irreversible one-click swap: promote a co-owner, confirm they're set up, then step back, with a built-in guardrail against a sole owner deleting their own account before someone else can take over.
• History stays with the team. Attendance, chat, roster and finance records are all attached to the team, not to a person's account; nothing is lost when an officer graduates and loses access.
• Removal ends access, not history. Someone taken off the roster loses their team chat access immediately; the messages they already sent stay part of the team's record.
• Real exports for the handoff itself: roster and finance data both export cleanly, so the incoming officer starts with an accurate snapshot instead of institutional memory.

If your club is heading into a leadership transition and isn't sure what actually needs to happen, request access and we'll walk through it with you.