For event organisers · Event operations scheduling

The jury moves the start by an hour. Your whole day just changed — one cell at a time.

Daily Runsheet is the schedule for everything around the show: gates, deliveries, accreditation, catering, briefings, security — every day of the event, build-up to teardown. Set the rule once — "gates open one hour before the first session" — and every day computes its own times from the programme. Change the programme, the whole event re-times itself.

Test it free — no account → Own it · €99
Built from real runsheetsWorld championships, World Cups, city events
25+ years of event workBonacube · Finland
Event venue during build-up before gates open
Every function asks the same question: when are we open, and when do we need to be there?
The problem

You know this file.

One row per operation, one column block per day. Somewhere around day five it stops fitting on a screen. It was serious work by serious people — and the tool fought them the whole way.

  • Forty-four columns. Thirteen days × start, end, info. By Thursday you're scrolling so far right the row names have left the screen, and you're setting times for a row you can't see.
  • The clever version has formulas: IF the first session is blank AND the first training is blank, then 07:00… — with 07:00 hardcoded as 0.2916666. One person understands the sheet. They are on holiday.
  • The other version has ditto chains: =F32, =G32, =I32 — "same as yesterday", copied across the week. One day differs. Nobody notices until the volunteers are standing outside a locked gate.
  • There is a row literally named "HAND FIXED Gates Open times" — an entire second row, because overriding the formula destroys it. The override system is a parallel universe.
  • The file is called 2020, the sheet is called 2029, the title inside says 2018. It has been copied event to event for a decade, and it shows. I have the file.

A file you may recognise

