Build a 48-hour incident chronology from the tickets and emails
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- Extract times, systems, actors and decisions from the incident tickets and correspondence into a chronology, marking gaps.
- What the lawyer must review
- Verify times against the source systems
- Use the chronology for the lawyer's assessment, not as a notification
- Written for / version
- US
Open a jurisdiction version of this task to see which instruments apply: US
Who does what
| Role | What they do |
|---|---|
| Assistance | Extract times, systems, actors and decisions from the incident tickets and correspondence into a chronology, marking gaps. |
| Lawyer | Set the scope, supervise the work closely, verify every part relied on, resolve omissions and exceptions, and approve the exact output. |
Checklist
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Verify every relied-on citation, figure and name against the source document.
- The responsible lawyer approves the exact version before use.
Sources
Confirm the required checking with the responsible lawyer before work starts. The checking approach does not establish permission to use AI.