Conflict checking before the retainer — a practical workflow

A PI firm that takes a retainer and only then realizes the case conflicts with a prior engagement has a problem with three bad endings. The firm has to return the retainer (operational headache). The current case has to be declined mid-stream (reputational damage). The prior client's confidentiality may be at risk (ethical and possibly legal exposure).

Conflict checks at intake — before the retainer is discussed, ideally — prevent all three. This post is about a practical workflow for running them without slowing down the engagement.

What a conflict check actually checks

A conflict check is a search of the firm's prior and current case files for any of the following:

• The subject of the new case has been a client of the firm in a prior matter.
• The subject of the new case was the subject of a prior investigation by the firm — on behalf of someone else.
• A close relative or business associate of the subject matches one of the above.
• The opposing party in the new matter (where applicable, e.g. legal-support cases) was previously a client of the firm.

If any of these turn up, the firm has a judgment call to make. Some conflicts are absolute (can't take the case). Some are waivable with informed consent from both parties. The firm's WSP and the investigator's licensing-board ethics rules govern the specifics.

The identifiers to capture at intake

A meaningful conflict check requires more than a name. The intake should capture:

• Legal name and any aliases the caller is aware of.
• Approximate date of birth or age range.
• Last known address or city.
• For corporate subjects: legal entity name, DBA names, principal officer names.
• Relationship context: who is the subject to the caller? (ex-spouse, business partner, employee, opposing party in litigation)

These fields are not invasive. They're what the firm needs to distinguish "Robert Smith in Tampa, age 45" from "Robert Smith in Tampa, age 67" — both of whom may exist, and only one of whom may be a conflict.

When the check runs

There are two reasonable patterns:

Pattern A: Check at intake, before the callback

The intake assistant captures the identifiers and the firm runs an automated check against the case management system in the background. The investigator's callback happens after the check completes — either confirming no conflict and proceeding to scope the engagement, or flagging a conflict and handling it.

This is the fastest pattern from the caller's perspective. The callback either moves forward without friction, or it surfaces the conflict early.

Pattern B: Check at first callback, before retainer discussion

The intake captures the identifiers, the investigator calls back, has a preliminary conversation, runs the conflict check during or after that call, and only then quotes a retainer.

This is the slower pattern but it gives the investigator more context before running the check (sometimes the conflict isn't visible from the intake identifiers alone — it surfaces from how the caller describes the relationship).

Most firms end up running both — a coarse automated check at intake, and a more careful check at first callback, with a final review before the retainer is committed.

The case management integration

A useful intake-to-CMS integration writes the conflict-check fields into the casefile in a structured way, runs the automated check if configured, and surfaces the result on the casefile:

CONFLICT CHECK — automated
Status: NO MATCH FOUND (search against 1,247 prior cases)
Subject identifiers used: Robert Smith / b.1979 / Tampa, FL
Search timestamp: 2026-05-27 14:32 EST
Manual review required: yes (always — automated check is not a substitute for investigator review)

The "manual review required: always" note is intentional. Automated checks have false negatives — name variations, address changes, aliases not captured. The investigator still reviews.

What to do when a conflict surfaces

A few common patterns:

• Hard conflict (subject is a current client): Decline the new case. Document the decline and the reason in the firm's records (without compromising the current client's confidentiality in the documentation).
• Hard conflict (subject was a recent investigation target for another client): Decline, same as above.
• Potential conflict (old matter, no current relationship): Investigator decides based on the firm's WSP. Some firms require a cooling-off period before taking a case involving a former subject; others use case-by-case judgment.
• Adjacent conflict (a relative or associate is involved): Investigator decides. Often requires informed consent from the prior client.

The decline call to the caller doesn't disclose the reason — only that the firm has identified a conflict that prevents taking the case, and ideally suggests they seek another investigator. Most callers accept this without pushing for details.

Recordkeeping

The conflict check itself is a record the firm should retain. The minimum is: who ran the check, when, against what identifiers, and what the result was. Some state licensing boards have specific retention requirements; check the firm's licensing jurisdiction.

If the firm declined the case based on the conflict check, the decline record should be kept as well, with the date and reason (in a way that doesn't compromise prior-client confidentiality).

What this changes for the firm

A firm that runs disciplined conflict checks at intake has fewer mid-case crises. The cases the firm takes are cases it can actually take. The retainer conversation happens once, and the engagement begins cleanly. The prior-client confidentiality is protected by design rather than by hope.

The reputational signal compounds over time. Attorneys who refer cases to the firm notice when the firm declines a referral because of a conflict — it tells them the firm takes confidentiality seriously, which is exactly what the attorney needs to know about anyone they're referring sensitive work to.

Indagor captures conflict-check identifiers at intake and writes them into Trackops with the search results surfaced on the casefile. Start your agency at indagor.com.