Your organization's standard positions, codified and applied automatically, ensuring consistent outcomes across every new agreement.
The challenge
Agreements vary widely in how they define essential provisions. Without a consistent standard, reviewers manually re-derive the organization's position on every new deal, creating a slow process that risks inconsistent outcomes across agreements.
The solution
Ask iManage lets you search your existing contract library, extract and compare language across agreements using Question Lists, and translate the patterns you find into Playbook rules. Once saved, Ask iManage applies those rules automatically to flag any new agreement whose terms deviate from your standard.
Open Ask iManage and use natural language to locate the contracts you want to learn from.
Using existing documents builds a set of agreements that your organization has drafted, reviewed, or executed in the past.
Copy this prompt
Retrieve the 20 most recent CloudsForged cloud service agreements.
Create a review project for identified documents.
Review Projects allow you to run a set of questions against a batch of documents to consistently compare results across each.
Use a Question List to run a standardized set of queries against the documents and capture the results in a structured format.
For Playbook development, Question Lists are the most effective way to extract comparable clause language across source documents.
Review responses with goals in mind:
Consistency - where has your organization used the same or similar language across multiple agreements? This is likely your standard position.
Variation - where has the language varied? Note whether the variation was favorable or unfavorable to your organization.
Fallback positions - when you have accepted language that differs from your standard, that language may represent a viable fallback position for Playbook inclusion.
Use Ask Across to identify the most common provisions in your source documents.
Copy this prompt
Create a suggestion of provisions for me based on the most commonly used language from each section of these agreements
Use a follow-up prompt to build a list of rules, standard positions, and fallback positions based on the provisions in your source documents.
Copy this prompt
Create a playbook for me for these provisions: Definitions, Services, Client Obligations, Fees and Payment, Intellectual Property, Confidentiality, Services Levels and Support, Data Protection and Security, Warranties and Disclaimers, Limitation of Liability, Term and Termination, and Indemnification. For each provision, summarize a rule of what language should be included. Also include an exact position statement based on the most commonly used language for each provision and label it as our standard position. If there is a second most common language used, please provide that as a fallback position.
Export your results as a Word document.
Exporting as a Word document provides easy reference for Playbook creation.
Move to Playbook creation by exiting your review project to the iManage Work homepage, then open Ask iManage side panel and select Playbook followed by New Playbook.
Provide a Name and an option Description for your new Playbook.
Select Add rule then:
Select Required, Preferred or Optional to define the rule status when the Playbook is run.
Enter a Rule description.
Add standard position from your previously exported Word document.
Add fallback position from your previously exported Word document.
Define the Playbooks Visibility across organization to specify if this Playbook can be run by anyone at the organization, or just you.
Continue to Add rule until all rules have been added. To save, select the back arrow.
Your Playbook is now ready to use. Depending on Visibility across organization specified, this will either be available for you or your organization.
More to explore
Email Analysis and Matter Intelligence
Use Case
Contract Vendor Performance Review & Renewal Pipeline
Use Case
Contract Analysis & Key Term Extraction
Question List