Schedule studio

Place sessions into rooms and times with conflict detection from Admin → Schedule.

Where scheduling happens

Open Admin → Schedule (schedule studio). Sessions are program slots; placements assign room and time range. Hard conflicts such as double-booking a room or speaker surface as conflicts the operator must resolve. Soft preferences may appear as warnings depending on product rules.

Place a session

Ensure rooms and tracks exist for the event. Create or select a session, choose room, start, and end in ISO-8601-compatible inputs the UI provides, and save. If the Worker returns a conflict, read the conflict list and adjust room or time.

  1. Confirm rooms and tracks for the event under settings or schedule setup.
  2. Open Admin → Schedule.
  3. Select or create the session to place.
  4. Choose room and time range, then save placement.
  5. If conflicts return, resolve them before announcing the grid.

CLI parity

Agents with schedule:write can place sessions via the CLI. Success exits 0. Hard conflicts exit 3 with conflicts in the JSON body. Missing scope exits 2. Always pass --json for automation.

speakerops schedule place \
  --event <eventId> \
  --session <sessionId> \
  --room <roomId> \
  --start <ISO-8601> \
  --end <ISO-8601> \
  --json

speakerops schedule list --event <eventId> --json
speakerops schedule unschedule --event <eventId> --placement <placementId>

Operator tips

Lock rooms before publishing a public grid. Place keynotes and constrained speakers first. Re-run readiness after large schedule moves. Unschedule instead of stacking overlapping drafts when exploring alternatives.