Here are some best practices for creating and managing your custom Playbooks in Spellbook:
Start With a Clear Goal
Before building your Playbook, define what “good” looks like. Ask:
What specific provisions or risks do you need to catch?
What should (or shouldn’t) appear in this type of document?
Are there fallback positions or preferred wording you want to recommend?
Playbooks are most effective when they’re purpose-built to enforce these expectations.
Focus on Reusability
Create Playbooks for documents you review regularly. These might include:
NDAs with third parties
Master Services Agreements
Vendor agreements
Employment offers or consulting contracts
Aim to build modular Playbooks that can be adapted for similar use cases or tailored per client.
Be Specific With Your Rules
The more precise your requirements, the more valuable your Playbook will be use:
Clear conditions (“The term should not exceed 12 months”)
Suggested language (“We prefer: ‘The agreement may be terminated by either party with 30 days’ notice.’”)
Fallback positions when ideal terms aren’t met
Avoid vague prompts like “Check termination clause”—instead, guide users toward the expected structure or red flags.
Assign Ownership
We recommend assigning one or two Playbook owners within your organization to:
Create and maintain Playbooks
Coordinate input from other stakeholders (legal, ops, compliance)
Keep Playbooks up to date with changes in policy or law
This helps ensure your Playbooks stay consistent, current, and aligned with your goals.
Review & Update Regularly
Your business and risk profile evolve—your Playbooks should too. Set a quarterly or biannual reminder to:
Remove outdated requirements
Add new fallback positions
Tweak wording based on real-world negotiation outcomes
Frequent review ensures your Playbooks remain relevant and helpful.
Test Before Relying on It
Before rolling out a new Playbook across your team:
Test it on sample documents
Check that it catches (and doesn’t miss) key issues
Ensure the suggestions and fallbacks make sense in real use cases
Getting feedback from reviewers who actually use the Playbook is essential.
Document Naming & Organization Matters
Use a consistent naming convention to keep Playbooks easy to find and manage. For example:
NDA - Vendor
MSA - Preferred Terms
Employment Agreement - Canada
If you work across multiple jurisdictions or clients, consider adding location or client names to your titles.
Common Pitfalls to Avoid
Creating overly broad or vague rules
Letting too many people edit the Playbook without coordination
Not assigning ownership for updates
Failing to test Playbooks on real documents before rollout
Have other questions? Please reach out to our Support team at Success@spellbook.legal