How to Read OpenSanctions Results
The most important discipline when using OpenSanctions is simple:
do not treat a hit as a conclusion.
What a result can actually mean
A result may indicate:
- a direct listing
- a related person or entity
- an alias or alternate transliteration
- a historical or adjacent risk signal
- a partial match that still needs manual judgment
Those are very different things. Good research keeps them separate.
Read the source context, not just the label
When a result appears, ask:
- Which source dataset is this coming from?
- Is it a sanctions list, a PEP dataset, or another type of risk source?
- Is the match clearly exact, or only plausible?
- What attributes actually support the match?
- What remains uncertain?
If you cannot answer those questions, you are not ready to write the result up as meaningful.
The most common mistake
The most common mistake is collapsing related into same.
Examples:
- a related entity is listed, not the target company itself
- a person with a similar name appears, but the jurisdiction or context does not line up
- the presence of a signal is treated as if it already changed the legal or operational status of the target
That is poor method.
Better framing
A safer way to write the finding is:
- “This entity appears in…”
- “A related person appears in…”
- “A potentially relevant match exists in…”
- “This requires manual confirmation…”
That language is not weak. It is precise.