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.
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, decision authority, and incident notes. Build it as one organized packet or shared file assigned to a lead planner, locked at the 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 internal schedule covering every milestone from vendor arrival to send-off, with a named owner assigned to each line. It should be detailed enough that any team member can pick it up mid-event and know exactly 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 just 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 event phase, 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.
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.