Ask a compliance officer when conflict checks fail in their firm and you will not hear about a difficult judgement call on a group structure. You will hear about a matter opened on a Friday afternoon for a client the firm has acted for before, where everybody knew the answer, so the check was going to be done on Monday. This piece is about that gap, from the compliance officer's side of the desk rather than the fee-earner's.
The compliance officer's actual week
The SRA's thematic review of compliance officers, published in December 2025, found that around 44% of COLPs and COFAs feel their role is valued by their firm, and that compliance officers spend about 26% of their time on compliance duties. Many combine the role with fee-earning.
Read those two figures together and the operating reality is plain. A quarter of the time, a role that is felt to be valued by fewer than half the people doing it, and a caseload alongside. Any control that depends on the compliance officer personally chasing people to complete a step is going to be applied unevenly, and unevenly in a specific direction: it will hold up in quiet weeks and give way in busy ones.
A separate step is a step that decays
Every firm's conflict process starts strong and erodes at the edges. Not through anybody deciding to skip it, but through the ordinary sequence: a matter is urgent, the check is a form, the form is completed later, later becomes after the client-care letter, and the letter has already committed the firm.
The fix is structural rather than cultural. If the check runs when the matter record is created, it cannot be deferred, because there is no separate moment at which to defer it. This is why the interesting question about conflict software is not how clever the matching is. It is whether running the check is an act somebody has to remember.
What the compliance officer needs that the fee-earner does not
A fee-earner needs the answer: is there a problem with this instruction. A compliance officer needs something else entirely, and the difference is the source of most friction between them. They need evidence of the search: what was compared against what, when, by whom, and what was found.
A spreadsheet cell reading 'no conflict' records a conclusion and destroys the evidence for it. Six months later, nobody can say whether the search covered former clients, whether it covered the parent company, or whether anyone looked at all. A record that shows the search happened is more useful than one that shows only its result, because the result is the part nobody disputes until something goes wrong.
How this works when a matter opens here
A matter is a record with a client, a reference, a responsible partner, a practice area and a jurisdiction. Creating it runs a conflict check. There is no button, because a button is a thing people do not press when they are busy. The comparison, the matching rules and the thresholds are covered in more detail in our earlier piece on conflict checks at matter open, and the mechanics have not changed.
What matters from the compliance side is that both the run and the sign-off are written to the audit and compliance register. The register can be filtered by period, matter or person, and exported as a spreadsheet or as a printable audit bundle carrying a SHA-256 content digest over the exact rows exported. So the monthly compliance job stops being a request to fee-earners for confirmations and becomes a filter and an export.
Redaction is not an ethical wall
When a conflict hits a matter the reader is not on, the result is redacted and names the partner to ask. The reader learns that a question exists and who owns the answer, and nothing else. That is deliberate: the one answer a conflict check must never give wrongly is that there is nothing there.
It is a redaction, not an information barrier, and the distinction is one a compliance officer should insist on with any supplier. A barrier names screened individuals, covers every system the firm runs, and comes with undertakings and a record of who was screened, when, and by whom. We do not have ethical walls, we are not building the label onto a narrower mechanism, and a firm that needs walls as a technical control should not accept this as a substitute.
The ten minutes at month end
A compliance officer with 26% of their time available cannot audit every matter. What they can do is sample. Filter the register to the period, sort for checks that returned matches, and look at two things: whether each match has a sign-off recorded, and how long the gap was between the check running and a partner reviewing it.
That gap is the most useful number in the whole process and almost nobody tracks it. A firm where checks are reviewed the same day has a working control. A firm where the average gap is eleven days has a control that exists on paper and a period of exposure it has never quantified.
What this does not do
It matches names, and only names. It does not know that one company acquired another last year, it does not resolve group structures, and it does not read Companies House. It does not clear anything: what comes back is a question for a partner, not permission to act.
It only knows what is in LegalAI Space, so matters that live only in your practice management system are invisible to it, and there are no live DMS connectors. If that rules the approach out for your firm, it should rule it out now rather than after a migration. What it does do is the part a manual process is worst at: running every time, comparing every name, and leaving the evidence behind without anyone having to remember to.
