The client confirmed 120 guests. A few days later, the number changed to 128 in a message. A revised menu arrived by email, a dietary requirement was mentioned during a phone call, and the updated room layout appeared in another attachment. Every arrangement was recorded somewhere, but the event manager, kitchen and service team were no longer working from the same version of the event.
This is how many event-day problems begin. Not because the team lacks experience or attention to detail, but because the information required to deliver the event is spread across too many places.
A calendar entry confirms that an event will take place. A complete event sheet shows the team how to prepare and deliver it.
A confirmed booking is not yet an operational plan
The date, client name, room and estimated number of guests are enough to reserve a time slot. They are not enough for the kitchen to plan production, the manager to monitor preparations or the service team to deliver the event.
Before the event, the team also needs to know:
when the room and individual areas must be ready,
when external suppliers can enter and complete their setup,
which guest count is current and when it will be confirmed as final,
which menu and beverage options the client selected,
how many special dietary meals are required,
when each stage of service should begin,
which tasks are still open and who is responsible for them,
where to find the approved room layout, menu and other documents.
If some information is stored in emails, some in a spreadsheet, some in messages and the rest in the manager’s notes, every department has to reconstruct the event for itself. One person checks the latest client email, another uses an older file, while someone else relies on what was agreed during a meeting.
The information exists – but there is no single, current version of the event.
What is an event sheet and what does BEO mean?
An event sheet is a central record containing the information required to prepare and deliver an event. In hospitality and the international events industry, it is often referred to as a Banquet Event Order, or BEO. Other commonly used terms include event order, function sheet and event worksheet.
Despite the word “banquet”, the document is not limited to formal dinners. BEOs are also used for weddings, conferences, private celebrations, corporate events, catered functions and other events requiring several teams to coordinate their work.
Its purpose is to translate arrangements made with the client into clear information for the people responsible for delivering the event.
A proposal shows what the client can purchase. An agreement sets out the accepted terms. The event sheet answers a different set of questions: what exactly needs to happen, where, when and under whose responsibility?
Some venues combine parts of these documents. What matters is that the operational plan remains clear, current and available to the right people.
What should a restaurant or event venue BEO include?
There is no single form suitable for every business. A wedding venue needs different fields from a conference hotel, a restaurant hosting private functions or a catering company.
However, every useful event sheet should answer the same essential operational questions.
1. Essential event information and key contacts
The first section should contain information that clearly identifies the event:
event name and type,
client’s name or company name,
event date and location,
selected room or function space,
event start and end times,
venue access, setup and breakdown times,
primary client contact,
person authorised to make decisions on the event day,
internal manager responsible for delivery.
The person who signed the agreement is not always available during setup or service. Recording a dedicated day-of contact prevents the team from searching through previous correspondence when a decision is needed immediately.
2. Guest numbers and confirmation deadlines
The event sheet may need to distinguish between several attendance figures:
initial estimated attendance,
current expected guest count,
final or guaranteed guest count,
number of seats to be prepared,
children, suppliers, performers or crew members requiring meals,
deadline for confirming the final number of guests.
Guest count affects the room setup, portion quantities, beverage requirements, staffing levels and sometimes the choice of function space. It should not be hidden in one of the client’s messages.
If the number changes, the update should also show when it was made and who confirmed it.
3. Selected package, services and individual arrangements
The team should be able to see exactly what was sold to the client. Depending on the venue’s offer, this may include:
selected event or catering package,
room hire and number of included hours,
chosen food and beverage option,
additional services,
equipment provided by the venue,
negotiated additions or exclusions,
relevant payment and approval deadlines.
Individual arrangements should never depend on one person remembering a conversation. If the client was promised an additional setup hour, a different service format or an item outside the standard package, the information must reach the people whose work it affects.
This does not mean that every employee needs access to all commercial information. The complete arrangements can remain attached to the event while individual roles see only the details required to complete their work.
4. Final menu, beverages and dietary requirements
For the kitchen and service teams, the menu is one of the most important parts of the event order. It should include:
final list of dishes and beverages,
required number of portions,
service format, such as plated service, buffet or food stations,
planned serving times,
meals for children, suppliers and external crew,
vegetarian, vegan and other dietary options,
reported allergies and special requests,
approved substitutions,
instructions affecting preparation or service.
A note stating that “dietary requirements have been confirmed” does not give the kitchen enough information. The team needs to know what must be prepared, how many portions are required and how the relevant meals will be identified during service.
The menu should also be connected to the current guest count. Otherwise, the venue may have an approved selection of dishes while still planning production and purchasing around an outdated attendance figure.
5. Event timeline and order of service
A useful event timeline is not limited to the schedule of activities shared with guests. It should also show the operational work taking place before and during the event.
Depending on the format, it may include:
venue access,
deliveries and supplier setup,
room preparation,
key kitchen production stages,
staff arrival and briefing,
guest arrival,
welcome and first service,
service of subsequent courses,
speeches, presentations or ceremonies,
entertainment and technical cues,
cake service or other key moments,
bar closing, guest departure and breakdown.
The purpose is not to create a plan that cannot move by even one minute. The timeline gives every department the same sequence of events and makes dependencies visible.
If a speech is delayed, the kitchen and service team can immediately see which stage of service may also need to move.
6. Room setup, equipment and external suppliers
The event sheet should describe not only how the space should look, but also how it needs to function. This section may include:
room and table layout,
seating plan and table numbering,
furniture, linens and décor,
stage, dance floor or presentation area,
lighting, sound and audiovisual equipment,
power, internet and technical support requirements,
signage, cloakroom, parking and accessibility arrangements,
delivery windows and setup rules,
supplier names and contact details,
attachments such as floor plans or technical drawings.
This information becomes especially important when several suppliers are involved or when the venue is hosting more than one event at the same time.
7. Staffing, responsibilities and preparation status
Collecting all the required information does not automatically make an event ready. Specific tasks still need to be completed by specific people.
The event record should therefore identify:
manager responsible for the event,
kitchen, floor and bar leads,
staffing requirements and working hours,
preparation tasks,
task owners and deadlines,
dependencies between tasks,
current preparation status,
issues requiring a decision or further contact with the client.
“The team will take care of it” is not a task assignment. Every important action needs an owner and a deadline. This allows the manager to check readiness in advance rather than discover missing work during setup.
8. Documents, approvals and change history
The event record should provide access to the documents used during planning and delivery, including:
accepted proposal or package,
agreement and relevant confirmations,
approved menu,
room layout,
event timeline,
supplier documents,
files and visual references provided by the client,
documents generated for the operational team.
A clear history of changes is equally important. The manager should be able to establish which information is current, when it changed and who confirmed it.
Without this, adding another file may create another version rather than bring greater clarity to the process.
When should the event sheet be created and updated?
An event sheet should not be prepared once, just a few days before delivery. Ideally, it should develop together with the booking.
At the enquiry stage, it may contain only the client’s details, preferred date, estimated attendance and requested event format. Once the booking is confirmed, the selected package, deadlines and responsibilities can be added.
During the planning process, the team completes the menu, timeline, supplier details, room setup and tasks. Before the event, final numbers and approvals are recorded.
On the event day, the same record becomes the reference point for the manager and operational teams. After the event, it can support document checks, final billing and a review of what should be improved for future bookings.
The process should include clear deadlines for approving the guest count, menu, room layout and timeline. However, a “final version” should never mean that later changes are recorded outside the system.
If the client makes an accepted change, the information should be updated at the source and made visible to every department affected by it.
Who should be responsible for the event sheet?
One person should be accountable for the completeness and current status of the event record. Depending on the business, this may be an event manager, restaurant manager, banqueting coordinator, sales employee or another designated team member.
This does not mean that one person must enter every detail alone. The kitchen can maintain production information, the floor manager can update service requirements, and the sales team can confirm arrangements with the client. The event owner makes sure that all these elements form one coherent plan.
When responsibility belongs to “everyone”, changes are easily missed. A clearly designated manager, defined contributors and appropriate access for each role make the process more reliable.
Why a ready-made BEO template is only the beginning
A standard event sheet template is useful because it ensures that the same categories of information are checked for every booking. For a venue handling occasional and relatively simple functions, a well-designed document may be sufficient.
Its limitations become visible when arrangements change frequently, several departments are involved or the venue is preparing multiple events at the same time.
A static file needs to be updated, redistributed and recognised by everyone as the latest version. On its own, it does not update related tasks, menu quantities, timelines or other operational materials.
This is why an event sheet should be treated not only as a printable form, but as a central record connected to the entire workflow. The venue can still generate a document for the client or team, while the current information remains attached directly to the event.
From a static event sheet to a connected workflow
ManageMyRestaurants.Events is being built for restaurants, hotels, wedding venues, conference venues, catering companies and other businesses that regularly sell and deliver events.
The event acts as the central record. Client details, menus, ingredients, quantities, shopping lists, costs, timelines, tasks, employees, work schedules and documents can all be managed in relation to a specific event instead of existing as separate, unrelated files.
If the guest count changes, the manager updates the event details and can immediately review every element requiring further verification. Once the menu is finalised, the kitchen works from the correct version and the required ingredients can be included in the shopping list.
A document generated from event data does not require the same information to be entered manually again.
The goal is not to give every employee access to everything. Each person should receive the current information required to complete their part of the work, while the manager retains a clear view of the event’s overall preparation status.
A practical standard for every event
Whether a venue uses its own document or dedicated event management software, the operating standard should remain the same:
one event has one current operational record,
every important detail has a clearly defined place,
tasks have assigned owners and deadlines,
key arrangements have been approved by the client,
changes are made at the source instead of being added to another version,
every department sees the information required for its work,
the delivery plan is easy to access on the event day,
completed events remain available for review and future planning.
The team does not need more messages to search through. It needs one reliable plan showing what has been agreed, what still needs to happen and who is responsible for it.
Frequently asked questions about event sheets and BEOs
What does BEO stand for?
BEO stands for Banquet Event Order. It is a document or central event record containing the information required to plan and deliver an event, including the timeline, guest count, menu, room setup, staffing and special requirements.
Is an event sheet the same as an event contract?
Not always. An agreement records the formal and commercial terms accepted by the client and the venue. An event sheet focuses on the information required by the team to prepare and deliver the event.
Some venues combine the documents or ask the client to approve the BEO, but its primary purpose remains the coordination of event delivery.
Who prepares the Banquet Event Order?
The BEO is usually coordinated by the person managing the booking, such as an event manager, restaurant manager, banqueting coordinator or sales employee. Other departments should contribute the information relevant to their work.
Does a small restaurant need an event sheet?
A small venue may not need a detailed document for every group booking. It still benefits from using one consistent event record containing the current guest count, menu, timeline, room setup, responsibilities and confirmed client requests.
The level of detail should reflect the complexity of the event.
One event, one current plan
The most expensive mistakes rarely begin with one major bad decision. More often, they start with a small change that reached one person but not the rest of the team: an updated guest count, a revised service time, an additional dietary meal or a different room layout.
A well-structured event sheet reduces that risk by giving every department one operational version of the event. When the record is connected to menus, tasks, employees, timelines and documents, it becomes more than a form. It becomes the plan the venue uses to prepare and deliver the event.
Want to organise future events around one connected record instead of collecting updates from multiple places?
Create your ManageMyRestaurants.Events account and start managing your events in one connected system today.