Planning the leavers' ball — alongside the book

The yearbook and the leavers’ ball run in the same term, with the same people, towards the same date. And they compete for exactly one resource: the time of six to nine people in May.

Do both with the same team at the same time and you do one of them badly. Usually the book, because the ball has a date that shouts.

The most important sentence first: split the teams

Not the people — the responsibility. One ball team and one book team, each with one person in charge and separate meetings. Two people can be in both, but nobody is responsible for both.

The reason isn’t bureaucracy, it’s scheduling logic: the ball and the book peak at the same moment. Whoever wears both hats has to choose in May between catering queries and proofreading — and chooses whatever shouts loudest.

How to distribute responsibilities cleanly is in Setting up the committee.

What actually takes a long time at the ball

Three things you can’t do at short notice. Everything else is doable in four weeks.

1. The venue — 9 to 12 months ahead. The only item that genuinely has to be early. Good halls for 250 people on a Saturday in June are gone a year in advance. That is the one task that has to happen in the autumn, while everyone else is still busy with the motto and the committee.

2. The money — 6 months ahead. A ball is more expensive than the book, often several times over. Hall rental, technical equipment, catering, decorations, music licensing. Settle early whether the ticket price covers it, and whether the book is in the package or sold separately.

3. The catering — 3 to 4 months ahead. It needs a binding head count, and you only get one with a registration that has a deadline.

The date you count backwards from

The ball is the fixed point for the book too — the copies are meant to be handed out there. That produces a chain you can’t negotiate with:

Leavers' ball                                 Day  0
Books delivered                               Day −4     (not day −1!)
Print handover                    Day −18 to −24        (ask your printer)
Internal deadline                             Day −32
Content closed                                Day −60

And in parallel for the ball:

Leavers' ball                                 Day  0
Final head count to the caterer               Day −21
Registration closes, with payment             Day −28
Tickets go on sale                            Day −70
Running order & programme fixed               Day −30
Technical check in the hall                   Day −7

The two chains meet in the same week, roughly a month before the ball. So: put the book handover before the hot ball week, not next to it. If you have to choose which project gets the buffer, give it to the book — the ball happens with improvised decorations, a book doesn’t happen with half a layout.

The registration is the whole problem

Almost everything that goes wrong at a ball goes back to an imprecise head count. Because a ball isn’t a year-group event: parents, siblings, partners and teachers come. 90 school leavers quickly become 250 people — and the caterer wants a number, not an estimate.

What you have to ask, in one go:

• Is the person coming? Yes/no, binding.
• How many guests? With an upper limit, or the hall gets too small.
• Food: vegetarian, vegan, allergies. This is the point where follow-up questions otherwise arrive one by one in the chat — 40 times.
• Paid? A registration without payment isn’t one.

In AbiHive you create the ball as a date — with location, day, cover image and accept/decline. On top of that you can attach your own questions to the registration, exactly the four above, instead of collecting them in the chat. The year group accepts in one step and answers what the caterer needs to know along the way; you get a list instead of 90 messages. Reminders for the date run automatically, so the registration deadline doesn’t depend on a chat message.

A practical note: ask for guests as a number, not a list of names. Names change right up to the evening; it’s the number the caterer and the seating plan need.

Where the book and the ball help each other

There are three points where separating them is not sensible:

• A joint sale. Ticket plus book paid in one go is more convenient for everyone and saves you a second round of chasing.
• Photos. The ball is the last occasion where photos of the whole year group happen — just not for this book any more. Collect them anyway: the next year group and the retrospective pages benefit, and you’ll want to see them yourselves later.
• Handing out the books is a programme item. Giving out books at the ball without planning it ends in a pile next to the cloakroom. Two people, one table, one name list, twenty minutes in the running order. Details: Distributing, selling, leftover copies.

Takeaways

• Two teams, two people in charge, separate meetings — the same humans are allowed, the same responsibility isn’t.
• The venue in the autumn; everything else can come later.
• Count both schedules backwards from the ball and put the book handover before the hot ball week.
• Registration in one go: acceptance, guests as a number, food, payment.
• Plan handing out the books as a programme item, not as a pile.

More: the module Dates and the schedule across the whole year.