Place every new inquiry in a conflict-screening hold. Collect only the information needed for the approved search, preserve each search result, and route possible matches to a lawyer. Do not allow consultation, legal advice, an engagement agreement, or matter opening to advance until the authorized decision is recorded. Reopen the check when a new party or relationship appears.
Scope: This is an operations framework, not legal advice or a conflicts opinion. Lawyers must configure search scope, decision authority, confidentiality, waiver, screening, and recheck rules under controlling law.
Why a search is not a conflict decision
Intake software can return exact names, similar names, prior contacts, former matters, adverse parties, witnesses, providers, or nothing. None of those outputs decides whether representation is permitted.
A clean search may be incomplete because the intake record omitted a driver, employer, insurer, product entity, property owner, family member, or another connected person. A match may be unrelated. A prior contact may still require restricted handling. Only an authorized lawyer should resolve the legal significance.
The American Bar Association’s client-intake guidance identifies potential-client, practice-area, and dispute information as basic conflict-analysis inputs. For adversarial matters, it discusses opposing parties, opposing counsel, forum, and subject matter. It also says checks should occur before legal advice and an engagement letter. The page is practice guidance; controlling jurisdictional rules remain decisive.
The operational model should therefore preserve four different states:
- required information is incomplete;
- search is complete with no possible match;
- a possible match awaits lawyer disposition; and
- an authorized decision is recorded.
An intake worker should never convert state two into a legal conclusion. Nor should a calendar appointment silently bypass state three.
Build the conflict-screening record
Create one record for the inquiry and link every search, exception, and decision to it.
Minimum party dataset
Use lawyer-approved fields appropriate to personal injury matters. They may include:
- prospective client’s verified name and approved aliases;
- adverse people and entities reported by the prospect;
- vehicle owner, employer, property owner, manufacturer, insurer, or public entity when relevant;
- other injured people, witnesses, and connected matters when the firm’s procedure calls for them;
- opposing counsel, venue, and high-level dispute description if known; and
- source, collector, collection time, and verification status for each name.
This is not a universal list. Staff should not guess legal relationships or demand extensive merits information merely to fill a field. Model Rule 1.18 addresses information learned from prospective clients, even where no relationship follows. The adopted rules in the governing jurisdiction control.
Search evidence
For every search, record:
- system or dataset searched;
- exact normalized search terms;
- filters and approved variants used;
- search time and operator;
- returned record identifiers, not unrestricted copies;
- ambiguous or unavailable systems; and
- the next required action.
“Conflict check done” is not enough. A reviewer should be able to tell whether the firm searched the right names in the right places using the approved procedure.
Lawyer disposition
The decision record should name the reviewing lawyer, identify the input version reviewed, preserve the disposition and timestamp, and state any approved next step. Possible states could include cleared to continue intake, more facts needed, declined, or another lawyer-controlled status.
Do not build a system that invites staff to select “waivable,” “screened,” “substantially related,” or another legal conclusion. Those labels require lawyer judgment under applicable law.
End-to-end workflow
1. Open the inquiry in hold status
Every channel—phone, web, chat, referral, email, or transferred call—should create the same hold. Give the inquiry an identifier and owner. Stop automated consultation booking or matter creation from treating receipt as clearance.
2. Collect the approved minimum
Use structured prompts and repeat names back for confirmation. Record uncertainty instead of correcting it from memory. If the prospect starts offering unnecessary sensitive detail, follow the lawyer-approved intake boundary.
3. Normalize without destroying the source
Preserve the entered form of each name. Add separate searchable variants for spacing, punctuation, suffixes, prior names, and entity abbreviations according to firm procedure. Never overwrite the source value.
4. Execute and document the search
Search the designated intake, matter, contact, document, and approved legacy systems. If one is unavailable, mark the search incomplete. Record results without exposing unrelated confidential matter detail to intake personnel.
5. Triage possible matches
Route a compact packet to the designated lawyer or conflicts team. Include source names, relationship labels, returned identifiers, system coverage, missing information, and reported urgency. Avoid a general mailbox unless someone must accept ownership.
6. Lock downstream actions
Until the authorized decision appears, block engagement generation, substantive consultation, legal advice, matter opening, file access expansion, and marketing sequences that imply acceptance. An urgent reported deadline should escalate; it should not erase the hold.
7. Record the decision and release the correct path
The lawyer reviews the source-linked packet and records the disposition. The system then releases only the approved branch: continue intake, collect named missing facts, follow a controlled decline workflow, or another counsel-defined action.
8. Recheck on changed facts
New defendants, employers, providers, insurers, witnesses, related cases, or lawyer assignments can change the search inputs. Create a new linked search event rather than editing the original result into invisibility.
9. Close with acceptance evidence
Completion means the required inputs, search coverage, exception resolution, lawyer disposition, released branch, and recheck triggers are visible. It does not mean software certified that no conflict exists.
Workflow at a glance
- Place inquiry on conflict hold
- Collect approved party and relationship data
- Preserve source values and approved search variants
- Search designated firm systems
- Route possible matches and missing coverage
- Record lawyer disposition
- Release only the approved intake branch
- Recheck when parties or relationships change
Responsibilities and controls
| Stage | Support role | Lawyer or authorized leader | Required evidence |
|---|---|---|---|
| Intake | Collect approved identifiers | Define scope and sensitive-information boundaries | Source and verification state |
| Search | Run documented queries | Approve systems, variants, and escalation rules | Search terms, coverage, time |
| Match triage | Assemble possible-match packet | Determine legal significance | Accepted review owner |
| Decision | Preserve inputs and status | Record disposition and next step | Decision linked to input version |
| Release | Enable the authorized branch | Control advice, acceptance, waiver, or decline | Branch release event |
| Recheck | Add newly surfaced parties | Decide changed-conflict implications | Linked subsequent search |
ABA Model Rule 5.3 addresses managerial and supervisory responsibilities for nonlawyer assistance. It supports a controlled role design, but does not turn an administrative search into lawyer judgment.
Technology and information boundaries
A useful integration transfers identifiers and status without flattening the controls. Configure:
- role-limited views of possible matches;
- immutable source values and separate normalized fields;
- search logs tied to the inquiry version;
- system-coverage and outage flags;
- an owned exception queue;
- downstream status locks;
- decision permissions restricted to authorized roles;
- recheck triggers for added parties; and
- an exportable audit history.
Fuzzy matching can surface candidates. It should not classify their legal importance. Generative tools may summarize a structured packet only when the firm has approved the data handling and a reviewer checks it against source records. Never allow a generated explanation to replace the underlying results.
KPIs and dashboard brief
Measure process health without inventing benchmarks.
Measures to define
- Complete-input rate: Percentage of inquiry checks containing every firm-required input at first review
- Unowned-match age: Elapsed time a possible match remains without accepted review ownership
- Decision-to-release integrity: Percentage of downstream releases linked to an authorized disposition
- Recheck completion: Percentage of configured changed-party events with a linked subsequent check
An accessible dashboard should show queue count by evidence state, oldest unowned match, incomplete system coverage, decision owner, and changed-party rechecks. Users must be able to reach the source record from each exception. Color cannot be the only status signal.
Review queue indicators
- input completeness
- search coverage
- possible-match ownership
- downstream hold integrity
- recheck status
Failure modes and jurisdictional limits
- Appointment before clearance: keep scheduling technically dependent on the recorded decision.
- Exact-name-only search: use lawyer-approved variants while preserving the original entry.
- Legacy system unavailable: show incomplete coverage and escalate; do not record a clean result.
- Too much match detail exposed: display the minimum needed for routing and restrict access.
- Staff resolves ambiguity: return the item to the lawyer queue with source evidence.
- New defendant added later: trigger a linked recheck before affected work proceeds.
- Deadline reported during hold: escalate promptly under counsel’s procedure without offering legal advice or implying representation.
- Conflict found: follow the lawyer’s jurisdiction-specific decision and communication procedure.
Rules concerning current clients, former clients, prospective clients, imputation, consent, screening, and confidentiality vary by facts and jurisdiction. This article does not define when a conflict exists or can be addressed.
Implementation checklist
- Map every inquiry channel to one hold state.
- Have counsel approve the minimum dataset and search systems.
- Preserve source names separately from normalized variants.
- Define unavailable-system and ambiguous-match exceptions.
- Name the lawyer or team that accepts review ownership.
- Prevent downstream automation from bypassing the decision.
- Link each disposition to the exact input and search version.
- Add recheck triggers for newly identified parties.
- Train support personnel on legal-advice and confidentiality boundaries.
- Pilot with synthetic records; do not place real client information in training screenshots.
- Review access logs, exception aging, and false release events.
- Keep internal routes and rendering checks pending until production validation.
Fit and not-fit guidance
This workflow fits firms with repeated inquiry volume, multiple intake channels, distributed staff, several data repositories, or recurring possible-match escalation. It helps when leaders need to see why an inquiry is waiting.
It does not fit a firm seeking software that issues conflicts opinions, bypasses counsel, or guarantees no disqualification or discipline. It cannot cure incomplete records, replace jurisdictional analysis, or make a virtual assistant responsible for representation decisions.
After the firm defines the legal boundary, personal injury law firm support can help organize approved administrative steps. The broader virtual legal assistant services page describes the capability model, while personal injury operations resources collect related workflows.
FAQs
What names and relationships should support staff collect before routing a potential conflict to a lawyer?
Use the minimum fields counsel has approved for the matter type and jurisdiction. Preserve the prospect’s original wording, identify the source, mark uncertainty, and collect adverse and connected parties required by procedure. Do not invent relationships or treat a generic checklist as universally complete.
Which conflict-check tasks can a virtual legal assistant prepare?
Under lawyer-defined procedures, support personnel may collect basic information, normalize names without overwriting source values, run approved searches, preserve results, assemble a possible-match packet, and track ownership. A lawyer must control the legal decision and any advice, consent, screening, waiver, acceptance, or decline.
Does no returned match mean the firm is cleared to take the case?
No. It means the documented search returned no possible match within its recorded scope. An authorized lawyer determines the significance of the information under controlling law and firm procedure.
When should the firm run another check?
Use counsel-configured triggers. Common operational triggers can include newly identified parties or relationships, changed claims, related matters, new experts or witnesses, or a changed legal team. Preserve each recheck as a separate linked event.
Sources and disclosure
- American Bar Association, How the Legal Client Intake and Conflict Check Process Works (date not visible; accessed 2026-09-13).
- American Bar Association, Rule 1.18: Duties to Prospective Client (model rule; accessed 2026-09-13).
- American Bar Association, Rule 5.3: Responsibilities Regarding Nonlawyer Assistance (model rule; accessed 2026-09-13).
- American Bar Association, ABA issues ethics guidance for lawyer’s use of legal assistants (2023-06-07; accessed 2026-09-13).
