Wedding Vendor Contact List Template for Indian Weddings

The painful version of vendor coordination is not that one phone number is missing. It is that the missing number gets discovered at 6:20 AM, while decor is waiting at the wrong gate, the sound vendor is calling the bride's brother, and the venue security guard has no idea who approved load-in.

The outcome you want is simple: anyone running the wedding should be able to reach the right vendor, confirm the right fact, and escalate to the right person in under 30 seconds. This template gives Indian wedding planners a contact list that works during production week, not just inside a planning spreadsheet.

What should be in a wedding vendor contact list?

A wedding vendor contact list should include every operational contact needed to run the wedding without calling the couple: company name, vendor category, contract owner, on-site lead, assistant contact, WhatsApp number, arrival time, payment status, dependencies, venue access notes, and escalation rules.

The fast decision rule: if a person could delay setup, payment, travel, food service, decor, rituals, photography, or guest movement, their contact belongs in the list. If a person only needs guest-facing information, keep them out of the private vendor sheet.

| Column | What to enter | Why it matters | | --- | --- | --- | | Vendor category | Decor, catering, photography, sound, transport, priest, venue | Helps the team filter quickly | | Company name | Legal or brand name | Avoids confusion when owners use nicknames | | Contract owner | Person who sold or signed the scope | Useful for scope and payment disputes | | On-site lead | Person physically present at the function | The most important production contact | | Assistant contact | Backup on-site number | Saves time when the lead is in setup | | WhatsApp number | Primary chat number | Most Indian wedding vendors coordinate here | | Arrival time | Load-in time, not guest-ready time | Prevents late setup | | Setup complete | Time the area must be ready | Connects vendors to the run sheet | | Payment status | Paid, balance due, release owner | Prevents event-day blockers | | Dependency | What must happen before this vendor can execute | Shows chain reactions | | Escalation owner | Planner, venue, family, or vendor owner | Stops random calls to the couple |

A wedding vendor contact list is the private production roster that tells the planning team who to contact, when to contact them, and who can make a decision for every vendor involved in the wedding.

How is this different from a vendor communication checklist?

A vendor communication checklist tells you what to confirm. A vendor contact list tells you who can confirm it during the wedding. You need both because a beautifully written brief is useless if the only saved number belongs to the sales manager who is not on-site.

Use the wedding vendor communication checklist to confirm scope, load-in, payments, dependencies, and staffing. Then move the final people and numbers into this contact-list template so the production team can act quickly during haldi, mehendi, sangeet, pheras, reception, and checkout.

The failure mode is predictable:

• The decorator founder promised a floral entry, but the on-site lead only has the mandap brief.
• The caterer knows the Jain meal count, but the service captain does not.
• The photographer has the family shot list, but the assistant handling candid coverage does not.
• The transport vendor gave the planner one office number, while drivers are calling the hotel desk.

The contact list exists to close that gap.

Which vendors should go into the master contact list?

Every vendor who can affect timing, guest movement, money, safety, rituals, or the couple's experience should go into the master contact list. For Indian weddings, that usually means more categories than a standard single-day wedding.

Start with this vendor set:

| Vendor type | Contacts to capture | Notes | | --- | --- | --- | | Venue | Banquet manager, security gate, housekeeping, AV room | Add separate numbers for each venue if events move | | Decor | Owner, on-site supervisor, floral lead | Include load-in gate and overnight setup rules | | Catering | Event manager, service captain, bar lead | Keep Jain, vegan, allergy, and vendor-meal notes nearby | | Photography/video | Lead photographer, cinematographer, editor/runner | Add family photo coordinator if separate | | Makeup/hair | Lead artist, assistant, salon desk | Add getting-ready room and arrival slot | | Priest/officiant | Priest, assistant, family ritual captain | Add ceremony items and language preference | | Sound/light | Sound engineer, light operator, generator contact | Add rehearsal and mic check time | | Entertainment | Choreographer, DJ, artist manager, emcee | Add performance order and cue owner | | Transport | Fleet owner, driver captain, hotel pickup lead | Link to the shuttle and rooming lists | | Hospitality | Desk lead, luggage captain, concierge lead | Useful for destination and NRI weddings | | Stationery/gifts | Welcome-bag lead, print vendor, signage vendor | Add delivery and storage location | | Security/permissions | Venue security, police permission contact if applicable | Keep sensitive contacts limited |

