The Handover Process
A practical guide to making your chapter outlive you
Introduction
A strong chapter should be able to thrive beyond any one President or board. The purpose of handover isn't to transfer files and passwords - it's to transfer knowledge, relationships, context, and ownership.
🧭 Here's What You'll Walk Away With
A realistic timeline that starts 1–2 months before the transition, not the night before
A shadowing approach that teaches context no document can capture
A checklist of the four things you're actually handing over
A way to pass on trust and relationships - the part that's easiest to forget and hardest to rebuild
What Counts as “Handover”?
The whole transition period: the weeks of overlap where the outgoing board is still running things and the incoming board is learning how, plus everything that gets documented, transferred, introduced, and formally signed over along the way.
Why Does This Matter for oikos Specifically?
Because oikos chapters rebuild themselves every one or two years. That turnover is a feature - it's how students get real leadership experience - but it's also the single biggest threat to continuity. Without deliberate handover, each board spends its first semester rediscovering what the last board already knew, which means a two-year term is really one year of learning and one year of doing.
Partners feel it too. A sponsor who has to re-explain the relationship to a new student every September eventually stops picking up the phone. Continuity is what turns a chapter from a series of restarts into something that compounds.
How: From Your Board to the Next One
Step 1 - Start Early and Put It on the Calendar
Handover should begin one to two months before the transition. Treat it as a period with milestones, not a final meeting where a folder changes hands.
Step 2 - Let Them Shadow You
Invite incoming leaders into board meetings, partner conversations, project discussions, and decisions before they formally take over. Most of what makes a chapter work is context - why that partner prefers email over calls, which faculty member to ask for room bookings, why last year's format was quietly dropped. None of that survives being written down, but all of it survives being witnessed.
Step 3 - Write the Handover Document Together
Not a report the outgoing board hands over, but a document you fill in side by side - the questions the newcomers ask are exactly the gaps you'd otherwise miss.
Folder 1 is the one chapters skip, and it's the most valuable. Write down what failed and why. A successor who knows which sponsor said no, which format flopped, and which deadline you missed will not spend their year rediscovering it.
Step 4 - Know What You're Actually Transferring
On access specifically: update recovery emails and phone numbers, and avoid sharing passwords over chat. On institutional access, don't forget the unglamorous items - university representation, student-union recognition, funding portals, and bank mandates are the ones that quietly block a new board for months if they're missed.
Step 5 - Tidy the Knowledge Base
Archive what's finished, keep what's live, and structure the rest so someone who wasn't there can navigate it. A folder called “final_FINAL_v3” helps nobody.
The long-term version of this is a chapter guidebook - one living document holding recurring deadlines, key contacts, annual events, university procedures, useful templates, and lessons from previous years. Each board adds to it rather than starting a new one.
Step 6 - Hand Over Trust, Not Just Tasks
Introduce your successors personally to professors, university representatives, partners, alumni, and contacts in the wider oikos network. An introduction from you carries credibility that a cold email from a new name simply doesn't.
Then mark the moment. A transition meeting, a reflection session, or a small celebration does two things at once: it recognises the outgoing team and it makes the transfer of ownership real for everyone watching.
Step 7 - Step Back Properly
Stay reachable for questions. Don't stay in charge. The new team will change things you built, drop things you loved, and make calls you wouldn't have - and that's the point. A handover that only succeeds if the next board does it your way isn't a handover, it's a lease.
Key principle: A successful handover creates continuity without limiting the freedom of the next generation to shape the chapter in its own way.
Summary
Start two months out, let the incoming board shadow real decisions, write the document together, transfer all four things (access, knowledge, relationships, ownership), keep a living chapter guidebook, introduce people personally, and then genuinely let go.
🎯 Main Takeaway
Handover isn't the transfer of passwords - it's the transfer of everything that lives in your head, plus the freedom to do it differently.
💡 Tips & Tricks - Try This Tomorrow
Open a blank handover document today, even if transition is months away. Add to it whenever something goes well or badly - it's impossible to reconstruct in the final week.
List every account, platform, and login your chapter uses in one place. Most boards underestimate this by about half.
Write down the three deadlines that would hurt most if the next board missed them, and put them in a shared calendar with reminders.
Invite one incoming member to your next board meeting as an observer. Shadowing is free and starts paying off immediately.
Draft the introduction emails to your three most important external contacts now, so handing over relationships takes ten minutes instead of never happening.
Last updated
Was this helpful?