Planning a multi-day celebration

Several events that share one guest list

Many of the world’s great celebrations happen over more than one day. A Nigerian wedding may include an introduction, a traditional engagement and a church or civil ceremony with a reception. An Indian wedding may move through haldi, mehndi, sangeet, the ceremony and a reception. Many Western weddings now run as a weekend, with a welcome evening, the wedding and a farewell brunch. Family reunions, milestone birthdays and festivals often do the same.

Each function is an event in its own right, with its own venue, timing, dress code, menu and guest list. Yet they share guests, suppliers and a budget. The difficulty is keeping them distinct enough to plan accurately and connected enough that a change in one is reflected in the others.

Define each function clearly

Start by listing every function and writing a short profile for each: purpose, date and time, venue, expected size, who hosts it, dress code, food and drink, and whether seating is assigned. Some functions are intimate family affairs; others are large and public. Some are hosted by the couple or the celebrant, others by parents or friends.

This list becomes the spine of the whole plan. Every guest invitation, supplier booking, budget line and schedule entry should point to the function it belongs to.

• Purpose and tone of the function
• Date, start and end times, and venue
• Expected number of guests and who is invited
• Host, and who pays
• Dress code, including any coordinated family colours
• Food, drink and whether seating is assigned

Invite per function, reply per person

Not every guest is invited to every function, and not every invited guest attends every one. Record invitations per function, so that the close family invited to the introduction and the wider circle invited to the reception are each clear. Then collect replies per person per function.

A worked example shows why. Suppose 120 people are invited to a mehndi, 300 to the sangeet and 400 to the reception. A household of five might attend all three; a colleague might attend only the reception; a grandparent might skip the late sangeet but come to the others. A single yes or no per invitation cannot capture this, and every catering count, seating plan and shuttle booking depends on it.

Show each guest only the functions they are invited to, ideally through a personal link. This avoids awkward questions from guests who were not invited to the smaller gatherings.

For multi-day events, the unit of planning is the person at a function. Headcounts, meals, seats and door lists all come from that.

Pace the schedule for guests

A celebration that runs over several days is a marathon for guests as well as hosts. Leave breathing space between functions, especially when guests must change outfits, travel between venues, or look after children. A late night followed by an early ceremony is hard on everyone, particularly older guests.

Write a single combined schedule for each guest showing only their functions, with times, venues, dress codes and transport. Make clear which parts are optional, such as a casual brunch, so guests do not feel obliged to attend everything.

Catering across functions

Each function needs its own catering count, and they rarely match. The menu may also change in character: a lighter daytime meal, a buffet at a festive evening, a plated dinner at the reception. Collect meal choices and allergies per function where the menu differs, and share each count with the caterer for that function.

Allergy information should travel with the guest across functions. If a guest has a severe nut allergy, every kitchen serving them needs to know, which is easy to forget when different caterers serve different days.

Travel and accommodation

Multi-day celebrations often mean guests stay for several nights. Reserve rooms near the venues where you can, and ask on the reply form when guests arrive and leave and where they are staying. This tells you who is around for each function and who might need transport.

If functions are in different places, plan transport between them, with shuttle times shared well in advance. Ask guests who need step-free transport to say so, and make sure any shuttle can accommodate them.

Seating for each function

Functions with assigned seats each need their own plan, built from that function’s replies. Some principles carry across: households together, guests of honour placed with care, access needs met. But the room and the purpose change, and so do the right placements. Elders may be seated prominently at a traditional ceremony and nearer the exit at a late reception.

Keep each plan separate so that a change to one does not quietly alter another, and make sure place cards and door lists are produced from the right function’s plan.

Suppliers who work more than one day

Some suppliers will work several functions, such as a photographer covering the whole celebration or a decorator transforming one venue for successive events. Others will serve only one. For each supplier, record which functions they cover, their arrival and finish times at each, and the payment schedule.

Write a run of show for each function and a short overall schedule that shows where every supplier needs to be and when. Handovers between functions, such as a venue being turned around overnight, are where things go wrong, so give them their own line on the schedule and a named person responsible.

Dress codes and coordinated attire

Each function often has its own dress code, and some traditions add coordinated colours or fabrics for family groups and close friends. Guests need this information early, because outfits may need to be bought, made or tailored, and fabric may need to be ordered and collected.

State the dress code for every function on each guest’s schedule, in plain words with an example or two. If you are coordinating fabric or colours, say who it applies to, how to order, the cost if any, and the date by which it must be collected. Keep a simple record of who has ordered, so that nobody arrives at the family photograph in the wrong colour without having been told.

A budget that knows which function is which

Assign every cost to a function, with shared costs such as the photographer split or recorded as shared. This shows which function is driving spending and makes conversations easier when different family members host different parts.

Track commitments and payments per function. With several hosts contributing, it helps everyone to see what has been agreed and paid for the part they are responsible for.

Bringing the days together

The challenge of a multi-day celebration is keeping many moving parts in step. Attergo treats each function as its own event within one celebration, with per-function invitations, replies per person, separate seating plans and door lists, and a single budget that knows which function each cost belongs to. Whatever you use, the core discipline is the same: define every function, record invitations and replies at the level of the person at the function, and let every plan flow from that.