SanctionTrail

Restricted party screening: what a good screening record actually contains

A screenshot of a search result isn't a screening record. A record that holds up shows exactly who you screened, which lists you checked, a timestamp nobody typed in afterwards, the result, and the decision. Here's what that looks like, field by field.

Checked against official sources on November 17, 2026. A plain-language summary, not legal advice.

You ran the check. Could you prove it in March?

Here's a scene that plays out in small exporting companies all the time.

Somebody — maybe you, maybe the person who left in October — checked a new customer against the restricted party lists before the first shipment went out. The check came back clean. The goods shipped. Everyone moved on.

Then an auditor, a bank, or a freight forwarder asks a simple question: show me the screening.

And what surfaces is… a screenshot. Maybe. Saved in a folder called “Compliance 2024 final FINAL,” with a filename like IMG_2041.png. No date you can trust. No record of which lists were searched. No note of which version of the name was typed in — and if you've ever dealt with transliterated names, you know the spelling is the story.

That screenshot isn't a screening record. It's a souvenir.

This post is about the difference, and about what a denied party screening record should actually contain if you want it to hold up when someone who doesn't know you, doesn't trust you, and is paid to be skeptical comes asking.

First: what the record is for

People tend to think of sanctions screening as the moment of the check itself. Type name, get result, ship or don't ship. Done.

But in export compliance, the check and the record are two different jobs:

  • The check protects the shipment. It stops you selling to someone on the OFAC list, the Entity List, or any of the other U.S. restricted-party lists you should never be selling to.
  • The record protects you. It's the evidence, months or years later, that the check happened, that it was done properly, and that the result really was clear at the time.

Lists change. A party that was clean in January can be designated in June. Without a dated record, a later reviewer sees a name that is now on a list and a shipment that went out — and the burden of explaining lands on you. With a dated record, the conversation is over in about thirty seconds: “Here's the screening, here's the date, here's the result against the lists as they stood that day.”

That's the whole game. A good record answers questions before they're asked, in a form a stranger can verify without taking your word for anything.

The five things a real screening record contains

1. Exactly who you screened — as typed, and as matched

Record the name precisely as it was entered, plus any variations you searched: alternate spellings, former names, trade names, the name in a different word order. Anyone who has screened names from the Middle East, China, or Eastern Europe knows one spelling is never the whole picture.

If the search returned a possible match that you reviewed and cleared, that belongs in the record too — who the potential match was, and why it wasn't your party (different date of birth, different country, different company registration). A cleared false positive, written down, is some of the strongest evidence you were actually paying attention.

2. Which lists you checked

“Checked against government lists” is too vague to mean anything. A useful record names them: OFAC's Specially Designated Nationals list, the Consolidated Screening List and the sources rolled into it, the Denied Persons List, the Entity List, the Unverified List, and the rest of the U.S. lists relevant to your business.

Why does the detail matter? Because “we ran an OFAC check” and “we screened against every U.S. restricted-party list” are different statements, and auditors know it. If a party was sitting on a list you didn't search, a record that honestly shows which lists you covered is still far better than a vague claim — and it shows you exactly where to widen your process.

3. When it happened — a timestamp you didn't type yourself

A date someone typed into a spreadsheet can be edited in four seconds, and everyone reviewing it knows that too. The timestamp on a screening record should be generated by the system at the moment of the search, not filled in afterwards from memory.

Time matters for a second reason: screening isn't a one-and-done event. Good practice is to re-screen — when a list updates, when an order changes, when a quiet customer suddenly places a much bigger order. A run of timestamped records over the life of a customer relationship tells a story no single screenshot can: this company screens as a habit, not as a panic button.

4. The result — including the boring ones

Most of your screenings will come back clear. Record them anyway.

It feels pointless to file a record that says “no match” — until the day someone questions a shipment and that dull little record is the only thing standing between you and a very long week. In compliance, the boring records are the load-bearing ones. A file where only the problems are documented looks, to a reviewer, exactly like a file where screening only happened when someone got nervous.

5. Who ran it, and what happened next

Name the person (or at least the role) who performed the screening. If there was a hit or a near match, record the decision: held the shipment, escalated to compliance, cleared with documented reasoning, walked away from the deal.

That last field — the decision — is the one most often missing, and it's the one that turns a search log into an audit trail. A result without a decision is trivia. A result with a decision, a date, and a name attached is evidence of a working compliance program.

What “tamper-evident” actually means, in plain English

You'll hear this phrase from us, so let's be honest about what it should mean.

A tamper-evident record isn't magic, and it isn't a promise that nothing can ever be changed. It means the record is built so that if anyone alters it after the fact — changes a date, swaps a result, quietly deletes an inconvenient hit — the alteration shows. The record carries a kind of fingerprint of its original contents, and if the contents and the fingerprint stop matching, you know something moved.

Compare that to the screenshot in the shared drive. Anyone with folder access can rename it, replace it, or crop it, and no one would ever know. Tamper-evidence doesn't make people honest. It makes dishonesty visible — which, for audit purposes, is the next best thing, and usually enough.

A quick self-test for your current process

Pull the record for the last new customer you screened. Not the policy — the actual record. Then ask:

  1. Could a stranger tell, from this alone, who was screened and under what name variations?
  2. Does it name the lists that were searched?
  3. Is the date trustworthy — generated, not remembered?
  4. If there was a near match, is the reasoning written down anywhere?
  5. If you deleted your own access tomorrow, would this record still make sense to whoever replaced you?

If you got five yeses, genuinely, well done — you're ahead of most companies your size. If you got the usual two or three, you're normal, and normal is fixable. The fix isn't more effort or a bigger spreadsheet. It's capturing these fields automatically, at the moment of the check, so the record builds itself while you get on with the actual work. Our guide to screening records an auditor will accept goes deeper on what to keep, and for how long.

Screening is a habit. The record is the proof it happened.

Nobody gets into exporting because they love record-keeping. You do it because the one time it matters, it matters enormously — and because “we definitely checked, I remember doing it” is not a defense, it's a hope.

Run the OFAC check. Run the full denied party screening. Then keep a record that would convince a skeptic: the name as searched, the lists covered, a real timestamp, the result, and the decision. Do that every time, for every customer, and screening stops being the thing you scramble to reconstruct under pressure. It's just the paper trail of a habit you already have.

Where SanctionTrail fits. That's exactly what we're building SanctionTrail to do: check a name against every U.S. restricted-party list in seconds, and keep a tamper-evident screening audit trail your auditor can verify without a guided tour. It's in early access now — if your current system is a folder full of screenshots, we'd love to show you the alternative.

Questions

Is a screenshot of a search result a screening record?

Not really. A screenshot rarely shows which lists were searched, which name variations were tried, or a date you can trust, and it can be renamed or replaced without a trace. It is better than nothing, but a record with the name as searched, the lists covered, a system-generated timestamp, the result and the decision is what holds up with an auditor, a bank or a forwarder.

What should a screening record contain?

Five things: the name exactly as entered, plus any variations searched (and any possible match you cleared, with the reason); the lists checked, named; a timestamp generated at the moment of the search; the result, including the clear ones; and who ran it and what happened next.

How long should screening records be kept?

The Export Administration Regulations generally require five years, and OFAC's recordkeeping rules run to ten years for sanctions records. Our guide to screening records an auditor will accept covers what to keep, and why, in detail.

Official sources