New to PlaybookOS? This article covers PlaybookOS (PbOS), our current contract review platform. If your organization is still using Playbooks v1, please refer to our legacy Playbooks v1 documentation. To learn about migrating to PlaybookOS, contact sales@docjuris.com or your Customer Success Manager.
Overview
PlaybookOS (PbOS) is the next generation of DocJuris Playbooks. Unlike legacy playbooks that functioned as long static checklists, PbOS generates task lists that highlight only the relevant clauses and actions needed for each contract. This task-driven approach reduces noise and ensures reviewers focus on what matters most.
PbOS playbooks are built in the DocJuris Admin Console and applied in the Contract Analyzer. Once applied, the system automatically identifies contract language and generates actionable tasks based on the playbook logic.
How Playbooks are Organized in PbOS
In PbOS, playbooks are structured into Topics. Topics represent a contract provision (e.g., Limitation of Liability) and contain:
Search criteria (how to identify the provision in a contract)
Outcomes (what to do when the provision is found or missing)
Actions (the guidance provided to the reviewer)
Scenarios (optional — contextual variations for different business lines, negotiation paths, or fallback positions)
When a playbook is applied in the Analyzer, these topics appear as Tasks in the Tasks tab.
Navigating Tasks
By default, tasks are grouped by Category (e.g., Risk Terms, Term & Termination).
Reviewers can also regroup and filter tasks by:
Category
Action (e.g., Accept, Add, Reject, etc.)
None (a simple flat task list)
Open or Completed task items
This flexibility lets users tailor their review workflow to the contract at hand.
Information Within Tasks
Each task carries forward the supporting content from legacy playbooks, including:
Drafter’s Notes
Internal Negotiation Commentary
Deviation Guidance
Preferred/Fallback Clauses
AI Drafter’s Instructions
Depending on how the playbook is built, this information may be presented at either the Topic level or the Scenario level. Reviewers can apply the base scenario (default AI instructions) or select a specific scenario for the contract context.
Action Badges
Each task is assigned an Action badge, which makes the reviewer’s next step clear. Common actions include:
Accept – Clause matches the standard; confirm and mark complete
Add – Missing clause; insert preferred or fallback language
Review – Needs manual judgment (e.g., project scope)
Reject – Push back or remove under policy
Edit – Clause present but not aligned; revise accordingly
Escalate – Requires approval from outside the drafting team
Ignore – Not actionable; filtered out of the task list
Methods of Review
PbOS supports two main review methods:
-
Task-List Driven (Recommended)
Reviewers go through the task list, resolving each flagged item in turn.
This ensures nothing is missed and reduces time spent scanning irrelevant issues.
-
Section-by-Section Review
Reviewers can still move through the contract directly.
Use “Show Matching Tasks” to reveal any flagged tasks for that section.
Both methods can be combined depending on the reviewer’s preference and the complexity of the contract.
Use Case Example: Governing Law
In legacy playbooks, users had to interpret “missing green” vs. “missing red” reports.
With PbOS:
The Governing Law topic automatically generates a task if relevant.
The task is labeled with an Action badge (e.g., Accept, Edit, Reject, or Review).
Supporting guidance, commentary, and fallback clauses are provided.
Reviewer confirms the action or applies edits, then checks off the task.
This streamlined approach eliminates the guesswork of V1 checklists and focuses the reviewer directly on actionable steps without the need to dive into every issue within your playbook or reference a screening report on an external application.