Use stable session, room, and presenter IDs, shared time blocks, and a separate revision review. The example below is a proposed program, not a published event or a reservation system.
Georgia Tech's official 2026 INFORMS conference overview groups activities by day, time, and location, with plenaries, breaks, and parallel-session blocks. That organization informs this original smaller example; no real speakers, room assignments, or routes are transferred. Georgia Tech's official program at a glance
Put shared blocks beside the parallel choices
The fictional Small Tools Forum runs from 09:00 to 11:00 in a proposed local schedule. Its actual date, time zone, venue, access arrangements, room assignments, and speakers remain TO CONFIRM. Room A and Room B, and presenter labels P01–P04, are illustrative identities.
| Proposed local time | Shared activity or Track A | Track B |
|---|---|---|
| 09:00–09:20 | Shared plenary | Shared plenary |
| 09:20–09:30 | Shared transition | Shared transition |
| 09:30–10:10 | A1 Documentation; Room A; P01 | B1 Handoffs; Room B; P02 |
| 10:10–10:20 | Shared break and move | Shared break and move |
| 10:20–11:00 | A2 Review; Room A; P03 | B2 Planning; Room B; P04 |
Keep each shared block as one program record even though the comparison table shows it under both track headings. Record session ID, start/end time, track, room ID, presenter ID, and status. Use the same identities in every view; a renamed title should not become a new session or move its presenter.
Count elapsed time without adding simultaneous rows
The wall-clock duration is 120 minutes: 20 minutes of plenary, 10 of transition, 40 in the first parallel block, 10 of break/move, and 40 in the second parallel block.
Adding all four parallel sessions gives 160 session-minutes. Adding the shared 40 minutes gives 200 session-minutes across the program's records. That is a different quantity from the two-hour elapsed event time. Both parallel sessions in a block occupy the same forty minutes on the clock.
A participant choosing A1 followed by B2 has a nonoverlapping proposed route within the 120-minute program, including the shared blocks. The ten-minute room-change allowance is proposed, not a verified walk through a venue. Access, travel between rooms, and the actual session arrangements still need confirmation.
Show a choice conflict without pretending to reserve a seat
Selecting A1 and B1 creates a time conflict: both run 09:30–10:10. The local HTML review identifies those session IDs and explains that a participant needs to choose between them. It should not move one session, claim attendance at both, or interpret selection as a booking.
When filtering Track A, keep the shared plenary, transition, and break visible. A filter changes what is shown; it does not remove shared records from the underlying program. Local selections are review choices, not saved personal agendas or verified seat availability. Check the local selection and conflict controls in the intended host before using the program with attendees.
Keep presenter revisions separate from the baseline
The baseline assigns P01 to A1 and P02 to B1. In the original revision variant, someone proposes replacing B1's presenter with P01 while leaving A1 unchanged. The review must flag P01 assigned to both A1 and B1 during 09:30–10:10.
Show the baseline and proposed change together, with the conflict labeled unresolved. Do not silently change a time, room, or presenter to clear the warning. A workable revision needs organizer decisions and actual speaker confirmation; the example supplies neither. Keep actual consent, room feasibility, access notes, and approved revision fields blank until verified.
Copy this prompt for the parallel-track program
Create a complete US English conference program review packet for the fictional Small Tools Forum, with baseline schedule, stable session/room/presenter records, elapsed-time explanation, attendee-choice conflict example and separate presenter-revision review. Not a published/approved event or reservation system.
Proposed local09:00-11:00. Actual date,timezone,venue,room assignments,speakers/access TO CONFIRM. Sharedplenary09:00-09:20,transition09:20-09:30;block1 09:30-10:10: A1Documentation RoomA P01 and B1Handoffs RoomB P02;sharedbreak/move10:10-10:20;block2 10:20-11:00: A2Review RoomA P03 and B2Planning RoomB P04.
Stable sessionID,start/end,track,roomID,presenterID,status. Sharedblocks one underlying record,always visible duringtrackfiltering. Wallclock20+10+40+10+40=120minutes;fourparallel40minute rows plusshared40=200sessionminutes,notelapsedtime.
AttendeeA1+B2 nonoverlap withproposed10minroommove,notverifiedvenuewalk/access. A1+B1 overlap09:30-10:10:requirechoice,no movedtime orreservedseat. Localchoices notsavedagenda.
BaselineB1P02. SeparatevariantproposesB1P01 withA1P01 unchanged:flagpresenterclash sameblock,baselinepreserved. Noautomaticconflictresolution/timechange,realconsent orapprovedrevision. Actualorganizerdecision/seats/access/consent fields blank.
If proposing HTML filter/choice/revision views,preservebaseline/IDs/sharedblocks andexplainexactconflicts;construction/testingpending. Noeventbooking,calendarupdates,savedchoices orparticipantcollection. Actualconfirmedprogram stays inorganizerworkflow.
Review the program in NOS
NOS can save and render a prepared HTML copy of the parallel schedule and separate conflict cases. Use it to inspect the shared blocks and unchanged baseline after any proposed controls have been built and tested. Maintain organizer decisions and the confirmed event program in the normal event workflow.
Finish with the two-hour program intact and each unresolved overlap tied to its session and presenter IDs, so the organizer can make a deliberate revision before participants rely on it.