Lunch moved to half twelve, but only on one sheet
The Monday operations meeting goes through the week's events with printed function sheets. On Tuesday, the organiser of Thursday's conference emails the events coordinator: lunch at 12.30 instead of 1pm, two extra vegetarians, and the afternoon breakout is now in the boardroom. The coordinator updates the booking system and reprints the sheet. The kitchen still has the Monday copy pinned up. The setup team never received the new one because they only look at the board on Wednesday night.
On Thursday, the boardroom is set for nobody, the breakout room is set for a session that is not happening, and lunch is plated for the old time.
Printed sheets cannot tell you what changed
A function sheet is a snapshot. Reprinting it does not tell anyone which line is different, and busy departments do not reread two pages to find one change. Changes also arrive through many routes: the organiser emails, calls the sales manager, or tells the duty manager on the day.
- Each department needs a different slice of the same event: kitchen times and numbers, setup layouts, AV kit, front of house arrivals.
- Version numbers on printed sheets are easy to miss.
- Changes agreed verbally often never reach the booking system at all.
- Nobody signs off that a department has seen the latest change.
Where the mistakes show up
Wrong setups, food at the wrong time, missing dietary meals, AV in the wrong room. Each one is small and each one is noticed by the organiser, often in front of their delegates. Behind the scenes, supervisors spend the event morning phoning each other to check which version is right, and duty managers improvise around gaps.
The same confusion makes it hard to bill fairly afterwards, because nobody can say what was agreed when.
How we build live event orders with a change log
- Event orders are generated from your booking data rather than typed, so the booking system remains the single place changes are made.
- Every change to an event is recorded with who made it, when and the reason, and compared with what each department last saw.
- Each department gets its own view on a tablet or screen in their area: the kitchen sees times, numbers and dietary counts; setup sees rooms and layouts; AV sees kit and timings.
- When something changes for a department, it gets a short notice showing only that change, and someone in that team acknowledges it.
- Unacknowledged changes close to the event are escalated to the duty manager.
- Printed sheets still exist for those who want them, stamped with the version and the time printed.
| Department | What they see | Change notice example |
|---|---|---|
| Kitchen | Service times, covers, dietary counts | Lunch 12.30 not 13.00, +2 vegetarian |
| Setup crew | Rooms, layouts, furniture | Breakout moved to boardroom, set U-shape for 12 |
| AV | Kit per room, timings | Screen needed in boardroom from 14.00 |
| Front of house | Arrivals, registration, contacts | Registration opens 08.15 |
An event day with one version of the truth
Supervisors start their shift by clearing their change notices rather than reading every sheet again. The duty manager can see at a glance that every department has acknowledged the latest changes for today's events. When the organiser asks why lunch was early, the log shows the email that asked for it.
Verbal changes still happen, but the habit becomes: tell the coordinator, it goes in the system, everyone hears.
You may have this problem if
- Departments have worked from different versions of the same function sheet.
- Changes are communicated by reprinting and hoping.
- Verbal changes on the day never make it into the booking.
- Nobody can easily show what was changed, when and by whom.
- The Monday meeting is the only time everyone sees the same information.