Event Communications Timeline and Message Audit
Audit your event announcements, reminders and day-of messages for missing information, timing gaps and conflicting details across channels.
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.
Please audit all the communication I have planned or sent for an event, to see whether attendees get the right information at the right time. I will paste the messages and the dates I sent them. Inputs: the event date and time [EVENT_DATE_TIME], the messages with channel and send date (email, social post, flyer text) [MESSAGE_LIST], the key facts an attendee needs, such as place, start time and cost [KEY_FACTS], and our audience groups [AUDIENCE_GROUPS]. Create: (1) a consistency table with rows for each key fact and columns for each message, marking Present, Missing or Conflicts, followed by a count of conflicts; (2) a timeline table with columns Days before the event (show arithmetic), Message, Channel, Goal; then identify gaps longer than a week and reminders that arrive too late to be useful; (3) a clarity score from 1 to 5 for each message, based on whether it has one clear call to action, a date and place near the top, and plain wording, with the reason; (4) a rewrite of the weakest message in under 120 words; (5) a recommended simple sequence of five messages to send, with the purpose of each. Guardrails: do not invent details; if a fact is absent, write "not stated" and list it as a gap. Do not suggest spam-like tactics such as fake scarcity. Mark any mailing rule or consent point as [VERIFY]. Do not send anything. Add a worked example with invented dates: event on 20 June, first announcement on 1 May, next message on 30 May. Show the 29-day gap and the fix.
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.
See an example result (fictional data)
Consistency table (invented) Start time: email 18:30, flyer 19:00. Conflict. Place: Present in all three messages. Cost: Missing from the social post. Conflicts: 1. Missing: 1. Timeline: event 20 June. First announcement 1 May = 50 days before. Next message 30 May = 21 days before. Gap between them: 29 days (30 May - 1 May). Flag: gap longer than a week. Clarity score for the social post: 2 out of 5. It has no date near the top and two calls to action. Suggested rewrite: "Join us Friday 20 June, 18:30, Town Hall. Free entry. Reserve your seat: [LINK]."
Illustrative only, made-up data. Your results will differ and must be reviewed.