vstorm-co Writing an alert narrative
The analyst needs the facts assembled, in order, with nothing characterised.
The structure
What the rule fired on, in plain language · the transactions that triggered it, with dates, amounts, counterparties and channels · what the customer's expected activity is, from onboarding · how the observed activity differs · what the customer has said about it, if anything · prior alerts on this customer and how they were closed.
Neutral language, throughout
"Six transfers of 9,800 over eight days to three new counterparties" is the narrative. "Structuring" is a conclusion, and writing it changes what the file means.
Always include
The negative findings — the checks made that found nothing. An analyst needs to know what has already been looked at.
Never
Reach a conclusion, recommend a filing, use typology names as descriptions, or tell the customer that any of this is happening.