Production and coordination · Bangalore, Goa & Kerala
Wedding-day coordination: the master run sheet, who owns it, and how vendors stay on one clock
A wedding day runs on one document, owned by one person. The master run sheet lists, minute by minute and space by space, what is happening, who is doing it, when each vendor arrives, what their load-in window is, and which moments cannot move because a muhurtham or a priest's timing fixes them. The lead planner owns it, issues it as individual call sheets to every vendor, and holds the only version that counts. When something slips, the planner decides — not the family, and not the vendor who slipped.
This page covers what the run sheet contains, how delays get resolved, when a bridal or family shadow is worth having, how vendors are kept on one clock, the setup deadline before doors open, and what a same-day turnover from ceremony to reception really takes. It names no timing as universal: every venue's access, end time and turnover capacity must be confirmed in writing with the property.
Updated 20 September 2026
What the master run sheet contains, and who owns it
One document, one owner, one version. The most common cause of a chaotic wedding day is not a late vendor; it is four people working from four slightly different schedules, each of them certain theirs is current.
What it must contain
- A timeline per space, not one timeline for the day. The mandap, the getting-ready rooms, the dining area and the reception space each run their own clock, and they intersect at named points.
- Vendor call times and load-in windows: who arrives when, through which gate, what they are bringing, how long they have, and who from the team receives them.
- Ritual fixed points. Muhurtham timings, priest arrival, the moments a family cannot move regardless of what else is running late. Everything else is scheduled around these.
- The getting-ready timeline working backwards from the ceremony: makeup and hair start times per person, outfit changes, photography windows, travel time to the venue.
- Contingency notes against each risk point: what happens if it rains, if a vendor is late, if the ceremony runs long, and who makes that call.
- Contacts: every vendor's on-site person with a phone number, plus the venue's duty manager and the desk.
Issue it as one master plus per-vendor call sheets, each carrying only that vendor's arrival, access, deliverables and on-site contact. A vendor who receives fourteen pages reads none of it. Ask for written acknowledgement from each one.
Who resolves delays on the day
Something will run late. What decides whether it matters is whether the decision rights were settled beforehand, in writing, and whether the family knows they are not the escalation point.
| Situation | Who decides | How it is handled |
|---|---|---|
| A vendor is late or short-staffed | The lead planner | Planner chases, re-sequences the affected window and briefs the vendors downstream; the family is told what changed, not asked what to do |
| The ceremony is running behind a fixed muhurtham | The priest and the family elder, advised by the planner | The planner compresses what surrounds it — photography, entry, seating — so the fixed moment itself holds |
| Weather forces a move | The planner, against a pre-agreed trigger time | The call is made at a named hour, not when the first drops land; crew and vendors already know both plans |
| A spend decision is needed — overtime, an extra vehicle, replacement equipment | One nominated family decision-maker | Agree before the day who that is and what they may approve alone, so a small cost does not wait for a family meeting |
The family should never be asked on the day where a vendor is, why a delivery is short, how to re-sequence a schedule, what to tell another vendor, or how to handle a venue's staff. Our practice is that the lead planner holds these decisions, a second carries the same run sheet, and one nominated family member is the only person we bring a money question to.
The bridal or family shadow, and when it earns its place
A shadow is one team member assigned to a person rather than to a function: usually the bride, sometimes the groom or both sets of parents. They do not run the wedding. They run that person's day.
What a shadow actually does
- Holds the timeline for that person — when to start makeup, when to change, when to move, how long the walk to the mandap takes in that outfit.
- Carries the kit: pins, spare dupatta, blotting paper, water with a straw, a phone charger, medication, snacks nobody remembered to eat.
- Manages the queue of people who want five minutes, so the bride is not simultaneously receiving relatives and being photographed and being asked about the cake.
- Coordinates directly with makeup, photography and the planner so the person is never the message-passer between vendors.
It is worth having when the day has more than one outfit change, when the rituals are muhurtham-timed and cannot absorb slippage, when the family is large enough that the couple will be intercepted constantly, and when an NRI couple has no local family in the room to do these things instinctively. It is worth less at a small wedding with one outfit, few guests and relatives who are already close at hand. Say which case you are in when you ask for a quote; it is a scoped role, not an assumption.
Keeping every vendor on one schedule
Photographer, makeup, caterer, decor, sound and entertainment all have their own idea of what time the day starts. The run sheet's real work is turning those into one clock and making the dependencies visible.
The dependencies that break days
- Makeup and hair feed the ceremony clock. A hair and makeup start time that is set without counting the number of people being readied, the travel to the venue and the photography window is the most common cause of a late ceremony.
- Photography needs windows, not gaps. Couple portraits, family groups and the getting-ready sequence each need a named slot in the run sheet with a named person to gather people, or they eat the ceremony.
- Catering needs a confirmed service start, counts per function, and clarity on sittings. A caterer told the guest number late will be short or wasteful, and both cost money.
- Decor and rentals need their load-in window ahead of everyone else, and their strike window agreed before build starts.
- Sound and light need a check with the venue's power settled, done before guests enter and after the decor is in place — not squeezed between them.
Practically: one call sheet per vendor, acknowledged in writing; a single group for on-the-day operations that vendors and the team are in and the family is not; and one person from our team assigned to receive vendors at the gate against the load-in schedule. Vendors who know exactly when they are wanted rarely arrive at the wrong time.
The setup deadline: finished before guests enter
Set the deadline as doors-open time minus a buffer, and treat it as the real end of build. Guests walking past a half-dressed entrance or into a sound check have already formed an impression that the wedding then has to overcome.
How the last hours before doors open are run
- Fix doors-open time in the run sheet, then work backwards: decor complete, then sound and light checks, then the walk-through, then the punch list, then guests.
- Hold a walk-through with the planner, the venue's duty manager and the decor lead, following the exact route a guest takes from the car to their seat.
- Run a punch list from that walk: what is unfinished, who fixes it, by when. Everything on it closes before doors open or it is removed rather than left half-done.
- Do sound and light checks after the decor is in place and before guests arrive, with the venue's power arrangement already settled.
- Plan an overnight build where the design needs one — a two-day mandap build needs overnight access, and that is a venue permission and a cost, not an assumption.
Confirm two things with the venue in writing before design sign-off: the earliest access time for load-in, and whether overnight work is permitted. A design that needs more build hours than the venue releases is a design problem discovered too late.
Morning ceremony, evening reception, same venue
It is practical, and it is the most demanding thing you can ask of a production team. Whether it works comes down to one question asked early: how many hours does the venue actually release between guests leaving the ceremony and guests entering the reception?
What a complete decor change really needs
- A strike of the first setup before anything new goes in: florals down, structures out, furniture cleared, floor cleaned. Strike is slower than people expect because it is unglamorous and usually understaffed.
- A second crew, or a second shift, rather than the same team working through. A crew that has built since dawn does not build well at four in the afternoon.
- A second set of inventory for anything that cannot be reused, which is most florals. Reusing the morning's florals in the evening is a plan that photographs badly.
- Guests physically out of the space, which is a hospitality problem as much as a production one: a lunch elsewhere, rooms to rest in, or a genuine gap in the day.
- A buffer that survives the ceremony running long — and ceremonies run long.
When a second space is the better answer: where the venue's released hours are fewer than the turnover honestly needs, where the two functions want opposite atmospheres, where the ceremony is muhurtham-fixed and cannot be shortened to protect the turnover, or where the guest lists differ enough that one set is waiting around for the other. A venue with two distinct spaces solves this without moving anybody — build both in advance and simply open the second.
| One venue | More than one | |
|---|---|---|
| Guests | No travel, no lost guests, elders and children far better served | Travel between functions, transfers to manage, stragglers at every move |
| Production | One load-in, one crew brief, one power plan — but turnovers under time pressure | Each space built in advance without a turnover, but crews, inventory and transport duplicated |
| Cost | Usually lower in logistics; a room block and catering concentrated in one contract | Higher in transport and crew; sometimes lower in venue hire if a cheaper space suits one function |
| Risk | One weather plan, one contract, one point of failure | More contracts and more moving parts, but a problem in one space need not affect the other |
Bangalore: slots, traffic and early muhurthams
Bangalore run sheets are written against two constraints the city imposes on everybody: venues that sell time in slots, and traffic that decides when people actually arrive.
What changes in a Bangalore run sheet
- Early muhurthams are normal here, which means makeup starting in the small hours and a build finished the night before. Ask the venue whether overnight access is possible before designing anything that needs it.
- At a kalyana mantapa or convention centre with morning and evening slots, your strike window may be dictated by another family's build. Get access and vacate times in writing and put the overtime rate in the run sheet, where the person who might trigger it can see it.
- Call times carry traffic. A vendor coming across the city to Whitefield, Electronic City or the Outer Ring Road in peak movement needs an earlier call than the distance suggests, and so does the bridal party.
- For venues beyond the airport and in the Nandi Hills belt, the crew usually cannot go home between build and function, so the run sheet has to account for crew meals and rest as well as work.
- Sound end times per space, in writing: the Noise Pollution (Regulation and Control) Rules, 2000 restrict loudspeakers between 10 pm and 6 am, and many Bangalore venues in residential surroundings set an earlier cut-off. Build the reception clock backwards from it.
Goa: distances, sunset and the sound cut-off
In Goa the run sheet is shaped by geography and by light. Vendors travel further, guests travel further, and the evening has a hard edge to it. We have produced 80+ weddings in Goa and these are the constants.
Goa-specific run sheet entries
- Travel time between north and south. A vendor or a guest crossing the state can spend well over an hour on the road, and longer in peak season, so call times are built around the journey rather than the job.
- Sunset governs a west-facing coastal ceremony. The golden window is short and fixed; the ceremony is scheduled around it and photography plans against it, which means the getting-ready clock is set by the sun rather than by preference.
- Wind is a production constraint on any beach or open coastal setup: weighting, flooring and wind-proofing take build time, and lightweight elements need a wet-weather and high-wind alternative.
- Sound cut-offs are enforced here. The national rules restrict loudspeakers between 10 pm and 6 am and properties often set earlier times, so the reception is sequenced backwards from the cut-off and the after-party is planned where it is permitted.
- Multi-day weekends are the Goa norm — welcome dinner, functions, departure brunch — so the run sheet spans days and the crew roster has to be staged so nobody works four days straight.
Kerala: institution timings, sittings and access
A Kerala run sheet usually has to satisfy someone else's schedule first. A church or a temple sets its timings, and the rest of the day is built around them.
What a Kerala run sheet has to carry
- The institution's timings and rules as fixed points: when the ceremony may start and must end, what decor, music and photography are permitted, and where vehicles may stop.
- Sadya service in sittings. Confirm with the caterer how many sittings your guest count needs, then schedule them in the run sheet with a named person sequencing guests — elders and families with small children first. Sittings set the shape of the afternoon.
- Movement between ceremony venue and reception property, with travel time, parking at both ends and a guest group who may not know the route.
- Access at backwater resorts reached by boat or a narrow road: last-boat times, load-in by water, limits on what can be carried, and a fixed cut-off for heavy fabrication.
- A weather-call trigger with a named decision-maker. Kerala sits under both monsoons — the south-west roughly June to September, with normal onset over Kerala on 1 June, and the north-east from October to December (IMD).
A sample run sheet extract
This is the shape, not your timings. A real run sheet is built against your venue's access hours, your muhurtham and your guest count, and it runs to many pages. Rows are generic and carry no real names.
| Time | Space | Action | Owner |
|---|---|---|---|
| Previous evening | Ceremony lawn | Overnight mandap build begins; venue overnight access confirmed in writing | Decor production lead |
| Early morning | Getting-ready rooms | Hair and makeup begins; order and per-person timings issued the night before | Bridal shadow |
| Mid-morning | Ceremony lawn | Sound and light check with venue power confirmed; priest arrives and sets the ritual space | Planner, second |
| Doors minus 60 min | Whole site | Walk-through on the guest route; punch list raised and closed | Lead planner |
| Doors open | Entrance, lawn | Guests received and seated; elders seated near the aisle and exits | Hospitality lead |
| Muhurtham window | Ceremony lawn | Ritual fixed point — nothing scheduled across it; photography positions pre-agreed | Priest, family elder |
| Afternoon | Ceremony lawn | Strike of morning setup begins; second crew takes over for the evening build | Decor production lead |
| Late afternoon | Reception space | Evening build, then lighting and sound re-rig; entertainment sound check | Planner, second |
| Doors minus 45 min | Reception space | Walk-through and punch list; build materials cleared from sight | Lead planner |
| After close | Whole site | Strike, inventory check, lost property to the desk, venue handover | Production lead, venue duty manager |
Every row has an owner. A row without a name against it is the row that does not happen — which is the whole argument for the document.
Questions couples ask
What should a wedding-day run sheet contain, and who owns it?
It should carry a timeline per space rather than one for the day, vendor call times and load-in windows with gate and receiving person, ritual fixed points such as muhurtham timings that nothing may cross, a getting-ready timeline worked backwards from the ceremony, guest-facing timings for doors, seating and meal service, contingency notes with a named decision-maker, and every on-site contact number. The lead planner owns it and holds the only version that counts, issuing per-vendor call sheets from it and collecting written acknowledgements. One document, one owner, one version.
Who resolves delays on the wedding day?
The lead planner, against decision rights agreed in advance. A late vendor is chased and the affected window re-sequenced, with the family told what changed rather than asked what to do. A ceremony running behind a fixed muhurtham is protected by compressing what surrounds it. A weather move is called at a pre-agreed trigger time, not when the first drops land. One nominated family member approves spend decisions such as overtime or an extra vehicle. The family should never be asked where a vendor is or how to re-sequence a schedule.
Do we need a bridal shadow, and what does one do?
A shadow is one team member assigned to a person rather than a function. They hold that person's timeline, carry the kit, manage the queue of people wanting five minutes, coordinate directly with makeup and photography so the bride is never the message-passer, and look after outfits and jewellery through changes. It earns its place when there are multiple outfit changes, when rituals are muhurtham-timed and cannot absorb slippage, when the family is large enough that the couple will be intercepted constantly, or when an NRI couple has no local family in the room.
How do we keep the photographer, makeup artist, caterer and entertainment on the same schedule?
Put them on one run sheet and issue each a call sheet containing only their own arrival, access, deliverables and on-site contact, acknowledged in writing. Then manage the dependencies: hair and makeup start times must count every person being readied plus travel and photography; photography needs named windows with someone gathering people; catering needs confirmed counts and a service start; decor needs its load-in ahead of everyone; sound and light check after decor and before guests. Run one operations group for vendors and the team that the family is not in.
How do we make sure decor and sound checks are finished before guests walk in?
Set the deadline as doors-open time minus a buffer and treat it as the real end of build. Work backwards: decor complete, then sound and light checks with venue power settled, then a walk-through along the exact route a guest takes from the car to their seat, then a punch list that closes before doors open. Clear cable runs, packing material, ladders and tools; the strike of the build is part of the build. Confirm the venue's earliest load-in time and whether overnight work is permitted before design sign-off, not after.
Is it practical to use the same venue for a morning ceremony and an evening reception with a complete decor change?
Yes, and it is the most demanding thing you can ask of a production team. Ask the venue first how many hours it actually releases between guests leaving the ceremony and guests entering the reception. A real turnover needs a full strike of the first setup, a second crew or shift rather than the same team working since dawn, a second set of florals and anything else not reusable, guests physically out of the space, a lighting and sound re-rig, and a buffer for a ceremony that runs long. If the released hours are fewer than that, a second space is the better answer.
Single venue or multiple venues — which is better for a multi-day wedding?
One venue means no guest travel, one load-in, one crew brief and usually lower logistics cost, with the trade-off of turnovers under time pressure and a risk that every function looks the same unless the design deliberately shifts. More than one venue lets each space be built in advance with no turnover and gives each function a fitting setting, at the cost of duplicated crews, inventory and transport, plus transfers and stragglers at every move. A single property with two distinct spaces usually gives you the best of both.
Sources
The sources above are the pages this guide relies on; where a source publishes no figure, this page prints none. Venue access hours, overnight build permission, turnover time between functions and sound cut-offs differ by property and must be confirmed in writing with the venue.
Wedding-day production
Send us your functions and your venue.
Tell us the functions, the venue or venues and the muhurtham timings. We will come back with how the day would be sequenced, where the turnover pressure sits, and what the property needs to confirm in writing before the design is signed off.