Lesson 07 of 8
SAR Quality Review: Reading Your Own Draft Like a Reviewer
5 min read · SAR
Run the same quality pass an examiner would: an elements check, the stranger and 'so what?' tests, accuracy and timeliness, and a confidentiality and tone review — so weaknesses are gone before anyone else sees them.
Read your own draft like a stranger
- The writer knows the case; the reader knows only the words
- Quality review closes that gap before filing
- FFIEC examiners assess SAR quality, not just whether you filed
- A weak narrative is a finding even when the decision was right
You've written a draft. This lecture is about the pass that comes next, reading it the way someone who knows nothing about the case would. The writer always knows more than the page says, because you lived the investigation; the reader knows only the words in front of them.
Quality review is the discipline of closing that gap before the SAR leaves your desk. And it matters beyond good practice: the F-F-I-E-C BSA slash AML Examination Manual makes clear that examiners assess the quality of SARs, not merely whether the institution filed them. A vague or boilerplate narrative can be a quality finding even when the underlying decision to file was exactly right.
So let's build a review pass you can run on every draft.
Pass one: the elements check
- Who, what, when, where, why — all present and specific?
- How — can a reader trace the money?
- Mark any element that's implied but not stated
- Add the missing one before moving on
The first pass is the elements check, and it's the fastest way to catch the most common defect. Go through your draft and find each of the six elements explicitly: who, what, when, where, why, and how. Don't accept implied; the why in your head doesn't count if it isn't on the page.
Ask of each: is it present, and is it specific? Can a reader name the subject, the activity, the dates, the locations, the reason it's suspicious, and the path of the money, using only what you wrote? The two that fail this test most often are why and how, exactly as we warned, so scrutinize those hardest.
Anywhere an element is missing or merely gestured at, fix it now. This single pass catches a large share of what reviewers would otherwise flag.
The stranger test and the 'so what?' test
- Stranger test: would an outsider understand it cold?
- Flag every undefined acronym, code, or assumed fact
- 'So what?' test: does each sentence advance the suspicion?
- Cut what doesn't; sharpen what does
Now two quick tests that sharpen quality fast. First, the stranger test: imagine a reader who has never seen your institution, your customer, or your systems, and ask whether they'd understand this narrative cold. Every undefined acronym, internal code, or fact you assumed but never stated fails the stranger test, so flag and fix each one.
Second, the so-what test: read each sentence and ask whether it advances the suspicion or supports an element. If a sentence does neither, it's padding, the too-long failure we named earlier, and it dilutes the real story, so cut it. Together these tests pull a narrative toward the target we keep returning to, complete and relevant, clear to an outsider and free of anything that doesn't earn its place.
They take two minutes and they catch a lot.
Completeness, accuracy, and timeliness
- Do the narrative and the structured fields agree?
- Check names, dates, amounts against the records
- Confirm the detection date and the 30/60-day deadline
- An error in a number undermines the whole filing
The next pass is mechanical but vital: completeness, accuracy, and timeliness. Check that the narrative and the structured fields tell the same story, because a subject or amount in the narrative that doesn't match the coded fields is a red flag of carelessness to a reviewer. Verify every name, date, and dollar figure against the source records; a transposed amount or a wrong date can quietly undermine an otherwise strong filing and, worse, mislead an investigator.
Then confirm timeliness: identify your detection date and confirm you're inside the thirty-day window, or sixty if no suspect was identified, that we covered last lecture. Accuracy is part of quality. A narrative can be beautifully written and still fail if the numbers in it are wrong.
The confidentiality and tone check
- No language that hints the subject was or will be told
- Objective, factual tone — no speculation beyond the facts
- State suspicion; don't assert guilt or a specific crime
- Keep it professional — this document may be read for years
A final review pass covers confidentiality and tone, two things easy to overlook. On confidentiality, make sure nothing in the narrative implies the subject was tipped off or will be, no hint that the customer was told why an account was closed, since that whole prohibition lives at thirty-one U-S-C fifty-three eighteen g-two and we don't want the narrative undercutting it. On tone, keep it objective and factual.
State suspicion, don't assert guilt or name a specific crime you can't support; a SAR reports reason to suspect, not a conviction. Avoid editorializing and speculation that runs past the facts. Remember this document may be read by investigators, examiners, and others for years, so a calm, professional, fact-anchored tone serves both the reader and the institution.
Then, and only then, the draft is ready.
Recap and next
- Pass 1: all six elements present and specific
- Stranger test + 'so what?' test
- Completeness, accuracy, timeliness
- Confidentiality and objective tone — then file
Recapping your quality-review routine, the pass that turns a draft into a filing. First, the elements check: all six present, specific, and especially the why and the how. Second, the stranger test for clarity to an outsider and the so-what test to cut anything that doesn't advance the suspicion.
Third, completeness and accuracy, narrative and fields agreeing, every name, date, and amount verified against the records, and timeliness confirmed against the deadline. Fourth, a confidentiality and tone check: no tipping off, objective and factual, suspicion stated rather than guilt asserted. Run those four passes and you've reviewed your own work the way an examiner would.
In the final lecture, we pull everything together into a single pre-filing checklist you can keep beside you for real casework and practice drills.
Sources
- FinCEN, Guidance on Preparing a Complete and Sufficient Suspicious Activity Report Narrative (FIN-2003-G002)
- FFIEC BSA/AML Examination Manual — Suspicious Activity Reporting (SAR quality and examiner expectations)
- 31 CFR 1020.320
- 31 USC 5318(g)(2)
Test your knowledge
A few SAR questions on this material — pick an answer to see the explanation.
Q1. An analyst writing a narrative for a trade-based money-laundering case needs to address 'how.' What specific content should the 'how' section cover?
Q2. A filer writes: 'Account holder conducts frequent large transactions.' Why is this language insufficient for a SAR narrative?
Q3. When addressing 'who' in a SAR narrative, what information about the subject should the writer include?
Q4. When writing the 'what' element of a SAR narrative about a layering scheme involving multiple wire transfers, what should the writer specify?