Wedding day timelines and run-of-show documents built from your templates
Every planner has a timeline template, and every event means rebuilding it by hand from emails, vendor details and the couple's wishes. We build a workflow that drafts the wedding day timeline or run of show from your template and the details already in your CRM, vendor records and RSVPs, keeps versions in sync as things change and sends each vendor, coordinator and family member their own view. The planner approves every version. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why wedding day timelines take hours to rebuild
A wedding day timeline or conference run of show pulls from everywhere: ceremony time, sunset, travel between locations, vendor arrival times, speeches, first dance, last orders. Building it takes hours and every late change means editing several copies.
Different people need different views. The photographer needs shot times, the caterer needs service times, the parents need when to be where. Sending the full document to everyone causes confusion; editing separate versions causes errors.
What we build
What our run of show automation includes
Draft from your template
Your timeline or run-of-show template filled from event details, vendor arrival times and guest numbers.
Smart checks
Gaps, overlaps and travel times between locations flagged for the planner to review.
One source, many views
Role-based views for each vendor, the coordinator team, the couple and family, all from one master.
Version control
Every change dated and named, with affected people notified of what changed.
Google Sheets or Docs
Run of show kept in Google Sheets or Docs so the team can edit on any device.
Day-of contact sheet
Names, roles and phone numbers for everyone working the event.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Details gathered
Event, vendor and RSVP details are pulled into the master timeline.
-
02
Automated
Draft built
A draft timeline is assembled from your template.
-
03
Automated
Views generated
Role-based views are created from the master.
-
04
Coordinator review
Coordinator checks
The coordinator checks flagged gaps and overlaps and fixes details.
-
05
Lead planner decides
Planner approves
The lead planner and the couple or client approve the timeline before it goes out.
How it behaves
How timelines and role views behave
What each person sees
- Their own view of the timeline
- A clear note of what changed and when
- Day-of contacts they need
What the planner sees
- A draft built from the template
- Gaps and overlaps flagged
- One master with full version history
What the automation does
- Pulls details from the CRM and vendor records
- Fills the template and generates views
- Sends change notices to affected people
Edge cases and fallbacks
- Two vendors need the same space at once
- Flagged as an overlap for the planner to resolve.
- Vendor arrival time missing
- Marked as a gap and added to the vendor confirmation list.
- Couple edits the shared document directly
- The change is logged and the planner reviews it before views update.
- Google or workflow outage
- The last approved PDF stays available and the planner is alerted.
Architecture
Timelines and run of show for an event at a glance.
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Event details and vendor arrival times are pulled from your systems.
- 2 n8n fills your template and flags gaps, overlaps and travel times.
- 3 The master timeline lives in Google Sheets or Docs for the team.
- 4 After the planner approves, each role gets its own view and change notices.
Project planner
How the project runs, phase by phase.
Wedding day timelines & run-of-show documents project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Current templates, data sources, roles and how changes are shared today.
-
02
Design
About 1 week
Template structure, role views, checks and version rules.
-
03
Build
1 to 2 weeks
Data pulls, template filling, checks, views and notices.
-
04
Shadow run
About 1 week
An upcoming event built side by side with your manual timeline.
-
05
Launch
1 to 2 days
Switch on for new events and train the team.
-
06
Support
Ongoing
New templates for event types and venues.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Templates, roles, checks and version rules.
$200 – $400
-
Build
Data pulls, template filling, checks and views.
$500 – $1,300
-
Integrations
Planning platform, Google Workspace and vendor records.
$150 – $400
-
Testing and shadow run
An event built side by side with your manual timeline.
$100 – $250
-
Launch and training
Switch-on and team training.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Extra templates for different event types can be added later. Google Workspace and n8n costs are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Google Workspace: Your existing Google Workspace plan.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
- AI model usage: Pay-per-use fees for drafts and checks, usually small.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
Day-of contacts shared on a need-to-know basis
Role views include only the contacts each person needs, in line with data minimisation and processor terms (GDPR Article 28).
Source: gdpr-info.euAccess needs are health data
Guest access and medical notes are special category data under Article 9 GDPR, so they appear only in the coordinator view.
Source: gdpr-info.euPeople decide on the day
The timeline is a plan; safety, weather and venue decisions on the day are made by the planner and venue staff.
Free tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Wedding day timeline and run of show questions questions, answered.
Start from fixed points, such as ceremony time, sunset and venue rules, then add vendor arrivals, photos, meal service and entertainment with buffers. The workflow fills your template from those details and flags anything that does not fit.
Yes. Many planners already keep a run of show template in Google Sheets; we fill it automatically and generate views from it.
A minute-by-minute plan of an event: who does what, when and where. It is the working document for the coordinator team on the day.
No. It drafts from your template and flags issues. The planner, couple or client approve every version.
Change the master; the workflow updates every view and tells each affected person what changed.
Hours spent building timelines, versions per event, change notices acknowledged and day-of issues traced to outdated timelines.
Free 20-minute call
Want this for your event & wedding planner?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for event & wedding planners
All servicesWedding & event planner CRM automation
Capture every inquiry from your website, directories, Instagram and email into one planner CRM pipeline, with stage-based follow-ups, consult booking and a monthly view of where booked clients come from.
From $1,000 · About 4 weeks Details
AI inquiry assistant & wedding inquiry responses
Reply to every wedding and event inquiry in minutes with a personal, on-brand response, ask the qualifying questions, answer FAQs from your approved wording and pass hot leads to the planner.
From $2,500 · About 5 to 8 weeks Details
Contracts, retainers & payment schedules
Send the right contract and retainer invoice the moment a proposal is accepted, chase signatures politely, and remind clients of every payment milestone until the final balance is paid.
From $1,000 · About 3 to 4 weeks Details