· Yair Knijn
You offboarded the only analyst who understood the match backlog
The Head of Financial Crime approved the offboarding the way you approve any offboarding. Laptop returned, accounts deprovisioned, knowledge-transfer box ticked because the analyst said "it's all in the system." The wrong assumption hid in that last sentence. It was not in the system. It was in her head, and her head walked out the door with three hundred open matches behind it.
She was the L2 who took the hard ones: the fuzzy names, the screened-but-not-cleared, the "I'm waiting on a UBO chart from the broker before I close this." None of that reasoning was written down anywhere a successor could read it.
The hidden state in a half-adjudicated match queue
A match queue looks like a list of binary decisions: clear or escalate. It is not. Each open alert carries state that never reaches a status field. Why this hit was treated as a likely false positive. Which corporate layer was still being unwound to reach the actual beneficial owner. That a near-namesake was waiting on a date-of-birth confirmation. The analyst held all of it as working memory.
When she left, every partially-adjudicated match reset to zero context. A successor opening alert #4471 sees a name, a list entry, and a PENDING flag. He does not see that three weeks of investigation already concluded the match was almost certainly the wrong person, pending one document. So he starts over, or he clears it fast to drain the queue and inherits a decision he cannot defend.
Why personal work queues are an offboarding landmine
The root cause is that the work lived in a personal queue instead of a shared case record. "Sarah's alerts" is an organizational pattern, not a tooling accident, and it turns a resignation into a compliance event. When adjudication state attaches to a person rather than a case, that person becomes a single point of failure for every open item they touched.
The FCA's 2025 sanctions systems review made the expectation blunt. Firms are expected to evidence escalation policies, investigation rationales, hand-off records, and case ageing as part of their controls. A positive match, the regulator noted, has limited control value if it is discounted without evidence or left unresolved. A personal queue produces exactly that failure: decisions with no recorded rationale, and matches that sit unresolved because the one person who understood them is gone.
Aging matches, SLA breaches, and the regulator's view of stale alerts
Backlogs are not a neutral operational state. They age, and aging is what a supervisor looks at first. Industry reporting puts global regulatory fines up sharply in 2025, and failure to act on alerts in a timely manner is a recurring line in those enforcement findings, alongside discounting matches without evidence. An alert that breaches your own SLA is your own control flagging that you did not do the thing you told the regulator you do.
It gets worse with turnover. Picture the timeline an examiner reconstructs:
- Match raised, assigned to an analyst's personal queue.
- Analyst leaves; no handover of in-flight rationale.
- Alert sits untouched past the internal review SLA.
- Successor clears it months later with no record of what was reviewed.
Every step is defensible in isolation and indefensible as a sequence, because the case record cannot answer the only question that matters: who decided what, when, and on what basis.
Case-based workflows that survive turnover by design
The fix is structural, not heroic. Adjudication state has to live in the case, not the analyst. Every open match needs a current disposition, the rationale for it, the evidence pulled, and the outstanding item blocking closure, all written at the moment of work rather than reconstructed at exit. Then offboarding is a reassignment, not an excavation. A successor inherits a case that explains itself, and an examiner inherits an audit trail instead of a gap.
This is what a screening workspace should enforce by default. InsureGuardAI keeps the disposition, the cleared-match reasoning, the ownership trail to the beneficial owner, and the raw match response together in the case record, so the institutional knowledge stays with the file when the person leaves. When the next analyst opens the queue, the backlog is a set of cases that answer their own questions. See how the case record holds the state your people carry today.