The conflict of interest screen sits at the entry point of every new matter, and it is the step that is most likely to be trusted to human recall. At a solo practitioner's firm, this is defensible — one attorney knows their own client book. At a 30-attorney firm carrying 300 active matters across three practice groups, it is not. And yet many mid-size firms in that range are running conflict checks that depend, in some part, on someone remembering something.
The consequences of a failed conflict check reach beyond professional responsibility exposure. A conflict discovered late in a matter — after work product has been exchanged, after settlement negotiations have begun, or after a partner has formed a relationship with the client — triggers withdrawal, potential fee disgorgement, and in egregious cases, malpractice claims. Model Rule 1.7 and its state analogs are unambiguous: representation that creates a concurrent conflict of interest without informed consent and waiver is not a recoverable situation. It is a disqualification situation.
What follows is an examination of why mid-size firms fail conflict checks not because they lack rules, but because of specific structural gaps in how those checks are run.
The Database Problem: What Gets Searched and What Doesn't
Most firms running a practice management system — whether that's a platform like Clio or an older matter management database — have a client list. The question is whether the conflict search runs against all relevant entities, or just the client of record.
Consider a scenario: a mid-size regional firm's real estate group is engaged to represent a developer on a commercial acquisition. The conflict check runs against the client name and returns clean. What the check doesn't surface is that the developer's principal is also the managing member of an LLC that is an adverse party in a pending litigation matter being handled by the firm's dispute resolution group. The LLC and the developer's name are connected in the relationship database only if someone input that connection at intake. If the prior matter was opened two years ago by a partner who has since left, that relationship record may exist only in a closed matter file that the conflict system doesn't query by default.
This is the most common structural failure mode: the search scope is narrower than the firm's actual relationship network. Fixing it requires both a comprehensive entity relationship model in the database — capturing not just direct clients but related entities, principals, adverse parties, and opposing counsel — and a conflict search that queries across all of those classes, including closed matters.
When "Clear" Means "No One Raised a Hand"
There's a second failure mode that is subtler: the conflict check process that technically circulates a request firm-wide but has no mechanism to verify that the relevant people actually reviewed it. An email to all attorneys asking "any conflicts with Client X?" is only as reliable as the response rate. When that email arrives on a Friday afternoon before a holiday weekend, or when three partners are in trial and not reading non-urgent email, the silence that follows is not confirmation of a clean check. It's confirmation that the inbox was full.
We're not saying that human review of conflict requests is unnecessary — it is essential, particularly for soft conflicts and relationship-based considerations that a database query can't surface. What we are saying is that a conflict clearance process should require affirmative confirmation of review, not treat non-response as clearance. The difference between these two approaches is the difference between a process that produces evidence of review and a process that produces evidence that a message was sent.
The Inherited Conflict: Lateral Hires and Matter Portability
Lateral attorney hiring introduces a conflict dimension that many firms handle inadequately. When a new partner joins from another firm, they bring a matter history — clients they represented, adverse parties they encountered, clients of their former firm with whom they may have had limited contact. ABA Formal Opinion 09-455 and many state bar ethics opinions address screening procedures for lateral hires, but the operational question is whether those procedures actually integrate with the ongoing matter intake process.
A firm that does a thorough lateral conflict intake at hire but then fails to maintain an ongoing screen as new matters come in — particularly if the lateral hire's former clients are on the adverse side of new matters — is exposed. The initial screen is a snapshot; the conflict landscape evolves. Mid-size firms that bring in laterals regularly without automating the reconciliation of the lateral's conflict list against incoming matters are carrying ongoing exposure they may not be tracking.
The Waiver Documentation Gap
Even when a firm identifies a potential conflict and obtains informed consent from the affected parties, the documentation of that waiver is a separate operational challenge. A verbal conversation between a partner and a client is not documentation. A client email saying "that's fine" is not the kind of written waiver that provides reliable protection under Model Rule 1.7(b)(4).
The operational gap here is that the conflict clearance workflow often ends at the decision — "conflict identified, waiver obtained" — without creating a durable record of what was disclosed, what was consented to, and by whom. When a matter later produces a dispute and opposing counsel raises the conflict, the firm's position depends entirely on what it can show. Firms that treat the waiver record as a checklist item ("waiver: obtained") rather than a substantive document in the matter file are creating a documentation gap that could undermine an otherwise defensible position.
What an Automated Conflict Check Actually Needs to Do
Automated conflict checking is often discussed as if the primary benefit is speed — and speed is real. Running an automated screen against 300 matters and 1,200 related entities in seconds rather than hours is a meaningful operational gain. But the more important benefits are completeness and auditability.
Completeness means the search runs against the full entity graph — direct clients, adverse parties, related entities, opposing counsel, and closed matters — not just the current client roster. It means the system flags not just exact name matches but relationship chains (the LLC that shares a principal with a direct client) and lateral hire overlap. It means the search is triggered by the matter intake event, not by someone deciding to run it.
Auditability means the system produces a durable record: what was searched, when, against which entity graph, who reviewed the results, and what disposition was recorded. This record lives in the matter file and is available for review if the conflict is later questioned. It is also available for the firm's own internal audit — a quarterly review of conflict check records can surface patterns (certain practice group laterals always triggering near-misses, for example) that inform process improvements before they become disciplinary situations.
A Word on Soft Conflicts and Relationship Complexity
Automated conflict detection is effective at finding hard conflicts: direct representation of adverse parties, prohibited business transactions, and clear relationship chains. It is not designed to replace the experienced attorney's judgment about soft conflicts — the relationship where a long-standing client would be uncomfortable with the firm representing an adverse party even if no technical conflict exists, or the reputational consideration that makes a technically clean representation strategically inadvisable.
These judgment calls belong to partners with relationship knowledge. What automation does is ensure that those partners see the relevant flags in a timely, structured way, rather than learning about a relationship connection two weeks into a matter. The value of a well-run automated conflict check is not that it replaces professional judgment — it is that it gets the right information to the right people before the judgment call needs to be made under time pressure or after the fact.
The firms that never fail conflict checks are not the firms with the best memories. They are the firms where the conflict check runs automatically, the entity graph is kept current, the review requires affirmative confirmation, and the waiver record is part of the matter file. The procedural investment to get there is relatively modest. The exposure avoided by getting there is not.