A law firm conflict check process should produce more than a search screenshot and a green tick. It should show which parties were searched, which sources were checked, who assessed possible matches, what decision was made, and when the result must be refreshed. That record gives the matter-opening team a dependable gate and gives reviewers enough context to understand the decision later.
This is an operations guide, not an interpretation of professional obligations. Official sources include the Advocates Act, 1961 on India Code and materials published by the Bar Council of India. Firms should obtain appropriate advice on the current rules, local requirements, and circumstances of a proposed instruction.
What information should be collected before a conflict search?
Search quality begins with the party map. Asking only for “client” and “opponent” assumes that every instruction has a simple two-party structure. Transactions, group-company disputes, insolvency work, investigations, and multi-party proceedings rarely do.
Collect the legal name and known variants of each relevant person or entity. Preserve the name as supplied, then add normalised and former names as separate searchable values. Record the relationship to the proposed matter rather than placing all names in one undifferentiated list.
| Relationship class | Examples to consider | Intake question |
|---|---|---|
| Proposed client | Instructing entity, represented affiliates | Exactly which legal person will be the client? |
| Adverse or counterparty | Claimant, respondent, seller, buyer, target | Who is opposite or materially affected? |
| Connected entity | Parent, subsidiary, promoter, fund, lender | Which relationship makes the entity relevant? |
| Individual | Director, partner, witness, expert | What role does the person have? |
| Adviser | Existing counsel, auditor, consultant | Could the relationship appear in firm records? |
| Payer or referrer | Third-party payer, intermediary | Is this entity distinct from the client? |
Include jurisdiction, matter type, and a short neutral description. They help distinguish two records with similar names. Do not collect substantive confidential detail just to improve a name search. The matter intake workflow can feed this structured record before the conflict gate begins.
Which systems and records should the search cover?
Define the approved source universe in firm policy. Depending on the firm's operations, it may include current and closed matter records, client and prospect registers, contacts, billing entities, document or email metadata, relationship records, and prior conflict decisions. Searching more systems is not automatically better if results cannot be interpreted or access is inappropriate.
For each source, establish:
- its owner and authoritative fields;
- the period and practice areas covered;
- how quickly new matters and party changes appear;
- whether former names and aliases are retained;
- who may search it and view underlying details; and
- what happens when it is unavailable.
Keep the conflict index current through the matter lifecycle. A search cannot reveal a relationship that was never entered or was entered only in a private spreadsheet. Connected systems should use a stable matter identifier so reviewers can distinguish duplicate references from separate engagements.
Technology can help unify searches, but a product page is not proof of fit. Review Gotham's legal workflows, security approach, and practice workspace against the firm's actual sources, permissions, and review model.
How should names be searched and matched?
Use a repeatable search protocol. Search the exact legal name, material words, aliases, former names, abbreviations, common transliterations, and known spelling variants. For individuals, consider reordered names, initials, and names shared by multiple people. For organisations, account for punctuation and common corporate suffixes without collapsing distinct entities.
A practical search log looks like this:
| Search term | Source | Filters | Candidate results | Reviewer note |
|---|---|---|---|---|
| Exact name | Matter index | All statuses | Record identifiers | Confirm entity identity |
| Trading or former name | Client register | Current and former | Record identifiers | Check date of name change |
| Key name fragment | Approved sources | Jurisdiction or practice | Broader set | Eliminate obvious false matches |
| Connected person | Relationship index | Role | Linked matters | Review nature of relationship |
Fuzzy matching is a discovery aid, not a decision. A broad algorithm may return dozens of weak candidates, while a meaningful relationship may use an entirely different name. Let reviewers see why a result matched, the record date, matter status, responsible professional, and enough context to route it safely.
Do not silently overwrite search terms with a standardised form. Retaining the original input shows what the intake team knew at the time and makes a later refresh reproducible.
How should potential matches be reviewed?
Separate search from assessment. The searcher assembles candidate results; an authorised reviewer determines what additional facts or internal consultation are required and records the operational outcome. This prevents a receptionist, automation rule, or matter-opening administrator from being asked to make a professional judgment outside their role.
Use a compact review record:
- candidate matter or relationship identifier;
- identity comparison and reason for the match;
- current or former status of the relationship;
- information source and access limitations;
- designated reviewer and date;
- outcome under the firm's approved categories; and
- condition, escalation, or refresh date, if any.
Limit visibility of sensitive review notes. The intake team may need to know that approval is pending or conditional, but not every detail of another client's matter. Role-based access and a separate restricted note can preserve the gate without exposing more information than the user needs.
If the reviewer needs legal research on a governing rule or decision, use a traceable method such as the legal research workflow for India. Record the official sources and research cut-off date rather than relying on an uncited summary.
What decision states should the workflow use?
Avoid a single checkbox called “conflict clear.” A binary field hides pending questions, conditions, and scope limits. Use states that reflect the operating process, while the firm's advisers define what each state means.
| State | Operational meaning | Next action |
|---|---|---|
| Data incomplete | Required parties or relationships are missing | Return to intake owner |
| Search complete | Candidate results are assembled | Route to reviewer |
| Review pending | Assessment or internal input is outstanding | Block matter opening |
| Approved | Required reviewer has authorised progression | Continue to remaining intake gates |
| Approved with conditions | Progress depends on recorded controls | Confirm implementation owner |
| Declined | Matter will not progress | Close intake under policy |
| Refresh required | Material facts changed or result expired | Repeat defined steps |
The matter system should enforce the gate. If a user can open a live workspace merely by ignoring a warning, the process relies on memory at the moment when urgency is highest. Any override should be exceptional, restricted, time-stamped, and reviewed under the firm's policy.
When should a completed conflict check be refreshed?
A completed check answers the party and scope picture available at a particular time. It can become stale. Define triggers rather than expecting people to remember when a recheck might be useful.
Common operational triggers include:
- a new party, affiliate, witness, funder, or adviser enters the matter;
- the client entity or payer changes;
- the scope expands to a new transaction, proceeding, or jurisdiction;
- a lateral hire or team transfer changes the firm's relationships;
- another firm joins or leaves a coordinated engagement;
- a dormant prospect returns after the firm's validity period; or
- a merger, acquisition, insolvency, or name change alters the entity map.
Store each refresh as a new event linked to the earlier record. Do not edit the historical decision until it looks current. The history should show the information used, changed facts, reviewer, and outcome at each point.
How can a firm audit the process without exposing sensitive files?
Audit the control evidence, not the merits of every underlying engagement. Sample matters across practice groups, urgent openings, declined prospects, reopened matters, and scope changes. Reviewers can often test timeliness and completeness through identifiers and status history while restricted reasoning remains protected.
Use this audit checklist:
- Every opened matter links to a completed conflict record.
- The searched party map contains required relationship classes.
- Search terms and approved sources are reproducible.
- Candidate matches have a named reviewer and disposition.
- Approval predates matter opening and substantive work.
- Conditions have an owner and visible implementation status.
- Later party or scope changes triggered a refresh.
- Sensitive notes are visible only to authorised roles.
- Declined and dormant prospect records follow retention policy.
Track exceptions as process-design feedback. Repeated missing affiliates may mean the intake form is unclear. Frequent manual overrides may mean the review route cannot meet real deadlines. The useful response is to repair the workflow, not merely remind people to comply.
What makes the conflict record defensible and useful?
A useful record is complete enough to reproduce, restricted enough to protect unrelated information, and short enough that reviewers actually maintain it. It distinguishes facts collected, search results produced, and judgments made. It also states the cut-off date and the conditions under which the result stops being current.
Before matter opening, confirm:
- the proposed client and scope are precisely identified;
- relevant parties and relationships are structured and searchable;
- searches covered the approved source universe;
- ambiguous matches were escalated rather than guessed away;
- the authorised reviewer recorded an outcome;
- conditions were translated into owned tasks or access controls; and
- the next refresh trigger is understood.
A mature law firm conflict check process slows the team only where a deliberate decision is needed. Everywhere else, structured data and clear routing reduce avoidable back-and-forth. To map these gates into a matter lifecycle, contact Gotham and bring the firm's current forms, source list, and approval policy to the discussion.
