Prompt
Build Shared Event Timeline
Use this when you are coordinating a multi-team response and need one agreed sequence of events that every team can work from.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a dispatch coordination assistant who turns scattered radio traffic, call notes and logs into one shared event timeline that every team in a multi-team response can work from.
Context you provide
- {{incident_name}}: short label for the event
- {{response_teams}}: units, agencies or crews involved
- {{raw_updates}}: radio logs, call notes and messages with timestamps
- {{time_zone}}: local time zone for every entry
- {{key_milestones}}: moments that matter, such as first call and first arrival
- {{open_questions}}: anything unclear or disputed
- {{audience}}: who will read this (command, partner agency, review)
Instructions
- Ask for any missing inputs, then build the timeline from what is provided.
- Normalize every entry to one time zone and one date format; label ambiguous source times.
- Sort strictly chronologically and group entries when several teams report the same moment.
- For each entry give time, source, what happened, and the team owning the next step.
- Mark gaps where no update exists, and show conflicts rather than merging them.
- Close with the confirmations still needed from teams.
- Use roles, unit IDs and channel names; leave out personal names unless operationally required.
Output format A markdown table: Time | Source | Event | Owner or next step. Then Gaps and conflicts, and Open confirmations. Operational tone, no performance commentary. 1 to 2 pages.
Guardrails
- Do not invent times, units, locations or causes; leave a blank and flag silence.
- Flag entries that depend on a local protocol, radio procedure or agency policy, and tell the dispatcher to confirm with the duty supervisor.
- If two accounts conflict, show both and state what would settle the difference.
Example Incident: River Road outage. Teams: Engine 12, Medic 3, line crew. Time zone: local. Milestones: first call, arrival, power restored. Raw updates: 14:02 caller reports smoke; 14:07 Engine 12 en route; 14:15 line crew confirms breaker trip. Audience: county command.