Function Sheet Builder for Caterers and Event Venues

A catering proposal is what you send a prospective client before they book, laying out menu options and pricing to win the business. A catering contract makes the booking official with terms both sides sign. An invoice bills for the work. The function sheet, or BEO, is different from all three: it is written for your own team, not the client, and its job is operational accuracy rather than persuasion or payment.

In practice, most of the same event data flows through all four documents. The guest count on the function sheet should match the count on the invoice. The menu on the function sheet should match what was proposed and confirmed. Rebuilding each document separately in Word or Excel is where numbers drift apart. A system that generates the function sheet, proposal, contract, and invoice from one shared set of event details keeps them aligned automatically.

Finalize and distribute the function sheet after the guest count is guaranteed, typically five to seven business days before the event for most caterers, or once the venue's own guarantee deadline has passed. Sending it too early means reprinting when the count inevitably shifts; sending it too late leaves the kitchen scrambling.

Copies should go to everyone who touches the event: the chef or kitchen manager for prep planning, the floor or banquet captain for setup and service, any bartenders for the bar package, and subcontracted vendors like rental companies or florists if their timing depends on yours. Keep a printed copy on-site the day of the event as the single source of truth if a dispute or question comes up mid-service.

The most frequent error is an outdated guest count, usually because someone updated the invoice but forgot to update the sheet the kitchen is working from, resulting in either wasted food or guests who don't get served. Close behind is a timeline that lists times in the order they were agreed to rather than the order they happen, which makes the day confusing to follow at a glance.

Vague dietary notes cause real problems too. Writing a general note like has allergies without specifying which guests, which allergens, and how many plates are affected puts your kitchen at risk of a serious mistake. And reusing an old file without fully updating the venue name, room, or vendor list is a quiet but common way outdated information ends up in front of a client.

Keep it to one or two pages whenever the event allows it. Staff read function sheets standing up in a busy kitchen or on a loading dock, not sitting at a desk, so dense paragraphs slow everyone down. Use clear section headers, bullet points for menu items, and bold the guest count and event time so they are impossible to miss at a glance.

Print in a legible size, at least 11 point font, since sheets often get read under poor lighting or by staff without reading glasses handy. If your kitchen works off a printed copy taped to a prep table, a clean single-column layout holds up better over a busy shift than a cramped multi-column spreadsheet export.