FactsonlyWhat you sawWhen it happenedWhat was said
← All insights

CC-101 · Lesson 6 · Escalate, do not decide

What your compliance officer actually needs from you

Escalating is easy. Escalating usefully takes a small amount of discipline, and it is the difference between a decision someone can make and one they cannot.

23 September 2026 · Amanda Dunn · 4 min read


Compliance officers rarely complain about too many escalations. What they get instead is escalations they cannot do anything with — an impression, with no observable facts underneath it.

The difference is small and entirely learnable.

Facts, not conclusions

This is the whole discipline. Write what you observed, not what you think it means.

  • Not useful: "Something felt off about this buyer."
  • Useful: "Buyer declined to meet in person three times, asked whether the deposit could come from two different accounts, and could not say what the company purchasing the property does."

The second version can be assessed. The first cannot, and if it is ever read back months later it will mean nothing to anybody — including you.

The five things worth including

  • Who — the customer and anyone else involved, including people who appeared without explanation.
  • What you observed — specific behaviour, in the order it happened.
  • When — dates, and whether this was one occasion or several.
  • What was actually said — a short quote beats a paraphrase.
  • Where the transaction is up to — what happens next, and how soon.

That is two minutes of writing, and it gives the officer everything they need to make a decision without coming back to you three times.

What to leave out

Your theory. Speculation about where the money came from. Anything about the customer that is not an observation — how they dressed, their accent, assumptions from their name. None of it helps, and some of it is a problem in its own right.

A useful test before you submit: could someone who has never met this customer tell exactly what happened, without knowing what you concluded? If yes, you have written a good escalation.

Do it while it is fresh

Detail decays fast. The exact phrasing that made you pause is gone by the following week, and the paraphrase you are left with is always weaker than the original. Write it the same day.

And then stop

Once it is escalated it is theirs. Do not chase the customer for more, do not investigate, and do not go quiet on them. Carry on as normal and let the process work.

The one rule where "I was only being helpful" is no defence →What you must not say once something has been raised.

Where Curlew fits

Curlew puts the escalation on the customer record, so the facts you wrote sit alongside the due diligence, the screening result and the risk rating that produced them. The compliance officer opens one file rather than assembling context from four places.

And the audit trail records the whole sequence — what was raised, when, by whom, and how it was dispositioned. That record is worth as much as the escalation itself.