Contract intake pre-check
Define the goal, inputs, expected output, acceptance criteria, and risk boundary before turning this into an agent workflow.
Draft a legal or compliance pre-check Skill without blurring review responsibility
Use this page to capture the review context, inputs, jurisdiction, output format, and escalation rules needed for a legal/compliance pre-check agent workflow.
Who this is for
- Legal Ops and Compliance Ops teams
- Business teams preparing materials before expert review
- Automation teams creating safe pre-check workflows
What the intake produces
- Jurisdiction and document context
- Checklist-style output requirements
- Escalation triggers
- Clear non-advice boundary
Skill specification fields
These fields make the request concrete enough for a delivery, research, or product team to draft a first Skill specification within 24 hours.
JurisdictionDocument or request typeInput materialsPre-check criteriaRisk flagsOutput formatEscalation ownerWhat the agent must not decide
Example use cases
Vendor compliance document checklist
Define the goal, inputs, expected output, acceptance criteria, and risk boundary before turning this into an agent workflow.
Policy exception request triage
Define the goal, inputs, expected output, acceptance criteria, and risk boundary before turning this into an agent workflow.
FAQ
Is this legal advice?
No. The intake is for scoping a pre-check workflow. Legal advice, approvals, and final decisions should remain with qualified humans.
Why is this useful for compliance teams?
It standardizes the information collected before review, reducing back-and-forth and making escalation boundaries explicit.