Table of Contents
When you run a name against a watchlist, the software gives you a result. The hard part comes next. You have to decide what that result means, then prove later that you decided it well. Learning how to document a screening decision is what turns a screening tool into a real compliance record. It is the difference between “we checked” and “we can show exactly what we checked, when, and why we cleared it.”
This guide walks through what a good decision record contains, how to write one for a clear pass and for a potential match, how long to keep it, and the mistakes that make records fall apart under audit. It builds on the wider process of denied party screening and focuses on the one step people skip.
Why the decision, not just the search, is what matters
A screening tool tells you there might be a problem. It does not tell you if there really is one. That judgment is yours. A regulator who reviews your file years later will not ask “did you screen?” They will ask “what did you find, and why did you ship anyway?” If you cannot answer, the search itself counts for little.
Most screening hits are false positives. A common name, a shared city, a partial spelling match. You clear these all day. Each clearance is a decision. Write it down at the moment you make it, while the reasoning is fresh. A record built after the fact, once a subpoena arrives, always looks weaker than one written the same day.
The seven fields every decision record needs
A defensible record captures the same core facts every time. Miss one and the record has a gap someone can attack. Here is the minimum set.
| Field | What to record | Why it matters |
|---|---|---|
| Party screened | The exact name and details you entered | Proves what you actually searched |
| Date and time | Timestamp with time zone | Places the check in sequence |
| List version | Which lists and the data date | Shows the list was current |
| Result | No hit, potential match, or confirmed hit | The raw output before judgment |
| Decision and reason | Clear, hold, or block, plus the why | The heart of the record |
| Who decided | Name and title of the reviewer | Ties the call to a person |
| Transaction link | Order, shipment, or account reference | Connects the check to the deal |
Log the screening time and the list data date as two separate things. If you screen on a Monday against a list published the previous Friday, that is a small gap. Recording both dates shows you know it and can defend it. This is a core part of a proper audit trail.
How to document a clear pass
Most screens return nothing. It is tempting to record only the hits and ignore the clean passes. Do not. A clean record proves the check happened. If you only keep exceptions, an auditor cannot tell the difference between a party you cleared and a party you never screened at all.
For a clean pass, the tool usually stores the fields for you. Confirm it captures the party name, the date, the list set, and a “no match” result tied to the transaction. That is enough. You do not need a written narrative for a true no-hit. The system log is the record. Just make sure the log cannot be quietly edited later.
How to document a potential match
This is where records earn their keep. When the tool flags a possible match, you compare the flagged party against the list entry field by field. Then you write down what you compared and what you concluded. The goal is that a stranger reading the note later reaches the same call without asking you a single question.
Compare the identifiers you actually have
- Name spelling. Exact, partial, or a known alias.
- Address or country. Does the customer location match the listed entry?
- Date of birth or company registration, where you have it.
- Match score from the tool, if it uses one.
- The reason the party was listed, from the official notice.
Write the conclusion in plain words
A weak note says “Reviewed and cleared” or “Cleared by JM.” That tells a regulator nothing. A strong note shows the work. For example:
“Potential hit on Acme Trading. Compared name (partial match, different spelling), address (customer in Houston, TX; list entry in Tehran), and listing reason (proliferation, not relevant to this party). Conclusion: false positive, different entity with a similar name. Cleared by Jane Ortiz, Compliance Analyst, on 12 August 2026.”
That note stands on its own. It names the fields checked, the finding on each, the conclusion, the person, and the date. For a deeper walk through clearing weak matches, see how to resolve a false positive in denied party screening.
When to escalate and when to block
Not every match is yours to clear. Your compliance program should set a line. Below it, an analyst can clear a plain false positive. Above it, the call goes up. Write that line down before you need it, so no one improvises under pressure.
- Hold the order the moment a real match looks possible. Do not ship on a maybe.
- Escalate high match scores and any hit you cannot rule out to a named senior reviewer.
- If the party truly appears on a sanctions list, block the transaction and follow your reporting duties. A confirmed match can mean freezing funds or filing with the authorities.
- Record the escalation itself. Who you told, when, and what they decided.
The rules behind these calls come from the agencies that publish the lists. In the United States, the Office of Foreign Assets Control sets both the listings and the record expectations. You can read its guidance at OFAC. Your process for handling matches should mirror the wider steps in how to process denied party screenings.
How long to keep the record
The common baseline is five years from the date of the transaction. Many firms keep records for seven years to line up with banking norms and to cover investigations that can reach back further. Storage is cheap. Rebuilding a lost history under investigation is not.
| Record type | Typical retention |
|---|---|
| Clean screening logs | 5 years minimum |
| Match reviews and clearances | 5 to 7 years |
| Blocked or reported transactions | 5 to 7 years, sometimes longer |
Keep the record where it cannot be silently changed. For more on retention and storage, see record keeping for denied party screening.
Mistakes that break a decision record
- Keeping records in a loose spreadsheet. Anyone can edit a cell and no one sees the change. Use a system that locks the history.
- Recording only hits. Without clean logs you cannot prove full coverage.
- Vague clearances. “Looks fine” is not a reason. Name what you checked.
- No decision-maker. A call with no owner is a call no one will defend.
- No link to the transaction. A floating screen you cannot tie to an order proves nothing.
- Saving only the current status. Keep the snapshot as it stood on the day, not just today’s view.
Avoiding these is core to good denied party screening best practices. If you want a step list to check your process against, use the denied party screening checklist.
Frequently Asked Questions
Do I need to document screens that come back clean?
Yes. A clean log proves the check happened. If you keep only the hits, no one can tell a cleared party from one you never screened. Store the clean result tied to the transaction and the date.
Who should sign off on a cleared match?
Whoever your program says. A plain false positive can be cleared by a trained analyst. A high score or an unclear match should go to a named senior reviewer. Record who made the call every time.
Can I use a spreadsheet to track decisions?
You can, but it is risky. Spreadsheets can be edited with no trace, so an auditor cannot trust the history. A dedicated system that locks changes and stamps each entry is far stronger. This matters more as volume grows, which is one reason firms weigh automated versus manual denied party screening.
How detailed does a match note need to be?
Detailed enough that a stranger reaches your conclusion without asking you anything. Name the fields you compared, the finding on each, the conclusion, the reviewer, and the date. A few clear sentences beat a one-word “cleared.”
Key Takeaways
A screening decision is only as good as the record behind it. Capture the same seven fields every time, write clean passes and match reviews the day you make them, and say plainly what you checked and why you cleared it. Name the person who decided, tie the record to the transaction, and keep it locked for at least five years. Do that and your screening stops being a box you ticked. It becomes proof you can stand behind. If you want help building a decision record process that holds up under audit, contact us.