Day of Event Timeline: How to Build One (+ Template)

By RunCue · 4 November 2026 · 10 min read

A day of event timeline is one schedule, broken into time blocks, that runs from load-in to the last guest leaving. It tells every venue contact, vendor, staff member and speaker where to be, what happens when, and who is responsible. Below is a template structure you can copy, with columns for each role, that works for any event.

What is a day of event timeline and who needs one?

A day of event timeline is the hour-by-hour schedule for the event day: load-in, vendor arrivals, setup, doors open, the run of show, strike and closeout. It tells you who is where, doing what, and when.

It's different from the run of show, which only covers the program from the first cue to the last. And it's different from the planning checklist, which covers the weeks of preparation. The timeline brings all of the day's moving parts into one schedule.

Give load-in more time than you think you need. AV and staging crews usually want to arrive well before doors open so they have time to set up, test and fix whatever isn't working, so build that lead time into the load-in block. Plan the money separately with an event budget template.

The people who use it are your planners, the venue coordinator, vendors, staff and often the client. A tool like RunCue keeps that one schedule in front of all of them, though a shared document works too.

What should a day of event timeline template include?

A template only holds up on the day if every row says who, what, where, and what has to happen first. Nine fields cover that: time, duration, block, owner, role, location, contact phone, dependencies and status. Leave out the phone column and you'll be scrolling through texts at 7 a.m. on load-in day. Leave out dependencies and a late caterer will hold up the seating chart without anyone noticing.

The nine columns that matter

Time, duration and block give you the outline. Owner, role, location and contact phone tell people what to do and how to reach each other. Dependencies and status are what let you actually run the day from it. Mark each row as not started, in progress or done, and anyone who opens the sheet can see where things stand. RunCue's run of show covers most of these columns for the day itself (time, end time, owner, location, notes and status), and its calendar is kept for planning deadlines.

One timeline or per-role views?

Keep one master timeline and give vendors, staff and speakers filtered views of it. A florist doesn't need your closeout rows, and your staff don't need every vendor arrival. Because every view comes from the same master, there's never a question of which copy is right.

How do you structure timeline blocks for load-in, doors, and closeout?

Break the day into seven blocks: load-in and vendor arrivals, setup and AV check, staff briefing, doors open, the show itself, teardown, and closeout. A block only ends when someone confirms a specific fact, and that confirmation gets written into the timeline so it isn't just in someone's head.

Load-in and vendor arrivals

Start from the load-in window the venue gives you, not the schedule you'd like. List each vendor with their dock or door, their arrival window and the person who signs them in. The block is done when every vendor has confirmed their arrival time in writing. If you're still settling vendor commitments in the brief, the client brief template helps you pin them down before they turn into surprises on the day.

Setup, AV check, and staff briefing

Run a full sound and sightline check in the room during this block, not later. Confirm how many mics you have, which version of the slides is loaded, and that the seating chart matches the floor plan. Brief the staff on the run of show, the cue names and who to go to when something goes wrong. The block ends when one named person signs off the AV and another named person has taken charge of the door.

The gap between setup and doors open is the one most agencies don't give enough time to. Event professionals on Reddit often point out that when ticketing, schedules, check-in and email sit in separate tools, they stop agreeing, and the mistakes show up at the door (eventist.ca). So this block has one job: in the hour before doors open, check that every list your check-in staff will use matches the master RSVP list, and note the time you checked. If badges were printed days ago and walk-ins turn up, your door staff will be improvising while guests wait. Sort the list out here, or you'll be sorting it out in front of a queue.

Doors open and show blocks

Treat doors open as a cue that someone calls, rather than a time that simply arrives. Each block in the show lists the cue, the person who owns it and a backup. A block ends when its cue has gone and the next speaker or act is in position.

Teardown and closeout

Teardown works like load-in in reverse: vendor by vendor, with departure windows and dock assignments. Closeout covers the venue walkthrough, lost property, the final headcount, and one exported copy of how the run of show actually went, for the client's file.

How do you build a day of event timeline in Word?

Setting up the table

Open a blank document, switch it to landscape, and insert a table with six columns: Time, Block, Action, Owner, Location and Status. Fill the Time column in 15-minute steps from load-in through doors open to closeout, then add rows wherever a block needs more detail. Use one row per action rather than one per block. A single "vendor arrivals" row covering four vendors doesn't tell your AV lead when their truck is due.

Formatting for print and mobile

Set the header row to repeat on every printed page, and keep the whole timeline to two pages at most, because staff on the day won't read more than that. Use bold only for fixed cues such as doors open and speakers walking on. Save a PDF copy before you print, because someone's laptop will run out of battery at check-in.

When a doc stops being enough

A Word timeline works until two planners edit different copies on the morning of the event and the record of changes lives in a text thread. If you run several client events at the same time, that's the risk you're carrying. A shared timeline with a change log, using something like RunCue's event change log template, keeps every edit visible to everyone. Until you reach that point, Word is fine.

How far in advance should you finalize the day-of timeline?

Work back from the event day in four passes. Draft the timeline when contracts are signed, as soon as the venue is holding your date. Fix the load-in window, doors open and the hard finish before anything else. This draft lives in your planning documents, not on anyone's call sheet.

Two weeks out, publish the version vendors have confirmed. By then every caterer, AV crew and florist has checked their arrival window against it, and any gaps show up while there's still time to fix them.

Send the final call sheet 48 to 72 hours before doors open. This is the version staff and vendors actually follow, with columns for each role, phone numbers and the run of show. If you're running several client events at once, a shared workspace like RunCue keeps each event's version current for the whole team (see pricing for plans), and the templates on RunCue's resources page follow the same structure.

Lock it the day before. After that, every change goes through one person.

How do you share the timeline with vendors, staff, and clients?

Full timeline vs filtered call sheets

Not everyone needs the whole run of show. Staff and the client get the full timeline, including load-in, cue times and closeout. Vendors get a filtered call sheet with only their own arrival, setup window and breakdown time, plus the venue contact. The caterer doesn't need your speaker cues, and every extra row is another chance for someone to act on the wrong line.

Version control and last-minute changes

Keep one master copy and name each version clearly, for example "Smith Wedding, v4, 12 Oct." If you use Google Docs, share view-only links and turn on notifications so edits are tracked instead of emailed around (Google Docs Help). If something changes after you've started preparing for doors open, send the updated call sheet with the change marked at the top, then ask everyone to confirm they've seen it. A quick "got it" text from each vendor and staff member is the only proof that counts on the day. If someone hasn't replied, assume they haven't seen it.

What common day-of timeline mistakes derail events?

No owner, no buffer, no phone number

The most common problem is a line on the timeline with nobody's name next to it. "Caterer arrives 3:00" doesn't help if nobody is responsible for checking the loading dock is clear. Every line needs an owner, and every owner's mobile number should be on the call sheet. When the florist is stuck in traffic at 4:15, you want the planner's number in front of you, not buried in an email.

The second is a schedule with no slack in it. Leave 10 to 15 minutes before every fixed transition, especially vendor arrivals and doors open. If load-in runs late, the buffer absorbs it. Without one, a single late truck pushes back everything that follows.

The third is leaving out closeout. A timeline that stops at "last guest out" leaves breakdown, vendor pickups and load-out with nobody assigned and nobody signed off.

Different tools showing different times

Your document says doors open at 6:00, but the check-in tool still says 6:30 because someone updated one and not the other. When the timeline, registration and RSVP tools disagree, you find out at the door. Pick one place to make changes, update it first, and copy changes out from there.