A run sheet is the single most useful document you'll produce for any presentation night. It's not a guest list, not a budget spreadsheet, and not a seating chart. It's a minute-by-minute schedule that tells every person involved exactly what happens, when it happens, and who's responsible. Without one, even a small club presentation night tends to drift. With one, the MC knows when to speak, the AV operator knows when to cut music, and the person handing out trophies isn't scrambling behind a curtain.
What a run sheet actually contains
A good run sheet works as a single source of truth for the entire event. Every column matters. The document should list the start time for each segment, the duration, a plain-English description of what occurs, the person responsible for executing it, and any equipment or cue that needs to be ready. That's five columns, and none of them is optional.
Keep descriptions short. "Welcome address – Club President, 3 mins, microphone on podium, no slides" is more useful than a paragraph of context. The person reading it mid-event has roughly four seconds to absorb each line.
Beyond those core columns, flag any segments with a hard dependency. If the junior awards must finish before the caterers begin serving, write that in. If the major award winner needs to walk from a seat near the back, add a note so the MC can pad with 20 seconds of context. Small logistics, written down, stop becoming large problems.
How to build the timeline from scratch
Start at the end. Pick the latest reasonable finish time, then work backwards. If 10:00 pm is the venue's curfew, you need to clear the room by 9:45 pm, which means the final award presentation and thank-you should wrap by 9:30 pm. Every segment you add pushes the start time earlier. This reverse-engineering step forces honest decisions about which segments actually fit.
Buffer time is not wasted time. Add 3 minutes between every significant transition: after the welcome address, after any video package, after interval. Transitions always take longer than rehearsed, especially when an audience is involved. A 3-minute buffer looks like slack on paper; on the night it looks like professionalism.
Once you've got a draft timeline, read it aloud against a stopwatch. Narrate each segment at a realistic pace. You'll find at least one segment that's been allocated 5 minutes when it genuinely needs 12. Better to find that now than at 8:47 pm on the night. For more on structuring the presentation itself, the article on how to structure a trophy presentation ceremony covers segment ordering and pacing in detail.
Award segments: the trickiest part to time
Award presentations are where run sheets typically break down. Each award looks like a 2-minute item. But factor in the MC reading the category, a brief description of the recipient's achievement, the recipient walking to the stage, the handshake and photo, and the return to seat, and you're at 3.5 to 4 minutes per award for a mid-sized room.
Do the maths before you commit to a count. Twenty awards at 4 minutes each is 80 minutes of award segment alone, before interval, before speeches. If that number surprises you, now is the time to either trim the category list or extend your venue booking. Changing it on the night isn't an option.
List every award category in the run sheet in presentation order, not alphabetical order. The order matters: junior categories typically run early, major awards close the night. If you haven't finalised your category list yet, the article on how to choose award categories that people actually care about walks through how to get that structure right before you build the run sheet around it.
Next to each award category, note the trophy or medal that will be presented. This gives whoever is managing the awards table a picking list. Trophies get set out in order, so the right one is always at the front of the queue.
Roles, not just tasks
A run sheet that assigns tasks to "the committee" is almost as bad as no run sheet at all. Every line needs a named person. Not a role title. A name. "Sarah – AV" is actionable. "AV team" is not.
Key roles to assign before you write the first draft:
- MC: controls the pace of the night and keeps every segment on time
- Awards table manager: responsible for setting out trophies in order and handing them to the presenter
- AV operator: music cues, microphone levels, any slideshow or video
- Photography coordinator: knows which awards need a formal photo and where the photographer will stand
- Door and seating coordinator: manages late arrivals without disrupting proceedings
Each of those people should receive a copy of the run sheet in advance, not just on the night. Give them 48 hours to flag anything that doesn't make sense from their position.
Contingency notes: the part most organisers skip
A run sheet without contingencies assumes nothing will go wrong. Something always goes wrong. The AV fails on a video package. A key award winner is absent. The caterers arrive 15 minutes late. The MC runs long on a speech.
Add a contingency column to your run sheet, or a short notes section at the bottom. For each high-risk segment, write one sentence: what to do if it doesn't happen as planned. "If video package fails: MC reads winner tribute from printed card, move directly to presentation." That's it. One sentence. The MC doesn't have to improvise from nothing, and the audience barely notices the pivot.
Award ties and disputed results are worth noting here too, since they tend to surface at the worst possible moment. If your selection process hasn't locked in how to handle them, that's a separate planning task worth resolving before the night.
Distributing and updating the run sheet
Print copies. Yes, in 2026, print them. A phone screen dims at the worst time. A shared doc needs a signal. A printed A4 run sheet in someone's hand works in a dark room, at a noisy venue, and when the wi-fi is unreliable, which describes most presentation night venues.
Mark the version date in the footer of the document. You'll produce at least 3 versions before the night. The person who shows up with version 1 while everyone else is running version 3 is the person who calls the wrong award at the wrong time. Version control on a run sheet is not bureaucracy. It's how you avoid a genuinely embarrassing moment.
Send the final version to all named staff by noon on the day of the event. At that point, lock it. Changes after midday create more problems than they solve.
A simple template structure to start from
If you're building your first run sheet, start with six columns across the top: Time, Duration, Segment, Person Responsible, Equipment/Cue, and Notes. Run your event from doors-open to venue-clear. Every segment gets a row, including the ones that feel obvious: "6:30 pm – Guests arrive, background music playing, bar open – AV: background playlist, 30 min." Obvious on the night means planned in advance.
A run sheet that covers every segment, names every person, and anticipates at least the three most likely problems is the difference between a night that feels effortless and one that feels held together with tape. The guests won't see the document. That's exactly the point.