Jump to section
A conflict search is only as honest as the data behind it. Run a check against a contacts list riddled with three spellings of the same numbered company, a party filed under a nickname, and two half finished records for one opposing lawyer, and the clean result you get back is worse than useless. It looks like safety. It is not.
Most conflict misses I have seen were not failures of judgment. They were failures of hygiene. The lawyer asked the right question, the system searched exactly what it was told to search, and the answer came back empty because the match was hiding under a variant nobody had reconciled. So here is the working checklist I hand new staff. Print it, pin it, and treat your contacts database like the safety instrument it is.
One Person, One Record
The single most valuable rule, and the hardest to hold: every human and every organization gets exactly one record. Not one per matter, not one per year, not one that a keen assistant created because search was slow that morning. One.
Duplicates are where conflicts go to hide. If Jean Tremblay the witness lives in a separate record from Jean Tremblay the guarantor on an unrelated file, your search finds one and not the other, and you have no idea there is a link. Before anyone opens a new matter, the person opening it searches contacts first and reuses the existing record. A tidy file opening process makes that the default rather than a suggestion.
Tip. Make "search before you create" a literal step in intake, not an ideal. If a new-contact form does not force a search first, staff will skip it under pressure, and pressure is constant.
Capturing Roles and Relationships
A name alone does not tell you why a conflict matters. The role does. The same individual can be a client on one file, an adverse party on another, and a director of a corporate client on a third. Store the role on the connection between the person and the matter, never baked into the person's name.
What to capture for every party tie:
- Their role on that specific matter (client, opposing party, witness, expert, referral source, related non-party).
- Who they are adverse to, so a search surfaces the relationship, not just the name.
- Corporate relationships: directors, officers, parent and subsidiary companies, and beneficial owners you know of.
- Family and financial links that could taint a file, such as spouses, business partners, and guarantors.
This is the layer that lets a conflict search answer a real question instead of a literal one. Tools like A1 CMS Matters let you attach roles at the connection level so one clean record can carry many relationships across many files.
Rules for Names, Aliases, and Corporations
Names are messier than anyone expects, and Canadian practice makes them messier still. Write down your conventions and apply them without exception, because consistency beats cleverness every time.
| Situation | The rule |
|---|---|
| Legal name versus known-as | Store the legal name in the primary field. Add nicknames, maiden names, and anglicized spellings as aliases on the same record. |
| Numbered companies | Record the full number and the operating name together (for example, 1234567 Ontario Inc. operating as Northgate Roofing). Search both. |
| Accents and hyphens | Keep the correct accented and hyphenated form, but ensure search matches the unaccented version too, so Cote finds Cote. |
| Suffixes and honorifics | Strip Jr., Sr., and titles from the name field. They belong in notes, not in the sort key. |
The alias field is your best defence against a silent miss. When a client is known to half the registry as Bill and to the courts as William, both belong on one record so either spelling lands the same hit.
Merging Duplicates Safely
You will find duplicates. Everyone does. The danger is in a careless merge that quietly drops a link and leaves you worse off than before. Slow down and follow an order.
- Confirm the records truly are the same entity. Two people share a name far more often than you think, so check identifiers, addresses, and file history before you touch anything.
- Pick the record with the most complete and correct data as the survivor.
- Carry across every alias, matter tie, and relationship from the loser record. Nothing gets orphaned.
- Preserve a note of the merge and the date, so an audit later can reconstruct what happened.
- Re-run any conflict checks that relied on either original record.
Careful. Never merge on a hunch during a busy afternoon. A merge that swallows a relationship can turn a caught conflict into a missed one, and you may not learn until it is far too late.
If your practice runs heavy on bulk historical data, bringing it in through a controlled de-duplication pass beats letting hundreds of near-matches settle in unnoticed.
A Quarterly Cleanup Routine
Hygiene decays. A list that was pristine in January drifts by April as new files, new staff, and rushed entries pile up. So put a standing appointment on the calendar and give one person the pen.
Each quarter, work through a short pass:
- Run the duplicate detector and clear the queue using the merge steps above.
- Scan for records with no matter ties and no notes, and archive the ones that are genuinely dead.
- Spot check a handful of numbered companies and common surnames for split records.
- Confirm opposing counsel and firm records are current, since lawyers move and firms rebrand.
This dovetails neatly with a broader file review habit, and it pairs well with clear ownership so nobody assumes someone else is watching the list. Our notes on who owns what cover that handoff. If you want the wider practice-management picture, the practice-management hub collects the rest.
A conflict system does not protect you from what it cannot see, and it cannot see a party hiding under a second spelling. Devon Reyes
None of this is glamorous, and that is rather the point. The firms that avoid the ugly conflict surprise are not the ones with the fanciest search. They are the ones whose contacts list is boring: one record per party, roles captured where they belong, aliases logged, duplicates merged with care, and a quarterly sweep nobody skips. Do the dull work now, and the day a real conflict surfaces, your system will actually catch it. That is the whole return on a clean list, and it is worth every quiet hour it takes.
