Demo
A week of events, checked as you plan
Plan an invented company’s week of events on a board or a timeline. Code checks every edit against the whole week: the same person or equipment in two places at once, too little time to travel between venues, and equipment nobody on the crew is qualified to run. Fix a conflict, or save it anyway with a reason, then download the plan.
This is a simulation. No AI model runs on this page: the checks are ordinary code in your browser, and the company, people, venues, events and equipment are all invented. Nothing you type leaves your browser or is kept, the CSV file is made in your browser from the plan on the page, and reloading the page starts again.
Lantern’s week
Day 1
E-1 09:00 to 15:00
Book fair
Venue: Riverside
Crew: Ivy and Rowan
Equipment: Sound system A and Lighting rig A
Checks clear
Day 2
E-2 08:00 to 12:00
Wedding ceremony
Venue: Glasshouse
Crew: Rowan and Heath
Equipment: Sound system B and Power unit
1 open conflict
E-3 11:00 to 17:00
Food festival stage
Venue: Castle
Crew: Rowan and Sage
Equipment: Sound system A and Lighting rig A
1 open conflict
Day 3
E-4 10:00 to 14:00
School prize day
Venue: Mill
Crew: Sage and Fern
Equipment: Video wall and Sound system B
1 open conflict
E-5 14:30 to 22:00
Jazz night
Venue: Pier
Crew: Sage and Clover
Equipment: Sound system A and Lighting rig B
1 open conflict
Day 4
E-6 09:00 to 13:00
Charity lunch
Venue: Riverside
Crew: Ivy and Fern
Equipment: Sound system A and Video wall
1 open conflict
E-7 12:00 to 18:00
Garden party
Venue: Glasshouse
Crew: Clover and Heath
Equipment: Sound system A and Lighting rig A
1 open conflict
Day 5
E-8 16:00 to 23:00
Outdoor film night
Venue: Castle
Crew: Rowan and Heath
Equipment: Video wall, Sound system B and Power unit
1 open conflict
Day 6
E-9 10:00 to 18:00
Kite festival
Venue: Pier
Crew: Ivy, Clover and Fern
Equipment: Sound system B and Power unit
Checks clear
Day 7
E-10 12:00 to 16:00
Choir concert
Venue: Mill
Crew: Rowan and Sage
Equipment: Sound system A and Lighting rig B
Checks clear
Conflicts
A conflict never blocks the plan. Fix it, or override it with a reason; an override lasts only while that exact conflict stands.
No conflicts on the plan.
open Double-booked crew
Rowan is booked on E-2 and E-3 at the same time on day 2 (11:00 to 12:00).
open Not enough travel time
Sage cannot get from the Mill to the Pier in time on day 3: E-4 ends at 14:00, E-5 starts at 14:30, and the trip takes 50 minutes (20 minutes short).
open Double-booked equipment
Sound system A is booked on E-6 and E-7 at the same time on day 4 (12:00 to 13:00).
open Missing qualification
E-8 uses the video wall, which needs someone qualified for rigging, and nobody on its crew is.
Saved changes
Each saved change and each override will be listed here with its reason.
Crew, equipment and venues
Crew and qualifications
- Ivy: rigging, mains power
- Rowan: sound desk
- Sage: rigging
- Fern: sound desk, mains power
- Heath: mains power
- Clover: rigging, sound desk
Equipment and what it needs
- Video wall: needs rigging
- Sound system A: needs sound desk
- Sound system B: needs sound desk
- Lighting rig A: needs rigging
- Lighting rig B: needs rigging
- Power unit: needs mains power
Travel times between venues
- Riverside and Mill: 30 minutes
- Riverside and Castle: 20 minutes
- Riverside and Glasshouse: 40 minutes
- Riverside and Pier: 45 minutes
- Mill and Castle: 25 minutes
- Mill and Glasshouse: 35 minutes
- Mill and Pier: 50 minutes
- Castle and Glasshouse: 30 minutes
- Castle and Pier: 40 minutes
- Glasshouse and Pier: 60 minutes
What the demo shows
- Checks that run as you edit. Every change to a draft is checked against the whole week before it is saved: double-booked crew, double-booked equipment, travel time between venues, and the qualifications the equipment needs.
- Warnings, not blocks. A conflict never stops the planner. It is fixed, or saved anyway with a stated reason, and the reason stays with that exact conflict. If the conflict changes, it opens again.
- Suggestions that wait for a person. A suggested fix is worked out by code (someone free and qualified, or the same kind of equipment that is free) and opens as a draft. Nothing is saved until the planner confirms it.
- Two views of one plan. The board and the timeline draw the same data, so a change made from one shows in the other.
- A plan you can take away. The CSV file lists every event with its crew, equipment, open conflicts and override reasons, and any cell a spreadsheet would run as a formula is made safe.