Timelab
Alpha Now open for early teams

Build your event timetable without fighting a spreadsheet.

Timelab helps teams plan multi-stage events with collaborative drag-and-drop scheduling, conflict checks, and clear shared views.

Not a spreadsheet. Built for timetables.

Built forMusic festivalsConferencesTheatre programsMulti-stage events

Live drag-and-drop across every stage — no clashing slots.

Who it’s for

Designed for stages and sets.

Timelab is built for events where the plan is a running order across lanes — stages, venues, or tracks. If your schedule needs more than one column, it belongs here.

Not a spreadsheet

A grid was never built for time.

Spreadsheets don’t know a slot has a start, a stage, and a neighbour. So you patch it with merged cells and colour-by-hand — until it breaks. Timelab understands the timetable.

The spreadsheet waylineup_final_v7.xlsx
ABCDE122:00Nocturne (live)DoorsBar222:30Vela?Vela?Panel323:00#REF!MøllerSable (moved?)423:30Kap B.Late
The Timelab wayAurora Nights
Slots know their placeEvery slot has a lane and a time. No merged-cell gymnastics.
Move without breakingDrag a slot and the plan stays intact, no broken references.
One shared viewEveryone reads the same grid, not the tenth email attachment.
The essentials

Everything a running order needs. Nothing it doesn’t.

Four things Timelab does that a spreadsheet can’t, each one built around the way a multi-stage plan actually works.

See the whole running order at once

A clear grid across lanes and time, made for multi-stage shows and multi-track programs. Stages, venues, or tracks. Each is a lane you can scan top to bottom.

Drag, drop, resize

Grab a slot, drop it in a new lane, pull its edge to change the length. Colour-code for fast scanning.

Share without losing control

Send one link and choose the access level that fits your team. Only the owner sets who can edit.

One source of truth

When the plan changes, everyone sees the same grid. No exports, no merges, no final_v7.xlsx.

How it works

From blank grid to running order.

Three steps. No template hunting, no formula wrangling.

  1. 1

    Create a timetable

    Set your date range and time grid. Start from a blank canvas built for scheduling.

  2. 2

    Add your lanes

    One lane per stage, venue, or track. Name them however your event runs.

  3. 3

    Add slots, then share

    Drop in sessions, colour them, and send one link with the right permissions.

Questions

Good to know.

The short answers. Everything else you’ll pick up in a minute of dragging slots.

Is Timelab only for music festivals?

No. Timelab is built for any event with a running order across lanes — music festivals, theatre programs, and conference tracks all fit the same grid.

Can people view a timetable without an account?

Yes. A public read-only link opens the timetable directly in the browser — no sign-up needed to look.

Can collaborators edit the timetable?

Yes, when the timetable is set to public editable. The owner always controls the access level, so you decide who can change what.

Can I tune the time grid?

Yes. Set your own date range and time granularity so the grid matches how your event actually runs, from 15-minute turnarounds to day-long tracks.

How do I share the plan with my team?

Every timetable has a simple /files/{id} link. Copy it, pick private, public-editable, or read-only, and send it. That's the whole flow.

Start planning your next timetable.

Build a multi-track running order in minutes then share one link with your whole team. For free.