# Mehendi Booking Management: Handling Auspicious-Date Pileups Without Chaos > Mehendi bookings cluster on the same auspicious dates — how to manage the calendar crunch, sequence same-day functions, confirm scope in writing, and never double-book. Canonical: https://brightdesk.app/blog/mehendi-booking-management Last updated: 2026-07-13 Author: Brightdesk Team Category: Wedding Business Mehendi has the most brutal calendar concentration in the wedding industry: the muhurat calendar plus the mehendi-is-two-days-before convention means half your season's demand lands on a dozen dates. On those days you'll be offered three functions and a bride simultaneously — and how you manage that crunch decides both your income and your reputation. Here's the booking-management system for it. ## Understand Your Real Capacity Per Date Start with honest arithmetic for a peak date: - A **bridal booking** consumes 4–8 hours plus travel — effectively a half-day exclusive - A **function** consumes its contracted hours + setup + travel between venues - You personally can realistically do: one bride + one evening function, or two functions, per day — *if* venues are close - With a [team bench](https://brightdesk.app/blog/mehendi-artist-business-guide), capacity multiplies: you take the bridal hands, hired artists staff parallel functions under your banner Write your capacity rule down ("peak date = 1 bridal + 1 function, or 2 functions ≤10 km apart") and let it make the decisions. Overbooking a muhurat day fails publicly, at someone's wedding. ## Sequence Same-Day Bookings Deliberately When stacking a peak date: 1. **Bridal first, always in the morning/afternoon slot** — bridal mehendi needs hours and your freshest hands, and brides' schedules are the least movable 2. Buffer 60–90 minutes between engagements: mehendi *always* runs over (one more aunty is a law of nature) 3. Cluster geographically — accept the second booking only if travel is sane; a cross-city dash between functions destroys both 4. Confirm timings in writing with a start *and end* ("2 artists, 4–8 pm") — the end time is your protection for the next engagement ## Confirm Scope in Writing (the Guest-Count Problem) Mehendi's classic dispute: booked for 25 guests, faced with 60. Every confirmation must state: - Date, venue, hours, team size - **Guest cap and the overflow rule:** "up to 30 guests; beyond that, additional artist-hours at ₹—, subject to availability" - Bridal design tier if applicable ([reference photos attached](https://brightdesk.app/blog/mehendi-artist-pricing-india)) - Advance received, balance and when it's due (at the function) A structured confirmation message or one-page [contract](https://brightdesk.app/contract-templates) takes three minutes and pre-answers the function-day argument. No confirmation, no date — WhatsApp "pakka aa jana" is not a booking. ## The Advance Rule Is Your Calendar's Immune System On dates where demand exceeds your capacity, unconfirmed "bookings" are poison — a family that holds your peak date verbally and cancels costs you the two paid functions you refused. The rule: **a date is blocked only when the advance (30–50%, non-refundable) lands.** Say it warmly and identically to everyone: "I hold dates on advance — the 12th has two other inquiries, so whoever confirms first gets it." This sentence is fair, true, and converts. Advances need paper too: [receipt on arrival](https://brightdesk.app/blog/advance-payment-invoice-guide), balance shown, both linked to the booking. ## Track the Pipeline, Not Just the Calendar In season you'll be juggling 20+ conversations at different stages: inquired, quoted, advance-pending, confirmed, done-but-balance-due. Memory and chat-scroll fail at exactly this scale, and the failure modes are expensive — double-booked dates, forgotten quotes, uncollected balances. What a real pipeline gives you: - Every inquiry logged with date, event, venue, and quoted price - Calendar view showing true availability including team allocation - Advance/balance status per booking, visible at a glance - Post-function follow-up prompts ([reviews](https://brightdesk.app/blog/how-to-ask-for-client-reviews) and photos while hands are still dark) [Brightdesk's booking system](https://brightdesk.app/auth/login) handles multi-event structures, unavailable-date blocking, advances, and balances in one free tool — designed for wedding professionals whose whole year happens on thirty dates. ## Peak-Season Rhythm - **Sunday night:** review next week's confirmed engagements — timings, teams, travel, cones stocked - **48 hours before each function:** reconfirm with the client (venue, timing, guest count) — the two-line message that catches every "oh, we shifted it to the lawn in Gurgaon" - **Function day:** balances collected on-site (UPI at the table), team paid same-week, tomorrow reviewed tonight - **Off-season:** the [marketing engine](https://brightdesk.app/blog/mehendi-artist-marketing) runs so the next muhurat cluster arrives pre-sold The artists who own the auspicious dates aren't the ones who say yes to everything — they're the ones whose calendar, confirmations, and advances made every yes stick. ## Related - [All blog posts](https://brightdesk.app/blog)