Skip to main content
GullySystem
A practical guide

Catering event planning: headcount, menu and kitchen sheet

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 4 min read

In this guide 6 sections
The short answer

Build one event sheet that starts from the guest count and flows down: menu items, quantity per dish, raw ingredients, kitchen stations, serving staff and vehicles. Date every revision so the kitchen cooks from the latest numbers, not an old phone message.

Start the sheet with a confirmed headcount

Everything downstream depends on the guest number. Record three figures: the client’s estimate, the confirmed count and the buffer you plan to cook for, with who gave each number and when.

Split the count where it matters. Vegetarian and non-vegetarian guests, children, drivers and the host family’s staff may eat differently, and allergy notes belong on the same line, not in a separate message.

Fix a cut-off date for the final count, usually two or three days before service, and tell the client in writing. Later changes are allowed but flagged.

  • Estimated, confirmed and cooking headcount
  • Dietary split and allergy notes
  • Service style: buffet, plated or live counters
  • Service times for each course
  • Venue address and kitchen access

Tie each dish to a quantity per guest

List the menu by course. Beside each dish, enter a standard serving per head, and prefer figures from your own past events over a guess. A dessert after a heavy meal goes further than a starter at a cocktail hour.

Multiply by the cooking headcount to get the batch size, then round up to a whole tray or vessel. A half-filled chafing dish looks poor. A short one looks worse.

Mark dishes that need advance prep, such as marinating, dough resting or stock reduction. Those go on the kitchen timeline.

Turn dish quantities into an ingredient list

Each dish has a recipe card with raw quantities per base batch. Scale the card to the event batch and add the lines across all dishes, since onion, oil, rice and paneer appear in many cards and should be totalled once.

Check the store before buying. Subtract what you hold, then group the rest by supplier: vegetables, dairy, dry goods, meat and disposables. Order perishables for the morning of the event.

Add the non-food items. Napkins, serving spoons, fuel cans, ice and water get forgotten until the van has left.

  • Raw material totals across all dishes
  • Stock on hand and shortfall
  • Supplier and delivery time per group
  • Disposables, fuel and ice
  • Equipment: vessels, burners, hot boxes

Plan staff and vehicles from the same sheet

Staff follow the service style. A plated dinner needs more servers per table than a buffet, so assign cooks to stations, a captain to the floor and a runner for restocking.

Work out the loading order for vehicles. Equipment goes in first, hot boxes last, ice at the end. Write the departure time, route and the driver’s phone number.

Add a return checklist. Count vessels and burners on the way back. Missing equipment is a cost nobody notices until the next event.

Track every revision until the event day

Clients change the menu and the count right up to the last day. Give the sheet a version number and a change log showing date, what changed, who asked and who approved.

Send the latest version to the kitchen head, the purchase person and the transport lead and ask each to confirm receipt. An old sheet in the kitchen is how forty extra guests arrive to find too little food.

On the evening before, freeze the sheet. Print it, sign it and hand it to the event captain.

Catering event sheet

A two-page template. Page one holds the event header, headcount block with dietary split, menu table with serving per head and batch size, and a revision log. The log has version, date, change and approver. Page two holds ingredient totals by supplier, station and staff roster, vehicle loading order and a return equipment count.

Open a blank worksheet to print

Questions owners ask

How much extra food should I cook beyond the confirmed count?

Use your own event history. Buffets with unpredictable walk-ins usually need a larger buffer than plated meals. Record actual leftovers after each event and adjust.

What should I do when the client changes the menu late?

Update the sheet, increase the version number and log who approved the change. Tell the kitchen and purchase teams directly. Confirm any extra cost before accepting it.

Who should own the event sheet?

The catering manager. Others read it and report changes through the manager, so there is one version of the plan.

Can catering software scale recipes automatically?

Yes. Software can scale recipe cards by headcount, total ingredients across dishes and list shortfalls against stock. You still set the serving sizes and check the output.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements