Conflict Checking for Law Firms: The Search That Must Come First

Almost no firm sets out to act against its own client. Conflicts are not usually decisions; they are oversights, and they surface at the worst moment — in a hearing, when a name in an opponent's filing turns out to be a client the firm already represents through a different matter, a parent company, or a shared director.

By then the damage is done: there is a file, an engagement letter, correspondence and invoices. The question is no longer whether there was a conflict but what the firm knew and when, and whether it can prove it looked.

The single most important property of a conflict check is when it runs. A check performed after the matter is created is a record of a decision already taken. The screening has to happen at intake, on the parties as entered, before anything is committed to the database.

That ordering is what turns the check from a formality into a control. If the system opens the matter and then offers to check, the check is theatre; the firm has already started acting.

The conflicts that undo firms rarely appear under the client's trading name. They sit one or two layers up: a counterparty owned by a company you act for, a director who also sits on a client's board, an ultimate beneficial owner in common.

A useful conflict engine screens organizations, their directors and their UBOs as first-class entities, not just a list of client names — and it matches fuzzily, because real filings spell the same name three ways. A check that only compares exact trading names will pass a conflict it should have caught.

Firms are rarely undone by conflicts they saw and waived. They are undone by conflicts they cannot prove they searched for. A search that found nothing is as much a record as one that found something — and it is worthless if it cannot be produced two years later.

So the output of every check must be stored: cleared, flagged or escalated, with a timestamp. Where a conflict is waived, the reason belongs in the file in the words of the person who decided, stamped with their name. "We discussed it and it was fine" is not a record a regulator accepts.

Mersal runs the conflict screen before the matter row is created. Intake holds the matter until the check resolves, searching clients, organizations, their directors and ultimate beneficial owners, and external counsel, with fuzzy name matching. If anything matches, the person opening the matter must type a waiver reason before proceeding, and it is stamped and attributed.

Every check is logged either way — a clean search is a stored record in its own right — and relationships between parties render as a graph as well as a list, so the question "how are these two connected" has a visible answer. The clearance lives in the append-only audit ledger, so it can be produced long after the matter closes.