Overview
If Topics define what matters and Search Criteria teach the AI how to find it, Outcomes define what happens next.
In PlaybookOS (PbOS), every topic must have two outcomes:
- FOUND – when the AI detects relevant language.
- NOT FOUND – when no matching clause is present.
Outcomes are what make your playbook actionable. They convert detection into clear reviewer tasks, ensuring consistent, defensible decisions across every contract.
Outcomes
Why Outcomes Matter
🎯 They Turn Findings Into Action
Outcomes tell DocJuris exactly what to do once a clause is identified (or missing). Each outcome triggers a task with an action label such as Accept, Edit, Reject, Add, or Escalate.
This is what powers the PbOS task list — reviewers immediately see what to focus on, what to change, and what to leave alone.
⚖️ They Create Consistent Decision-Making
When the same clause appears in multiple contracts, every reviewer sees the same guidance.
- No more subjective calls.
- No more guessing what “good enough” means.
Each outcome pairs an action with a short explanation — helping reviewers understand not just what to do, but why it matters for your business or risk profile.
🤖 They Drive Automation and AI Redlines
Outcomes are also where automation begins.
When paired with Scenarios or AI instructions, DocJuris can automatically:
- Generate redlines,
- Apply fallback language, or
- Flag issues for escalation.
That means fewer manual edits and faster turnaround — without losing human control.
Actions You Can Assign in Outcomes 🚫
Each outcome can initiate one of several standardized actions. These actions appear directly in the reviewer’s task list and define the next step.
✅ When a Clause Is Found
| Action | Description |
| ACCEPT | Clause meets company standards; no changes needed. |
| REVIEW | Clause may be acceptable but needs human review or context. |
| EDIT | Clause exists but needs revisions or redlines to align with policy. |
| REJECT | Clause is unacceptable and should be deleted. |
| ESCALATE | Requires higher-level approval before finalizing. |
| PROCEED | Leads to deeper analysis through a Position (e.g., jurisdiction or carve-out review). |
🚫 When a Clause Is Not Found
| Action | Description |
| ADD | Insert your preferred or standard language. |
| ACCEPT | It’s okay that this clause is missing. |
| REVIEW | Human review needed before deciding whether to add it. |
| ESCALATE | Raise to leadership for decision or policy guidance. |
These predefined actions ensure that every outcome in PbOS is actionable, traceable, and consistent with your organization’s risk framework.
Designing Strong Outcomes
Keep explanations short
One or two sentences are enough to orient the reviewer.
Always define both outcomes
Every topic needs a FOUND and NOT FOUND path.
Be specific with actions
Avoid vague guidance — tell reviewers exactly what to do next.
Use “Proceed” wisely
Only use PROCEED when a deeper analysis (via Positions) is truly required.
Pair with Scenarios for flexibility
If a clause’s handling depends on context (e.g., region or counterparty), use Scenarios to adapt your guidance.
Example: Outcomes in Action
Topic: Limitation of Liability
- FOUND → REVIEW: Check that liability caps include carveouts for confidentiality and IP breaches.
- NOT FOUND → ADD: Insert your standard limitation of liability clause.
The reviewer now sees two clear, guided tasks — one for review and one for insertion — each tied to a specific business rationale.
Key Takeaway
Outcomes are the decision engine of PlaybookOS. They turn clause detection into clear, consistent, and auditable next steps for your reviewers.
When written clearly, Outcomes ensure that every clause leads to confident action — whether that means accepting what’s there, redlining what’s not, or escalating what needs another set of eyes.