SAR narratives: drafted by AI, filed by people
Author
Audrey
NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.
Date Published
Writing the narrative for a suspicious activity report is slow, careful work. An analyst has gathered the transactions, the customer history, and the alert that started the case. Then comes the part that takes the longest: turning it all into a clear account of what happened and why it looked unusual.
That is the kind of job an AI assistant can help with. It can read the case, organize the facts in order, and produce a first draft in the analyst's house style. The analyst then reads it, corrects it, and takes responsibility for it.
The problem in the BSA team's terms
The BSA officer wants the time savings in the drafting. What they cannot accept is any path by which the filing itself happens without a person deliberately submitting it. A filing goes to the regulator and carries the institution's name, so it should be a decision a person made.
There is a second concern that is particular to this work. Case management for these reports is sensitive, and the number of people and tools that can see it should be small. The BSA officer wants the assistant to be a drafting aid for the analysts on the case, and not a tool that expands who or what can touch the filing.
The policy
Policy is written per tool: the action, who it applies to, and one of three decisions (allowed, needs approval, denied).
Action | Who | Decision |
|---|---|---|
Read a case and its supporting records | BSA analysts' assistants | Allowed |
Write a draft narrative in the case management system | BSA analysts' assistants | Allowed |
Submit the filing | Every agent | Denied |
The assistant can read and draft. The filing tool is denied to every agent, so no prompt, workflow, or user can get an AI session to submit. The submission is something a person does in the system, with the controls the institution already has around it.
Who handles it instead
The analyst reviews the draft, edits it, and files. Whatever approval the bank's own process requires before filing still applies and stays where it is. The AI policy does not replace that process or sit in the middle of it.
Because the tool is denied, no approval is routed anywhere. Where a team wants an AI path that waits for a person, a tool can be set to needs approval instead, with the request going to a named approver or role who answers in Slack or the web inbox. For a regulatory filing, most teams will prefer deny.
What the Record of Decisions shows
The Record of Decisions has an entry per decision: who asked, which agent, which tool, the decision, who approved, and when. For this workflow the BSA officer can see the following.
- Which analysts used the assistant to draft, on which days, and through which agent.
- Each attempt on the filing tool, shown as a refusal.
The refusals are the part that matters in a review. Saying "the assistant cannot file" is a claim. Showing that the filing tool is set to deny for every agent, with each attempt on it listed as a refusal, is evidence. The record covers calls that go through NobleCloak, and the case management system's history remains the record of filings.
Use it as the working record of policy decisions, kept alongside the case management system's own history.
What this does not do. It does not evaluate the narrative or decide whether a report should be filed. Those decisions belong to the analyst and the BSA officer. It also does not describe or promise anything about how a regulator will view the use of AI in the process. It controls one tool and records what happened.
Related scenarios
- SAR tools invisible outside BSA: case management tools entitled to the BSA role only.
- OFAC hits can't be cleared by AI: the clearing tool denied, while screening is allowed.
- Recommend, don't decide: the assistant writes a recommendation and the decision tools are denied.
- Rate filings stay with actuarial: another regulatory submission denied to every agent.
Get started and put the same line on your case management tools.

