Where catering errors actually come from
Ask a catering operator to describe their worst service failures and the causes cluster tightly. Almost none of them are cooking failures. They are information failures, and they share a structure.
A number was agreed with the client. It was recorded somewhere. Then it was communicated to the kitchen through a different document. Somewhere between those steps, the two copies diverged: a late change reached one and not the other, or a digit was mistyped, or the kitchen was working from a sheet printed before Tuesday’s update.
This is not a discipline problem, and telling people to be more careful does not fix it. It is a structural consequence of having the same fact stored in two places. The only durable fix is to have one record and derive everything else from it.
Every document that is typed rather than generated is a copy that can go stale.
The information a kitchen actually needs
A kitchen sheet is not a summary of the event. It is a work order, and its contents are determined by what has to be decided in the kitchen.
- Final guest count, and the date it was confirmed, so the age of the number is visible.
- Menu selections in full, including any agreed substitutions.
- Dietary requirements and allergies, with the number of covers each affects.
- Service times by course, not just the event start time.
- The venue and space, which determines kitchen access and plating logistics.
- Any equipment or staffing agreed, since that often lives only in the sales conversation.
- A named contact for the day who can make decisions if something changes.
Counts that change, and how to handle them
Guest counts always change, usually downward, usually late. A catering operation that treats the count as a single fixed number will be wrong at least half the time.
The practical approach is to treat the count as a value with a timestamp. Recording that the count was 145 as confirmed on the 12th tells you something that recording 145 alone does not: it tells the kitchen how much to trust the number and whether it is worth chasing an update before ordering.
It also makes the commercial conversation cleaner. When a client drops from 145 to 120 three days out, the record shows what was confirmed when, which is the difference between applying your guarantee terms and arguing about what was said.
Knowing which events are worth taking
Catering businesses frequently discover, on inspection, that a category of work they have been chasing for years is barely profitable. Small weekday drop-offs often look like useful volume and behave like a loss once travel, staffing and the sales time to win them are counted.
Recording the value of each event alongside its type, size and date makes this visible without a project. An export of a season, sorted by event type, usually answers the question in ten minutes.
The point of this data is not reporting for its own sake. It is deciding what to say no to, which for most catering businesses is a more valuable capability than winning more work.