This topic will walk you through the basics of playbooks.
Skip To:
Playbooks
Playbooks enable you to standardize use and substitution of clauses in your contracts. You can build a playbook that walks your team through standard language and approved clauses in contracts. This empowers legal teams to delegate reviews and revisions, only requiring escalation if your playbook does not provide adequate support for your specific use case.
Playbook permissions are additive. This means if a user had Edit permissions for playbooks from one group they’re in, they have Edit permissions regardless if they are also in groups with None or View permissions.
Conditional Clauses and Playbooks are two features in Ironclad that help simplify the substitution of language in your contracts. We do not recommend using Playbooks and Conditional Clauses simultaneously for the same clause on any workflow configuration.
Clauses
There are three different types of clauses:
- Standard: your default language
- Fallback: additional clause options that are commonly requested
- Custom: indicates that a custom language is used in the agreement as an alternative to the provided fallbacks
You can physically order the fallback tiles in your playbook. You can also include instructions on which order they can be applied in.
The Name and Description fields enable you to create a naming convention that indicates your order of preference. For example, Fallback 1, Fallback 2, etc. You can also leave detailed instructions about how, when, and where to substitute fallback language.
Playbooks are built at the workflow configuration level, meaning they are attached to specific contract types. All contracts launched from that workflow configuration have the same playbook. If you save an update to your playbook, it automatically renders that update into every playbook attached to contracts launched from that configuration, even ones in flight. You are reminded of this when you publish your playbook changes, and you can easily cancel if you do not want the changes to be pushed out to all the contracts connected to that workflow configuration’s playbook.
Use Case
WonderWeb Inc. deletes Fallback 1 in their Services Agreement playbook and saves their changes. All playbooks tied to workflows launched from that Services Agreement configuration no longer have Fallback 1, even the agreements that are live.
Access Your Playbook
You can access playbooks within Workflow Designer and the Editor experience.
When you access playbooks within the Editor, you see a paper icon in the sidebar located to the right of your document.
When you access playbooks within Workflow Designer, playbooks are located in the same panel as Fields and Conditions.