A Household Menu Brief for Your Dubai Chef

A household menu brief turns “please cook what we like” into a useful conversation. It tells a chef who is eating, when meals need to be ready, which ingredients matter and what a successful week looks like. For a Dubai household juggling work, school, travel and guests, that clarity is often more valuable than a very long list of recipes.

The brief should be easy to update and short enough to use. Start with the household’s stable preferences, then add a weekly note for changing plans. This guide explains both parts and includes an example you can adapt for a regular private chef arrangement.

Build a household menu brief around real meals

Begin with the meals that actually need support. Do you want dinner cooked on visit days, prepared lunches, breakfast components or a combination? Identify how many people eat each meal rather than multiplying the household size by every day of the week.

A family of five might only need lunch for two people on weekdays. One adult might travel every second week. Children might eat at school on some days and at home on others. Those details have a direct effect on quantities, shopping and the amount of preparation that makes sense.

Separate ordinary household cooking from entertaining. A Friday dinner for guests may require different staffing, presentation and timing from Tuesday’s family meal. Add it as a separate request instead of quietly treating it as another line in the same visit. The private chef versus catering guide explains the distinction.

Your first version does not need to be perfect. It needs to replace vague assumptions with enough information for a sensible menu proposal. The chef can then identify questions that only become clear when dishes, timings and kitchen capacity are considered together.

Keep stable preferences separate from this week’s changes

Create two sections. The household profile contains information that rarely changes: regular diners, ingredients to avoid, favourite cuisines, dietary requirements, usual portions and the preferred communication contact. The weekly note contains travel, guests, unusual meal times and specific requests.

This separation prevents the chef from rereading a long message thread to work out whether a temporary instruction still applies. “No dinner on Wednesday this week” should not accidentally become a permanent rule. Equally, an important ingredient restriction should not disappear because it was mentioned in a one-off weekly message.

Put a revision date on the profile and keep one agreed version. When something changes, update the relevant line and draw attention to it. Avoid circulating several documents with similar filenames and different instructions. A brief is only useful if everyone knows which one is current.

For sensitive information, share what is necessary to prepare the food and organise service. You generally do not need to include a full family history. Where a medical eating plan is relevant, provide the actual instructions from the qualified professional rather than asking the chef to infer a treatment plan.

Describe preferences with examples

Broad labels can mean very different things. “Mediterranean”, “light”, “high protein” or “family friendly” may start a conversation, but they do not finish it. Add examples of meals the household enjoys and explain what you like about them.

For instance, “We enjoy grilled fish with vegetables and a separate sauce” is more usable than “healthy dinners”. “The children like mild tomato sauces but dislike visible onion pieces” gives the chef something concrete to work with. If you enjoy spice, distinguish warmth from heat and say whether stronger condiments can be served separately.

Include foods you are willing to try. A brief made entirely of restrictions can trap the household in a very small menu. You might ask for one new dish each week alongside familiar favourites, or a different preparation of an ingredient everyone already enjoys.

Do not assume every family member has the same preference. Record differences only where they affect cooking: one person wants a sauce separately, another does not eat a particular protein, and a child needs an earlier serving time. The aim is a workable shared structure with a few deliberate adjustments.

Record requirements without vague shorthand

Preferences, allergies, intolerances, religious requirements and clinician-directed eating plans should not be merged into one “special diet” box. Explain the requirement in the guest’s or household member’s own confirmed terms and ask the chef to acknowledge it before proposing a menu.

Specify ingredients where possible. If someone avoids dairy, clarify whether that is a preference, an intolerance or an allergy, because the handling discussion may be different. If you require halal ingredients, discuss the sourcing and preparation expectations directly rather than relying only on a cuisine name.

Do not use the brief to declare that a home kitchen is free of an allergen unless that statement has actually been assessed and confirmed. Ask what can be accommodated and what limitations remain. A written discussion through the dietary requirements enquiry helps establish what the team needs to know.

For a varied household, it can be easier to build a shared base with separate finishes than to cook entirely different menus. The mixed-diet dinner planning guide explains that approach for entertaining; the same organisational idea can also inform an ordinary meal plan.

Map the week before choosing the dishes

Use a simple grid showing the meals that need preparation. Add the number of diners and whether food is intended for immediate service or a later meal. The chef can then propose dishes suited to that pattern.

Day	Meal support needed	People	Practical note
Monday	Family dinner on visit day	Four	Children eat earlier; adult sauce can be separate
Tuesday	Prepared lunch components	Two	Follow the agreed dish-specific instructions
Wednesday	No evening meal required	None	Household is out
Thursday	Family dinner on visit day	Four	One person returns later
Friday	Lunch only	Two	Keep the evening free for a separate guest plan

This is an illustrative schedule, not a recommendation to store every dish for a particular number of days. The chef should decide which dishes fit the planned timing and provide appropriate handling instructions. If the pattern does not suit the available visits, change the schedule or the menu rather than stretching the food beyond its intended use.

