Use a controlled release gate between intake and consultation. Capture the required people and organizations, preserve the exact search terms and data sources, route every possible match to an authorized lawyer, and release the appointment only after that lawyer records a disposition. A search with no documented reviewer is not clearance, and a booked time slot should not override an unresolved check.
Scope: This is an operations framework, not legal advice. Firm counsel must define the controlling jurisdiction, who qualifies as a prospective client, which names and relationships must be searched, who may analyze a conflict, and what the firm may communicate. Support staff must not decide whether a conflict exists, seek consent, give advice, or promise representation.
Why conflict checks stall or get bypassed
A caller provides one defendant's name. A web form supplies a business trade name. A police report later identifies the driver, vehicle owner, employer, and insurer. Meanwhile, the consultation is already on a lawyer's calendar.
The problem is not simply whether someone clicked “search.” The firm cannot tell whether it searched the right parties, searched the right records, resolved possible matches, or obtained an authorized decision.
Public law-firm discussions describe basic screening by intake staff followed by attorney confirmation. They also describe consultation scheduling after a check passes. Those comments do not establish a universal method. They expose a handoff that needs an owner, evidence, and a visible hold state.
Volume increases the pressure. Staff may interpret a blank result as approval, send a possible match through email without an accepted owner, or book a consultation while waiting for more names. The calendar then becomes the operational decision even though nobody made the legal decision.
Define clearance before configuring tools
Give the firm one test:
An intake conflict screen is cleared only when required party data is sufficient under firm policy, the approved sources were searched with preserved terms, possible matches received an authorized disposition, and the consultation-release decision is recorded.
This definition separates events that are often collapsed:
- Captured: the intake record contains a name or organization.
- Normalized: staff preserved the source value and added an approved searchable form.
- Searched: the approved data sources returned a result for recorded terms.
- Flagged: at least one result requires human review.
- Reviewed: an authorized reviewer examined the source-linked result.
- Disposed: the reviewer recorded the firm's permitted next state.
- Cleared for consultation: the appointment gate may open under firm policy.
“No matches displayed” is a search result. It does not prove that the party list was complete or that an authorized lawyer approved the next step.
Build the names-to-clearance workflow
1. Create one control record
Link the conflict-screen record to the inquiry identifier. Do not rely on a calendar note or an email thread as the only record.
The control record should show its current state, accepted owner, age, last action, next action, and consultation hold. Sensitive details should remain inside approved systems with role-based access.
2. Capture party roles before detailed facts
Use counsel-approved prompts for the prospective client, adverse parties, known organizations, other involved people, prior counsel, and relevant name variations. Personal injury matters may reveal additional roles later, so the template must support additions without overwriting the original answer.
Preserve what the caller actually provided. A normalized search value should supplement, not replace, the source value. If two identities might be the same, mark the uncertainty for review.
3. Test whether the input is sufficient
Firm policy should define which fields are required before a search can be treated as complete. A missing adverse-party name should create an exception, not a false “clear” state.
Support staff can follow an approved sufficiency checklist. Questions about whether a relationship is legally relevant belong with an authorized lawyer.
4. Search approved sources and preserve provenance
Record each term, its party role, the systems searched, search time, worker, and result reference. If an archive or integration is unavailable, record that limitation and keep the consultation on hold unless firm policy supplies another path.
Avoid copying unnecessary confidential information into a broad intake dashboard. The dashboard needs status and control evidence, not unrestricted matter detail.
5. Route possible matches with an accepted handoff
A possible match needs a decision packet containing:
- the source-provided and normalized names;
- each party's stated role;
- the inquiry and search identifiers;
- the systems and terms searched;
- source-linked candidate matches;
- missing or uncertain information; and
- the requested disposition and consultation time.
Assign the packet to an authorized reviewer. “Sent to legal” is not an accepted handoff. Capture who accepted it and when.
6. Reserve disposition for authorized lawyers
The reviewer determines what the result means and which next action is permitted. Workflow labels should avoid implying that software or support staff reached a legal conclusion.
Useful operational dispositions might include cleared for the defined step, more information required, duplicate search required, decline communication required, or restricted escalation. Counsel must design the actual labels and authority.
7. Release or maintain the consultation hold
Only a permitted disposition should release the appointment. Record the reviewer, decision time, scope, related search version, and the worker or automation that changed the calendar state.
If an appointment was tentatively reserved, the external message should use counsel-approved wording. It should not promise representation or disclose why a conflict concern exists.
8. Reconcile and re-check
Reconcile open screens against tomorrow's consultation calendar. Any appointment without the required clearance evidence remains visible to its owner.
New parties, corrected identities, changed relationships, newly connected firm records, or a move from inquiry to matter opening may trigger another check under firm policy. Preserve prior searches instead of replacing their history.
Workflow at a glance
- Create the inquiry-linked control record
- Capture source names and party roles
- Check input sufficiency
- Search approved firm data and preserve provenance
- Route possible matches to an accepted reviewer
- Record the authorized disposition
- Release or maintain the consultation hold
- Reconcile appointments and re-check defined triggers
Separate screening from legal judgment
ABA Model Rule 1.18 addresses duties concerning qualifying prospective clients, including certain information learned even when no client-lawyer relationship follows. It is a model rule, and jurisdictions may adopt or modify it.
ABA Model Rule 5.3 describes managerial and supervisory responsibilities concerning nonlawyer assistance. Delegating data capture or search administration does not transfer the lawyer's professional responsibilities.
| Activity | Intake support | Intake manager | Authorized lawyer |
|---|---|---|---|
| Capture names using approved prompts | Perform | Monitor quality | Approve scope and prompts |
| Normalize names without deleting source values | Perform | Review exceptions | Decide legally significant ambiguity |
| Run documented searches | Perform if policy permits | Verify provenance | Define approved sources |
| Decide whether a match creates a conflict | No | No | Lawyer only |
| Seek or evaluate consent or screening options | No | No | Lawyer only |
| Release a held consultation | Execute recorded rule | Reconcile gate | Authorize disposition |
| Communicate a decline reason | Use approved workflow only | Route exceptions | Control content and authority |
The comment to ABA Model Rule 1.7 says procedures should be appropriate to the firm's size, type, and practice. The draft therefore provides control components, not a universal legal determination.
Configure technology and access
Keep search evidence durable
Do not let a transient result panel serve as the only proof. Preserve the terms, scope, timestamp, result reference, reviewer, and disposition according to firm policy.
Make uncertainty explicit
Exact, possible, phonetic, alias, and relationship matches should remain distinguishable. Do not let an automation silently dismiss a candidate or equate a fuzzy match with identity.
Separate operational views from sensitive content
An intake dashboard can show that a decision is overdue without displaying confidential facts or the identity of another firm client. Configure access around role and need.
Test degraded states
Test a missing adverse party, misspelled business, duplicate person, unavailable archive, delayed integration, unaccepted reviewer assignment, decision without a linked search, and party added after clearance. Each test needs a visible state and owner.
Measure the control
Targets should come from firm policy and a measured baseline. No external benchmark is asserted.
Measures to define
- Clearance-ready input rate: Screens with every firm-required party field present divided by screens submitted for review
- Possible-match acceptance time: Elapsed time from routing a possible match until an authorized reviewer accepts ownership
- Consultation gate defect count: Consultations released without the required source-linked disposition
- Re-check completion rate: Defined trigger events with a completed follow-up check divided by trigger events due for review
Review queue indicators
- held consultations by age and owner
- incomplete party-role records
- unaccepted possible-match packets
- decisions missing search provenance
- re-check triggers awaiting action
The accessible dashboard should pair color with text labels, expose the owner and last action, support keyboard operation, and stack on mobile. It should link authorized users to source records rather than duplicating sensitive contents.
Handle exceptions and re-checks
A caller will not provide a name
Record the refusal or inability without guessing. Use the counsel-approved explanation and escalation. Do not release the consultation merely to preserve a scheduling target.
A name produces many possible matches
Keep all candidates linked to the search. Provide identifiers that policy allows the reviewer to see. Support staff should not select the legally relevant result based on intuition.
The search system is unavailable
Record the unavailable source and time. Route the exception to a named owner. A partial search should remain visibly partial.
A new party appears after clearance
Create a new version or follow-up check linked to the prior disposition. Counsel decides whether work or communication must pause.
A prospective client asks why the appointment is delayed
Use lawyer-approved language that explains the administrative hold without revealing another person's confidential relationship or implying representation.
Implement the workflow
- Have firm counsel define jurisdiction-specific search inputs, sources, reviewers, dispositions, communications, retention, and re-check events.
- Map every current path from inquiry to consultation booking.
- Create one inquiry-linked conflict-screen record and consultation-hold field.
- Build source-value preservation and party-role capture.
- Require search provenance and accepted reviewer ownership.
- Configure only authorized dispositions to release the hold.
- Test missing, ambiguous, unavailable, duplicate, and late-added-party scenarios.
- Pilot with a bounded queue and compare defects with a baseline.
- Review exceptions and revise the process under lawyer supervision.
Decide whether this approach fits
This framework fits firms that receive inquiries across several channels, schedule consultations through multiple teams, or need consistent evidence across offices. It can also help when support staff administer searches but lawyers retain conflict-analysis authority.
It does not fit a firm seeking software to make legal conflict decisions automatically. It also cannot repair incomplete historical data by itself. Firm counsel must choose the controlling rules and procedure.
After the educational workflow is defined, personal injury law firm support may help carry out approved administrative steps. Supervised virtual legal assistant services can support bounded capture, search administration, routing, and reconciliation under firm controls. Browse personal injury operations resources for related workflow guidance.
Frequently asked questions
How can my personal injury law firm keep consultations on hold until conflict checks are cleared?
Use an inquiry-linked hold that only an authorized, source-linked disposition can release. Required party data, search provenance, possible-match review, reviewer identity, and scope should be complete before the calendar advances.
What should my intake team record before sending a possible conflict to a lawyer?
Record source-provided names, normalized search values, party roles, the systems and terms searched, result references, uncertainties, the inquiry identifier, and the requested decision. Capture the authorized reviewer's acceptance separately.
When should my personal injury law firm rerun an intake conflict check?
Firm counsel should define the triggers. Operational candidates include corrected identities, newly identified parties, changed relationships, newly available records, and movement from inquiry to matter opening. A support worker should execute the rule, not decide its legal necessity.
Sources and disclosure
- American Bar Association, Model Rule 1.18: Duties to Prospective Client, page dated April 13, 2020; accessed 2026-09-13. ABA Model Rules are not controlling in every jurisdiction.
- American Bar Association, Model Rule 5.3: Responsibilities Regarding Nonlawyer Assistance, page date not visible; accessed 2026-09-13.
- American Bar Association, Comment on Model Rule 1.7, page date not visible; accessed 2026-09-13.
