Lorixen.
EN

From Client Call Notes to an Event Run Sheet for a Caterer

Short answer: A caterer's run sheet is the single page the kitchen, drivers and front of house follow on the day. The details to build it arrive piecemeal: phone calls, emails, a venue message, a late change from the host. AI can gather those scraps into a draft run sheet with a consistent layout and a list of open questions. Because errors here have real consequences, especially on allergens and guest numbers, a named person checks every figure and instruction before the sheet reaches the team.

Why this task suits AI, and why it needs care

Run sheets are structured, repetitive documents. Every event needs the same kinds of information, and the same gaps cause the same last minute panics: nobody confirmed the loading door, the dessert count differs between two emails, or a guest's allergy was mentioned once on a call. A tool that reads all the source material and lays it out in one format reduces missed details.

The risk is also clear. A language model can fill a blank with something plausible. A run sheet that confidently states a guest count nobody gave is worse than an empty field. So the design rule is simple: facts only from sources, blanks stay visibly blank.

The anatomy of a run sheet

Build the template first. Each section answers a question someone will ask on the day.

1. Header

Event name, date, client, venue and address, on site contact with phone number, your lead for the event, and a reference to the booking.

2. Guest numbers

Total, adults and children if relevant, split by menu choice, and the date numbers were last confirmed. Add the cut off date after which changes are not accepted, if you have one.

3. Dietary and allergen register

Each guest or group with a requirement, the requirement itself, which dish is the safe alternative, and who prepares and serves it. This is the section where a person must verify every line against the original request. In Ireland, the Food Safety Authority of Ireland publishes official guidance on allergen information for food businesses; use it for the rules, not a tool.

4. Menu and quantities

Courses, items, portions, and service style (plated, buffet, canape rounds). Quantities come from your recipes and portion standards, not from the AI.

5. Timeline

Back-timed from service: loading, travel, arrival, setup, cooking or reheating, plating, service start, clearing, departure. Each entry has a time and an owner.

6. Venue and logistics

Access route, parking, loading door, kitchen facilities, power, water, lifts, waste arrangements, and any restrictions from the venue.

7. Staffing

Names, roles, start times, uniform notes and any briefing points.

8. Equipment and supplies

Lists for kitchen, service and front of house. Anything hired and its return time.

9. Payment and changes

Deposit status, balance due, and who may approve extra orders on the day.

10. Open questions

Anything missing or contradictory, with who is chasing it.

Turning notes into a draft

  1. Collect sources in one place. Call notes, email threads, the booking form, the venue's information sheet. Number each source so statements can be traced.
  2. Give the AI the template and the rules. Use only the supplied sources. If a field has no source, write "not confirmed". If sources conflict, list both with their source numbers instead of choosing.
  3. Ask for the open questions first. This makes the gaps visible before the layout looks finished.
  4. Review against sources. A person ticks the guest numbers, dietary register and times against the original messages.
  5. Call the client for the gaps. Update the sheet and note the date of each confirmation.
  6. Freeze and share. Issue a dated version to staff, with the changes since the previous version highlighted.

What not to delegate

Item Reason
Allergen safe substitutions A food safety judgement belongs to your trained staff
Final quantities and food costs Come from your recipes and costing
Hazard or licence conditions at the venue Check with the venue and authorities directly
Promises to the client A person confirms anything that changes the contract

Handling late changes

Events change in the last days. Keep a changes log at the top of the sheet: date, what changed, who approved, who was told. When a client message arrives, paste it into the tool and ask which sections it affects, then update them yourself. This keeps the history readable and prevents silent edits to critical sections.

Keeping client data tidy

Run sheets may include guests' names alongside medical or religious dietary needs, which can be sensitive personal data. Share the minimum necessary with the AI tool, for example anonymised guest labels that you map back to names offline. Check your provider's terms as of November 2026 on retention and training. Staff should receive only the version they need, and old sheets should be deleted according to your retention policy.

An illustrative example

This is an invented scenario. A call note says "about 80, some vegetarian, one nut thing". An email later says 76 confirmed and four vegetarian. The draft shows the guest total as "76 per email dated Tuesday, 80 per call note", leaves the nut line flagged with "type and severity not confirmed, client to be asked", and lists the loading door as unknown. The events manager phones the client, resolves all three, and issues the sheet with the questions closed.

FAQ

Can AI work out the quantities of food for us?

It can do arithmetic if you give it your portion rules, but we suggest your recipe and costing system holds the real figures. Treat any AI quantity as a cross check.

Should the run sheet be a document or an app?

A shared document works for most small caterers. An app or form based workflow becomes sensible when you handle many events a week and need version control and staff checklists.

How do we stop the sheet going out of date?

Give it a version number and date at the top, and a single owner who is the only person allowed to issue new versions.

What if the tool misreads a handwritten call note?

Photograph notes clearly, or type them. Treat any figure read from handwriting as unverified until confirmed.

If you would like a run sheet template and drafting workflow tailored to your catering business, you can send us the details through our enquiry page.

Sources

WhatsAppBook a call