PlaybookOS Modeling: Positions

Overview

If Outcomes tell you what to do next, then Positions tell you how to do it in specific situations.

Positions are the deeper analysis layer in PlaybookOS (PbOS). They let your playbook handle variations within a clause — things like jurisdictions, thresholds, or business exceptions — without overcomplicating the main topic.

You’ll only use Positions when your FOUND outcome uses the PROCEED action. This signals that a clause was found, but more context is needed before deciding how to handle it.

Why Positions Matter

🎯 They Add Depth Without Chaos

Without Positions, your playbook can become bloated with separate topics for every small variation (e.g., “Governing Law – Texas,” “Governing Law – New York,” etc.).

Positions fix that. They let you layer intelligence under a single topic — keeping your playbook streamlined while still handling nuance.

For example:

• Topic: Governing Law 
• Position 1: New York (Accept) 
• Position 2: California (Escalate) 
• Position 3: Foreign Jurisdiction (Reject)

All under one clean, manageable topic.

⚖️ They Reflect Real-World Negotiation Logic

Contracts aren’t one-size-fits-all. Positions allow PbOS to adapt guidance depending on the specific scenario detected in the clause.

That could mean:

• Adjusting your approach for a particular region or country, 
• Evaluating a monetary threshold, or 
• Handling a specific business exception.

This keeps your playbook realistic and practical — mirroring how real negotiations actually unfold.

🧠 They Create Final, Context-Aware Actions

A Position is essentially a mini-topic. It has its own criteria (what to search for within the detected clause) and its own outcomes (what to do when found or not found).

The difference:

• Positions never “proceed” further — they’re the final step in the analysis chain. 
• Their outcomes end with actions like Accept, Edit, Reject, or Escalate.

That makes Positions the point where abstract detection becomes a concrete decision.

How Positions Work in Practice

1. Start with a Topic. 

   Example: Governing Law 

2. Set an Outcome to 

   “Proceed.” Found → Proceed (tells PbOS to analyze the next layer) 

3. Create Positions. 

   Each position defines a deeper check, such as: 

   • Position 1: “New York” → Accept (Preferred) 
   • Position 2: “California” → Review (Needs Legal Sign-Off) 
   • Position 3: “Foreign Jurisdiction” → Reject (Not Allowed) 

4. Add Criteria. 

   Write prompts like: 
   “Search within governing law clauses for mentions of New York.” 
   “Search within governing law clauses for mentions of foreign countries.” 

5. Define Outcomes. 

   Each position includes its own FOUND and NOT FOUND actions, just like a topic — but this time, those outcomes are final.

Example: Positions in Action

Topic: Governing Law

• FOUND → PROCEED: Analyze the specific jurisdiction.

Positions:

• New York → ACCEPT: Standard jurisdiction, no changes required. 
• California → REVIEW: Requires legal sign-off. 
• Foreign Jurisdiction → REJECT: Not permitted per company policy.

This setup means reviewers see clear, contextual tasks that match your actual business rules — without creating three separate topics.

Best Practices

Use Positions Sparingly 

Only add them when a clause truly needs deeper evaluation — most topics don’t. 

Be Clear in Titles

Titles should describe the exact situation being analyzed (e.g., “Foreign Jurisdiction” or “Over $1M Liability Cap”). 

Keep Descriptions Focused 

2–3 sentences explaining when and why this position matters. 

Avoid Nesting Further

Positions are the final layer — they cannot contain additional positions. 

Use Clear Outcomes

Since Positions are final, actions like ACCEPT, EDIT, REVIEW, or REJECT should be explicit and actionable.

Key Takeaway

Positions give PlaybookOS its depth and flexibility. They allow you to capture real-world negotiation complexity without cluttering your playbook with dozens of similar topics.

Think of them as the “sub-logic” that turns a simple clause detection into a context-aware decision. When used wisely, Positions make your playbook smarter, cleaner, and easier to maintain — all while mirroring the way your team actually negotiates.