Wedding Services Editing and Proofreading Services

The wedding day timeline sent to every vendor says "ceremony 2pm, reception 6pm." The florist reads it as when to have arrangements in place. The caterer reads it as when to start serving. The photographer reads it as when to arrive. Nobody has been told who is actually in charge if the ceremony runs forty minutes late, whether the timeline that changes is the version everyone received or a version only the planner has, and what happens to the cocktail hour if the wedding party's photographs overrun. Six vendors are all working from the same two lines and building six different days around them.

We edit what wedding businesses and planners produce to coordinate a single day across many vendors — day-of coordination timelines, vendor contact and responsibility sheets, run sheets distinguishing who does what on whose signal, load-in and breakdown schedules, and the correspondence used to communicate a timeline change on the day itself. Our editors work on the document that has to keep a dozen businesses working from the same understanding of one unrepeatable day.

The specific, sequenced run sheet is what keeps a wedding day from drifting into six different versions of itself, and its failure is a timeline of headline events with nothing about who does what around them or who has authority to adjust it. Ceremony 2pm, reception 6pm tells every vendor when the big moments are and nothing about the ninety decisions in between. We work through these so each vendor's specific tasks are tied to a time and, where relevant, to a trigger rather than a clock time alone, since "florist to have centrepieces placed by 5:30pm" is clearer than a general instruction to be ready before the reception, and "caterer begins service once the wedding party is seated, confirmed by planner" accounts for a ceremony that runs long in a way a fixed clock time cannot; so one person is named as having authority to adjust the timeline on the day, given that a schedule with no single owner means every vendor either waits for someone else to decide or makes an independent call that conflicts with another vendor's independent call; so a single, live version of the timeline is maintained and any change is communicated to every affected vendor at the same time, because a change relayed only to some vendors recreates exactly the fragmentation the timeline was meant to prevent; so load-in and breakdown times are specified per vendor with any shared space or access conflicts flagged, as two vendors needing the same loading dock at the same time is a foreseeable problem if anyone actually checks the schedule against itself; so contingency for a common disruption — a ceremony delay, weather, a venue access issue — is addressed in advance with what actually happens next, rather than left to be improvised on the day; and so every vendor confirms receipt of the final timeline, given that a timeline sent and never confirmed is indistinguishable from a timeline never sent at all. Timelines written this way keep a dozen businesses moving as one day instead of six.

Everything you send is treated in confidence, including client details, vendor information and event plans. We are editors rather than wedding planners or event coordinators, and we offer no view on vendor selection or event logistics. What we can do is make sure every vendor is reading the same day.