For food-specific details, pair the roster with the Indian wedding catering checklist. For hotel and airport movement, connect it to the wedding hotel rooming list and NRI wedding guest travel form.

Who should have access to the vendor contact list?

The vendor contact list should be shared with the people who will actually solve operational problems: lead planner, planner assistant, venue coordinator, hospitality desk lead, transport captain, and one trusted family captain. Do not turn it into a guest document.

Use access levels:

| Person | Give access to | Do not give access to | | --- | --- | --- | | Lead planner | Full contact list, payments, escalation notes | Nothing withheld | | Planner assistant | Full vendor roster and run sheet | Sensitive payment amounts if not needed | | Venue coordinator | Load-in vendors, security, housekeeping, AV | Family private numbers | | Hospitality desk | Transport, hotel, guest help, planner escalation | Vendor payment notes | | Transport captain | Drivers, hotel desk, airport pickup lead | Decor, makeup, photography private notes | | Family captain | Emergency planner, priest, key hospitality contacts | Every vendor's private number | | Couple | Final escalation only | Routine vendor calls |

Guests should get the clean version: itinerary, venue pins, transport timing, dress code, food notes, and who to contact for help. Put that into the wedding website, guest PDF, or Mandap Chat for wedding planners so the private vendor roster does not leak into family WhatsApp groups.

When should you finalize vendor contacts?

Finalize the wedding vendor contact list seven days before the first event, then reconfirm it 48 hours before production begins. The seven-day check catches staffing changes. The 48-hour check catches phone numbers, arrival times, and escalation gaps.

Use this timing:

| Timing | What to confirm | Output | | --- | --- | --- | | 30 days out | Vendor categories, contract owners, broad scope | Draft roster | | 14 days out | Load-in rules, venue access, dependencies | Logistics-ready roster | | 7 days out | On-site leads, assistants, phone numbers | Production contact list | | 48 hours out | Arrival times, setup-complete times, escalation rule | Final contact list | | Morning of event | Any changed phone, driver, or security contact | Live correction note |

Do not accept "same as before" as confirmation. Ask vendors to reply with the exact on-site lead and number. If the answer is a voice note, convert the important details into text and paste them into the list.

What is the best format for the contact list?

The best format is a shared spreadsheet with locked column names, filtered vendor categories, and one printable PDF version for the planner desk. A contact list is only useful if it stays readable on a phone, laptop, and printed clipboard.

Keep the master sheet simple:

1. One row per vendor category per function when the contacts differ.
2. One primary phone number and one backup phone number.
3. Separate fields for contract owner and on-site lead.
4. A short note field for access, payment, or dependency warnings.
5. A final-confirmed timestamp.

Avoid these mistakes:

• Combining three vendors into one cell.
• Saving contacts only inside individual WhatsApp chats.
• Using nicknames like "DJ guy" or "decor uncle".
• Mixing guest help numbers with vendor escalation numbers.
• Letting each planner keep a private version.

WhatsApp Business labels can help teams organize chats by status or category, and WhatsApp's own help center describes labels as a way to organize and quickly find chats (WhatsApp labels guide). That is useful, but labels are not a substitute for a master sheet because labels do not show dependencies, payment status, or setup-complete time.

How should you use WhatsApp without losing control?

Use WhatsApp for quick confirmations, but keep the source of truth in the contact list and run sheet. WhatsApp is where vendors reply. The spreadsheet is where the planning team decides what is final.

The clean workflow:

1. Send the vendor a numbered confirmation message.
2. Ask for the exact on-site lead and backup number.
3. Paste the confirmed details into the contact list.
4. Mark the final-confirmed timestamp.
5. Share only the final run sheet and vendor-specific details back to the vendor.

For one-to-many updates, WhatsApp's Help Center says broadcast lists let you send a message to several contacts at once without recreating the list each time (WhatsApp broadcast lists guide). For wedding planners, broadcasts can work for general reminders, but never use a broadcast as proof that a critical vendor has confirmed. You still need individual acknowledgement from each vendor.

Use this message:

Hi [Name], final vendor contact confirmation for [Wedding / Event]. Please reply with:

1. On-site lead name and phone
2. Backup contact name and phone
3. Arrival time
4. Setup complete by
5. Any access, payment, or dependency issue

We will use this as the production-week contact list.

What should the final template look like?

The final template should be short enough to scan under pressure and complete enough to prevent bad calls. Do not make the contact list a project-management novel. Make it a command sheet.

