Build a technology-dispute chronology from the correspondence
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- Turn the contract and the correspondence file into a chronology of alleged breaches, notices and responses, with a list of missing documents.
- What the lawyer must review
- Check dates against the file
- Decide limitation, notice and breach from the contract and current law, not chronology labels
- 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 | Potential support includes summarising source material. Confirm the tool’s capability and permitted scope. |
| Lawyer | Set the scope, supervise the work closely, verify every part relied on, resolve omissions and exceptions, and approve the exact output. |
Checklist
- Calculate operative dates independently from the current rule and actual triggering event. Check exceptions and record the verified deadline.
- Review operative clauses in the complete document, including definitions, cross-references, schedules and inconsistencies with the instructions.
- Confirm that the wording reflects the client’s instructions and contains no unintended admission, concession or commitment. Check the recipient and tone.
- Verify dates, people and sequence against contemporaneous records. Preserve uncertainty and identify gaps or conflicting accounts.
- Verify the applicable jurisdiction and the version of each relevant law, rule or instrument in force at the material time.
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Resolve exceptions and record the responsible lawyer’s approval of the exact output and intended use.