Blog
Practitioner writing on how the work is actually done
Craft and methodology, not regulatory citation. These articles cover the parts of an AML programme that generalise across regimes — tuning detection, writing a case file a reviewer can follow, building a risk model that discriminates — so they can be written properly rather than hedged.
Articles
Published
Long reads. Each one is written to be usable by someone with a queue to clear and a review to prepare for.
- Transaction monitoring8 min read
Why transaction monitoring rules produce false positives, and what to do about it
If most of your alerts close with no further action, that on its own is not evidence of a broken system. It becomes evidence when nobody can say which rule the noise came from, why the threshold is the number it is, or what coverage was given up the last time somebody changed it.
Read the article - Investigation quality7 min read
What makes an investigation defensible to a reviewer
The reviewer might be your own quality assurance function next month, internal audit next year, an examiner after that, or a court long after everyone involved has left. All four ask the same question in different words: on what basis did you decide this, and can you show me?
Read the article - Risk assessment7 min read
Structuring a customer risk assessment that actually discriminates
A customer risk rating is only worth producing if something downstream changes when it changes. If the same due diligence, the same monitoring sensitivity and the same review frequency apply whatever the rating says, the model is documentation rather than a control.
Read the article
Bylines and publication dates are not yet set on these articles. They carry no author attribution and no date rather than a placeholder one, so nothing here can be quoted as having been published by a named person on a given day.
Go deeper
The guides take these methods further
Worksheets, test designs and the governance records each exercise should leave behind — outlined now, written next.