# Booking Confirmation Best Practices: What Makes a Booking Actually Booked > The difference between 'confirmed on WhatsApp' and a real booking — the confirmation stack, what the document must contain, reconfirmation cadence, and edge cases. Canonical: https://brightdesk.app/blog/booking-confirmation-best-practices Last updated: 2026-05-18 Author: Brightdesk Team Category: Booking Management "Pakka ho gaya, bhaiya" is not a booking. Neither is a thumbs-up emoji, a screenshot of intent, or a warm phone call. A booking exists when three things exist: written scope, signed agreement, and money received. Everything short of that is a *conversation* — and conversations don't hold dates, survive disputes, or pay cancellation compensation. Here's the confirmation discipline that separates professionals from hopefuls. ## The Confirmation Stack A real booking assembles in a fixed order ([the onboarding sequence](https://brightdesk.app/blog/client-onboarding-process-freelancers)): 1. **The written confirmation** — every material fact in one document (below) 2. **The signature** — e-sign link, [valid under the IT Act](https://brightdesk.app/blog/e-signatures-legality-india), signable on a phone in two minutes 3. **The advance** — [30–50%, non-refundable, receipted](https://brightdesk.app/blog/deposit-and-advance-policies); the payment *is* the commitment 4. **The block** — only now does the date leave your available inventory ([the hold-vs-confirmed rule](https://brightdesk.app/blog/double-booking-prevention)) State the sequence up front, identically, to everyone: "Your date locks once the signed confirmation and advance are in." No exceptions for relatives-of-past-clients, planners in a hurry, or very confident-sounding families — *especially* not those. ## What the Confirmation Document Contains One page. Every dispute you'll never have: - **Parties and contacts** — including the [single point of contact](https://brightdesk.app/blog/how-to-handle-difficult-clients) for multi-stakeholder bookings - **The event grid:** every event/session with date, venue, timings, and deliverable — [multi-event weddings itemized per event](https://brightdesk.app/blog/wedding-photography-contract-essentials), never summarized as "wedding" - **Scope specifics by service:** looks and face-counts (makeup), coverage hours and team (photo), guest caps (mehendi/catering), rig spec (DJ) — the [scope table](https://brightdesk.app/blog/makeup-artist-contract-guide) native to your trade - **Money:** total, advance received, balance and its due date, [what happens on late payment](https://brightdesk.app/blog/invoice-payment-terms-explained) - **The protective clauses:** [cancellation/reschedule scale](https://brightdesk.app/blog/photography-cancellation-policy), overtime rates, travel terms - Anything promised verbally — if it was promised, it's in the document; if it's not in the document, it wasn't promised ## The Reconfirmation Cadence Confirmation isn't a moment; it's a maintained state. The cadence that catches every drift: - **On any change** — new venue, shifted muhurat, added event — the confirmation gets amended *in writing* same-day ("updating our confirmation: sangeet now at [venue], 7 pm — all else unchanged"). Verbal amendments are how airtight bookings rot - **One week out:** the [pre-event check-in](https://brightdesk.app/blog/client-communication-templates) — venue, timing, counts, balance reminder — the single message that catches "oh, we moved it to the farmhouse" - **Day before:** arrival time, your number, calm ## Edge Cases That Test the Discipline **The planner booking:** confirmations run *through* the planner but should name the end client and event facts; clarify who pays you and [whose paper you're on](https://brightdesk.app/blog/wedding-planner-business-guide-india). **The "hold it, money's coming" family:** a hold with an expiry, in writing — "holding the 14th till Friday 6 pm" — then released without guilt. Holds that don't expire are [phantom bookings](https://brightdesk.app/blog/double-booking-prevention). **The repeat client who "doesn't need paperwork":** they get the same document with a warmer first line. Familiarity is exactly when scope drifts — and the paperwork protects the *relationship*, which is the thing you're both claiming to value. **The last-minute booking (event in 72 hours):** compress, don't skip — confirmation + full payment upfront (no time for balance mechanics), signature before you leave for the venue. ## Why This Feels Heavy and Isn't The whole stack — document, signature, advance, receipt — is a 15-minute assembly with templates, and a 3-minute one with a system that generates confirmation, [contract](https://brightdesk.app/contract-templates), [invoice](https://brightdesk.app/invoice-generator), and receipt from the booking record itself. [Brightdesk does exactly that](https://brightdesk.app/auth/login): booking in, paperwork out, date blocked, balance tracked (bookings and invoices free; contracts on Pro). The payoff compounds silently: the family that experienced your confirmation process [refers you as "so professional"](https://brightdesk.app/blog/client-referral-strategies); the dispute that never happened cost nothing; and every date in your calendar is real — which, in a business where dates are inventory, is simply what solvency looks like. ## Related - [All blog posts](https://brightdesk.app/blog)