The Complete Group-Booking Checklist for Andheri West

Start with a booking brief, not a long group chat

A group dinner becomes difficult when ten people hold ten slightly different versions of the plan. Before contacting a restaurant, reduce the evening to a one-page brief. Record the date, preferred arrival time, earliest and latest realistic headcount, occasion, likely meal length, approximate spend and any non-negotiable needs. Then nominate one organiser to speak for the group.

This is the central purpose of a group-booking checklist: it turns vague enthusiasm into information a restaurant can act on. “Around fifteen of us, sometime after work” cannot produce a reliable table plan. “Twelve confirmed, up to fifteen, arriving between 7:45 and 8:15 pm, with one wheelchair user and two children” can. The second message helps the host team assess space, pacing and service before anyone arrives.

1. Fix the headcount range and arrival pattern

Separate confirmed guests from probable guests. If the venue sets a minimum spend, takes a deposit or needs a final number, ask when the headcount locks and what happens if it falls. Do not reserve extra seats “just in case” without discussing them; empty places affect the table shape and can leave confirmed guests spread too far apart.

Next, work out how people will arrive. Andheri West groups often converge from offices, the metro, the railway line and neighbouring suburbs. Share the exact map pin, entrance photo and organiser’s number. If people will be late, decide whether the table should order starters on time or wait. That small choice protects punctual guests from an hour of uncertainty.

2. Match the table to the people

A large table is not automatically a useful table. Ask whether guests will sit at one continuous table, two nearby tables or a reserved section. Tell the restaurant about a wheelchair, walking aid, pram, high chair, older guest who needs a supportive seat, or anyone who should avoid stairs. For speeches or introductions, check sight lines; for conversation, ask about speaker proximity and whether a quieter position is available.

If the group prefers an open-air setting, review the venue’s outdoor seating information and request a weather fallback. “Outdoor preferred, indoor acceptable” and “outdoor only” are different instructions. Mumbai Fire Brigade guidance for eating houses says entrances, exits and a clear passage should remain unobstructed, so decorations, gifts and spare chairs should never turn circulation space into storage (Mumbai Fire Brigade requirements).

3. Map dietary needs before choosing dishes

Ask guests for dietary information privately and precisely. “Vegetarian” is not the same as vegan; a preference is different from an allergy; and “no nuts” needs more detail if cross-contact is a concern. Send the restaurant a consolidated list without making a guest explain their medical history to the whole table. For a serious allergy, speak directly with the restaurant and understand what the kitchen can and cannot guarantee.

FSSAI’s food-service guidance identifies allergen categories including gluten-containing cereals, crustaceans, milk, eggs, fish, peanuts and tree nuts, soybeans and sulphites. Its display requirements apply to specified food-service businesses, but the list is a useful prompt for every organiser (FSSAI food-service information FAQ). Use the current food menu to shortlist possibilities, then explore preparation-led dish stories and verify ingredient questions with the team.

4. Choose the service format before choosing every plate

Decide whether the table will order freely, use a set menu, pre-order key dishes or work within a per-person plan. For a social dinner, a staged shared menu usually flows better than twenty unrelated individual orders. Begin with plates that can reach the table soon after arrival, follow with dishes that reward sharing, then time mains for when most guests are seated. Keep a vegetarian route through every stage rather than offering one isolated substitute.

Pre-ordering is most useful when there is a speech, a hard finish time or a very large party. It should still allow a little flexibility for appetite and late changes. Goat Brew’s group-ordering guide explains how a Pan-Asian table can balance sushi, dim sum, small plates, mains and dessert without ordering everything at once.

5. Make the cost legible

Write down the budget in the format that matters: food only, food plus drinks, or a complete ceiling including applicable taxes. Ask whether there is a deposit, minimum spend, cancellation window, cake or corkage policy, and how unused deposits are handled. If guests will split the bill, agree beforehand whether alcohol is separate and whether the restaurant can support multiple payments. Settling this at the end of a busy night is slower and more uncomfortable.

The Central Consumer Protection Authority’s current position is that restaurants must not add a service charge automatically or by default and must inform consumers that it is voluntary (Department of Consumer Affairs, January 2026). Your written confirmation should distinguish the agreed package price, taxes, optional items and any other venue-specific terms.

6. Plan drinks without making them the default

Estimate drink preferences separately from food. Count guests who want cocktails, beer, wine or spirits, and give equal thought to people choosing zero-proof drinks. Browse the current drinks selection, ask what can be served efficiently to a group and confirm any legal or date-specific restrictions directly. Do not promise a particular label, tap or cocktail until the venue confirms availability.

If alcohol is part of the plan, appoint drivers or arrange cabs before the first round. Maharashtra’s excise framework includes prescribed closure days and election-related closures, so a group built around bar service should reconfirm close to the date (Maharashtra State Excise manual). A good dinner plan should still feel complete for guests who do not drink.

7. Send two confirmations: 72 hours and day-of

About three days before the meal, send the final guest range, dietary matrix, seating preference, menu format, cake or décor requests, arrival window, payment structure and organiser’s phone number. Ask the restaurant to reply with what is confirmed and what remains a request. On the day, send only changes. Reopening every decision creates errors.

Your final message can be short: “Fourteen confirmed; arrival 8 pm; one vegan guest; one shellfish allergy already discussed; outdoor table with indoor rain fallback; shared starters from 8:15; cake at 10; one bill; organiser S.” Save that message where another trusted guest can find it if your phone dies.

The copy-and-send Andheri West checklist

• Date, arrival window and finish time
• Confirmed, minimum and maximum headcount
• Occasion and age mix
• Mobility, accessibility and seating needs
• Outdoor preference and weather fallback
• Allergies, vegetarian, vegan and other dietary needs
• À la carte, set menu or pre-order format
• Food, drinks and total budget limits
• Deposit, cancellation, minimum-spend and payment terms
• Cake, décor, gifts, AV or photography requests
• Parking, cab and precise map-pin plan
• One organiser and one backup contact

For Goat Brew, send these details through the group-booking page or begin with a table reservation. For more local planning ideas, browse the Goat Brew Journal. The checklist is complete only when the venue and organiser share the same written version of the evening.

Frequently asked questions