Conflict check software for law firms: legal conflict check software and attorney conflict check systems compared

A conflict check tool runs a search across the records your firm already holds and returns anyone connected to the new inquiry. In practice that means matching names against current clients, former clients, matters, related contacts, opposing parties, witnesses, and in the better implementations the text inside stored documents. The output is a report listing every hit, which a human then reads and judges.

That last part matters and gets glossed over in demos. The software does not decide whether a conflict exists. It surfaces candidates, and a lawyer decides whether the match is the same person, whether the matters are substantially related, and whether the conflict is waivable. A conflict check product is a search engine with an audit trail attached, not a compliance decision engine, and any vendor implying otherwise is overselling.

The audit trail is a genuine part of the value. A dated record showing that a check was run, what it returned and who cleared it is what protects the firm later if the question ever gets asked. Firms that run conflicts through an email to the partners group get the check without the record, which is most of the work and none of the protection.

Feature depth varies more than the marketing suggests. The questions worth asking any vendor: does it search document contents or only structured fields, does it handle fuzzy and phonetic name matching or only exact strings, does it search leads and prospective clients or only signed matters, can it search across related entities such as a corporate parent, and does it produce a saved report you can retrieve two years later.

This is the point that decides how your conflict check has to be wired, and it is the one most software setups get wrong. Under the ABA Model Rules, obligations to someone who merely talks to your firm attach immediately, before any fee, any engagement letter, or any decision to take the case.

Model Rule 1.18(a) reads: "A person who consults with a lawyer about the possibility of forming a client-lawyer relationship with respect to a matter is a prospective client." Rule 1.18(b) continues: "Even when no client-lawyer relationship ensues, a lawyer who has learned information from a prospective client shall not use or reveal that information, except as Rule 1.9 would permit with respect to information of a former client."

Then the consequence, in Rule 1.18(c): "A lawyer subject to paragraph (b) shall not represent a client with interests materially adverse to those of a prospective client in the same or a substantially related matter if the lawyer received information from the prospective client that could be significantly harmful to that person in the matter, except as provided in paragraph (d). If a lawyer is disqualified from representation under this paragraph, no lawyer in a firm with which that lawyer is associated may knowingly undertake or continue representation in such a matter, except as provided in paragraph (d)." Note what that second sentence does: the disqualification spreads to the whole firm unless the exceptions in (d) are met.

Read those together and the practical rule falls out. The person who called on Tuesday, spoke to your intake coordinator for eleven minutes, described their dispute in detail and then hired somebody else is inside your conflict universe permanently. If that record was never created, because they were never a client and nobody opened a file, your conflict search will return nothing when the other side of that same dispute calls next year. The search worked correctly and the answer was still wrong. The rules that govern current and former clients, Rule 1.7 on concurrent conflicts, Rule 1.9 on former clients and Rule 1.10 on imputation across a firm, sit alongside this and are the reason firms keep matter records indefinitely.

So the timing question is not really about software. Run the check before the substantive consultation and you risk turning away work on an incomplete match. Run it after and you may already have heard something disqualifying. Most firms settle on a two-stage approach: a fast name-based screen before anyone discusses facts, then the full search before the engagement letter. What makes the first stage possible is having the names, and that is a data collection problem rather than a search problem.

We checked the vendor pricing pages and help documentation directly on 13 August 2026. The pattern here is the same one that holds across every legal software category we track: the feature buyers assume is standard is priced as premium, and the vendor that markets hardest tells you least.

MyCase is the clearest, because it publishes everything. Basic is $60 per user per month monthly or $50 annual. Pro is $120 or $100. Advanced is $150 or $130. Client Intake Forms and Legal CRM appear at Pro. Conflict Check Tracking appears only under MyCase Advanced, described by MyCase as searching "across cases, contacts, and documents to identify potential conflicts of interest before taking on a new case". So conflict checking, an obligation rather than a convenience, sits on the most expensive of three plans at two and a half times the entry price.

Clio is harder to pin down. Its help documentation confirms conflict checks run in both Clio Manage and Clio Grow, and carries the note that the feature "is available to select plans" with a link to the pricing page and a suggestion to ask a firm administrator about upgrading. It does not name the plans. Clio pricing itself lists four tiers, Starter, Core, Signature and Elite, attaches a Get pricing button to each and publishes one figure across the whole page, that plans start at $49 per user per month. Worth flagging if you are reading third party comparisons: several currently claim Clio conflict checks are included on Essentials, Advanced and Expand, and none of those plan names exist on Clio pricing page any more.

