Modules · Timetable
The timetable is what your visitors see: who plays where and when. It comes straight from the block schedule, so it is always right, on your site, at the gate and in the crew tent.
A glimpse of this module
with sample data, liveTimetable shares data with Programme & stages, Festival site per edition and Run sheet & the day itself. Change one thing and they move with it.
Nineteen modules, one system. Change it here and it stays right everywhere.
What it does
The classic festival grid: stages in columns, times in rows. Built automatically from the block schedule, no double entry.
Visitors always see the current version. Publishing is a switch, not an export chore.
On mobile you browse per stage or per time slot. Exactly what you need on a festival site with bright sunlight and 3G.
An act moving half an hour? Site, timetable and the internal run sheet all change in one move.
A tidy print version for the entrance, the crew tent and the press, in your own house style.
Not everything is an act. The opening ceremony, moments of silence and eating together get the same place in the schedule.
A timetable is the public schedule of your festival: which act plays on which stage and at what time. It is the grid visitors use to plan their day, with the stages in columns and the times in rows. You do not build it separately; you derive it directly from your internal running order.
That way the timetable is correct everywhere: on your festival site, at the gate and in the crew tent. If an act moves by half an hour, the site, the timetable and the production schedule all shift at once, with no outdated printouts. The timetable is phone friendly for use on site, and there is a clean print version for the entrance and the press. It is not a separate visitor app, but the schedule from your own system, published on your own site.
Timetable is part of festival.productions, the operating system for festivals, and shares data with the programming, site and production schedule modules.
Frequently asked questions
A timetable is the schedule that shows visitors which act plays on which stage and at what time. It is the public side of your internal running order. In festival.productions the timetable builds itself automatically from that running order, so there is no need to enter anything twice.
Not necessarily. Many visitors simply want a timetable that opens on their phone without installing an app first. The festival.productions timetable publishes straight to your festival site and is phone friendly, so you do not need a separate native app to share your schedule.
You publish the timetable on your festival site, so visitors always see the current version. If you work with loose printouts or PDF files, changes get missed. In the system, publishing is a switch: the site immediately shows the latest schedule from your running order.
The running order is the internal plan where you arrange acts, changeovers and soundchecks; the timetable is the cleaned up public version of it, showing only the performance times. They belong together, because the timetable comes from the running order. Change the running order and the timetable updates automatically.
By having the timetable come from a single source instead of maintaining it separately in several places. As soon as an act moves, every place where the schedule appears has to move with it. In festival.productions the site, the timetable and the production schedule all adjust in one motion, so no outdated times are left behind.
Yes. Not everything at a festival is a music act; an opening ceremony, a shared meal or a moment of silence also deserves a place in the schedule. In the timetable those moments get the same treatment as a regular act, so the audience knows what happens when.
Everything in one place
In festival.productions, Timetable feeds straight into Programme & stages, Festival site per edition and Run sheet & the day itself. You change it in one place and it stays right everywhere, from the budget to the event day.