How can event teams keep an event-day issue log and brief the director with AI?
A coordinator pastes the floor messages and voice-note transcripts into an issue-log Skill set up with your own log format. ChatGPT turns them into a running log with a time, area, owner and status for each issue, and drafts a short summary for the event director on request, such as every hour or before a key moment in the show. It marks anything unclear as “to confirm” instead of guessing. Safety, medical and security incidents still go through your venue emergency plan by radio and phone first; the log only records them.
Why issues get lost on the day
On event day, problems arrive from everywhere at once: a supplier WhatsApp group, the crew group, a radio call, a voice note from the registration desk. Each one is handled, but nobody has the whole picture. The director asks “what is still open?” and the answer depends on who is standing nearby. After the event, the same scattered messages are needed again for the client report and the supplier conversations. A running issue log fixes both, and the slow part, typing it up while the show runs, is the part a Skill can draft.
What goes into each log entry
Swipe to read every column, or focus the table and use the arrow keys.
| Field | Drafted from | Who confirms |
|---|---|---|
| Time reported | Message or voice-note time | Coordinator, where the time is unclear |
| Area | Words in the message, matched to your floor plan names | Coordinator |
| Issue | One plain sentence summarising the message | Coordinator checks it against the original |
| Owner | Your role list, such as AV lead, catering lead or registration lead | Production manager assigns or changes it |
| Status | Open, in progress or resolved, from follow-up messages | Owner confirms it is resolved |
| Client or supplier impact | Flag only, for example “guests affected” | Account manager decides what to tell the client |
A worked example
What the coordinator pastes at 19:40 (synthetic)
18:52 Registration: printer for badges jammed, using spare 19:05 Voice note (transcript): "lift to ballroom level stuck, guests using stairs, venue informed" 19:18 AV: mic 2 crackling, swapping before speeches 19:31 Catering: 14 extra vegetarian meals requested, kitchen checking 19:36 Registration: spare printer working nowDraft issue log and director summary from AI
1. 18:52 · Registration · Badge printer jammed Owner: Registration lead · Resolved 19:36 2. 19:05 · Ballroom lift · Lift stuck, guests using stairs Owner: Venue, via operations lead · Open, TO CONFIRM 3. 19:18 · Stage · Mic 2 crackling Owner: AV lead · In progress 4. 19:31 · Catering · 14 extra vegetarian meals Owner: Catering lead · Open Director summary, 19:40 - 3 open items. None reported as a safety incident in these messages; confirm item 2 with the venue duty manager. - Before speeches at 20:15: mic 2 swap (AV lead). - Item 4 may affect the main course timing on the run-of-show. - Item 1 resolved with the spare printer.
Synthetic event, messages and timings for illustration only.
How it fits your event day
- Your format and roles. The Skill uses your log template, area names and role list, so owners appear as your team knows them. When the template or role list changes, the production manager approves the new version and the Skill is refreshed from it.
- Manual input is the default. A coordinator copies messages and voice-note transcripts into ChatGPT at set times. Reading WhatsApp groups, radios or a ticketing system directly would need a separately agreed, configured and tested integration.
- One log, used twice. The same log feeds the post-event report for the client and any timing change on the run-of-show.
Guardrails
- The log is a record, not an alarm. Medical, fire, crowd and security incidents follow your venue emergency plan by radio and phone first. ChatGPT does not monitor messages, raise alerts or notify anyone; instructions do not make it an alerting system.
- AI drafts can misread a transcript, merge two issues, drop a message or invent a detail. The coordinator checks each entry against the original messages, and the production manager confirms owners and status before the summary is relied on.
- Nothing is sent to the client, suppliers or crew automatically. The account manager decides what the client hears and when.
- Start with a past event’s messages with names and phone numbers removed. Real guest, VIP or crew details belong in your approved ChatGPT workspace, configured with the access and retention your business decides. See ChatGPT governance.
An issue-log Skill can be a single Skill for AED 97. Event companies that want the log, run-of-show and post-event report working together usually choose a fixed-price package from AED 7,500. See the pricing page.
Common questions
Can ChatGPT keep an issue log during a live event?
Yes, as a drafting tool. A coordinator pastes floor messages and voice-note transcripts at set times, and ChatGPT updates a log with time, area, owner and status in your format for the production manager to check.
Does it alert us when something goes wrong?
No. It does not watch your messages or send alerts. Urgent and safety issues are handled by radio and phone under your venue emergency plan, and are added to the log afterwards.
Can it read our WhatsApp groups directly?
Not by itself. The default is that staff copy messages in. Reading groups or other systems directly needs a separately agreed, configured and tested integration.
What happens to the log after the event?
It becomes the issues section of the client report and the starting point for supplier conversations, after the account manager has checked it.