PracticePanther publishes a complete four tier card, Solo at $59 monthly or $49 annual, Essential at $79 or $69, Business at $99 or $89 and Business Pro at $124 or $114, all per user per month, all unchanged from our previous read. Its published feature matrix runs to several dozen named features across always included, advanced, automation and accounting groups. A conflict check is not among them. That is not proof the product cannot search contacts, it is a statement that PracticePanther does not sell conflict checking as a named feature on the page where it lists what you get.

Smokeball has to be reported differently now, because what it publishes changed while we were tracking it. On 13 August 2026 its pricing page showed "From $149/mo" with an asterisk on each plan, alongside a term toggle offering 12 months or 36 months rather than the monthly and annual choice its competitors present. Re-read on 19 August and again on 20 August 2026, there is no dollar figure anywhere on that page and the toggle is gone, so we no longer present the $149 as a current price. What Smokeball does now state, in its own pricing FAQ, is that its price "depends on the number of users at your firm, your selected plan, your contract term, and any optional products or services". It still does not name a conflict check among the features it lists. Read the term point carefully anyway: a multi year commitment in a market where MyCase and PracticePanther are month to month is a material difference that never appears in a price comparison table.

Here is the structural limit that no conflict check product on the market solves, and the reason we built what we built. Every one of these tools is a search over a database. A search can only return names that somebody put in. So the real determinant of whether your conflict check works is not the quality of the search engine. It is whether the names ever got captured, completely and consistently, at the point of first contact.

Consider what a thorough conflict screen needs from a single personal injury inquiry: the caller full name and any former names, their spouse, the other driver, the other driver insurer, the employer if it happened at work, any passengers, any witnesses, the treating providers, and any lawyer already consulted. Now consider what a typical web form captures: name, email, phone, and a free text box headed "tell us about your case". The search engine on the far end can be flawless and it will still be searching against four fields.

The gap widens with the inquiries that never convert. A firm that opens records only for signed matters has no trace of the two hundred people who called, described a dispute and went elsewhere, which is exactly the population Rule 1.18 says the firm owes duties to. Every one of those is a future conflict search that will come back clean and be wrong.

This is where Consultations sits, and it is a narrower claim than the rest of this page might suggest. We run the qualifying conversation when an inquiry arrives, ask the structured questions your practice area needs including the adverse party and related party names, collect the documents, screen the matter against the criteria your firm sets, book the paid consultation and hand you a prepped brief, at a flat $49 to $299 a month per firm with no per user charge. What that produces for conflict purposes is a complete, structured, dated record of every person who contacted the firm, including the ones you declined, in a form your conflict search can actually read.

What we do not do, plainly: we are not a conflict search engine, we do not hold your matter database, we do not run the search, and we do not tell you whether a conflict exists. That decision belongs to a lawyer looking at a report from the system that holds your records. If you need conflict searching, you need one of the platforms above or a dedicated tool. What we fix is the input side, which is the half of the problem the conflict software vendors do not address and mostly do not mention.

Software fails at conflict checking in one predictable way: the check becomes a step somebody can skip when the phone is ringing. Every firm that has had a conflict problem had a procedure at the time. The design question is not what the procedure says, it is what happens when a partner wants a file opened this afternoon.

Make the check a gate rather than a task. If your platform lets a matter be opened without a completed conflict report attached, someone will eventually open one. If it does not, the procedure enforces itself. This is worth testing specifically in a demo, because most tools present the conflict search as something you run rather than something the workflow requires.

Standardize how names get entered, because your search is string matching against whatever was typed. Decide once whether corporate entities are entered with or without Inc and LLC, whether hyphenated and former surnames are both recorded, and how a business trading name is handled. A firm that records the same company three ways has a conflict database that will miss it at least twice.

Keep the report, not just the result. Save the full output with the date, the search terms used and the name of the person who reviewed it. When a question arises three years later, "we ran a check" is worth very little and a retrievable dated report is worth a great deal.

And screen at the earliest possible moment. The cheapest conflict to handle is one found before anyone at the firm has heard confidential facts, because under Rule 1.18 it is the receipt of significantly harmful information that creates the disqualification risk. A name screen that runs at first contact, before the substantive conversation, costs almost nothing and removes most of the exposure.