Tier 4 · ODS & Parties
The Operational Data Store (ODS) is where the same organisation ends up recorded four times, where connections point at parties that no longer exist, and where a party can quietly sit on both sides of a matter. This audit resolves the duplicates — conservatively — and surfaces the screening signals your conflicts process needs.
Case, punctuation, and suffix variants of the same organisation are grouped — with a deliberate no-auto-merge guardrail that rejects look-alikes rather than risk a wrong merge.
Orphaned edges — connections pointing at parties that no longer exist.
ODS references reconciled against the practice-management system (PMS) to find records that disagree across systems.
Parties marked inactive but still connected to live matters.
Parties appearing on both the acting and the opposing side — surfaced as screening candidates for your conflicts process, never as conflict determinations.
Entity-resolution and graph lenses run over ODS parties and connections on an on-premise stack (client and third-party data — full authority gate, controlled environment only). The matching guardrail is deliberately conservative: when two records only look alike, it rejects the merge.
The register held 333 duplicate organisation groups. The guardrail correctly refused to merge 380 look-alike name groups that shared a spelling but carried different company reference numbers — distinct real entities — and the graph surfaced 1,305 acted-both-sides screening candidates.
A cleaner party register with no dangerous auto-merges, reconciled external references, and a both-sides screening list your conflicts team can clear — surfaced for a human to decide, not decided for them.