A function sheet is the operational document that ties a single event together: what gets produced and served, in what order, for how many guests, with which staff and which equipment. In hotel and banquet operations the same document is usually called a banquet event order, or BEO. Caterers and event venues more often say function sheet or kitchen sheet. All of these names refer to the same document.
What makes it distinctive is not its content alone but that several departments depend on it at the same time. Kitchen, service, technical crew and often outside partners all work from the same information on event day. A function sheet that is out of date or incomplete does not just cost one person time - it disrupts the whole run of the event.
This guide covers what a complete function sheet needs to contain, who reads which part of it, where the traditional paper-and-spreadsheet process breaks down, and how software can generate the document directly from the booking instead of maintaining it as a separate file.
Function sheet, kitchen sheet, BEO - one document, several names
The term BEO comes from the English-language hotel and banquet world and stands for banquet event order - historically a work order passed from sales to the kitchen. Caterers and independent event companies more commonly say function sheet or kitchen sheet, because in those operations the document is read primarily in the kitchen and on the floor.
The content barely differs between the terms. All of them describe a document that translates a booking or a signed quote into the operational detail needed on event day: what to cook, how much, for whom, and by when. Which term a venue or caterer uses often just reflects which side of the industry they come from. When comparing banquet software, the terminology matters far less than whether the system keeps this document accurate without manual upkeep.
Who reads a function sheet - and for what
A function sheet does not have one audience. It has several, each of which only needs a slice of it, but needs that slice to be reliable:
- Kitchen: the menu with target quantities, prep lead times, allergens and special requests - the basis for production and mise en place.
- Service staff: timing, course sequence, beverage selection, and any special arrangements made with the client.
- Technical crew: setup and teardown windows, power and room requirements, delivery times for rented equipment.
- Outside partners: rental companies, subcontractors or casual staff hired for a single event, who should never need a permanent login to the venue's system.
That last group is often underestimated. A rental company or a freelance kitchen crew needs the event's key details, not an account in the internal system. Systems such as Univents handle this with a public link that shows the current function sheet without any login - the outside partner sees exactly the same version as the in-house team, without anyone forwarding a copy by email.
The building blocks a complete function sheet needs
Key facts and timeline
Event name, date, venue, contact person, guest count and a timeline running from setup through the event to teardown. Without this frame, none of the other blocks can be read correctly.
Menu with target quantities
The items actually booked, grouped by food or product category in a consistent, maintained order - starters before mains, cold before hot - with subtotals per category. Every line carries a target quantity the kitchen has to produce.
Beverages
The same logic as the menu: booked beverage items with quantities, usually split into non-alcoholic, wine, spirits and any client-specific requests.
Staffing plan
Who is working which role - kitchen, service, technical - and during what window on the day. The function sheet is therefore also the interface into staff scheduling, not just into the kitchen.
Technical and logistics details
Seating layout, stage and technical setup, delivery times, access routes - everything the setup and service crew need to find on site to plan their own work.
Allergens and special requests
Allergens per menu item, plus individual requests from guests or guest groups - vegetarian, vegan, religious dietary requirements. In practice this is the block most often skipped, and the one with the most direct impact on guest safety and satisfaction.
Where the target quantities actually come from
The target quantity for a line item is rarely just "the number booked". It results from the booked quantity multiplied by a basis taken from the underlying order - most commonly the guest count, sometimes a duration or a number of stations. If a client books a buffet package for a guest count rather than individual items, the function sheet has to resolve that math itself, otherwise the kitchen sees "1 package" instead of the actual portions to produce.
This is where most errors creep into the traditional process: if the guest count changes two days before the event, someone has to recalculate every affected line by hand - and experience shows at least one gets missed.
Common failure points in a manual kitchen sheet process
Outdated printouts. A function sheet printed a week ahead and pinned up in the kitchen no longer reflects the current state if the client changes an item the day before. Working from paper on event day means, in practice, sometimes working from stale numbers.
Version chaos. As soon as several people edit the same Word or Excel file, email copies around, or drop it into a shared folder, three different versions exist at once - and no one can say with confidence which is current.
Manually recalculated quantities. Every manual recalculation is a potential error source, especially with multi-component packages or last-minute guest cancellations. The later the change, the less time there is to check the numbers properly.
A gap between sales and kitchen. What the quote says and what actually gets produced can drift apart when each side works from its own document.
How software generates the function sheet directly from the booking
The obvious fix for all four failure points is the same: stop maintaining the function sheet as a standalone document, and derive it from the items actually booked for the event. When the inquiry, quote, booking, production, staffing and invoice all sit on one shared event record, a change to the guest count automatically pulls quantities, staffing needs and the invoice along with it - the function sheet no longer needs manual updates, because it is not a separate copy of the data, it is a view onto it.
In systems such as Univents, the function sheet is built this way from the booked line items, grouped by food and product category in a maintained order, with subtotals per category. It stays fully editable when wording or ordering needs a manual touch, exports print- and PDF-ready with scaling, and can be shared with the kitchen or outside partners through a public link that requires no login. How kitchen and staffing work together on top of that is covered in Kitchen and staff in one system.
The practical effect: whoever opens the function sheet on event day sees the same state as the last change made in the office - no one had to remember to send out a new version.
Function sheet vs. production list vs. kitchen display - where the lines are
These three terms get blurred together in practice, even though they cover different jobs:
- Function sheet is the full document for the whole event - key facts, menu, beverages, staffing, logistics, allergens - aimed at every role involved.
- Production list is a kitchen-specific derivative: generated from bookings, filterable by category, tag or delivery note, and meant as a printable PDF for the production day. See Kitchen production for detail.
- Kitchen display goes a step further: an interactive board where each item carries a status - open, in progress, done - and shows recipe and ingredient detail scaled to the actual order quantities, including in the staff portal. More at Kitchen display.
An operation that only cleans up its function sheet but still runs production by shouting across the kitchen has covered half the distance. The double data entry disappears only once the function sheet, production list and staffing plan all come from the same booking - including the handoff into staff scheduling.
Frequently asked questions about function sheets and BEOs
What is the difference between a function sheet and a BEO?
None in substance. BEO (banquet event order) is the term used in hotel and banquet operations for the same document that caterers and event companies usually call a function sheet or kitchen sheet.
What must a function sheet always include?
Key event facts and a timeline, the menu with target quantities, beverages, the staffing plan, technical and logistics detail, and allergens with special requests. Missing any one of these means someone has to chase the answer on event day.
How are quantities on a function sheet calculated?
The target quantity is the booked quantity of a line item multiplied by a basis from the order, usually the guest count. For package bookings, that math has to be resolved per component so the kitchen sees an actual portion count instead of just "1 package".
Who is responsible for creating the function sheet?
Traditionally, event planning or sales, built from the confirmed quote - often as a separate file. In systems that connect booking and kitchen directly, the function sheet is generated automatically from the booked items and is never manually rebuilt.
Can outside partners see a function sheet without a system login?
Yes, through a public link that shows the current function sheet without requiring an account. This matters most for rental companies, subcontractors or casual staff who only need information for a single event.
What happens if the guest count changes at short notice?
In a manual process, every affected line has to be recalculated by hand - a common source of errors. When the function sheet is derived from the booking, quantities, staffing needs and the invoice update automatically as soon as the guest count changes in the system.
Is a function sheet the same thing as a production list?
No. The function sheet covers the whole event and is aimed at every role involved. The production list is a kitchen-specific derivative, usually filtered by category or delivery note and formatted as a PDF for the production day.