Jump to section
Here is a scene that plays out in far too many firms. A prospective client is sitting across the desk, the kettle is on, and someone in the back office types a surname into a search box, sees no match, and calls out, "You are clear." That is not a conflict check. That is a name search that creates a false sense of safety and protects almost no one.
A real conflict check is one of the few things standing between a small firm and a complaint to the law society, a disqualification motion, or a very awkward call to your insurer. When it is done carelessly, it fails in exactly the moments you most need it to hold. And most of us are doing it carelessly.
The name search that misses everyone who matters
The single name search is seductive because it is fast and it feels definitive. Type "Bianchi," get nothing, move on. But conflicts do not live at the level of a single tidy name. They live in spelling variants, in maiden names and married names, in numbered companies, in the difference between "Bianchi Holdings" and "Bianchi Holdings Ltd." and the "2148877 Ontario Inc." that Mr. Bianchi actually contracts through.
If your only input is the string a client happens to give you at intake, you are searching for the version of reality that is most convenient, not the one that will hurt you. The person you acted against three years ago might be in your system under a nickname, a former corporate name, or a file your predecessor opened and closed before you ever arrived.
Warn. A clean search result is not the same as a clean file. Absence of a match often means you searched the wrong terms, not that no conflict exists.
Related parties are where firms get burned
Ask a room of litigators where their near-misses came from and you will rarely hear "the opposing party." You will hear about the witness who turned out to be a former client, the corporate director who sits on both sides of a deal, the spouse in a family matter who is also a shareholder in a company you represent. The direct adversary is the one everybody remembers to check. The related parties are the ones who sink you.
A protective check captures the whole cast: the client, the adverse party, and everyone orbiting the matter. That means directors and officers, shareholders, guarantors, beneficiaries, key witnesses, the accountant, the other side's principals, and any related corporate entities. It is tedious. It is also the entire point. If your intake form has one line for "opposing party" and nothing else, your process is built to miss the very people who create the conflict.
The direct adversary is the one everybody remembers to check. The related parties are the ones who sink you. Devon Reyes
Why the check has to happen before the coffee, not after the retainer
Timing is where good intentions go to die. Everyone agrees conflicts should be checked. Fewer firms agree on when, and the "when" is what actually determines whether the check does anything. If you run the search after you have taken the retainer, learned the client's confidences, and started drafting, a hit does not save you. It just tells you how much you now have to unwind.
The check belongs at the very front of the relationship, before you hear anything privileged, ideally before the first substantive meeting. Screen on the initial phone call. That is the moment a conflict costs you nothing but a polite decline. Ten minutes later, once you have heard the story, it costs you a file, possibly a client relationship, and possibly your ability to act for the person you were already representing.
Tip. Build the check into your intake sequence so it is impossible to skip. When conflict screening and matter opening live in the same workflow, as they do in a system like A1 CMS, no one has to remember to do it as a separate step.
This is also an argument for treating intake as a real process rather than a vibe. If you have written down how a matter gets opened, the conflict check is simply step two, not an afterthought someone does under pressure. Firms that have invested in simple standard operating procedures tend to have conflict checks that actually run, because the step is baked into the routine instead of depending on memory.
Documenting the check so it holds up later
Here is the uncomfortable truth: a conflict check you cannot prove you did is, for practical purposes, a conflict check you did not do. If a dispute arises two years from now, "I am sure we searched" is worthless. What you need is a record showing what names you searched, when, against what database, who ran it, and what you concluded.
Good documentation does two things. It gives you a defensible answer if your judgment is ever questioned, and it forces the person running the check to slow down and be deliberate. You cannot write down "searched all related entities" honestly if you only typed one surname.
| A check with gaps | A check that protects |
|---|---|
| One name, typed once | Client, adverse parties, and related parties, with spelling and corporate variants |
| Run after the retainer is signed | Run before any privileged information is shared |
| Verbal "you are clear" | Dated written record of terms searched and result |
| Done by whoever is free | Owned by a named person as a defined step |
When to decline and how to say no gracefully
Sometimes the check works exactly as designed and hands you a problem. There is a genuine conflict, and no waiver is available or appropriate. This is the good outcome, even though it does not feel like one. The whole apparatus exists so you can catch this while declining is still easy.
Declining does not have to be awkward. You are not obligated to explain the details, and often you cannot, because the existence of the other matter may itself be confidential. A simple, warm version works: "I have run our conflict check and I am not able to take this on. I want to be upfront rather than get partway in. Here are a couple of firms I would trust with it." You keep your integrity, you protect both clients, and you often earn more respect than you would have by quietly taking a file you should have refused.
If you want to go deeper on building the front end of this properly, it is worth reading alongside our notes on how to track limitation periods and the wider set of practice management habits that keep small firms out of trouble.
None of this is exotic. It is not a new rule or a piece of software you must buy. It is a decision to treat the conflict check as a real process rather than a quick formality. Search everyone who matters, do it before you know anything you should not, write down what you found, and be willing to say no. Do that, and the check becomes what it was always supposed to be: the thing that actually protects you.
