The most important part of an organisation: management
Two events with the same budget, the same room and the same speakers: one runs smoothly, the other falls apart. The difference is almost never resources. It is whether people know who decides what, and where the truth is kept.
Why it all comes back to management
Organising is not a pile of tasks that can be done independently. It is dozens of small jobs — invitations, venue, catering, registration, promotion, the door, certificates — connected in the right order. Where those connections break is almost never the job itself; it is the handover between two jobs.
An example: one person opens the registration form, another shares the announcement. If the person sharing doesn't know capacity is 100, they announce it to a group of 400. Nobody made a mistake, yet capacity fills in a day and 300 people are disappointed. The loss came from information that was never handed over, not from incompetence.
Management is precisely the work of designing those handovers. The four pillars below hold it together at any scale.
Role ownership: "everyone" means nobody
The most common mistake in volunteer teams is assigning work to the group rather than to people. "Let's share the announcement" is not a task — it has no owner, so it either never happens or three people do it separately.
The rule that works is simple: every line of work needs exactly one name on it. Others can help, but only one person is accountable. Even for a small event, separating these four roles is enough:
- Coordinator — holds the timeline and the whole picture, unblocks what is stuck. They should not take on delivery work; if they do, coordination stops.
- Registration and attendees — the form, capacity, lists, and questions coming in.
- Venue and logistics — room, equipment, catering, layout.
- Promotion and communication — invitation copy, posting schedule, reminders.
With fewer than four people the roles merge, but they do not disappear. One person can hold two — just write down that both belong to them.
Decision rights: what can be changed without asking?
Teams usually manage to divide the work; where they stall is decision rights. Who can raise capacity from 100 to 130? Who can move the date? Who can turn down a sponsor? Asked on the day, these questions get answered too late.
The practical fix is to sort decisions into three buckets:
- Decide alone: reversible, cheap calls (improving the announcement copy, changing the seating). A team that waits for approval on these is a slow team.
- Decide and inform: reversible but affecting others (adding a field to the form, shifting a reminder time).
- Decide together: irreversible or expensive (date, venue, going over budget, raising capacity).
Drawing this line in advance buys you the most valuable thing on event day: a team that can act without asking. If opening a second check-in desk needs approval while a queue builds, the queue triples first.
A single source of truth
The most expensive class of mistake is everyone looking at a different list. If the same information exists in two copies, one of them will eventually be wrong. A single source collapses three questions into one answer each:
Who is registered?
Form responses, requests that arrived by message and manual additions must land in the same list. A team merging two lists on the morning of the event will always miss someone.
How many are we?
Capacity, registrations and actual attendance should be read from one place. Catering is ordered against that number; if the number is disputed, so is the budget.
Who showed up?
Attendance should be marked on the registration list, not on a separate sheet. Attendance kept separately never makes it back into the post-event report.
Handover: does it run without its founder?
For associations, clubs and communities this pillar is existential, because the team turns over every year. The real test of an organisation is this: if the person who built it is away for a week, does the event still happen?
If the answer is no, the knowledge lives in people's heads. Fixing that does not require long procedures — just leaving three things behind:
- The last event's record: how many registered, how many came, where the budget overran. Three numbers stop the next team from guessing.
- The templates used: registration form, announcement copy, reminder message. Copy rewritten from scratch each term repeats the same mistakes each term.
- Access: accounts and lists should not sit in one person's private account. An attendee list left in a graduating student's inbox does not come back.
Symptoms of weak management
The root cause is hard to spot because the symptoms always surface elsewhere. These are nearly always indirect signs of missing management:
- The night before, everyone is up and nobody is quite sure what they are doing.
- The same question gets two different answers (capacity, time, price).
- The attendee list exists in more than one place and people argue about which is current.
- After the event, nobody can say for certain how many people came.
- The same mistakes recur at the next event.
If three or more of these feel familiar, the problem is not how hard your team works — it is the absence of a system carrying the work. The good news: none of these four pillars costs money.
A team with clear ownership, defined decision rights, one shared list and a real handover will out-deliver a better-funded but disorganised team every time.
Frequently asked questions
Do small teams really need defined roles?
Yes — arguably more. In a team of three the roles merge but do not vanish. Writing down a single owner for each line of work removes the "I thought you had it" gaps entirely.
Doesn't defining decision rights slow a team down?
It does the opposite. What slows teams is every decision waiting for approval. Releasing reversible decisions up front is what lets the team act without asking on event day.
Does a single source of truth require software?
The principle comes before the tool: never keep two copies of the same information. For small events one shared sheet is enough; once registration, attendance and reporting need to feed each other, keeping them in one panel removes the manual syncing.
Our team changes every year — how do we keep continuity?
Hand over three things: the numbers from past events, the templates you used, and account access. When those live somewhere organisational rather than personal, the knowledge survives the turnover.