The Conflict-Check Workflow for Small Firms (Build)

Every firm knows it should run a conflict check, and every firm intends to, which is precisely the problem, because intention is not a system. A check that happens because someone remembers to do it will, sooner or later, not happen, and it will fail exactly when the firm is busiest and the pressure to just get the matter open is highest, which is also when a missed conflict is most likely to matter. This is not a knowledge gap; firms understand conflicts perfectly well. It is a reliability gap: the check is a discretionary human action in a busy environment, and discretionary human actions in busy environments get skipped. The fix is to stop relying on memory and build a workflow that fires the check on its own, captures what it needs, and puts the results in front of the attorney, so that the one professional obligation nobody means to skip stops being skippable. Critically, the workflow handles the process; the lawyer keeps every judgment.

Why the check needs a workflow

The case for systematizing the conflict check is the same case that runs through all of risk management, sharpened by the stakes. A conflict issue is not a minor administrative slip; it goes to the heart of professional responsibility and can carry consequences well beyond a single matter, and the malpractice data reflects that conflicts are a live and, in the most recent figures, rising category of claims (ABA 2020-2023, via Minnesota Lawyer). When a category of serious exposure depends on a step that is easy to skip, the only responsible move is to make the step impossible to skip, which is what a workflow does. It converts the check from something a person has to remember into something the process does automatically, so the firm's compliance no longer rides on anyone's memory on a hard day.

It is worth being precise about what "systematize" means here, because the distinction is the whole ethical safety of this build. Systematizing the conflict check does not mean automating the judgment of whether a conflict exists; that judgment is legal and belongs to the attorney, and no system should touch it. It means automating the process around that judgment, ensuring the check is triggered, the right information is gathered, the search is run, and the results reach the attorney, so that the lawyer's judgment is reliably invoked at the right moment with the right information in front of them. The workflow makes sure the attorney is always asked the conflict question at the right time; it never answers it. This is the same operational-versus-legal line that governs everything we build, and in conflicts it is especially bright.

The five-step build

The workflow is five operational steps, sequenced so the check fires reliably and ends with the attorney's determination and a durable record. Each step is process; none is legal analysis.

The design principle across all five steps is that the operational parts are made automatic and the legal part is made unavoidable. The trigger is the linchpin: by firing the check at defined events rather than leaving it to someone's initiative, the workflow guarantees the check is at least started every time, which is where most failures actually occur, the check that never begins. Capture and search gather and match the party information, the identifying data the firm already maintains for this purpose, and surface puts any potential matches in front of the attorney with enough context to evaluate them. That hand-off to the attorney is deliberate and total: the system's job ends at presenting potential matches, and the attorney's begins. This build extends the front-of-matter discipline covered in the intake pipeline and belongs on the new-matter checklist.

The line the workflow never crosses

Because conflicts sit squarely in professional responsibility, this is the build where the operational-versus-legal line has to be brightest, and it is worth stating without any hedging. The workflow triggers the check, gathers the names, runs the match, surfaces potential hits, and records the outcome. It does not, and must not, determine whether a potential match is an actual conflict, whether any conflict can be addressed, or whether the firm may take or continue the matter. Those are professional-responsibility judgments that depend on the rules of the jurisdiction, the specific facts, and the lawyer's ethical obligations, and they belong entirely to the attorney. The system is deliberately built to surface and stop, handing every question of interpretation to the person qualified and obligated to answer it.

This is not a limitation to apologize for; it is the feature that makes the build safe and sound. A system that tried to clear or flag conflicts on its own would be making legal judgments it has no business making, and would be worse than useless, because a firm might rely on it. By contrast, a system that reliably ensures the attorney is always presented with the conflict question, at the right moment, with the right information, and never presumes to answer it, strengthens the firm's professional compliance without ever intruding on it. Being explicitly not a law firm, and building tools that surface rather than decide, is exactly what lets us work near this obligation at all. The attorney owns the conflict analysis, the determination, and the professional judgment; the workflow owns only the reliability of the process around them.

Why documentation is half the value

The final step, recording that the check ran and what its outcome was, is easy to treat as an afterthought and is in fact half the point. A conflict check that happened but was never documented is, from the firm's perspective later, nearly as exposed as one that did not happen, because there is no record to show it did; conversely, a documented check is durable proof that the firm met its process obligation at the moment it mattered. The workflow captures this automatically as a byproduct of running, so the firm accumulates a clean, contemporaneous record of every check without anyone having to maintain one by hand. That record is quietly one of the most valuable things the workflow produces.

A closing word on confidentiality, because conflicts inherently involve names. The workflow is built to hold only the identifying information a check requires, party and related-entity names and the metadata of the check itself, and never the substance of any matter or any privileged content; the firm controls exactly what is entered, and the design is to hold the minimum the function needs. This keeps the workflow consistent with the confidentiality discipline we treat as non-negotiable, even as it operates on the one kind of information, party identity, that conflict-checking unavoidably requires. Build the workflow to fire reliably, hand every determination to the attorney, and document each check automatically, and the firm gets a conflict process that is both far more reliable than memory and cleanly within the ethical lines that this obligation demands. Because professional-responsibility rules vary by jurisdiction, the firm and its counsel should confirm the workflow fits their specific obligations.

Where to go next

• The Intake Pipeline

  Where the conflict check is triggered.

• The New-Matter Checklist

  Where the documented check belongs.

• The Malpractice Stats Update

  Why conflicts are worth systematizing now.

• The SOP Template

  The format to document the workflow.

Frequently asked questions