NOTE: THIS TIMELINE IS BASED ON A STANDARD, SIMPLE IMPLEMENTATION A CHECKLIST
- Includes up to 3 revisions to a checklist; your contract may be different
- More sophisticated checklists may add additional time to the timeline
[Checklist name] Implementation |
Tasks and Meetings (see below for more details) | Estimated Work Time/Turnaround Time |
|---|---|---|
| Week 1 | Legal Engineer (LE) Consult Meeting | 60 minutes |
| LE to build 1st Draft of Checklist | 1 week | |
| Week 2 | LE previews Checklist to Stakeholders, asks questions to help complete | 1 hour |
| LE makes required changes and Stakeholders are trained for Checklist testing | 3 days for changes, 1 hr for training | |
| Stakeholders test by running at least 2 docs through the Checklist, and provide feedback | 1-2 hours per document (2-4 hours total) | |
| Week 3 | Weekly check-in meeting | 30-60 minutes |
| Stakeholders continue testing by running at least 2 docs through Checklist, and provide feedback | 1-2 hours per document (2-4 hours total) | |
| Week 4 | LE makes requested changes and releases Checklist for additional testing by Stakeholders | 3 days |
| Stakeholders continue testing by running at least 2 docs through Checklist, and provide feedback | 1-2 hours per doc (1-4 hours total) | |
| Weekly check-in meeting with LE and Stakeholders | 30-60 minutes | |
| Week 5 | Stakeholders perform final testing by running at least 2 docs through Checklist. and provide feedback | 1-2 hours per doc (1-4 hours total) |
| Week 6 | Go-Live/Early Adopter training | 60 minutes |
| Weekly check-in meeting with LE and Stakeholders | 30-60 minutes |
Week 1: Getting Started
Legal Engineer (LE) Consult Meeting
Attendees: Onit Legal Engineer and [Customer] Playbook Stakeholders
Topics:
- Introduction to Legal Engineer,
- Discussion of documents provided (Playbooks, Templates, Clauses)
- Confirm Checklists to build, which to build first, and paper type (First or Third Party)
-
If [Customer] does not have Playbooks, determine the best strategy to start drafting the first Checklist
- Building a Playbook from scratch requires an additional 1-2 weeks
- Schedule Weekly Check-in meeting (if not already scheduled)
Work to be Done after LE Consult Meeting
- Stakeholders: Provide or complete information still needed to start building the first Checklist.
- LE: Create a Draft Checklist to present at the next Weekly Check-in meeting.
Week 2: Draft Checklist and Release for Testing
First Weekly Check-in Meeting
Attendees: Onit Legal Engineer and [Customer] Playbook Stakeholders
Topics:
- LE presents a Draft Checklist and delivers training to enable testing
- Stakeholders to confirm that the Draft Checklist is on the right track and agree to test
Work to be Done after the first Weekly Check-in Meeting
- LE: Make any required changes identified in the Check-in Meeting and release the Checklist (with Testing Guide) to Stakeholders for testing
- Stakeholders: Test by running at least 1 document through the Checklist in Catalyst Contract Review, prepare questions and revision requests for the next Check-in Meeting
Week 3: First Revision and Continued Testing
Weekly Check-in Meeting
Attendees: Onit Legal Engineer and [Customer] Playbook Stakeholders
Topics:
- Discuss testing feedback to identify appropriate changes
- LE answers Stakeholders' questions
Work to be Done after Check-in Meeting
- LE: Make changes arising from feedback and the Check-in Meeting, and release the updated Checklist (Revision 1) to Stakeholders for continued testing
- Stakeholders: Test by running at least two documents through the Checklist in Catalyst Contract Review; provide feedback to LE via email
Week 4: Second Revision and Continued Testing
Weekly Check-in Meeting
Attendees: Onit Legal Engineer and [Customer] Playbook Stakeholders
Topics:
- Discuss testing feedback to identify appropriate changes
- LE answers Stakeholders' questions
Work to be Done after Check-in Meeting
- LE: Make changes arising from feedback and the Check-in Meeting, and release the updated Checklist (Revision 2) to Stakeholders for continued testing
- Stakeholders: Test by running at least two documents through the Checklist in Catalyst Contract Review; provide feedback to LE via email
Week 5: Final Revision
Weekly Check-in Meeting
Attendees: Onit Legal Engineer and [Customer] Playbook Stakeholders
Topics:
- Discussion of final testing feedback
- Schedule Go-Live/Early Adopter Training
Work to be Done after Check-in Meeting
- LE: Make final changes arising from feedback and the Check-in Meeting
- LE or Stakeholder: Send meeting invitation for Go-Live/Early Adopter Training
Week 6: Final Revision and Sign-off
Go-Live/Early Adopter Training
- Attendees: Playbook Stakeholders, Early Adopters, or all users
- Topics: How to use your Catalyst Contract Review Checklist
Week 7: Begin the process again for the following Checklist, if any remain to implement
End of Implementation
Close Out Meeting
Attendees: Onit Legal Engineer and AI Adoption Manager, Playbook Stakeholders
Topics:
- What went well during implementation
- What could have gone better during the implementation
- Measuring success with Catalyst Contract Review
- What's next