Con season planner
Two must-sees at 11:00, one of you.
A big convention runs hundreds of hours of programming, and the panel you came for clashes with the one your friend came for. Paste the programme and tag what you care about: the page lays the weekend out like a TV guide and flags every clash, every hall change you cannot walk in time, and every day with no gap for lunch. Ask for a plan when you want one path through it - arrival times for the queue, a repeat or a backup for each drop, and the meals in the gaps.
1 The programme
One session a line: day | start-end | room | title | tag, e.g. Sat | 12:00-13:00 | Hall A | Voice cast Q&A | must. Tags: must, want, maybe, fixed (a ticket or appointment you hold), or leave it empty for a session you only want on the guide. A line with just Saturday (or a date) sets the day for the lines under it. Tab- or comma-separated exports work too.
2 You and the venue
Big halls fill early: the queue time is added before each must-see. The walk counts only when the room changes.
3 The guide
- must-see
- want
- maybe
- fixed slot
- on the guide
- clash
- meal window
- queue
- R = runs again
Starred, day by day
Each day
What the page sees
The rules the page uses
- Starred = must, want and fixed. Maybes never raise a flag of their own; the page only notes when one overlaps a starred session.
- Clash = two starred sessions overlap on the same day. It is a fix when both are must or fixed and neither runs again at a free time; otherwise worth a look.
- Tight hop = less time between two starred sessions than the walk (when the room changes) plus the queue (when the next one is a must-see).
- No meal = a day that spans 13:00 with no gap as long as your shortest meal between 11:30 and 14:30 (and the same for dinner, 17:30-20:30, on a day that spans 19:00).
- Long day = from the first queue to the last session end runs past your longest day.
- Overbooked = any fix flag. Trim = any worth-a-look flag. Fits = none.
- Times and rooms are the programme as pasted. Walking, queueing and meal times are your settings, not measurements of the venue.
4 Get the plan
Metered. The planner reads the programme, your tags, the flags and your notes, picks one path through every day - fixed slots first, then must-sees - settles each clash with a repeat, a late join or a drop, times your arrival for each queue and puts the meals in real gaps. The page re-runs its rules on the path and says what is still off.
Take it with you
Share sends the path as text - and, with the first day's date set, the calendar file - to a friend or your phone's calendar through the device's share sheet; where there is none, it copies the text. The calendar file puts every session on the path (or every starred session, before a plan) and each break into your phone's calendar - set the first day's date above. The .csv lists arrival, start, end, room and the planner's reason for each stop.