VILLA OWNER GUIDES · BALI · Lovina
Pass breakfast preferences to the right kitchen contact
When breakfast is offered at a Lovina villa, the useful task is to collect requests accurately and pass them to whoever prepares the meal. A preference form should distinguish guest wishes from options the kitchen has actually confirmed.
This is an owner guide. HostKeeper’s operating priority is Uluwatu and the Bukit; management in this area must be confirmed for the exact property before any agreement.
Ask only practical meal questions
Collect the meal choice, serving arrangement and number of people, using the options currently offered. Include a separate field for allergies or dietary requirements the guest wants conveyed. Preserve their wording and ask for clarification if the request is unclear rather than interpreting it yourself.
Use a checked kitchen handover
A simple card can contain: guest reference, breakfast choice, dietary message, kitchen recipient and confirmation status. Example: a request mentioning an ingredient remains “awaiting kitchen confirmation” until the responsible cook has reviewed it. Keep requests from different guests separate to avoid accidental substitutions.
Confirm what can actually be provided
Ask the responsible kitchen contact to confirm what they can offer and communicate that answer accurately. Do not describe a meal as suitable for an allergy based only on its name or photograph. If a choice changes, update both the guest confirmation and kitchen card before preparation.
Fictional example — A preference is not a kitchen confirmation
In a hypothetical Lovina villa offering breakfast, two guests select different meal options. One adds an ingredient-related dietary message, while the team sheet places both guests under a single “special breakfast” label. The coordinator separates the choices and preserves the guest’s exact request for the kitchen contact. The kitchen has confirmed one meal but has not answered the ingredient question. The guest receives that unresolved status rather than an assurance based on the meal name. A later change must update both the kitchen card and the guest confirmation. This scenario concerns accurate communication; it does not establish allergy suitability, a food preparation method or a real guest’s medical information.
Keep wishes and confirmed options separate
Use one identifiable reference per meal request and record the kitchen recipient’s answer. Dietary wording should reach the responsible kitchen contact without interpretation by the host. A request stays awaiting confirmation until that answer is received, and any changed choice must be reconciled in both the kitchen handover and the guest message.
| Meal reference | Guest request state | Kitchen recipient | Confirmation state |
|---|---|---|---|
| Meal M1 | Current menu option selected | Assigned kitchen contact | Option confirmed |
| Meal M2 | Ingredient question preserved | Assigned kitchen contact | Answer pending |
| Change M2-A | Revised choice requested | Same responsible contact | Update both records |
Practical owner checklist
- Use the current breakfast options.
- Preserve dietary requests in the guest’s wording.
- Identify the kitchen recipient and status.
- Confirm changes with guest and kitchen.
Questions owners ask
Can the host confirm an allergy-related request alone?
Pass the exact request to the responsible kitchen contact and relay their confirmed answer. Avoid making an unsupported assurance.
Keep one dietary request visibly pending
Hypothetical example — not a client result or a market forecast
Hypothetical example: breakfast is requested for four people. Three choices are confirmed by the kitchen; one dietary request awaits clarification. The handover shows three confirmed meals and one pending request, preserving the guest’s exact wording. A count of four guests does not justify describing all four meals as suitable before the kitchen confirms.