Skip to content

Session Conflict Detector

Example prompt: "Read our conference schedule from Airtable and check for any problems — rooms double-booked, speakers assigned to overlapping sessions, or back-to-back sessions in the same room with no buffer. Post a summary of any conflicts to #conference-planning on Slack."

The Problem

Multi-track conference agendas are constantly in flux. Speakers cancel, sessions move, rooms get reassigned. Each change can introduce conflicts — a speaker booked for two overlapping sessions, a room double-booked, or back-to-back sessions with no setup buffer. Manually cross-referencing the schedule across rooms, time slots, and speaker availability is tedious and error-prone, and conflicts discovered on the day are difficult to fix gracefully.

How GloriaMundo Solves It

We build a workflow that reads your master session schedule and systematically checks for problems. An integration step pulls the full schedule from Airtable, including rooms, times, and speaker assignments. A code step runs conflict detection — checking for room double-bookings, speaker time overlaps, and sessions that exceed their allocated slot or leave no buffer for room changeovers. An LLM step turns any detected conflicts into a clear, human-readable report with specific recommendations (e.g., "Move Session B to Room 3, which is free at that time"). An integration step posts the report to your planning channel on Slack. Glass Box preview shows you the full conflict report before it posts, so you can verify the findings and make scheduling adjustments.

Example Workflow Steps

  1. Trigger (scheduled): Runs daily at 8am during the planning phase, or on demand.
  2. Step 1 (integration): Read the master session schedule from Airtable, including session names, rooms, time slots, and speaker names.
  3. Step 2 (code): Analyse the schedule for conflicts — room double-bookings, speaker overlaps, sessions exceeding their time slot, and back-to-back sessions with less than 15 minutes buffer.
  4. Step 3 (conditional): If no conflicts are found, skip to a brief "all clear" message. Otherwise, continue to the detailed report.
  5. Step 4 (LLM): Generate a conflict report with each issue described clearly, the affected sessions listed, and a suggested resolution.
  6. Step 5 (integration): Post the conflict report to #conference-planning on Slack.

Integrations Used

  • Airtable — master session schedule with rooms, times, and speaker assignments
  • Slack — conflict reports and all-clear notifications

Who This Is For

Conference organisers and programme managers running multi-track events with 20 or more sessions, where schedule changes happen frequently and manual conflict checking is no longer practical.

Time & Cost Saved

Manually auditing a 40-session conference schedule for conflicts takes 30-60 minutes each time the agenda changes, and subtle issues are easily missed. Running this workflow daily during the planning phase catches problems within hours of a schedule change. The combination of integration, code, LLM, and conditional steps costs a small number of credits per run.