Skip to main content
Last Updated: 2026-06-26
Set Up AI Playbooks

Set Up AI Playbooks

  • Configure the
    Clause Library
    with approved variations if you intend to reference them in your Negotiation Requirements.
  • Ensure you have
    Library: Manage
    role-based access.
Administrators create Playbooks to ensure AI guidance and suggested redlines are specific to the organization’s legal requirements rather than generic best practices.
  1. Click the
    Library
    tab and select the
    Playbooks
    subtab.
  2. Click
    Create Playbook
    .
  3. Choose a creation method:
    1. Start from an Example
      : Select a pre-configured template for Non-Disclosure Agreements (NDAs), Software License Agreements (SLA/EULA), or Master Services Agreements (MSAs). Best for: New customers, trials, or teams that don't have a documented Playbook to start from.
      Examples are only available in Sandbox accounts by request.
    2. Input Negotiation Requirements Manually
      : Build a Playbook from scratch for specific, non-standard requirements. Best for: Teams with specific, non-standard negotiation requirements or those who want complete control over every Playbook input.
  4. Enter a unique name and description.
    Playbooks and Negotiation Requirements require unique names; you can’t reuse names from deleted items.
  5. In
    Scope
    , define the specific workflows or contract types you want to target.
  6. Add or create
    Requirements
    for the playbook:
    1. Clause Name
      : enter the clause name.
    2. Review Criteria
      : enter the prompt instructions for the AI.
    3. (Optional) Select
      Suggest Redlines
      and click
      Add Existing Clause Variation
      to link language from your Clause Library.
  7. Click
    Create
    .
  8. Open the playbook and click
    Publish
    to change the state from Draft to Published and make the playbook available for reviewers in workflow tickets.
Workday adds the clause requirements to the
Negotiation Requirements
subtab located under the
Library
tab. You can modify these clause requirements as many times as you need and reuse them across other playbooks.
If you need a variation that applies only to a specific playbook, without affecting shared instructions, create a new clause requirement with a distinct name and link it to that playbook only.