Event or Conference Schedule Audit for Overlap, Breaks and Flow
Check a programme for clashes and tired attendees.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit an event schedule. The programme with times, rooms and speakers: [PROGRAMME]. Attendee types and numbers: [ATTENDEES]. Venue layout and travel time between rooms: [VENUE_AND_TRAVEL_TIMES]. Check for overlapping sessions that appeal to the same audience, transitions shorter than travel time, long stretches without a break or food, late starts after a long morning, too many sessions in one format, speaker repeats, and an ending that loses people. Make a table with Time, Session, Room, Conflicts, Transition time, and Fix. Calculate the total sitting time per day, the number of breaks, and the longest block without a break, with the arithmetic. Suggest changes and a 'plan B' if a speaker cancels. Provide an attendee-facing summary of the day. Do not invent venue details; mark them [VERIFY]. Add a worked transition check: session ends 10:45 in Room A and the next starts 10:50 in Room D with a 6-minute walk, so the transition is short by 1 minute plus time for questions; recommend a 15-minute gap and show the effect on the rest of the morning schedule.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.