Patena
Product · Risk

A score you can take apart.

Patena scores risk for every subject your organization tracks: companies, places, routes, suppliers. Each score is built from the twelve domains, keeps its history, and comes with Atlas’s explanation of what moved it and which sources it trusted. When there is not enough evidence, it says so instead of showing a number.

Halvard Shipping ASSanctionsConflictSubject · watched by 3 · updated 07:41 UTC
Risk score74
7 days▲ +6
30 days▲ +21
Sources · 30d61
Peak81 · Oct 14
Oct 14 · EU annex
Why 74 · the components Atlas scored
Listed in EU Annex I; OFAC SDN match pending3 sources · T1+28
Two vessels transited a strike area in 14 days17 sources · T1–T2+19
Insurer withdrew war-risk cover, per trade press6 sources · T2+11
Crew strike at Bergen office2 sources · T2+4
No events0 sources
Atlas explainsGenerated 07:41Z

The score rose from 53 to 74 over 30 days. Most of the move came on 14 October, when the EU listed the company in Annex I 1. The conflict component reflects two transits through the Red Sea strike area, confirmed by AIS and three T1 outlets 2.

I am not counting the reported Tallinn stoppage: one T3 source, no corroboration 3. If a second source appears, the unrest component would rise by about 6.

1Official Journal2Reuters · Lloyd’s List · FT3ERR · T3
Related subjects
Nordfracht GmbH58▲+9
Port of Gdańsk41▲+12
Bergen Marine InsuranceInsufficient · 2 in 30d
Machine-extracted. Events, entities, places and scores may be delayed or wrong. Verify against cited sources.
Last ingest 14:58 UTC · Lag 47 s

The Risk detail for one subject: the score, its 30-day history with the day the EU annex landed, the domain components that add up to 74, and Atlas explaining the move with citations. On the right, related subjects, one of them honestly marked insufficient.

Every subject, every morning

The portfolio view ranks your subjects by score and by movement. Agents watch it so you do not have to.

Halvard Shipping ASSanctions
74▲+6 · 7d
61 sources in 30d · updated 07:41 UTC
Port of GdańskUnrest
41▲+12 · 7d
38 sources in 30d · updated 14:45 UTC
Suez approachesConflict
67▼−3 · 7d
142 sources in 30d · updated 14:58 UTC
Bergen Marine InsuranceEconomy
Insufficient data · 2 articles in 30d
No score is shown below 5 articles. Atlas will tell you when the count is reached.

How a score is made

Four steps, each visible on the subject’s page. No weights are hidden.

01

Evidence

Stories mentioning the subject, or a place within its radius, in the window. Counted once per story, not per article, so a wire story reprinted 40 times is one piece of evidence.

02

Domain components

Each story adds to the component of its domain, scaled by severity, coverage tier and recency. Twelve components; the page shows every one that is non-zero.

03

Thresholds and history

Your organization sets the thresholds that make a score a hit. History is kept per day for 13 months, with the stories behind each move.

04

Explanation

Atlas writes the “why” from the same components and the same sources, with citations. The number and the explanation can never disagree, because they are computed from the same evidence.

What a score will never do

Pretend to know

Fewer than 5 stories in 30 days: no score, an Insufficient badge with the count. A dash is a lie; a zero is a bigger one.

Hide its sources

Every component expands to the stories behind it. Every story links to the articles. Every article shows outlet, language, tier and time in UTC.

Move silently

A change of 10 or more in 7 days is a hit for the subject’s watchers, with Atlas’s explanation attached. Delivery is wherever you asked.

Score the subjects you already track.

Bring your list of companies, places and routes. We will set up the first subjects with you.