{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Sessions{{ computation.ok ? values.session_count : '—' }} Content{{ computation.ok ? formatDuration(values.total_session_minutes) : '—' }} Flow{{ computation.ok ? values.flow_status : '—' }}
Paste CSV, TSV, pipe-delimited, or plain text. One row per session; a header row is optional.
{{ sourceStatus || 'Drop one CSV, TSV, or TXT file onto the textarea. Content stays in this browser.' }}
Use the production name that hosts and crew should see.
Times are interpreted as local wall-clock values in the selected time zone.
{{ startStatus }}
Choose the event's operating time zone; calendar import depends on receiver support for it.
Enter a room, building, stage, virtual room, or production channel.
Use mixed flow for locked cues and continuous flow for a fully sequential plan.
Zero is neutral; choose up to 90 minutes between auto-flowed sessions.
min
24-hour time is the neutral handoff format.
Zero is neutral and disables short-gap warnings; overlaps remain blocking.
min
StartEndSessionMinutesOwnerLocationHandoffCopy
{{ row.start_label }}{{ row.end_label }}{{ row.title }}{{ row.duration_minutes }}{{ row.owner }}{{ row.place }}{{ row.handoff }}

The chart renderer is unavailable. The same schedule remains available in the Schedule tab.

CheckStatusEvidenceNext actionCopy
{{ row.label }}{{ row.status }}{{ row.evidence }}{{ row.action }}
On-call Handover Report Prepare an on-call handover with normalized incident rows, ownership checks, readiness rules, and warnings for risky or incomplete transfers.
Calendar ICS Generator Create an import-ready ICS event with correct date boundaries and time-basis handling, plus escaped text, reminders and validation checks.
Attendance Sheet Generator Build printable attendance sheets from roster text or CSV with flexible sessions plus duplicate-name, page-fit, and privacy checks before printing.
Pomodoro Timer Plan focus rounds and short or long breaks, estimate a goal finish time, and run a browser-based Pomodoro countdown with quiet cues.

An event run sheet turns a program into an operating plan. Session titles matter, but timing, ownership, location, and handoffs determine whether speakers, crew, rooms, and attendees can move through the day without collisions.

Three kinds of time need to be distinguished. Duration is the space reserved for a session. A gap is unused time between one session ending and the next starting. A buffer is a deliberate gap added to flexible sessions for questions, setup, movement, or recovery.

Programs often combine locked cues with flexible blocks. A livestream opening, keynote, meal delivery, or venue booking may have a fixed start. Workshops and reset periods can usually follow the previous item. When an earlier block grows, a fixed cue stays put and may expose an overlap instead of moving automatically.

Situation Timing risk Evidence to check
Back-to-back speakers No room for applause, questions, microphone changes, or late arrivals. A zero-minute gap may be intentional, but it deserves a production check.
Room or stage move The next owner or audience cannot reach the new location in time. Compare the location change with the preceding gap.
Locked cue The prior session runs beyond the fixed start. Any positive overlap must be repaired.
Long program A schedule crosses midnight or a calendar displays the wrong local time. Check the date rollover, named time zone, and imported calendar.

A run sheet can be internally consistent and still be operationally weak. A session without an owner, an unrealistic room move, or a calendar receiver that does not understand the named time zone can break an otherwise valid timeline.

Treat schedule generation as an early stress test. The final plan still needs confirmation from the people who own fixed cues, venue access, catering, technical transitions, accessibility needs, and calendar distribution.

How to Use This Tool:

Start with one row per session, then decide which clock times are fixed and which sessions should flow continuously.

  1. Paste or load session rows. Use start time, title, duration, owner, location, track, and notes where available; a recognized header row is skipped.
  2. Set the event name, date, default start, time zone, and fallback venue. Times are treated as local wall-clock values in the selected zone.
  3. Choose Keep typed starts for a mixed plan with locked cues, or Continuous flow to ignore typed starts and place each row after the previous one.
  4. Add a Default buffer from 0 to 90 minutes when flexible sessions need breathing room. Set Short handoff warning from 0 to 60 minutes; zero disables only short-gap warnings.
  5. Read the run sheet and timeline, then open Checks. Repair overlaps first, assign every TBD owner, and confirm tight location changes.
  6. Import the ICS file into the calendar system that will distribute the event. Compare several session times with the run sheet before sending invitations.

Interpreting Results:

Flow is Fix when any overlap exists, Review when there are no overlaps but at least one short positive handoff, and Ready otherwise. A warning threshold of 10 minutes flags gaps from 1 through 9 minutes; a 10-minute gap is not short.

  • Overlap minutes are blocking because two sessions occupy the same timeline.
  • A zero-minute gap is back-to-back, not an overlap and not a short positive handoff.
  • TBD marks a missing owner even when the timing itself is valid.
  • A location change at or below the warning threshold needs review. Travel time, room access, and audience movement are not estimated automatically.
  • The timeline reports scheduled wall-clock offsets. It does not model attendance, setup complexity, or the chance that a session runs long.

Technical Details:

Each session occupies a half-open time interval: its start is included and its end is the point at which the next session may begin. This makes a session ending at 10:00 and another starting at 10:00 back-to-back rather than overlapping.

Formula Core:

Session end is the start offset plus the rounded duration in minutes.

Ei=Si+Di

For every session after the first, the signed gap compares its start with the previous end. A negative gap becomes positive overlap minutes.

Gi=Si−Ei−1,Oi=max(0,−Gi)

In continuous flow, the next start equals the previous end plus the selected buffer.

Si=Ei−1+B

Here S is the minute offset from the event date, E is the end offset, D is duration, G is the signed gap, O is overlap, and B is the default buffer. The total span runs from the first start to the last end; content minutes are summed separately from positive gaps and overlaps.

Rule Core:

Rule Exact behavior
Row parsing CSV, tab, and pipe rows are accepted. A row may begin with a clock time; duration accepts minutes, hour notation, or H:MM.
Duration Must be greater than 0 and no more than 1,440 minutes, then rounds to the nearest whole minute.
Mixed timing A valid typed start is kept. A backward jump of more than 12 hours is treated as a move into the next day.
Continuous timing Typed starts are ignored; every row follows the previous end plus the default buffer.
Short handoff Requires no overlap and a positive gap strictly less than the selected threshold.
Location move A changed location is tight when its signed preceding gap is less than or equal to the warning threshold.
Missing fields Missing owner becomes TBD, missing track becomes General, and missing location falls back to the default venue or TBD.

The ICS output writes each session with local date-time values and the selected time-zone identifier. It does not embed a full time-zone definition, so successful display depends on the receiving calendar recognizing that identifier.

Accuracy Notes:

The arithmetic is deterministic, but the schedule remains a plan rather than a forecast. Durations, movement time, and buffers come from the values supplied by the organizer.

  • Daylight-saving transitions are not simulated in the minute-offset model.
  • The selected time zone is preserved for calendar export, but calendar applications may differ in zone support.
  • Check accessibility, venue capacity, staffing, travel paths, and technical setup outside the timing calculation.

Worked Examples:

A fixed cue exposes an overlap

A welcome starts at 09:00 and lasts 30 minutes. The next locked session starts at 09:25, so its signed gap is −5 minutes and the schedule reports 5 overlap minutes with Flow set to Fix. Move the locked cue or shorten the welcome before publishing the run sheet.

Continuous flow adds recovery time

With a 10-minute default buffer, a 30-minute session beginning at 09:00 ends at 09:30 and the next flexible row begins at 09:40. A 10-minute warning threshold does not flag that handoff because short warnings apply only below the threshold.

References: