The daily runsheet that computes itself β built by an event director, not a software company. Gates, deliveries, accreditation, catering, briefings: set the rule once ("gates open one hour before the first session") and every day's times follow the programme. Change the programme, the whole event re-times itself.
One row per operation. One column per day. The times compute themselves.
The rundown runs the show. The daily runsheet runs everything around it: gates, deliveries, accreditation, catering, briefings, security β for every day of the event, build-up and teardown included. It answers the question every function asks: when are we open, and when do we need to be there?
π Days holds the whole span β set each day's date, label and type (build-up, event day, rest day, teardown). Rows live in sections: your programme first, then one section per customer group or function β teams, media, spectators, volunteers, organisation. Sections marked PROGRAMME drive the timing: their first start and last end are the anchors of each day.
Click the rule chip on any row. An operation can start and end relative to the first programme start, the last programme end, or another row β "gates open one hour before the first session, close thirty minutes after the last". Set the rule once; every day computes its own times from that day's programme. Change the programme and the whole event re-times itself. Rules can chain: the delivery window can follow the gates, which follow the programme.
Type over any computed time and it becomes hand-fixed β the cell turns gold and gets a "β¦ Fixed manually" label, so everyone can see it no longer follows the rule. The rule is remembered: βΊ Return to rule in the cell (or in the β editor) puts the day back on it. A dash (β) marks an operation as not running that day.
The β Needs attention button in the toolbar filters to every row that deserves a second look: no owner, a time that cannot be calculated, a hand-fixed override, a broken rule, a missing time on an event day, overnight hours, or a rule with no programme to anchor to. Rows with issues also carry a β next to their name β hover it for the list. Work the filter down to zero before event week.
Every computed cell explains itself on hover: Start: "Gates open for public" start 13:00 β2:00 = 11:00. If a number surprises you, the tooltip shows exactly where it came from.
Every day has its own tab: the full day in time order, programme highlighted, hand-fixes marked. It prints as an A4 day sheet β the one that goes on the ops centre wall and into the morning briefing. The all-days grid prints A3 landscape.
βΆ Day Board is the full-screen operations view: what's open now, what opens next (with a countdown), what's done. Filter by owner so each function sees its own day. π Share sends a view-only link β including a direct Day Board link for the ops centre screen.
π Ops library holds the classic operations β gates, delivery windows, traffic plan, accreditation, team services, media centre, volunteer catering β each with the timing rule that ran real events. Add one and its times appear on every day, computed. Then make it yours. The event-type packs add the operations typical for your kind of event: outdoor sports, indoor arena, city festival, conference & congress, expo & trade fair.
Everything saves automatically in this browser. π My events holds all your event projects. β€ Save file / β€ Open file in the top bar move an event between computers or into your archive as a file.
Want the worked example as a reference? π My events β οΌ Example event. Your own events start clean.