Draft a data-processing, IP, SLA or exit schedule from the playbook
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- Produce a first-draft schedule from the playbook and deal facts, listing definitions, service levels, change control and transition terms that need commercial input.
- What the lawyer must review
- Read each schedule against the main agreement
- Confirm privacy, IP ownership and liability work together under the governing law
- 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 preparing preliminary structure or wording and 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.
- Confirm that the actual tool, feature and processing terms permit use of this information, including access, retention, training and disclosure conditions.
- 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.
Forms and precedents for this task
| Form or precedent | Kind | AI use | Summary |
|---|---|---|---|
| Service level schedule with service credits (SaaS, managed or hosted services) | Clause | AI use Yellow | A service level schedule for a technology services contract: availability and support response targets, measurement and exclusions, service credits and caps, chronic failure rights, reporting, and an ACL check on whether credits can be the sole remedy. |
Signed-in accounts can read the full text of each one. All precedents.