Wedding Production Week Checklist for Indian Wedding Planners

The dangerous part of an Indian wedding is not the wedding day. It is the final week, when everyone thinks the plan is "almost done" and starts changing small details that break big systems.

One cousin adds six guests. A parent changes the reception entry time. The decorator's on-site lead is different from the person who sold the package. The hotel moves breakfast to another hall. Guests ask the same shuttle question in five WhatsApp groups. None of this looks dramatic alone. Together, it eats the planner's attention exactly when the planner needs to run production.

Use this wedding production week checklist to turn the final seven days into a controlled handoff instead of a panic sprint.

What is wedding production week?

Wedding production week is the final operating window before the first wedding event. The planner's job shifts from exploring options to executing confirmed decisions: vendors, family owners, guest communication, transport, rooming, payments, backup plans, and escalation rules.

In plain English: production week is when "we are considering" becomes "this is the plan." If a detail is still a preference debate during this week, it needs an owner, a deadline, and a consequence.

Wedding production week is the seven-day handoff period where the planner freezes the operating plan, confirms every execution owner, and separates guest support from vendor coordination.

The fast rule: if a change affects money, time, guest movement, food, rituals, transport, or vendor scope, it must go through the production decision owner. If it is only cosmetic and late, it waits.

What should be frozen before production week starts?

Before production week starts, freeze the facts that vendors, guests, and family owners need to execute without calling the couple. The plan can still handle real emergencies, but it should not be accepting casual changes.

Use this freeze list:

| Item | Freeze by | Owner | | --- | --- | --- | | Event schedule and venue rooms | 7 days out | Lead planner | | Guest arrival times and itinerary | 7 days out | Guest communication owner | | Vendor load-in and setup-complete times | 7 days out | Planner operations lead | | Final event-wise guest count | 5 to 7 days out | RSVP owner | | Rooming list and hotel desk notes | 5 days out | Hospitality lead | | Transport pickup points and shuttle windows | 5 days out | Transport captain | | Family photo lists and ritual cues | 4 to 5 days out | Family captain | | Guest reminder messages | 3 to 5 days out | Communication owner | | Final run sheet | 48 hours out | Lead planner |

This is why the wedding planner client update template matters earlier in the month. It turns open decisions into approved facts before they become production-week surprises.

What is the best seven-day production checklist?

The best seven-day checklist works backwards from the first event. Each day has one operating goal: confirm facts, remove ambiguity, and assign the person who can act when something changes.

Here is the practical version:

| Timing | Main job | Output | | --- | --- | --- | | 7 days out | Confirm vendors and family owners | Final owner roster | | 6 days out | Check guest data and hotel/transport lists | Clean guest movement plan | | 5 days out | Lock food, seating, and VIP exceptions | Caterer and seating handoff | | 4 days out | Publish guest reminders | One approved public answer set | | 3 days out | Check emergency kits and backup plans | Named owners for small problems | | 2 days out | Freeze run sheet and escalation tree | Final production command sheet | | 1 day out | Send short reminders, print backups, sleep | Calm execution mode |

This is not the week to redesign decor, rewrite the sangeet flow, rebuild the guest list, or change the communication system. Those are planning tasks. Production week is for controlled execution.

What should the seven-day vendor check include?

The seven-day vendor check should confirm who is actually coming, when they arrive, what they are responsible for, what can block them, and who decides if something conflicts on-site.

Confirm these fields for every critical vendor:

• Company and vendor category.
• Contract owner and on-site lead.
• Backup contact.
• Load-in time.
• Setup-complete time.
• Venue gate, lift, parking, and security notes.
• Payment balance and release owner.
• Dependency on another vendor.
• Staff meal or room requirement.
• Escalation contact.
• Final confirmation timestamp.

Do not rely on "already shared." Production teams change. Assistants replace founders. Drivers rotate. Venue gate rules shift. Use the wedding vendor contact list to make the people real, then use the vendor communication checklist to make the facts confirmed.

How should planners handle guest communication in the final week?

Guest communication should be treated as its own production system. Guests need clear answers, but they should not get access to the planner's private vendor channel or the family's decision thread.

Send one approved reminder for each function:

Tomorrow: Mehendi at 4:00 PM. Guest arrival from 3:30 PM. Venue: Palace Lawn, Hotel Arya. Dress code: festive greens, yellows, or florals. Snacks start at 4:15 PM. Shuttle leaves the hotel lobby every 20 minutes from 3:00 PM. Ask schedule, dress code, transport, or food questions here: [Mandap Chat link].

Every reminder should include:

• Event name.
• Guest arrival time.
• Venue or room name.
• Map pin or pickup point.
• Dress code.
• Food timing.
• Transport instruction.
• One question channel.

If guests are still asking basic questions in family WhatsApp groups, the public answer set is not complete. Put the approved schedule, venue pins, dress codes, transport notes, food rules, hotel information, and kids policy into Mandap Chat for wedding planners so guests can ask in their own words without interrupting vendor coordination.

Which production-week channels should stay separate?

Keep three channels separate: vendor execution, family decisions, and guest support. Mixing them is how good plans become unreadable.

Use this channel map:

| Channel | Who belongs | What goes there | | --- | --- | --- | | Vendor execution | Planner team, vendor leads, venue ops | Load-in, setup, timing, dependencies | | Family decisions | Couple, parents, approval owners, lead planner | Money, guest exceptions, ritual changes | | Guest support | Guests, hospitality desk, Mandap Chat | Schedule, venue, dress code, food, transport | | Internal planner ops | Planning team only | Staffing, task ownership, private risks |

