Incident timeline from chat and logs without blame Prompts
Builds a sourced timeline from your chat history and log excerpts, flags missing times and leaves causes open, without assigning blame.
- Area
- Development & IT
- Level
- Advanced
- Good for
- Prepare the timeline for an internal debrief after an outage
- Clarify the order of events from on-call chat and logs
- Collect missing timestamps and open questions before the analysis
How it works
- Paste the chat or ticket history and the relevant log lines with timestamps.
- State the visible start, the visible end and what customers or users actually noticed.
- Do not treat a guessed cause as a fact; resolve open points with your team.
To copy
Create an incident timeline from my material. Do not assign blame, do not invent causes and do not assert technical facts that are not in my material. Time window: [start and end, as far as known] What was visible: [what customers, users or monitoring showed] Chat or ticket history (with timestamps): [paste history] Log excerpts or monitoring notes (with timestamps): [paste excerpts] Already known facts (optional): [paste facts] Check and organise: 1. Timeline: list every event with time, source (chat, ticket, log, monitoring) and the verbatim evidence. 2. Order: where do times or sources disagree? Mark the contradiction instead of resolving it. 3. Gaps: which minutes or steps are missing before anyone can name a cause? 4. Impact: what was visible to users or customers, as far as my material shows? 5. Causes: give only hypotheses that rest on evidence, each labelled as a hypothesis, not as a finding. Output: - table: time | event | source | evidence | certain or unclear - list of gaps and questions for the team - short, blameless summary in five sentences Rules: no names with blame. Do not invent root causes, timestamps or metrics. Do not send or enter anything anywhere.