Institutional Memory Is Free: A Committee Handover That Doesn't Rely on Vibes
There's a specific kind of quiet that falls over a new committee in early October. Someone has just asked, "So who has the Eventbrite login?" and the room has realised that the answer is a group chat from eight months ago, a dead phone, and a former treasurer who has moved to Berlin.
This is the annual ritual of institutional forgetting, and it's entirely avoidable. Handover season doesn't need a grand ceremony or a forty-slide deck. It needs one shared drive, one afternoon, and a small amount of discipline from people who are, let's be fair, mostly thinking about their dissertations.
So here's the practical version of the folder every society swears it will make and almost never does: what goes in, what gets updated, what gets deleted, and why it matters more than the farewell social.
Start with a one-page front door
Before you build anything, put a single document at the top of the drive called something unmissable like START HERE — read this first. Inside, keep it to one page: who the current committee are, what the society actually does week to week, which term the big events land in, and the three things that would genuinely break if nobody knew them.
Think of it as the note you'd leave for a housesitter. Not a biography of the house — just where the stopcock is, which bin day is which, and the fact that the back door needs a shove.
Passwords: the actual crown jewels
This is the section people fudge because it feels slightly illicit to write things down. Don't fudge it. Use a shared password manager with committee access, or at minimum a locked document that gets transferred to the incoming chair and treasurer on the day they take over. Never in the society WhatsApp group. Never in an email subject line. Never in a pinned Instagram DM to yourself.
List everything, and be honest about what's legacy: the SU mailbox, the society email alias, Instagram and TikTok, the Facebook page and group, Eventbrite, the ticketing platform, the bank account (and who the signatories currently are), Canva, the Linktree, the domain if you have one, and any sponsor portals.
Add a note next to each one explaining what it's actually for. "We pay for Canva Pro annually, it renews in March, the card on file is the treasurer's" is dramatically more useful than a username on its own.
Suppliers, deposits and the awkward email trail
Societies accumulate relationships that nobody documents. The venue in Hackney that does a cheap hire on a Tuesday. The photographer who invoiced late. The caterer who needs a fortnight's notice. The AV company that saved the winter panel at four hours' notice and should absolutely be booked again.
Build a simple table: name, what they do, contact, typical cost, and a one-line verdict. "Reliable, slightly chaotic invoicing, book early" is perfect. If there was a deposit paid and it hasn't been refunded yet, write that down too — chasing a £200 deposit in February for a room booked in November is nobody's idea of fun.
The run sheet is the load-bearing document
Event run sheets are the closest thing a society has to a recipe. If you built a good one for the autumn speaker panel, keep it. Future committees will adapt it for years.
A useful run sheet covers the timeline from six weeks out to the morning after: room booking confirmation, risk assessment, catering numbers, speaker liaison, tech check, door rota, the person holding the card machine, the person with the backup laptop dongle, and the all-important "who's locking up". Save the final version after the event, not the hopeful one from the planning stage. The differences between the two are where the real lessons live.
Emergency numbers and the things you hope never to use
Put the boring safety stuff in an obvious folder and label it clearly. First aiders on the committee, the venue's duty manager, the SU activities contact, the out-of-hours number, the university security line if you're on campus, and the name of whoever holds the society's public liability insurance.
This isn't dramatic, it's just sensible. If something goes sideways at 9pm on a Thursday, you do not want the person in charge scrolling through three years of chat history to find a phone number.
Budget quirks, sponsor quirks and the odd tenner
Every society has financial habits that make no sense to outsiders. Someone always pays for the printer ink out of pocket. There's usually a float that lives in a tin. There's a sponsorship deal with an unusual invoicing schedule. There's a termly grant that has to be claimed before a specific date or it vanishes.
Write it all down in plain English, alongside the current budget spreadsheet. Flag which lines are fixed, which are guesses, and which ones you'd cut first if the money didn't arrive. Incoming treasurers inherit enough stress without also inheriting a mystery.
The lore file
This is the fun one, and the one people forget. A short document of unwritten rules: which room in the SU building has the good projector, why the society never books that one pub anymore, who to ask about the spare banner, the fact that the annual quiz always sells out in forty minutes if you post at 7pm on a Sunday, and the deeply held tradition that the chair is never allowed to pick the playlist.
Lore is what makes a society feel like a society rather than a small events business. It's also the first thing to disappear when a committee turns over completely. An hour of typing preserves years of it.
Archive, update, delete
Be ruthless in three directions. Archive the finished stuff — old event photos, past budgets, last year's minutes — into a clearly labelled folder by academic year so the live drive stays navigable. Update anything dated: the constitution, the committee list, the sponsor deck, the safeguarding policy, the membership stats you quote to sponsors.
And delete what shouldn't exist. That means old member lists, sign-up sheets with personal details, and anything holding data you no longer need under UK GDPR rules. Keep the aggregate numbers, bin the spreadsheets with people's phone numbers on them. If in doubt, ask the SU for guidance — they'd much rather answer the question now than deal with it later.
Do it before the mince pies
Handover folders are one of those tasks that expand to fill whatever time you give them, so give them ninety minutes in late November, while the term is still standing and the committee is still speaking to each other. Assign one person to own the drive, one to audit the passwords, and one to write the lore file. Then actually transfer access on the day the new committee is elected, not "at some point in the new year".
Your successors will probably never say thank you. They'll just quietly not have a crisis, which is the highest compliment a committee can receive.