DailyRunSheet_2020_01112019.xlsx
Sheet nameSalppuri 2029
Title insideDAILY RUN SHEET 2018
Width44 columns · 13 days
Cell F26=IF(AND(ISBLANK(F$9),ISBLANK(F$14)),0.29166…
Row 48"HAND FIXED Gates Open times"

Every rule in it was right. Gates an hour before the first start, deliveries until the gates, briefing at 8:15. The sheet just couldn't hold the rules — only the numbers they produced.

Rules, not numbers

Picture the same event with a runsheet that does the math.

  • Every day of the event on one view — build-up, competition days, teardown. No horizontal archaeology.
  • Operations carry rules, not typed times. Gates: first start −1:00. Deliveries: until the gates open. Debrief: last end +0:30.
  • The programme changes — every dependent time on every day updates itself. The chain holds: deliveries follow gates follow programme.
  • Hand-fix any single day and it turns gold, so everyone sees it left the rule. One click puts it back.

Change one session time. Thirty operations across six days re-time themselves. That's the whole trick.

The product

Daily Runsheet.

A daily runsheet with an engine. Rows are your operations, grouped by customer group — teams, media, spectators, VIPs, volunteers, organisation. Columns are your days. Programme sections anchor each day; every other row can compute its times from the first start, the last end, or another row.

Each day also has its own tab: the full day in time order, printable as the A4 day sheet for the ops centre wall and the morning briefing. The whole grid prints A3 landscape, exports to Excel, and travels as a view-only web link.

The structure follows daily runsheets used from World Cup weekends to the Lahti 2017 World Championships — thirteen days, one sheet, every function reading the same times.

Scheduled 128/134 · 96%▶ DAY BOARD
OperationRuleWED17.2. SETUPTHU18.2.FRI19.2.SAT20.2.
MAIN PROGRAMME PROGRAMME
Competition session 1programme—14:00–15:3011:00–12:3011:30–13:00
SPECTATORS
Gates open for public1st −1:00 → last +0:30—09:00–20:3007:30–17:4507:30–22:30
Ticket control activeGates open → Gates open—09:00–20:3007:30–17:4507:30–22:30
GENERAL OPERATIONS
Delivery window (morning)Gates −2:00 → Gates08:00–18:00 ✦07:00–09:0005:30–07:3005:30–07:30
Accreditation centre open1st −3:00 → last +1:0012:00–19:00 ✦07:00–21:0005:30–18:1505:30–23:00
ORGANISATION
Morning briefing (all functions)manual08:15–08:3008:15–08:3008:15–08:3008:15–08:30
Venue team daily debrieflast +0:30 → +1:00—20:30–21:0018:00–18:3022:30–23:00
Why it works

Six problems from real runsheets. Six fixes.

01

Rules, not typed times

An operation starts and ends relative to the programme — or to another row. Set the rule once; every day computes its own times. The logic that lived in one person's head now lives on the row.

02

The whole event, one view

Build-up, event days, rest days, teardown — all columns on one grid, each day tagged. And every day has its own tab when you need the detail. No more 44-column archaeology.

03

Hand-fix that shows its hand

Type over any computed time and the cell turns gold — everyone can see it left the rule. The rule is remembered; one click puts the day back on it. No more parallel "HAND FIXED" rows.

04

Chains that hold

Deliveries end when the gates open. Ticket control runs exactly the gate hours. Gates follow the programme. Move one session and the whole chain re-times — nothing is copied, so nothing drifts.

05

Every function its own sheet

Filter by owner and print: each function gets its own A4 day sheet for the wall and the briefing. The full grid prints A3 landscape. View-only links for venues and partners — no accounts.

06

The ops library

Gates, delivery windows, traffic plan, accreditation, team services, media centre, volunteer catering — the classic operations with the rules that ran real events, plus packs for outdoor sports, arenas, festivals, congresses and expos. Add one; its times appear everywhere, computed.

Day Board

The ops centre view: what's open, what's next.

Full screen, dark, built for the wall of the operations centre. What's open right now. What opens next, with a countdown. What's done. Filter by owner and each function watches its own day.

On the day it runs itself — because the times were computed in peace, weeks earlier, from rules everyone agreed on. Print it as the A4 day report for the morning briefing.

Open the demo and press ▶ Day Board
My Winter Event 2027 · Day Board09:41:26
SAT 20.2. · sold outOpen now 9Still to open 6Programme 11:30–22:00
Open now
07:30–22:30Gates open for publicSecurityOPEN NOW
08:00–14:30Team service deskSportsOPEN NOW
09:00–23:30Volunteer catering openServicesOPEN NOW
Opening next
10:15–11:15VIP host briefingProtocolin 34 minOPENS
11:30–13:00Competition session 1Sportsin 1 h 49 minOPENS
Jesse Kiuru walking through an event hall during build-up
Who built this

An event director. Not a software company.

I'm Jesse Kiuru. I help event organisers and host cities bid, plan and run better events. Event director of the Lahti 2017 FIS Nordic World Ski Championships. Currently structuring the Winter World Masters Games 2028.

Daily Runsheet exists because I kept this sheet for a thirteen-day world championship — gates, deliveries, shuttles, media, volunteers, all of it — in a 44-column Excel file with formulas only I understood. The rules were right for ten years. The file fought us for ten years. This tool keeps the rules and loses the fight.

270,000spectators, Lahti 2017
3,000workforce coordinated
25+ yrschampionships to conferences
Pricing

Test first. Buy when it earns its place.

The free test runs on a full example event — six days, build-up to teardown, thirty operations on rules. Everything works, nothing saves. When you want your own event saved and shareable, one payment.

Daily Runsheet · Full version
€99 one time · no subscription
  • Unlimited events, days and operations
  • Timing rules: anchor to the programme or chain to any row
  • All days on one grid + a detail tab per day
  • Hand-fix marked in gold, revertable per day
  • Ops library: classic ops + 5 event-type packs (outdoor, arena, festival, congress, expo)
  • Day Board live view with owner filter
  • View-only share links · A4 day sheets · A3 grid PDF · Excel export
  • All updates to the current version included
Get Daily Runsheet · €99 → or test it free first — no account, 2 minutes

Pairs with Rundown Master: the rundown runs the show minute by minute, the runsheet runs everything around it. Ten tools in the toolbox.

Questions

Asked before buying.

Do I need to install anything?

No. Daily Runsheet runs in the browser — laptop, tablet or phone. Your events save automatically to your account.

How is this different from Rundown Master?

The rundown is the show: cues, minutes, one session at a time. The runsheet is everything around the show: gates, deliveries, services, offices — across all days of the event. Rundown Master answers "what happens next on stage." Daily Runsheet answers "when are we open, and when do we need to be there." Serious events run both.

Our programme isn't confirmed yet. Can I still build the runsheet?

That's exactly when rules beat typed times. Build the operations on rules now — gates first start −1:00, deliveries until gates — with a placeholder programme. When the real session times land, type them in and the whole event re-times itself. No TBC cells waiting to be forgotten.

What about overnight operations — security 22:00 to 06:00?

Type them as they are. The runsheet understands that 06:00 after 22:00 means the next morning, on every day, without a formula.

Do venues, suppliers and partners need accounts?

No. You send a view-only link — the all-days grid, or the Day Board directly for the ops centre screen. Or you print: each day as an A4 day sheet, the whole event as A3 landscape.

What does "free test" mean exactly?

The full tool on an example event — six days, thirty operations, the rules doing the work. Move a session time and watch the day re-compute. Nothing saves — 100 people can test at once and never see each other's changes.

Change one session time.
Thirty operations re-time themselves.

Test it free → Own it · €99

Two minutes in the demo tells you more than this page can.