This Recipes program is currently in pilot, and we'd love to hear your feedback! Once you've finished this recipe, please consider taking a moment to complete this short survey to help us improve our current and future recipes.
Overview
This Playbook is created to take advantage of AI redlining tools in order to streamline the negotiation process for a busy legal user.
The goals of this recipe are:
- Use AI Clause labeling to speed up initial document review
- Reduce time spent on repetitive redlining
- Reduce overall workflow time to completion
Use Case
The ideal workflow configuration for this Playbook recipe is a high-volume workflow that features relatively repetitive redlining, but the Playbook can add value in any workflow where the redlining for a given agreement is done by one or more legal users.
The Playbook leans heavily into Precise Redline functionality, which requires the Playbook user to have approval access over individual clauses.
What You'll Need
| Features | AI Playbooks, AI Assist |
| Permissions | Workflow Designer, AI Playbooks, AI Assist |
| Playbook Options | AI Clause Type, Precise Redlining, Templated Comments |
Supporting Resources
Instructions
To build and use a basic playbook, follow the steps below in order:
Build the Playbook
When building a playbook for workflows with regular legal involvement during negotiation, start by adding 3–5 clauses. Focus on clauses that are frequently negotiated and where your company has a strong preferred position. For each clause, adjust the playbook settings to reflect your preferred language, fallback positions, approvers, and more. This setup ensures consistent, efficient responses during contract negotiations, helping reduce the time Legal needs to be involved.
To create a playbook, you must be an administrator and have Workflow Designer access.
Configure Each Clause
- In Ironclad, click the Workflow Designer tab and select the workflow template you want to edit.
-
On the Document step, locate the panel on the left and click the down arrow located next to Attributes. Click Playbook.
- Click Add Clause indicated by a plus sign.
- Select the AI Clause Type from the dropdown menu. This optional step can assist in detecting clauses. If your clause or term is not available in the list of AI-powered clauses, you can create AI Custom Clauses. Both Out of the Box AI Clauses and AI Custom Clauses will be displayed in this dropdown menu. For more information on AI Clause Types, refer to AI Clauses and AI Customer Clauses Overview.
-
Set a Trigger and Presence Rule. For this recipe, we recommend the following:
- Set Clause Applies When to Always.
- Set Presence Rule to None.
- In the Positions section, hover over Non-standard language and click the three stacked dots. Select Require approval to use position.
-
Define your playbook positions. In the Pre-approved section, click Add, and then configure the following:
- Add a Title: Add a descriptive title of the position.
- Configure Display Position When: Leave Display Position When set to Always.
- Add Default Language: In the Default Language section, enter the default language. This is the language that will be proposed to the clause approver.
- Add Reviewer Notes: You can add internal reviewer notes or comments intended for the counterparty. Use this space to provide context, clarification, or guidance as needed.
- Configure Preferred Position: Under Additional Settings, select Mark as preferred position. This setting signals your preferred positions to your end users that have access to Playbooks.
-
Configure Require Approval to Use Language: Under Additional Settings, you can select or deselect Require approval to use language. This setting allows you to specify which Playbook positions need conditional approval before they can be used. It gives you greater control and visibility over language that requires additional review.
- Your clause's Positions should look like the following:
- Select an approver. We suggest selecting a group instead of a specific user. This helps prevent delays in the contract process if someone is out-of-office. Precise redlining only displays for users that are added as clause approvers.
- Click Add.
- Repeat these instructions to create 3-5 clauses, and then Save your playbook.
Use the Playbook
In an active workflow that uses a workflow configuration containing your new playbook, any clause that doesn’t exactly match your preferred language will appear in the Needs Review section of your playbook.
To initiate Precise Redlining, click the ✨Redline button. Ironclad will generate multiple AI-powered suggestions that align the clause with your preferred position, each accompanied by a Suggestion Rationale explaining the reasoning behind it.
To use a templated comment, open the clause, select your preferred position, and click Add as Comment to replace the clause with the pre-written feedback.
Result
This Playbook is available for any workflow participant who has Playbook negotiation access. The full Precise Redlining functionality is available on a clause-by-clause basis to users who meet the above criteria and have approval access over the clause in question.
Precise Redlining gives you 1-click, AI-powered redlining suggestions based on your company’s preferred language, including several options to choose from for each clause. In addition to these options, you can also strike the existing clause and swap in your existing language fully.
Tips & Variations
This Playbook is designed specifically to help you get started with Playbooks in general and Precise Redlining in particular. If you are comfortable with these features and looking to add additional nuance to your Playbook, consider the following options:
- Add a presence rule of ‘Clause is Required’ to flag if this clause cannot be found.
- Use a condition to configure this Playbook clause to only trigger in certain situations. Perhaps a clause is only negotiated for contracts with a value above a certain dollar amount.