Planning
How to Write an Event Running Order People Can Actually Use
A running order is not a minute-by-minute prediction. It is a shared record of what needs to happen, in what sequence and who is responsible. The best version is short enough to consult during the event and detailed enough to prevent the same questions being asked repeatedly.
List the fixed moments first
Begin with the elements that genuinely have a fixed time: access, a ceremony, a planned meal or the point at which the room must be clear. Confirm these with the relevant people before arranging everything else around them. Keep provisional timings visibly separate from confirmed ones.
Then add the main guest-facing moments. Arrival, seating, food, speeches and music create a sequence, but their exact order depends on the occasion. Do not copy a sample timetable so closely that it starts dictating a day nobody actually wants.
Write the transitions, not just the highlights
A schedule can look spacious until it is time for everyone to move. Include the interval between a speech ending and a meal beginning, or between guests arriving and finding their places. Ask what needs to happen in that interval and whether somebody needs to give a cue.
Also consider what is being reset behind the scenes. A room change may require equipment, furniture or serving items to move. Put those tasks in the working plan rather than treating the gap on the page as unallocated time.
Give every task a clear owner
Use a named role for each practical action, such as event coordinator, catering lead or music operator. A line saying play the entrance track is incomplete unless somebody knows they are responsible for starting it. Agree the role with the person involved; writing it down is not the same as arranging it.
A useful working row contains four items: time or cue, action, responsible role and any dependency. For example, a speech might begin after plates are cleared rather than at a rigid minute that conflicts with service. Mark which entries depend on a cue and which are fixed.
Keep the guest version simpler
Guests usually need the outline, not the delivery schedule. Separate their useful information from setup tasks and internal notes. A concise programme can explain the flow without asking everyone to track equipment checks or supplier access.
Share practical access and dietary information only with the people who need it. The widely circulated running order is not the right place for private details. A separate, appropriately handled record can support the relevant team without turning personal information into a general attachment.
Review it as a walk-through
Read the plan from the perspective of someone arriving for the first time. Who welcomes them? How do they know where to go? What happens if one part runs late? Discuss those questions with the people delivering the event and agree how changes will be communicated.
Finally, add a version date and make it clear which copy is current. A plan everyone understands is more valuable than an exquisitely formatted timetable that changed in three different message threads.
Explore the subject: Event planning.
