Skip to main content
Last Updated: 2026-06-26
Concept: Library

Concept: Library

Library enables administrators to create a repository of approved clauses and negotiation playbooks that ensure consistency across all contract reviews.
You can access the Library from the top navigation, where you can manage 3 key components:
Clauses
,
Negotiation Requirements
, and
Playbooks
.

Clause Library

  • Use the Clause Library as a reference for markups and requested edits instead of redrafting from scratch.
  • With just 2 clicks, you can drop in preferred language or acceptable fallback clauses, which administrators can designate for each clause type.
  • To ensure legal and business best practices, provide contract negotiators with guidance on preferred and fallback clauses, flag unacceptable or non-negotiable terms, and supply admin-generated guidance on using context-specific clause variations.
  • Clauses added to the Library can be filtered by using the clause name or position labels:
    • Preferred
      for clauses that are the first choice for contracts. We display preferred clauses with a green background. [Note: We can change this language.]
    • Fallback
      for acceptable clauses that aren't the primary option. We display fallback clauses with a gray background.
    • Walk away
      for clauses that are unacceptable for any contract. We display walk-away clauses with a red background.

AI Playbooks and Requirements

Playbooks and AI Requirements enable you to transform the Library from a static reference tool into an automated AI review engine.
  • Negotiation Requirements
    : These are reusable, auditable instructions that tell the AI exactly what to look for. You can define specific logic for the AI to evaluate, such as checking for required terms or flagging language that deviates from a preferred position. Negotiation Requirements can be linked directly to your Clause Library to suggest automated redlines.
  • Playbooks
    : These act as the orchestration layer. You can group specific Requirements into a Playbook and scope them to certain contract types or specific workflows.