WhatsApp can be useful for fast coordination, but it should not be the source of truth. WhatsApp's own help center explains labels and broadcast lists as ways to organize and send messages; planners can use those features for speed, but final facts still need to live in the run sheet, contact list, and guest FAQ (WhatsApp labels, WhatsApp broadcast lists).

What belongs in the 48-hour freeze?

The 48-hour freeze is the final operating version of the wedding. It should be short enough to execute under pressure and complete enough that the planner is not carrying the plan in their head.

Freeze these:

• Final wedding day run sheet.
• Vendor contact list with on-site leads.
• Event-wise guest count.
• Final rooming list and hotel desk instructions.
• Transport schedule and driver captain.
• Family photo call sheet.
• Ritual items and priest timing.
• Food service timing and dietary exception counts.
• Payment balance release owners.
• Weather or indoor backup trigger.
• Emergency kit owner and location.
• Guest reminder messages.
• Escalation tree.

After the freeze, allow only five types of change: safety, health, weather, accessibility, and unavoidable travel disruption. Everything else needs a very good reason.

What can go wrong if production week is loose?

Loose production weeks fail because nobody can tell which version of the plan is final. The planner may have the right answer, but the vendor, family, hotel desk, and guest all act from different documents.

Common failure modes:

• Two schedules: the guest itinerary says 7:00 PM while the vendor sheet says 7:30 PM.
• No owner: everyone knows the problem, nobody can approve the fix.
• Payment blocker: a vendor refuses setup because the balance owner is unavailable.
• Rooming mismatch: hotel desk, family, and transport captain use different guest counts.
• Guest noise: planner misses vendor calls while answering dress code and shuttle questions.
• Weather delay: nobody knows when Plan B becomes active.
• WhatsApp drift: a casual family message becomes an unofficial instruction.

The fix is boring: one run sheet, one guest answer set, one vendor roster, and one escalation tree.

What is the production-week escalation tree?

The escalation tree says who decides when the plan cannot execute as written. It prevents five people from debating a time-sensitive call in public.

Use this structure:

| Decision type | First owner | Backup owner | | --- | --- | --- | | Vendor timing | Lead planner | Planner operations lead | | Money or balance payment | Named family finance owner | Couple-approved backup | | Ritual timing | Priest plus family ritual captain | Lead planner | | Guest exception | RSVP owner | Family captain | | Hotel or room issue | Hospitality lead | Hotel coordinator | | Transport delay | Transport captain | Planner operations lead | | Weather backup | Lead planner plus venue manager | Couple/family approval owner | | Medical or safety issue | Venue emergency lead | Family emergency contact |

This table should be in the planner's phone, the printed production folder, and the internal team chat. It should not be posted to guests.

The 20-minute production-week reset

If production week has already started and the plan feels messy, do this now:

1. Open the current run sheet and mark the latest approved version.
2. Create one vendor contact list with on-site leads and backup numbers.
3. Write one guest-facing answer set for schedule, venues, dress code, food, and transport.
4. Put those guest answers into Mandap Chat, the website, or one official FAQ link.
5. Assign one owner for vendors, one for family decisions, one for guests, and one for transport.
6. Freeze any change that does not affect safety, weather, travel, accessibility, food count, or ritual timing.
7. Send a short "this is the final source of truth" note to the internal team.
8. Print the run sheet, vendor list, rooming list, and emergency contacts.

This is the highest-leverage move: stop trying to answer every question personally. The planner should be a command center, not a human search bar.

Where Mandap Chat fits

Mandap Chat belongs in the guest-support lane of production week. It should answer routine guest questions so the planner can protect attention for vendors, family cues, payments, setup, transport, weather, and timing.

Upload the final guest-facing facts:

• Event schedule and venue names.
• Map pins and pickup points.
• Dress codes.
• Food timing and dietary notes.
• Hotel block and rooming rules.
• Transport and shuttle instructions.
• Kids, plus-one, and accessibility notes.
• Emergency or help-desk contact.
• What guests should not call the couple about.

Then put the Mandap Chat link in every final-week reminder. Guests get instant answers. The planner keeps the vendor phone clean. That split is the difference between a busy final week and a chaotic one.

FAQ

What is wedding production week?

Wedding production week is the final seven-day operating window before the first wedding event. The planner moves from planning options to executing confirmed details: vendors, family owners, guest communication, transport, payments, backup plans, and escalation rules.

What should a wedding production week checklist include?

Include the final run sheet, vendor contact list, payment status, event-wise guest count, rooming list, transport schedule, family owners, emergency kit, weather backup, guest reminders, and one escalation tree for urgent decisions.

When should the wedding run sheet be frozen?

Freeze the run sheet 48 hours before production starts, after a seven-day confirmation pass with vendors and family owners. After that, only critical changes such as weather, safety, accessibility, travel disruption, and ritual timing should reopen the schedule.

How do planners avoid WhatsApp chaos during production week?

Separate vendor execution, family decisions, and guest support. Vendors use the private run sheet and escalation contacts. Families use a decision log. Guests use the itinerary, reminder messages, and Mandap Chat or another FAQ layer.

How does Mandap Chat help during production week?

Mandap Chat answers guest questions about schedule, venue pins, dress code, transport, food, hotel rules, and event access. That keeps the planner focused on execution instead of repeating the same guest answers across WhatsApp groups.