Conflict Check
Run a prior-representation conflict check before any vendor dispatch, so adverse-party work never goes to a conflicted vendor.
How it works
Scope ships the dispatch workflow. Your AI calls it. Here is the back and forth.
- You say
Have we ever worked a matter involving Mercer Logistics?
Scope doesScope searches your structured conflict-party log across every matter and returns where that party appears.
- You say
Dispatch the serve.
Scope doesBefore any dispatch goes out, Scope runs the conflict gate against the matter's adverse parties and filters conflicted vendors automatically.
- You say
Show me the gate result for the record.
Scope doesScope returns the conflict-check result on the matter: when it ran, how many vendors were filtered, and which ones.
What you get
- A prior-representation search across your structured conflict log
- An automatic conflict gate that runs before every dispatch
- Conflicted vendors filtered out before quotes return
- The gate result recorded on the matter for OCG and Rule 1.7 review
Vendor categories covered
Sample call
The tool your AI calls to run this workflow.
scope_conflict_log({ party_name: "Mercer", party_type: "defendant" })
// the gate also runs automatically inside scope_dispatch_matterTry it from your AI
Connect Scope to Claude, ChatGPT, Cursor, or any MCP client, then describe a matter and let your AI run the dispatch.
Connect Scope to your AI ->