Spot departures from the playbook before counsel reviews them.
Compare a vendor agreement with attorney-approved guidance, collect related matter context, and prepare a structured issue list for counsel.
How this composition works
This workflow organizes first-pass contract review without treating model output as legal advice. It retrieves the approved agreement and playbook, identifies language that may depart from documented positions, and prepares questions with citations. Counsel validates every conclusion and proposed change.
Open the approved matter files
Retrieve the agreement and related documents from the scoped folder.
Apply the legal playbook
Compare terms only with the attorney-approved positions and fallback guidance.
Prepare the issue list
Draft cited questions and proposed language in the standard review format.
Route to counsel
Prepare the review email but leave the external send to the accountable lawyer.
Connected systems
These are the real product connectors composed for this example, each scoped to the credential permissions your workspace approves.
Google Drive
Read, search, and manage files in Google Drive.
Explore connectorNotion
Read, search, and update Notion pages and databases.
Explore connectorCraft
Manage markdown blocks in collections with create, edit, delete, move, and undo capabilities.
Explore connectorOutlook
Read Outlook mail and calendar via Microsoft Graph (read-only).
Explore connectorOptional skills
Where relevant, skills add reusable method and verification. The connectors and agent instructions remain the primary building blocks.
Try asking
More examples for Legal
Build a governed workflow like vendor contract review.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.