A breakfast package forecast is a starting point for planning, not a guaranteed count of people who will eat. Before briefing the restaurant, identify what the report counts, verify the meal date and distinguish included entitlements, confirmed additional orders and unresolved requests. This original worksheet keeps those quantities separate.
Read the report's unit
Oracle describes the Package Forecast Report as a daily breakdown of reservations, or anticipated reservations, with an attached package. Do not silently rename a reservation count “breakfast covers.” A reservation may involve more than one person, and the applicable entitlement still needs checking.
Oracle's package-code guidance documents different calculation rules and separate next-day posting and forecasting settings. These are configured system rules, not proof that a guest will attend breakfast. Check the property's actual setup and service date rather than changing settings to make a forecast look right.
Build an explicit fictional count
For this classroom example, a supervisor has checked twelve distinct reservations for the same breakfast service. All guests in the exercise are adults. The worksheet records each person's verified included breakfast entitlement; it is not a claim about a real hotel's package or child policy.
- Eight reservations each have two people entitled to that breakfast: 8 × 2 gives 16.
- Four reservations each have one entitled person: 4 × 1 gives 4.
- The checked total is 20 included breakfasts across 12 reservations.
Counting one breakfast per reservation would give 12, understating this worksheet by 8. Assuming two for every reservation would give 24, overstating it by 4. Neither shortcut is justified by the reservation count alone.
Update a planning version without hiding uncertainty
Before the service, one of the two-person reservations cancels and the supervisor confirms that its two breakfast entitlements no longer apply. The included count becomes 20 − 2: 18, across eleven remaining package reservations.
Three other people have separately confirmed paid breakfast orders for this service. The exercise specifies that none is already in the included group. The planning base is therefore 18 + 3: 21 people. Two further enquiries, each for a different additional person outside both confirmed groups, remain unconfirmed; list them separately rather than describing the base as 23 confirmed breakfasts.
If both enquiries later become confirmed orders and nothing else changes, the updated base would be 23. That is a conditional scenario, not a probability forecast. Record the new information and issue a revised version; do not overwrite the earlier assumptions without a trace.
Brief the team with the right labels
A practice read-back is: “For the stated breakfast service, we have 18 verified included entitlements and three distinct confirmed paid orders: a planning base of 21. Two enquiries are pending. These are planning inputs, not actual attendance.” The kitchen and restaurant should use their own approved production and staffing procedures.
- State the service date, report time and person who checked the inputs.
- Confirm the report's unit, package rules and applicable meal date.
- Check that additional orders are not counted twice.
- Keep cancellations, confirmations and pending enquiries traceable.
- After service, record actual covers separately; a difference from the planning base does not by itself explain why people did or did not attend.
Do not infer food quantities, staffing ratios or revenue from this count alone. For broader service learning, explore HCA food and beverage service training.
Explore HCA food and beverage service training
