Generate a Playbook with AI

Writing a playbook from a blank page is slow. You know your negotiation standards, but turning them into a structured list of positions, each with a requirement and a not-found setting, is the part that stalls.

The AI wizard does the first draft for you. You pick the agreement types it covers, answer a few questions about your requirements, and Pactly generates a complete playbook of positions you can review and refine. It is one of four ways to create a playbook, alongside importing a document, starting from scratch, and cloning.

• You need the playbook permission on your role. This is the same permission used for all playbook authoring; there is no separate “playbook editor” role.
• Have your standards within reach. The wizard asks about your requirements, so a policy document, an approval matrix, or a clear sense of your red lines makes the questions faster to answer. You do not upload anything in this flow. To have the AI read an existing document instead, use Import from a document.
• Decide which agreement types the playbook covers (for example, NDA or MSA). The type drives which playbook is offered when you review a contract of that type later.

The wizard runs in four steps: pick the agreement types, answer context questions, let Pactly generate, then review and create.

A generated draft is a starting point, not a finished playbook. The AI infers your standards from a few answers, so before you publish, check each position against what you actually require. In the editor, open the positions Pactly created and confirm three things:

• The description says what the contract must or must not contain. Each position carries a description (the requirement the review judges against), plus three optional note types: Rationale, Technical Drafting Notes, and Internal/Operational Notes. Keep the description declarative and specific. Vague wording such as “liability should be reasonable” gives the AI nothing to judge.
• The “Classification when no evidence found” setting is right. This decides the verdict when a review finds no relevant clause for the position. For a requirement (“must include X”), missing means Not compliant. For a prohibition (“must not contain X”), missing means Compliant. Setting this backwards is the most common reason a review flags the wrong things.
• The suggested clauses are language you would actually use. Any Suggested clauses the AI proposes become the fallback language reviewers can insert during a review. Replace generic wording with your pre-approved clauses where you have them.

For the deeper craft of writing positions well, see Writing Playbook Positions.

The generated playbook stays a draft, visible only to you, until you publish it. Publishing makes it available for reviews and locks its positions. To change a published playbook later, you create a new version. See Creating Your First Playbook for the publish and versioning flow.

Once published, the playbook is selected automatically when you review a contract of a matching type, or you can choose it manually. Running the review itself happens in the web app or the Word add-in, not here in the editor.

• Creating Your First Playbook
• Writing Playbook Positions
• Import a Playbook from a Document
• What is a Playbook?
• Reviewing a Third-Party Contract