In short: for a restaurant, planning a corporate Christmas dinner or holiday party begins with an event record—not with the seasonal menu. First capture the client, date, expected guest count and decision-makers. Then build the menu, review costs, assign work, schedule staff and map out the event. Before purchasing begins, the quantities on the event menu must match the current number of servings: changing the guest count alone does not update dishes or the shopping list.
This guide is for restaurant managers, event teams, chefs and F&B departments. It is not a guide for companies looking for a venue. It explains how a restaurant or event venue can sell, prepare and deliver several corporate holiday events without departments working from different versions of the plan.
2026 seasonal update: review your holiday packages, catalog prices and estimated per-serving costs in August, before enquiries build through September and October. If your market books earlier, move this review forward. Refresh the materials again in January 2027 for the following season.
What should a restaurant record at the first enquiry?
An initial enquiry rarely includes a final menu or confirmed attendance. It should still be enough to create a working event record, so the team does not have to reconstruct the booking from an inbox later.
In ManageMyRestaurants.Events, an enquiry can be entered as a regular event. There is no separate “lead” object. The event can immediately include:
the event name,
the client or company,
the date and service hours,
the planned guest count,
a description and internal notes,
contact people.
Restaurants can create their own event statuses. “Planning” and “Finalized” are available as starting statuses, but changing an event status only labels its stage. It does not finalize the menu, lock editing or recalculate costs.
If the enquiry starts as a large table booking, it can first be entered in the reservation log. From there, a team member can open a new-event form with the name, date, time and party size already suggested. The event is created only when that form is saved.
One company, several contacts
For the same corporate Christmas party, an HR contact may coordinate the program, an executive assistant may approve the menu, and accounts payable may handle the documents. A client record in ManageMyRestaurants.Events is an internal database record; it does not create a login or self-service account for the client.
Several people can be added to the same company record, with a name, telephone number, email address, job title and note. An event can use a contact already stored under the client or a one-off contact created only for that booking. Use the notes to make it clear who confirms attendance, who can approve changes during the event and who should receive the paperwork.
A T-minus timeline for 2026 corporate holiday events
The timeline below is a practical starting point for restaurants and event venues. Adjust it to your deposit rules, suppliers, production lead times and event scale.
Timing | Client and sales | Kitchen and F&B | Operations and staffing |
|---|---|---|---|
T-10–12 weeks | Record the enquiry, client, date and planned guest count. | Check whether the requested format and menu options are workable. | Review the event calendar and check space and equipment availability under the venue’s own procedure. |
T-8 weeks | Present package options, additional services and an initial price. | Add or review estimated per-serving costs. | Create the first set of preparation tasks. |
T-4 weeks | Collect the client’s choices for food, drinks and additional services. | Review package variants and the information received about diets and allergens. | Build the first run-of-show and plan the staff shifts likely to be needed. |
T-14 days | Remind the client of the deadline for final attendance. | Review serving quantities and special meal requirements. | Confirm suppliers, setup times and operational tasks. |
T-7 days | Record the confirmed guest count and final commercial arrangements. | Correct menu quantities, finalize the menu and generate the shopping list. | Check the rota, overlapping shifts and service sequence. |
T-1 day | Confirm who is authorized to make decisions during the event. | Compare the current menu, recipes and shopping list. | Brief the team using the event brief. |
T+1–3 days | Complete the post-event notes and documentation. | Enter the actual food spend if it is known. | Close tasks and record improvements for the next event. |
Planned and confirmed guest counts: what actually recalculates?
Each event has separate fields for the planned and confirmed guest count. For additional services priced per guest, the system uses the confirmed number first. If it is empty, it uses the planned number. If both are empty, the service is calculated for one person.
That does not mean the guest count controls the entire holiday party menu. If the client changes attendance from 60 to 68 people, the system behaves as follows:
Element | What happens after the guest count changes? |
|---|---|
Additional service priced per guest | Its sales price and estimated cost recalculate for the new guest count. |
Meals, drinks and packages | Their quantities on the event menu remain unchanged. |
Estimated food cost | It does not increase until the menu-item quantities change. |
Shopping list | It does not update solely because attendance changed. |
Finalized menu cost snapshot | It does not refresh solely because the guest count was saved. |
This is one of the most important cost-control checks in corporate holiday event planning. The event record may already show 68 guests and a revised per-person service total while the menu still contains 60 packages. Compare those figures manually before updating the offer, purchasing ingredients or briefing the team.
Holiday party menus in 2026: a package does not replace dish selection
Packages make seasonal selling easier when several companies book a similar offer. In ManageMyRestaurants.Events, a package can contain meal categories, drink categories and food-service categories. For an individual event, the team selects the dishes and drinks available within those categories.
The package catalog price is a separate field. On an event menu, it is multiplied by the package quantity entered for that event. Selecting a more expensive dish does not automatically change the client’s price, but it can increase the estimated delivery cost because the package cost is based on the estimated costs of the selected meals and drinks.
Before finalizing the menu, check:
Has a specific dish and drink been selected for every package choice?
Does the package quantity match the current number of servings?
Does every selected item have a manually entered estimated cost?
Are the kitchen notes unambiguous?
The estimated cost of a meal is entered manually for one serving. The system does not calculate it from ingredient purchase prices. If a selected item has no estimated cost, the calculation is marked as incomplete; missing data is not treated as a cost of zero.
Dietary requirements and allergens: what is not assigned to an individual guest?
The event record does not contain a structured “guest name + diet + allergen + number of servings” table. Information can be recorded in a menu-item note or event note, and a catalog dish can carry a label such as “vegan” or “contains nuts.” A label describes the dish; it does not state how many portions are required or identify the person receiving them.
For that reason, “dietary requirements confirmed” is not enough for production or service. The kitchen needs the quantity of each variation, while the floor team needs an agreed method for identifying and serving special meals.
Client information and kitchen information are not the same thing
Client and sales | Kitchen and F&B |
|---|---|
Package price and scope | The specific dishes and drinks selected |
Planned and confirmed attendance | Quantities entered against each menu item |
Discount and negotiated terms | Estimated serving cost and data completeness |
The program shared with the organizer | Preparation and service times |
The person authorized to approve changes | Notes on special variants and how they will be served |
These two views should not be used interchangeably. A package price does not tell the kitchen what to produce, and a recipe or per-serving cost does not need to appear in the client-facing plan.
Three cost and staffing checks before the holiday rush
1. Guest count versus menu quantities
Compare confirmed attendance with the quantities of packages, dishes, drinks and special meals. Do not assume that saving a new guest count completes this check automatically.
2. Service scope versus staff hours
A seated Christmas dinner with speeches and a late bar requires a different working window from a two-hour buffet reception. An employee shift is stored separately, with its own start and end time. The application warns about overlapping shifts for the same employee, but it still allows them to be saved. Review staffing together with the service format; our guide to how many servers you need for 100 guests provides an additional planning reference.
3. Food cost versus other event costs
The event summary can include estimated food cost, estimated costs for additional services and extra expenses such as transport or equipment hire. It does not include employee wages or the venue’s fixed overhead. The displayed estimated contribution is therefore not the event’s full accounting profit.
Finalizing the menu and generating the shopping list
A menu can be finalized once it contains at least one item. Finalization records the sales total using the current catalog prices and saves the first estimated-cost snapshot. Only then can a shopping list be generated manually for that event.
The shopping list uses the recipes for meals and drinks, multiplied by their quantities on the event menu, including the selected items inside packages. It does not consolidate purchasing across several corporate holiday events. An additional food service without a recipe does not create an ingredient requirement.
A finalized menu can still be edited. Saving a changed menu item recalculates the cost, increases the revision number and deletes the existing shopping list in full. A new list must then be generated manually, and any previous “purchased” flags disappear. Changing the guest count or editing a recipe alone does not recalculate the list.
Run-of-show, tasks and the event brief
The run-of-show can include deliveries, room setup, staff arrival, guest arrival, each service, speeches and teardown. Every timeline item has a title, description, group, start time and end time. It is not assigned to a person and is not linked automatically to a dish.
Tasks are managed separately. A task has a title, description, board column and any number of assignees, but it does not have a due date. A task template can add a repeatable set of actions when an event is created. One timeline item can be linked to one task, but later edits do not synchronize in both directions.
For the pre-event briefing, the team can print an event brief containing the overview, client, contacts, menu quantities and notes, package selections, services without prices, timeline, assigned employees and selected notes. The brief does not contain ingredients or financial amounts.
Selected timeline groups can also be shared through an unindexed, read-only link. The link can expire and does not give the client access to the full event record.
For more on maintaining a single operational source of truth, read Banquet Event Order (BEO): What Every Restaurant and Event Venue Should Include and How to Organize Restaurant Event Operations: A Manager’s Guide.
Corporate holiday event checklist for restaurants
Is the person who approves the menu identified, along with the decision-maker available during the event?
Does the confirmed guest count match all quantities on the menu?
Have specific options been chosen inside every package?
Are special-meal quantities clear to both the kitchen and the floor team?
Are estimated costs complete for every selected dish?
Was a new shopping list generated after the latest menu change?
Does the run-of-show include setup, service and teardown?
Do tasks have assignees, and do employees have separate shifts in the schedule?
Does the event price still match the current scope?
Have space and equipment been checked outside the application where the venue’s process requires it?
Frequently asked questions about corporate Christmas events
Does the “Finalized” event status lock the event?
No. An event status is a label defined by the venue. Menu finalization is a separate action, and the menu can still be changed after it has been finalized.
Will the system create one serving for every confirmed guest?
No. Quantities for meals, drinks and packages are entered manually on the event menu.
Can shopping lists from several holiday events be combined?
No. Each shopping list belongs to one event menu.
Does the application control room and equipment availability?
No. Parallel events are visible on the calendar, but the system does not reserve rooms or equipment and does not block conflicts. The table-reservation module can, however, block a restaurant zone or the entire venue from online reservations while an event is taking place.
A corporate holiday event should be a repeatable restaurant process, not a collection of exceptions scattered across emails and messages. ManageMyRestaurants.Events connects the event with its client, menu, cost data, tasks, run-of-show and staff schedule. Create an account and prepare your first 2026 holiday event.