Which version is on the pass?
Tuesday's function sheet for Friday's awards dinner says canapes at 6.30, starters at 7.45, and a vegetarian main for 22. On Wednesday, the client moves the timings back fifteen minutes and adds a dessert option. The events coordinator updates the document and emails it round.
The head chef printed Tuesday's version and pinned it on the pass. The front of house supervisor has Wednesday's on their phone. The driver was never sent either and uses the delivery time from the original booking. On Friday, the starters are ready fifteen minutes early and the dessert option is a surprise.
A document cannot tell you it has changed
Function sheets carry a lot of information for several teams at once, and it changes often in the last week. Documents are good at holding information and bad at telling people it changed.
- Every edit creates a new file, and people keep the one they printed.
- Change emails say 'updated sheet attached' without saying what changed.
- Each team needs a different part of the sheet but receives all of it.
- Late changes by phone are added to one copy and not the others.
- There is no point at which everyone confirms they have the final version.
So each team works diligently from the version they have. The failure is in the handover, not in anyone's work.
Agency and casual staff make it worse, because they are often only sent the parts of the sheet someone thought to forward. A supervisor briefing a team at the venue may be reading from a phone screenshot of a version that was replaced that morning.
What version drift costs
Timings out of step between kitchen and floor mean food waiting or guests waiting, and both show. Missing dietary variations mean a chef improvising at the pass. Drivers arriving at the wrong time or entrance lose time at the start of the event, when there is least of it.
Behind the scenes, the events coordinator spends the final week answering 'is this the latest?' and resending documents. When something goes wrong, working out which version each person had is its own small investigation.
One live sheet with a view for each team
- Each event has a single live record: timings, menu with dietary counts, venue details, access and parking, staffing and contact numbers.
- Each team has a view: the kitchen sees menu, counts and service times; front of house sees timings, table plan and staffing; drivers see addresses, access times and load lists.
- Changes are logged, and each person sees what changed since they last opened the sheet, highlighted.
- Key changes (timings, numbers, menu, dietary) trigger a notification to the teams they affect.
- At a set point before the event, each team lead confirms they have read the final version, and the event shows who has and has not.
- The sheet can still be printed for the pass, with the version and time on it, so an old printout is obvious.
| Change | Who is notified | What they see |
|---|---|---|
| Timings move | Kitchen, front of house, drivers | Old and new times |
| Dietary count changes | Kitchen, supervisor | The new counts by dish |
| Venue access updated | Drivers, supervisor | The new instructions |
| Extra staff added | Supervisor | Updated team list |
If your event management software already holds most of this, we connect to it and add the change tracking and sign-off it lacks rather than replace it.
The last week before a big event
The coordinator makes changes in one place and the right people hear about them. The chef opens the sheet and sees only what moved since Tuesday. On the day, a printed sheet shows its version and time at the top, so anyone holding an old one can tell.
When something does go wrong, you can see exactly what each team was told and when, which makes the debrief about fixing the process rather than finding someone to blame.
Signs this is happening to you
- Function sheets go out as attachments with each update.
- Kitchen and front of house have worked from different versions.
- Drivers get event details separately, or not at all.
- Nobody formally confirms they have the final version.