For households mainly seeking organised meals between visits, discuss weekly meal preparation. For more regular cooking support, compare the scope of a part-time chef arrangement. The schedule should drive the choice of service.

Make portion feedback practical

“Large portions” and “small portions” are not reliable measurements across different households. Begin with the agreed number of diners, explain whether leftovers are wanted and then review what actually remains after a representative meal.

You might discover that the main dish is well judged but the starch portion is consistently too large. Another household may want extra cooked vegetables because they become part of lunch. Record those observations by component rather than increasing or reducing the whole menu indiscriminately.

Planned leftovers should have a destination. “Extra chicken for two lunches, handled according to the chef’s instructions” is more useful than “make plenty”. If plans change, tell the chef before shopping where possible so that the quantities can change too.

Avoid making weight loss, sports performance or other health outcomes the chef’s unqualified responsibility. If a person follows a prescribed plan, share the relevant professional specification and ask whether the service can prepare it. The household brief is an operational document, not a substitute for personalised clinical advice.

Agree grocery rules once

State who shops, who approves substitutions and how spending is recorded. List the staples normally available in the house and identify items that should always be checked before another purchase. A short pantry inventory can save repeated conversations and unnecessary duplication.

Specify when the menu and shopping list should be agreed. The deadline should leave enough time for the actual sourcing arrangement, rather than being an arbitrary number copied from another household. Ask how late changes are handled and whether they may affect the scope or cost.

Give the chef room to propose sensible substitutions, but identify decisions that need approval. A change of seasonal vegetable may be straightforward; replacing an ingredient tied to a dietary requirement needs explicit review. Make that distinction before the chef is standing in a shop waiting for a reply.

Keep grocery spending distinct from the service fee. The pricing page provides the current framework, and your proposal should identify the arrangement for ingredients, shopping time and any additional work. A clear brief reduces confusion, but it does not replace the commercial agreement.

Include the kitchen and handover requirements

Mention anything that affects the food plan: available oven capacity, suitable cookware, refrigerator space and containers. Update these details if equipment changes or the home is being renovated. Photographs are helpful when descriptions leave room for interpretation.

Explain how you want finished dishes organised. Some households prefer serving bowls for the same evening and labelled containers for later meals. Others need individual portions because diners eat at different times. Agree what labels or written notes are included and where they will be left.

Request dish-specific storage, reheating and use instructions for food intended for later. Ask who will receive the handover if the usual household contact is absent. A carefully prepared meal is less useful if nobody knows what it is or how it was intended to be served.

The first-visit kitchen guide covers these practical arrangements in detail. Once they are settled, keep only the stable essentials in the profile and use the weekly note for exceptions.

An example profile you can adapt

Household: two adults and two school-age children. Main need: dinner on two agreed visit days and additional components only where confirmed in the visit scope. Preferences: Mediterranean and mild Indian dishes, vegetables served visibly rather than hidden, sauces separate where practical. Favourites: grilled fish, chicken with rice, lentil dishes and roasted vegetables. Requirements: listed individually in the approved dietary section; please acknowledge any proposed ingredient change. Portions: standard first portions, with additional vegetables welcomed and leftovers prepared only for an identified meal. Communication: one household contact approves menus and groceries. Handover: explain the dishes, identify food intended for later and provide the relevant handling instructions.

This example deliberately leaves the menu open. A useful profile gives the chef room to cook while making the important boundaries clear. Replace the generic requirements line with your actual confirmed information before using it.

Keep a separate short weekly note: “Wednesday lunch is cancelled; one adult is away; please repeat last week’s fish dish with a different vegetable; no guest meal is included this week.” That is enough to adapt a stable profile without rewriting it.

Review with a three-question routine

After each visit, ask: what should we repeat, what should we adjust, and what changed in the schedule? These questions produce useful information without turning dinner into a formal review meeting.

Collect comments before sending them to the chef. If one person wants more spice and another wants less, the solution may be a separate condiment rather than a contradictory instruction. The household contact should state the agreed direction.

Review the pattern after several representative meals. One unusually hungry evening does not necessarily mean every portion is wrong. A repeated mismatch is more meaningful. The chef trial scorecard can help if you are still assessing the service fit.

Update the profile when an adjustment becomes a stable preference. Keep temporary requests in the weekly note. This small discipline is what stops the system from becoming a long, confusing message history.

When the brief should change the service

Sometimes the finished profile shows that the household needs a different arrangement. Daily cooking, multiple meal times and frequent guests may exceed the scope of a limited visit plan. Equally, a household away most evenings may need less support than it initially expected.

Discuss the complete pattern with the team before choosing between full-time support, a part-time arrangement or a preparation-focused service. The right answer depends on the work required, not just the number of people at home.

Send the profile, a sample week and any open questions with your enquiry. A good brief makes the proposal more concrete: the chef can see the meals, the household can understand the scope, and both sides can identify what needs to be confirmed before the first visit.