Copy this structure:

| Field | Example | | --- | --- | | Function | Sangeet | | Vendor category | Sound and lights | | Company | Rhythm Events | | Contract owner | Arjun Mehta | | Contract owner phone | +91 XXXXX XXXXX | | On-site lead | Sameer | | On-site lead phone | +91 XXXXX XXXXX | | Backup contact | Pooja | | Backup phone | +91 XXXXX XXXXX | | Arrival time | 2:00 PM | | Setup complete | 5:00 PM | | Dependency | Stage decor complete before light focus | | Payment status | Balance release after setup check | | Venue access | Service gate 2, basement lift | | Escalation owner | Lead planner | | Final confirmed | June 17, 7:45 PM |

For multi-day weddings, add a "function" column instead of creating separate files for every event. One master filtered sheet is easier to maintain than six competing sheets.

How does the contact list connect to the run sheet?

The vendor contact list identifies the people. The run sheet identifies the timing. They should agree with each other before the planner shares either document with the production team.

Before locking the final wedding day run sheet, check:

• Every vendor in the run sheet exists in the contact list.
• Every arrival time in the contact list matches the run sheet.
• Every setup-complete time has a named owner.
• Every dependency has a realistic time buffer.
• Every payment blocker has a release owner.
• Every event has at least one planner escalation number.

This is where many weddings quietly break. A contact list says "decor arrival 2 PM"; the run sheet says "photography family portraits 3 PM"; the venue says "decor load-in allowed after 3:30 PM." The sheet is not the point. Finding conflicts before production week is the point.

How can Mandap Chat reduce vendor-contact chaos?

Mandap Chat reduces vendor-contact chaos by moving guest questions away from the people managing vendors. The planner still owns the private vendor roster, but guests can ask the AI concierge about schedule, venue, dress code, transport, food, hotel rules, weather, and help-desk instructions.

That split matters during production week. If the hospitality phone is answering "where is the mehendi?" for the 60th time, the same phone may miss a driver, caterer, or venue access call. Upload the guest-facing answers once, then let guests self-serve.

Use Mandap Chat for:

• Venue pins and room names.
• Transport pickup points.
• Dress codes and footwear notes.
• Jain food, allergy, and meal timing answers.
• Rain-plan instructions.
• Hotel desk rules.
• Help-desk escalation instructions.

Keep the private vendor list with the planner team. Give guests instant answers without giving them the decorator's, caterer's, or priest's personal number.

The 20-minute setup checklist

If production week has already started, build the 80/20 version now.

1. List every vendor category involved in the next 72 hours.
2. Add one decision-maker and one on-site lead for each vendor.
3. Add arrival time, setup-complete time, and venue access note.
4. Mark any payment balance that could block setup.
5. Add dependencies in plain language: "decor before photo", "sound before rehearsal", "transport before baraat".
6. Send the final contact confirmation message to each vendor.
7. Paste replies into one shared sheet.
8. Add the contact-list link to the private planner run sheet.
9. Put guest FAQs into Mandap Chat or a guest-facing itinerary so the vendor phone stays clear.

The goal is not a perfect spreadsheet. The goal is a calm command center where nobody has to ask the couple, "Do you have the decorator's number?"

FAQ

What should be in a wedding vendor contact list?

A wedding vendor contact list should include vendor category, company name, contract owner, on-site lead, assistant contact, WhatsApp number, arrival time, setup-complete time, payment status, dependencies, venue access notes, and escalation rules.

Who needs access to the wedding vendor contact list?

The lead planner, production assistant, venue coordinator, hospitality desk, transport captain, and one trusted family captain need access. The couple should be a final escalation point, not the default phone number for every vendor issue.

How many contacts should each wedding vendor provide?

Each critical vendor should provide at least two contacts: one decision-maker and one on-site lead. For destination weddings or multi-day Indian weddings, add an assistant contact because the owner may be unavailable during setup.

Should vendor contact lists be shared with guests?

No. Guests should receive guest-facing help information, not the private vendor contact list. Share schedules, venue pins, transport, dress code, food notes, and help-desk instructions through the itinerary, wedding website, or AI concierge.

When should the vendor contact list be finalized?

Finalize it seven days before the first event, then reconfirm 48 hours before production begins. The final check should confirm on-site leads, phone numbers, arrival times, setup-complete times, and escalation paths.