Working With Playbooks


As discussed in previous sections of our Help Site and DocJuris University, Playbooks are high-level function based on a static set of rules and policies your team has developed for a specific Contract Type. The expert driven AI system of DocJuris uses Playbooks as a cornerstone function within the Contract Analyzer. Playbooks are optional, but increase the utility of DocJuris.

While in DocJuris Users can also create their own Playbooks and see their application in real time. As a Contract is reviewed in the Analyzer, language is being compared and Analyzed against Playbooks and their component Issues.

Note: Playbooks, their components, and utility are discussed at length in the Playbook Sections of the Help Site and DocJuris University.

How Playbooks are Organized and Shown in the Analyzer

Playbooks are organized and composed of Issues that appear on the Left Side within the Sidebar. From the Sidebar, it is easy to “navigate” to different parts of the Contract by clicking or selecting each Issue, which are organized under Issue Groups (Headings to prevent an excessive list of Issues). Issues are created in Playbooks on specific language (Issue Tags) designated by the User for the AI system to search and highlight during Analysis. Issues reflect the User’s or Counterparty’s Position, and have a robust organization of customizable information.

What Information Can Be Found Within Each Issue

Issues contain relevant information beyond the highlighted language. Drafter’s Notes, External Negotiation Commentary, Deviation Guidance, and Preferred Position are just some of the available fields.

Using Playbooks and Functions

  • To access a Playbook in the Analyzer, select the relevant Playbook.
  • When an Issue is found, it will appear in the Sidebar in addition to highlighting the text within the Contract. The number next to an Issue represents the total times the Analyzer has found the appropriate language relevant to the Issue.
  • If the Analyzer does not find the Issue within the Contract, it is listed as “Missing”. Two strategies for using the Analyzer with the Missing function are Missing Green and Missing Red. Missing Green is when objectionable language is not found, and Missing Red is when preferred language is not found. The Contract can also be marked Complete.
  • Issues are configured with Issue Tags, which is essentially the language or information associated with a particular Issue. The Issue Tags do not just identify a concept, but help determine what is wrong. The AI system allows for data processing in this case.
  • The Contract Analyzer does not just apply the Playbooks to a Contract, but also utilizes advanced AI to add and edit Provisions, upload, attach, and Export Amendments.

Note: While in the Analyzer, the Playbook fields can be edited in a limited fashion. Fields can be edited, but no new Issues can be added. To add an Issue, access the Playbook from the Playbook Editor.

Methods for Using Playbook Issues

Contract review in DocJuris typically has two methods for using a Playbook.

Users can:

  1. Go line by line through the contract, editing each Issue.
  2. Go Section by Section.

By navigating to each Issue within the Sidebar regardless of methodology, User’s can not only see the relevant language but add Drafter’s Notes, insert clauses and provisions, and standard commentary.

Use Case Example: Governing Law

See the Video Overview on the a Use Case for the application of the Playbook feature within the Contract Analyzer.

When a Contract is Analyzed, the Playbook is configured with a “Governing Law” Issue.

By clicking on the Governing Law Issue, it expands in the Sidebar to Section Level.

Within the Issue, the information is provided that shows Deviation Guidance, Drafter’s Notes, External Negotiation Commentary.

Video Overview