Conflict-of-Interest Checker
For the two-to-ten-attorney firm running intake off a spreadsheet, instead of the conflicts module you’d have to buy a whole practice platform to reach.
One name goes in, and back comes a ranked list of every record in your party file scoring 0.7 or higher.
Each hit carries the role and the matter it came from.
$15/mo for the firm, not per attorney. Fuzzy matching, alias screening, and CONFLICT_REPORT.md plus conflicts.json on every run. Cancel any day, and every report you’ve already run stays yours.
The name on the phone
Somebody calls on a Tuesday and wants to retain you. You have a name, a rough sense of who’s sitting on the other side, and one phone call in which to say yes or say you’ll call back.
Somewhere in the office is the list of every client, adverse party, and related party this firm has ever touched. It’s a spreadsheet. Nobody opens it mid-call.
So you screen it from memory. That’s how a prior adverse party under a slightly different corporate name, or a DBA nobody wrote down, walks in as a new client. The motion to disqualify shows up months later, and the work you did in the meantime is work you can’t bill and can’t keep.
What happens when you run it
- Export the party list to CSV. One row per party, with a
name, aroleofclient,adverse, orrelated, and thematterit belongs to. PointPARTIES_CSVat it. If your headers are named differently, override them withNAME_COLUMN,ROLE_COLUMN, andMATTER_COLUMN. - Name the party you’re screening.
NEW_PARTYis the caller. Known DBAs, prior corporate names, and other aliases go inALIASES, comma separated, and each one gets screened the same way. - Run it. Every record is scored against every query name, anything at or above
THRESHOLDis kept, and the hits come back ranked highest first inCONFLICT_REPORT.mdandconflicts.json.
What the report actually catches
- It matches on tokens rather than string order, so “Smith, John LLC” sitting in your spreadsheet still finds “John Smith LLC” on the intake sheet. Word order stops being a reason a hit disappears.
- An edit-distance score rides alongside, so “Jon Smith” surfaces against “John Smith” instead of scoring zero and vanishing into a clean report you shouldn’t trust.
- Every alias you list is screened next to the primary name, and each record keeps only its best score across all of them. A prior corporate name doesn’t need its own separate run.
- Each hit arrives with the
roleand thematterattached, so the reviewing attorney sees what it matched against and why, not just that something pinged. THRESHOLDis yours to set. Leave it at 0.7, or drop it to 0.6 when the party is a common surname and you’d rather read twenty leads than miss one.- The CSV parser survives quoted fields, embedded commas and newlines, and
""-escaped quotes, which is what a real export out of a real practice system actually looks like. conflicts.jsoncarries the same detail as the human report, so the run itself becomes a record of what was screened, against what, and when.
Who it fits, and who it doesn’t
Sized for a firm of two to ten attorneys where intake happens on the phone and the party list is a spreadsheet somebody exports every quarter. If you have a conflicts department, or a system that screens automatically the second a matter is opened, this is beneath you and you should keep what you’ve got.
It also decides nothing. It ranks names by how close they look. Whether a match is an actual conflict is a judgment call under your jurisdiction’s rules, and it stays with the attorney making it.
What it replaces
Ctrl-F in a spreadsheet, which is free, and which fails the instant a name is spelled differently than the way you remember it. Or the conflicts screen inside Clio, MyCase, or Smokeball, which are better at this in one concrete way: they check against the matters already in the system, automatically, with no export step, because the data is already theirs.
That’s the trade. You keep your list in a CSV and you run the check yourself, and you pay $15 a month instead of buying a platform to get to the check.
Where the party list goes
Nowhere. PARTIES_CSV is read off your disk, matched in memory, and never transmitted, which matters more here than almost anywhere, because that file is a list of every client and every adversary your firm has represented. The only writes are the two output artifacts, and only inside OUTPUT_FOLDER, with each path checked against that root first and each file set to 0600. There’s no account holding your party list, because there’s no account.
What $15 buys, and how soon
$15 a month, per firm, for the whole tool. No screening cap, no per-search charge, no tier sitting above you. Setup is a CSV path and a name in a .env file, so the first conflict report lands a few minutes after install rather than a week after an onboarding call. Cancel any day, and every CONFLICT_REPORT.md you’ve run stays in your folder.
Security and privacy
Handles a firm’s own client / adverse-party / matter list — sensitive, privileged-adjacent business data. Security is designed in.
Principles
– Local-first. PARTIES_CSV is read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
– Non-destructive. PARTIES_CSV is only read, never modified or deleted.
– Least privilege. Reads only the path in PARTIES_CSV, writes only under OUTPUT_FOLDER.
Protections implemented (v0.1.0)
– Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so the conflict report can’t be written outside OUTPUT_FOLDER.
– Fail-fast config validation — clear errors for missing/invalid PARTIES_CSV/NEW_PARTY/OUTPUT_FOLDER/THRESHOLD before any file is touched.
– Restrictive permissions — the generated output (CONFLICT_REPORT.md, conflicts.json) is written 0600.
– Defensive parsing — the CSV parser never throws on malformed input (missing fields default to empty string); a row with an unrecognized role value is kept and labeled unknown for manual review rather than dropped or crashing the run.
– Secrets discipline — .env and any generated output folder are git-ignored; no secrets or client/matter data in the repo.
Distribution / AV trust
Known limitations / roadmap
– NOT legal advice. This tool performs deterministic name-similarity matching only. It has no knowledge of jurisdiction-specific conflict-of-interest rules, imputed-conflict doctrines, or ethical-wall exceptions, and cannot itself determine whether a name match constitutes an actual conflict. It is a screening aid to surface candidates for a human (the reviewing attorney) to evaluate — never treat a hit, or the absence of one, as a final conflicts determination.
– Fuzzy matching can miss or over-flag. THRESHOLD (default 0.7) trades false negatives against false positives: too low and unrelated names are flagged, too high and a genuine variant (nickname, maiden name, DBA not listed in ALIASES) is missed. Always review CONFLICT_REPORT.md in full, not just the top hit, and keep ALIASES current for every known variant of the new party’s name.
– No absence-of-hits guarantee. A clean run (zero hits) means nothing in PARTIES_CSV matched above THRESHOLD — it does not mean the firm has no conflict. Data entry errors, missing rows, or an out-of-date PARTIES_CSV will silently produce false negatives.
– THRESHOLD is a single global cutoff — per-deployment tuning (e.g. a stricter threshold for adverse-party rows than for related-party rows) is on the roadmap via .env.
Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.
Frequently asked questions about Conflict-of-Interest Checker
What does the conflict-of-interest checker software do, and how does it screen a new party?
The Conflict-of-Interest Checker screens a prospective client or party against everyone the firm has already represented or opposed, before the firm agrees to take the matter. You give it a new name, and the conflict-of-interest checker software compares that name against your existing clients, your adverse parties, and the related entities tied to your past matters. Instead of one lawyer trying to recall every case the firm has handled, the tool does the remembering, and it does it the same thorough way on every intake. The result is a ranked conflict report showing the potential hits and the context around each one.
The workflow is short and repeatable. You load your client, matter, and parties list as a CSV. You enter the new party you want to screen. The conflict-of-interest checker software returns a ranked report, with the strongest matches at the top and the reason each one surfaced attached. A lawyer then reads the report and decides whether a real conflict exists, because that judgment is legal work no tool should pretend to do. What the software provides is a complete, consistent search so the decision is made on full information rather than a partial memory.
That report is also a record, and keeping it matters. Running a documented conflict check on every new client, and saving the result, is how a firm shows it actually looked. The Internal Revenue Service reminds every business to retain the records behind how it operated, and its guidance on how long to keep records lays out retention periods that run for years. A dated conflict report filed with the matter is exactly that kind of record, proof that the screening happened when it should have.
Setup does not upend how the firm already works. The tool reads the client and party data you already maintain, so there is no separate database to build and no migration to survive. You can read more about how the screening fits into new-client intake on the Conflict-of-Interest Checker page.
The scope is honest. The tool finds and ranks potential conflicts. It does not decide whether to decline a matter, seek a waiver, or build an ethical wall, because those are calls that depend on facts and judgment the software cannot weigh. Its job is to make sure nothing was missed at the search stage, so the human decision starts from a full picture. For a firm that has been running conflicts from memory or a hand-searched spreadsheet, that shift from partial to complete is the whole point of the check, and it is why the search runs the same way for every single new party.
The buyer this is built for is the firm that runs new-client intake regularly and needs a documented conflict check every single time, not just when someone remembers. For a solo or small practice, that discipline has always competed with billable work, and the check that gets skipped is usually the one that mattered. A tool that turns screening into a two-minute step, load the list, enter the name, read the report, makes the compliant path the fast one. When doing it right is quicker than doing it from memory, the check stops being the corner that gets cut on a busy afternoon.
How does the conflict-of-interest checker software help a firm document its conflict checks?
Professional conduct rules require a firm to check for conflicts before taking on a client, but the practical failure is rarely forgetting to check. It is failing to prove the check happened. A conflict caught later, with no record that the firm ever looked, is far harder to defend than one that was screened and documented at intake. The conflict-of-interest checker software builds that documentation automatically. Every screening produces a dated, ranked report tied to the new party’s name, so the firm has contemporaneous evidence that it ran the search before the engagement began.
Keeping those reports is a recordkeeping obligation the firm should treat seriously. The Internal Revenue Service guidance on how long to keep records describes the general duty of a business to preserve the documents behind its operations for years at a time, and a conflict report is part of the operational record of how a matter was accepted. Filed with the matter, it sits alongside the engagement letter as evidence the intake was handled properly rather than skipped in a busy week.
The value of a consistent record shows up most when a firm grows or its people change. A conflict check run from one lawyer’s memory is only as good as that lawyer’s tenure and recall. A conflict-of-interest checker software search reads the firm’s full history every time, so a new associate screening a client on their first day performs the same complete check a founding partner would. The institutional memory lives in the data, not in a person who might be on vacation or long gone.
Because the reports are files the firm owns, they stay accessible even if the firm later changes tools. Nothing is trapped inside a vendor’s portal. You can see how the checker fits next to the rest of the practice tools on the legal and professional page.
The documentation is not a guarantee against every conflict. A party screened under a misspelled name or an entity the firm never recorded can still slip through, which is why the tool ranks fuzzy matches rather than demanding exact ones. What the record does guarantee is that the firm can show what it searched and when. For a small firm without a dedicated conflicts department, that dated proof is the difference between a defensible intake and a story no one can back up when a former client raises a question years later.
There is also a quiet benefit in how the record ages. A conflict report captured at intake reflects what the firm knew on that day, which is the standard a later reviewer will actually apply. No one expects a firm to have screened against a matter it had not yet taken, so a dated report drawing a clean line around what existed at the time is precisely the right evidence. Reconstructing that picture years later, after the client list has grown and memories have faded, is nearly impossible without the contemporaneous file. For firms that want to go further, saving each report under the matter number keeps the conflict history searchable alongside everything else about the engagement, so the check, the decision, and any waiver all live together in one place.
Where does our client and party data live, and is it safe?
A conflict system holds a uniquely sensitive dataset, the names of everyone the firm has represented and everyone it has opposed. That list alone can reveal who a firm’s clients are and what disputes they are in, which is information clients expect to stay confidential. The Conflict-of-Interest Checker handles that by keeping the work local. You load your client and party data, the screening runs on your own machine, and the report is written there. The conflict-of-interest checker software does not ship your client roster off to a hosted service to be searched, so the firm’s most confidential list never leaves the building.
The Federal Trade Commission has laid out how any business should handle information like this. Its guide, Protecting Personal Information: A Guide for Business, gives five steps: take stock, scale down, lock it, pitch it, and plan ahead. A tool that reads only the party data you provide, screens it locally, and stores the report in your own systems lines up with locking the data down and knowing exactly where it sits. There is no third-party copy to take stock of, because there is no third party in the loop at all.
Local operation also means access to the conflict data follows the firm’s existing controls. The CSV you load and the reports the tool writes live inside your file structure, protected by the same permissions as the rest of your matter files. No separate cloud login has to be provisioned or revoked when staff change. You can read more about how the tool handles firm data on the Conflict-of-Interest Checker page.
The honest caveat applies here too. Running locally protects the client list from a vendor breach, but it does not protect a machine left unencrypted or a CSV emailed around carelessly. The conflict-of-interest checker software keeps your client and party data on your own equipment and adds no cloud copy of who you represent. The firm still owns the discipline around that data, encrypting the drive, controlling who can open the files, and disposing of old exports properly. Local-first shrinks the risk of an outside breach. Everyday security habits inside the firm are what finish the job and keep the confidential list genuinely confidential.
It also helps to be precise about how little the tool needs. To screen a name, it requires the party names and the matter links that tie them together, not the underlying case files, financial records, or privileged notes. That narrow appetite keeps the sensitive footprint small, which is the take-stock and scale-down thinking the Federal Trade Commission urges put into practice. A system that never collects a document cannot leak that document. Because the CSV and the reports are ordinary files, the firm can also see exactly what data went in and what came out, and it can delete old exports on whatever schedule it sets. There is no vendor retention policy to decode and no hidden copy sitting in a backup the firm never authorized. The firm decides what is kept, where, and for how long, which is the level of control a confidential client list deserves.
How is the conflict-of-interest checker software different from Clio, MyCase, or Intapp?
The tools most firms reach for handle conflicts as one feature inside a much larger product. Clio and MyCase bundle conflict tracking into their practice-management plans, which means you pay for the whole platform to get the check. Intapp Conflicts sits at the enterprise end, priced for large firms with dedicated risk staff. The Conflict-of-Interest Checker takes the opposite approach, a single-purpose tool at a firm-wide price of a few dollars a month, aimed at the small practice that wants a real documented check without adopting or replacing its whole system.
The other difference is where the data goes. The bundled and enterprise options are cloud services, so your client and adversary list lives on a vendor’s servers. Running the screening locally keeps that list on the firm’s own machine. The National Institute of Standards and Technology frames good security around identifying and reducing risk, and its Cybersecurity Framework emphasizes knowing your assets and limiting exposure. Fewer copies of your confidential client roster, held in fewer places, is a smaller attack surface to defend, which is precisely the kind of reduction the framework encourages.
The conflict-of-interest checker software is also narrower by design, and that is a feature for the right buyer. It does not do billing, calendaring, or document management, so it will not replace a practice-management suite a firm already likes. Instead it slots alongside whatever the firm runs, reading the client and party data those systems already hold. You can see how it fits with the other practice tools on the legal and professional page.
The trade-off is real. A firm that wants conflicts, billing, calendaring, and matter management in one login will prefer an all-in-one platform, and that is a legitimate choice. The conflict-of-interest checker software is for the firm that already has the rest, or that wants its conflict data kept separate and local rather than folded into a cloud suite. It does the one job, keeps the data close, and leaves a documented report, at a price a solo practice does not have to think twice about before running a check on every new intake.
The pricing gap is worth sitting with, because it changes who can afford to do this well. A per-seat practice suite that includes conflict tracking can run tens of dollars per user each month, which a solo or two-lawyer firm feels immediately. A flat firm-wide price of a few dollars a month removes the excuse of cost from the decision to screen every client. There is also a portability point that favors the smaller tool. All-in-one platforms tend to hold your conflict history inside their ecosystem, so leaving means untangling it. Because this tool reads standard CSV input and writes reports the firm keeps, the conflict record is never hostage to a subscription, and a firm can change systems without losing the documented history of every check it ever ran. That independence is rare in enterprise software, and for a small practice it is worth nearly as much as the lower monthly price, because it keeps the firm in charge of its own conflict history rather than a vendor.
How does the fuzzy name and alias matching find conflicts a simple search would miss?
Exact-match searching is where do-it-yourself conflict checking quietly fails. A person named on one matter as Robert Smith may appear on another as Bob Smith, or a company may show up as ABC Holdings in one file and ABC Holdings LLC in another. A plain text search for the new name walks right past those, and the conflict hides in plain sight. The conflict-of-interest checker software uses fuzzy name and alias matching instead, so a near-match on a nickname, a spelling variant, or a differently formatted entity name still surfaces for a human to judge.
The matching also reaches past the obvious party. The tool checks not just direct clients and the new party, but adverse parties and related entities recorded across the firm’s matters, because a conflict often lives in a relationship rather than a name. Screening a new client whose parent company the firm once sued is exactly the kind of hit an exact search on the client’s own name would never catch. Each potential match comes back ranked, with the context showing why it surfaced, so the reviewer can tell a coincidence of common names from a genuine concern.
Because the screening works on the party names the firm supplies, it is handling personal information, and that carries a duty to protect it. The Federal Trade Commission guide, Protecting Personal Information: A Guide for Business, asks a business to know what data it holds and to keep only what it needs, which the tool supports by reading the party list locally and writing its report to the firm’s own systems. You can read more about how the matching works on the Conflict-of-Interest Checker page.
Fuzzy matching has an honest cost, and it is worth naming. Ranking near-matches means some hits will be false alarms, two unrelated people who share a common surname. That is by design. A conflict system that only ever returned certain matches would miss the variants that matter, so the conflict-of-interest checker software errs toward showing a borderline hit and letting a lawyer clear it. Reviewing a handful of ranked possibilities is a small price for not missing the one alias that would have turned into a real conflict down the road.
Tuning the sensitivity is part of using the tool well. A firm that practices in a region full of common surnames will see more near-matches than one with an unusual client base, and the ranking is what keeps that manageable, floating the strongest candidates to the top so a reviewer spends their attention where it counts. The alias handling matters most for entities, where the same company can wear several names across a firm’s history. A subsidiary, a former name, and a doing-business-as label can all point to the same adverse party, and only matching that tolerates those variations will connect them. Catching that link at intake, before the engagement letter goes out, is exactly when a conflict is cheapest to address. That is why the screening belongs at the front door of every new matter rather than as an afterthought once the work has already begun.
| Attributes | Value |
|---|---|
| Deployment |
Cloud |
| Platform |
Web |
| License Type |
Subscription |
| Billing Period |
Monthly |
| Target Customer |
Law Firms |
| Free Trial |
Yes |
Frequently bought together
-
Bates Numbering & Production Stamper
$69.00 -
Contract Review Workbench
$75.00 -
Docket & Deadline Calculator
$29.00 -
Statute of Limitations Tracker
$39.00 -
Time Entry Reconstructor
$119.00 -
Trust / IOLTA Three-Way Reconciliation
$49.00





