Skip to content
New: a sample workflow audit report
Scenox Studios

Run conflict checks on new matters

When a new matter is opened, the system extracts the parties and related names, searches your client and matter records, and lists possible conflicts with the match reasoning. A lawyer clears or escalates each one. For firms where conflict checks wait on a person with the database access.

Run conflict checks on new matters

6 steps

  1. 01

    Extract the names

    Model
  2. 02

    Search the records

    Rules
  3. 03

    Assess the matches

    Model
  4. 04

    Clear or escalate

    Person
  5. 05

    Record the decision

    Rules
  6. 06

    Notify the requester

    Rules

At a glance

Trigger
A new matter or prospective client is submitted.
Typical inputs
  • New matter intake form
  • Client, adverse party and related-party records
  • Past matter data
  • Conflict policy
Systems it usually connects to
  • Clio
  • NetDocuments
  • iManage
  • Outlook
How the work splits

3 rules, 2 model, 1 person steps

How it runs, step by step

6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.

  • Rules Fixed logic in code
  • Model AI reads or drafts, with a confidence score
  • Person A named person decides
  1. 1

    Extract the names

    Model

    A model pulls parties, related companies and individuals from the intake form and attached documents.

  2. 2

    Search the records

    Rules

    Names and aliases are searched across your clients, adverse parties and past matters using exact and fuzzy matching.

  3. 3

    Assess the matches

    Model

    A model explains each potential match, such as a former client with a similar name, and suggests whether it needs attention.

  4. 4

    Clear or escalate

    Person

    A lawyer or the conflicts team reviews each potential match and decides whether it is a conflict.

  5. 5

    Record the decision

    Rules

    The search, the matches and the decision are stored with who decided and when.

  6. 6

    Notify the requester

    Rules

    The matter opens or is held according to the decision, with the reason communicated to the requester.

Where people approve

The decisions that stay with your team, whatever the confidence score says.

  • The conflicts team decides every potential match.
  • Partners decide waivers and ethical walls.
  • No matter opens until the check is cleared.

KPIs to track

What to measure, before and after. Targets come from your own baseline.

  1. 01Hours from request to decision
  2. 02Potential matches reviewed per matter
  3. 03Matters opened before clearance (should be zero)
  4. 04Checks that needed a second search

Questions about this workflow

Can a model decide that there is no conflict?

It can rank and explain matches, but a person clears them. A missed conflict has professional consequences, so the model widens the search and the lawyer makes the call.

Does it use data from other clients?

Only within your own records and under your confidentiality rules. Search results are visible to the people who are allowed to see them, and access is logged.

Which steps use rules, a model and a person?

Rules: search the records; record the decision; notify the requester. Model: extract the names; assess the matches. Person: clear or escalate. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.

What do we need to start?

Typically: new matter intake form; client, adverse party and related-party records; past matter data; conflict policy. You also need read access to Clio, NetDocuments, iManage and Outlook, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.

Where this fits at Scenox

More use cases like this one

All 60 use cases

Plan how to run conflict checks on new matters with an engineer.

A 30-minute call with an engineer. You will leave knowing what a system could do for that workflow and what it would take to build.

What happens next

  1. 1

    Strategy call

    We learn how the workflow runs today and what a good outcome would be.

  2. 2

    Workflow audit

    We map the process and measure where a system would save the most time.

  3. 3

    Proposal

    A written scope, timeline and fixed price for your first system. No obligation to build.