Operations guide
How to Build a Wedding-Day Command Center for the Planning Team
A practical guide to building a wedding-day command center: run of show, contacts, layouts, decision authority, and backup plans for the whole team.
The short answer
A wedding-day command center is the single, offline-accessible source the planning team relies on for the run of show, contacts, layouts, arrival times, decision authority, and incident notes. Build it as one organized packet or app view assigned to a lead planner, reviewed at final walkthrough, and updated the moment anything changes on-site.
What belongs in the run of show?
The run of show is a minute-by-minute schedule covering every milestone from vendor arrival to send-off, with an owner assigned to each item. It should be detailed enough that any team member can pick it up mid-event and know what happens next.
The run of show is not the client-facing timeline. It includes internal buffer time, setup and teardown windows, vendor arrival and departure times, and cues for transitions like the processional or first dance. Every line should name who is responsible for making it happen, not just what is happening.
Build it from the finalized vendor timeline and client schedule, then add the operational detail clients never see: which door the caterer uses, when linens go down, when the DJ needs a sound check. Update it only after the final walkthrough confirms all vendor times.
- List every milestone with a specific time, not a time range
- Assign a named owner to each line item, not a role
- Include setup and breakdown windows for every vendor
- Build in buffer time between transitions that commonly run long
- Note which items are flexible and which are fixed by contract
Which contacts need to be on the sheet, and how should they be organized?
Every vendor, venue contact, and key wedding party member needs a phone number, arrival time, and one-line role description on a single sortable sheet. Organize contacts by arrival order or by function, not alphabetically, so the team can scan quickly under pressure.
A useful contact sheet groups people the way the day unfolds: early-morning vendors first, then ceremony contacts, then reception contacts, then late-night or breakdown contacts. Include a backup number where one exists, and mark who has signing or payment authority if final payments are due on-site.
Avoid cramming every historical contact from planning into this sheet. Only include people who are actually on-site or reachable during the event window.
- Group contacts by arrival time or event phase, not alphabetically
- Include a backup phone number wherever one is available
- Mark who has authority to handle final payments on-site
- Exclude vendors who are not present or reachable that day
- Note each contact's specific role in four words or fewer
How should venue layouts and floor plans be included?
Include the final approved floor plan for every space in use, labeled with table numbers, vendor setup zones, and access points. Print or save layouts as static images so they remain usable without an internet connection.
Layouts should match exactly what was confirmed at the final walkthrough, including any last-minute adjustments like a moved bar or an added lounge area. If the event uses multiple spaces, ceremony, cocktail hour, reception, label each layout clearly and order them to match the run of show.
Keep a version note on each layout so the team knows it reflects the latest confirmed plan rather than an earlier draft that may have been superseded.
- Include a separate labeled layout for each distinct event space
- Mark vendor setup zones, load-in paths, and guest access points
- Date-stamp each layout so outdated versions are not mistaken for current
- Confirm layouts match what was approved at the final walkthrough
How should arrival times and check-ins be tracked during the event?
Track actual arrival times against planned times in real time, using a simple checklist the on-site lead updates as vendors and wedding party members arrive. This creates a live record of what is running on schedule and what needs attention.
A basic checklist with planned time, actual time, and a status column is enough. The point is not documentation for its own sake, it is early warning. If a vendor is thirty minutes late, the team needs to know immediately so they can adjust the run of show rather than discover the gap when the moment arrives.
Assign one person to own this tracking for the full event so updates do not get missed between shift changes among team members.
- Record planned arrival time and actual arrival time side by side
- Assign one team member to own arrival tracking for the full day
- Flag any arrival more than fifteen minutes behind schedule immediately
- Use the tracking sheet to trigger run-of-show adjustments in real time
Who has decision-making authority when something goes wrong on-site?
Decision authority should be defined before the event, not negotiated during it. Typically the lead planner has final say on schedule and vendor issues, with named backups for weather calls, budget-impacting changes, or anything requiring client approval.
Write out a short authority list: who can approve a schedule shift, who can approve an unplanned expense, who can make the weather call for an outdoor ceremony, and who contacts the client if a decision needs their input. This prevents well-meaning team members from making calls above their authority or stalling on a decision that needed to happen five minutes ago.
If the lead planner is unreachable for any stretch of the day, a named second must know they hold authority during that window.
- Name the lead decision-maker and one designated backup in writing
- Define which decisions require client approval before acting
- Set a dollar threshold above which spending needs prior sign-off
- Clarify who makes the weather or contingency call, and by when
What communication channels should the team use during the event?
Use one primary channel for real-time coordination, typically a group text or a dedicated messaging thread, and reserve phone calls for urgent issues only. Avoid splitting communication across multiple apps, which causes missed updates during the busiest hours.
Set the channel and ground rules at the final team briefing: what counts as urgent enough for a call versus a text, how quickly team members are expected to respond, and who monitors the channel continuously versus periodically. If vendors need to reach the planning team, give them one number, not several.
Keep the channel focused on operational updates during the event. Save debrief conversations and non-urgent notes for after the wedding ends.
- Designate one primary channel for all real-time team coordination
- Reserve direct phone calls for genuinely urgent issues only
- Give vendors a single point of contact number for the day
- Set expected response times so no message goes unanswered too long
How should incidents, changes, and privacy concerns be handled and recorded?
Log any incident, change, or deviation from plan in a shared notes section as it happens, with a timestamp and the name of who handled it. Keep sensitive notes, family conflicts, medical issues, security concerns, accessible only to the lead planner and essential team members.
A brief incident log protects the studio and informs the post-wedding debrief. Note what happened, who was involved, what action was taken, and whether the client needs to be informed. Separate sensitive personal information from general operational notes so it is not visible to every team member or vendor who might see the shared document.
Have a backup plan for the command center itself: a printed copy, a downloaded offline file, and a designated person who carries it if the primary device fails or loses signal.
- Log incidents with a timestamp, description, and the person who responded
- Keep sensitive or personal notes restricted to essential team members only
- Maintain a printed or offline backup of the entire command center
- Assign a specific person to carry the backup copy at all times
- Review the incident log during the post-wedding debrief for patterns
Common questions
Who should own the command center on wedding day?
One lead planner owns the master version and has final authority to update it. Associates and assistants work from that version rather than keeping personal copies that can drift out of sync.
How far in advance should the command center be finalized?
Lock the core structure at the final walkthrough, typically one to two weeks out, then only update it for confirmed changes. Avoid major restructuring in the final 48 hours unless a vendor or timeline change forces it.
What happens if there is no signal at the venue?
This is why the command center must exist in a printed or downloaded offline format, not only in an app that requires connectivity. Test offline access during setup, before guests arrive.
Should clients see the full command center?
No. Clients typically get a simplified day-of schedule, while the full command center with vendor contacts, layouts, and incident notes stays internal to the planning team and key vendors as needed.
How is this different from the event-week checklist?
The event-week checklist tracks preparation tasks leading up to the wedding. The command center is the reference document the team actually uses during the event itself.
Continue the system
Related planner resources
Turn this guidance into a repeatable process for your planning team.