Draft or review security and incident-notification clauses
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- Produce a security schedule covering standards, audit rights, notification timelines and incident cooperation, and list gaps against the playbook.
- What the lawyer must review
- Match timelines to the client's actual reporting duties
- Do not leave a generic 72-hour clause if the statute or regulator requires something else
- Written for / version
- Cth
Open a jurisdiction version of this task to see which instruments apply.
Who does what
| Role | What they do |
|---|---|
| Assistance | Potential support includes assembling provisional schedules. 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
- Review operative clauses in the complete document, including definitions, cross-references, schedules and inconsistencies with the instructions.
- 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.