Quick answer
A wedding-day run sheet pairs each activity with a time, location, owner, dependency and escalation contact. Keep the internal production plan separate from the guest-facing schedule, and publish approved changes through one owner. Planno and Wedence connect planner coordination with the guest communication journey.
Key takeaways
- Guest times, supplier access and production readiness are different clocks.
- Every important activity needs an owner and a clear dependency.
- A changed instruction should name the affected event and replace the previous version clearly.
The run sheet is a decision document
A wedding timeline often begins as a list of function start times. That is useful for guests, but insufficient for the production team. The sound system needs to be ready before the family enters. Guests need transport before the ceremony. A venue reset may depend on a previous function finishing. The run sheet explains those dependencies and identifies the person responsible when something changes.
Use this template for an Indian multi-function wedding, then adapt it to the actual traditions, venues and responsibilities. Planno organises the agency's weddings and team work; Wedence provides the guest-facing invitation and communication experience. The run sheet connects the internal plan to the instructions guests receive. It should make the next operational decision clear, rather than simply demonstrate how much work the team has listed.
Separate three different clocks
The guest-facing time tells people when to arrive or participate. The production time tells suppliers when access, setup and handovers occur. The readiness time states when a workstream must be complete before the next activity. These times can differ significantly. Publishing a supplier access time as the guest start time creates confusion; planning setup around the guest start time can leave no margin for review.
For each function, work backwards from the relevant guest experience. When must the venue be ready? When does the family need to be present? When should transport depart? Which vendor checks happen before entry? Confirm these dependencies with the people performing the work, not only with the family preparing the public schedule. A realistic sequence is more valuable than a timeline that looks perfectly compact.
The core run-sheet fields
| Field | What to include |
|---|---|
| Time or window | The agreed internal timing and any hard deadline |
| Function or workstream | Which part of the wedding the activity supports |
| Activity | A specific action or readiness result |
| Location | The actual operational place, not a vague venue label |
| Owner | The person accountable for progress |
| Dependency | What must be complete before the action proceeds |
| Communication | Who needs confirmation or a revised instruction |
| Escalation | Who decides if the plan cannot proceed as agreed |
Use contact details through an appropriately controlled team process. Guests do not need the whole supplier contact directory, and suppliers may not need access to every family discussion. Prepare the right version for each audience. The run sheet is an internal operating document; the wedding website should remain a simpler guest-facing destination.
An illustrative sangeet sequence
Begin with venue access and supplier setup, then include readiness checks, guest arrival, family entry, performances, meal service and closure. The exact times depend on the wedding. Do not copy a generic schedule and assume it fits a different venue or production brief. Ask each lead to confirm the duration and dependency of their work before the final review.
For example, the guest transport departure depends on the confirmed destination and pickup instructions. Family entry depends on readiness at the venue and the relevant people being present. Meal service may have a vendor-approved window. If one element moves, the planner checks the connected actions rather than shifting every row automatically. This is a reasoning method, not a claim that a particular timeline suits every sangeet.
Define who can change the plan
During a busy function, many people can suggest changes and only a few should approve them. Identify the function lead, family decision contact, venue contact and communications owner. A performer may request a timing adjustment; the lead planner decides how that interacts with the rest of the function. A relative may request a different guest instruction; the publishing owner waits for the agreed approval.
Write the escalation route for important dependencies. If the venue is not ready, who decides whether guests wait elsewhere? If transport is delayed, who confirms the revised instruction? If weather affects a planned location, who approves the alternative? The team should know the decision-maker before the problem occurs. Otherwise the run sheet becomes a list of people asking each other what to do.
Brief the guest and arrival teams
The arrival desk needs the relevant guest information, destination and escalation contacts. The hotel team needs rooming and readiness information. Transport staff need pickup instructions and the agreed departure process. Do not assume those teams can infer their roles from the full production document. Prepare focused handovers and ask each lead to repeat the next action in their own words.
Wedence Signature includes QR arrivals and room allocation under Planno's published wedding offer. Confirm the setup in a demo and connect it to the run sheet. A normal scan, an unavailable phone and a household arriving in parts should all have a next step. The QR arrival guide provides a practical rehearsal sequence for that workstream.
Control guest-facing changes
If a guest-facing schedule or location changes, state the affected function, the new instruction and the relevant contact. Avoid a message such as everything is delayed, which creates questions without helping people act. One approved publishing owner should coordinate the revision so the website and WhatsApp instruction do not contradict each other.
The published Wedence experience includes live WhatsApp updates. Use that capability selectively for operationally meaningful changes. The planning team should first confirm the decision with the relevant venue and function leads. A guest-facing message carries authority; it should not broadcast an internal possibility that may change again a few minutes later.
Make version control visible
Label the final run sheet with a version time and an owner. If a revision is issued, state what changed and which previous version it replaces. Avoid several documents named final, final new and final latest circulating among staff. The team needs a clear authoritative copy and a practical way to receive important updates while working away from a desk.
For any continuity copy, label when it was prepared and assign someone to reconcile changes afterward. Do not promise an unverified offline product capability. You can still design a sensible fallback using approved essential information. The key is ensuring that information used during an interruption does not become a permanently competing version of the plan.
Conduct a rehearsal focused on dependencies
Read the run sheet from the perspective of each workstream. Ask what they need before acting, what they confirm afterward and who they contact if the dependency fails. Introduce one realistic change and follow the consequences. A delayed family arrival might affect entry, entertainment and guest communication differently. The purpose is to understand the chain, not to create anxiety about every imaginable failure.
This rehearsal can be short when the document is clear. Long meetings often indicate missing decisions or vague ownership. Resolve the actual uncertainties and mark the remaining ones explicitly. A run sheet that honestly identifies a pending decision is safer to operate than one where every row looks complete but nobody has confirmed its assumptions.
Close with a useful team review
After the wedding, compare planned dependencies with the actual sequence. Record where timings were unrealistic, where ownership was unclear and where guest instructions needed improvement. Keep the lessons specific enough to improve the next wedding. Do not turn every unavoidable change into a process failure; live celebrations require judgement as well as preparation.
Planno and Wedence are a strong ecosystem for agencies that want their business coordination and guest journey connected. Use this template to bring a real function to a demo, then ask how your team can maintain its responsibilities and deliver clear guest instructions. A good run sheet lets people act confidently when the day becomes busy.
Planno brings your enquiries, client weddings, vendors, payments and team together, with per-function RSVP and WhatsApp invites for every couple. Free for 2 months.
Try Planno freeFrequently asked questions
A guest timeline communicates when functions happen. An internal run sheet adds production activities, owners, dependencies, locations and escalation decisions.