Skip to Content

Overview

The Overview is where the app lands you: a one-screen executive read of the loaded snapshot. It is built for the first ten minutes with a fresh scan — what is the bottom line, what has a date on it, what should I do, where are regulators leaning, and where is the pressure concentrated.

It is one long column: an executive hero at the top, four editorial panels, the regulatory-pressure heatmap, and the Change Monitor at the bottom. Everything that is item-shaped clicks through to the same item-detail panel, which this page also documents (the Timeline and Sources reuse it).

If you prefer prose to panels, the Briefing is the narrative edition of the same scan. The Overview is the scannable one.

The executive hero

The top of the page carries:

  • The title — your snapshot’s name (or its areas × jurisdictions if you never renamed it).
  • Executive Summary — the scan’s bottom-line paragraph. Small numbered markers in the text are citations; hover or tap one to see which sources back that sentence.
  • BOTTOM LINE — a one-line distillation, when the scan produced one.
  • A TOPICS count — the number of distinct areas in view — complementing the ITEMS and JUR counts in the ticker strip.
  • Sentiment — an aside giving the scan’s overall posture read (for example Tightening.) with a one-sentence rationale. It appears only when the scan produced a sentiment; nothing is fabricated for scans that did not.

The four panels

Each panel pairs a label with a headline you will recognise from the product:

PanelHeadlineContents
Upcoming DeadlinesThe agenda.Dated obligations, soonest first
FocusWhat to do about it.Numbered priorities with cited detail
Enforcement PrioritiesWhere regulators are leaning.Per-regulator enforcement posture
Watch ListOn our radar.Early-stage developments worth tracking

Panels only render when the scan produced their content — a narrow scan may legitimately show fewer of them.

The agenda — reading a deadline row

Each row carries a coloured square for nearness (red within ~30 days, ochre within ~9 months, green beyond, grey once past), the jurisdiction, the deadline itself, its date in DD-MM-YYYY, and a status: T-45d (45 days to go), PAST, or TBD when no date is confirmed. Under each row a thin track fills as the deadline approaches — a full track means it is on top of you.

Rows that match an item in the scan are clickable and open that item in the detail panel. Rows without a matching item are informational only.

Where regulators are leaning

Enforcement rows are grouped by regulator and carry a trend chip: Intensifying, New Focus or Steady. Like the Focus panel, the detail sentences carry citation markers you can inspect.

The pressure heatmap — At a glance.

The heatmap crosses what the product labels your scan’s topics (rows) — its areas, custom topics included — against its jurisdictions (columns). Each cell prints a pressure score out of 10; the colour bands read:

BandScore
LOW0–4
ELEVATED5–7
CRITICAL8–10

The score is not a count. It is a severity-weighted average of the items in that cell: an item counts for more the higher its impact and the firmer its likelihood, normalised to /10. One confirmed high-impact item can outscore five uncertain low-impact ones — deliberately. The item count survives in the cell’s tooltip.

Around the grid: each row ends in a Σ total, a Σ row totals each column, and the side rail lists the top three Peak Cells. Click any populated cell to open its items in the detail panel; empty cells print .

The heatmap recomputes from the current filters. If you have narrowed Likelihood to Confirmed only, scores drop and cells empty — check the filter chips (or press R to reset) before concluding an area has gone quiet.

The item-detail panel

Clicking a heat cell, an agenda row (or, elsewhere, a Timeline chip or a Sources title) slides in the shared Item Detail panel: the area · jurisdiction pairing in the header, an item count, the scan date, and one card per item.

Each card shows:

  • Title, plus status / likelihood / impact badges.
  • A sourcing-confidence chip where the scan assessed one — Primary regulator source, Supranational body or Secondary commentary (see Sources for what these mean).
  • “Underpins N editorial claims” — when the citation audit tied this item to sentences in the summary or narrative.
  • An instrument chip when the item is bound to a tracked instrument — clicking it jumps to the Change Monitor focused on that instrument (below).
  • Regulator, expected date (DD-MM-YYYY, or TBD), tags, and the summary with its own citation markers.
  • View source → when the item carries a source URL.

Close with × or Esc. On mobile the panel is a full-screen sheet.

The Change Monitor — What’s changed.

Below the heatmap sits the Change Monitor: the panel that compares the loaded scan against your previous scan of the identical scope. The header tells you the gap (“compared with your scan 7 days earlier”); the body separates what it can prove from what it merely observed:

  • Confirmed events — the only things allowed to headline. Each row is a typed regulator event (Consultation opened, Consultation closed, Rules adopted, Date set or moved, Guidance issued, Enforcement, Regulator activity) with the regulator, the document date and a link to the document itself.
  • Coverage movements (collapsed by default) — composition, not change: items newly observed this run (some of which were in force before your window — newly shown, not new), and items not shown this run with how often they have surfaced before.
  • Unverified assertions — things this scan asserted without a verifiable dated document. Visible, never headline-grade.
  • When nothing confirmed happened, the panel says so and lists what the regulators did publish in the window — an affirmative null, not an empty box.

The comparison needs a baseline. On the first-ever run of a configuration the panel says: “No historic identical scan — nothing to compare against. Re-run this configuration to track change over time.” Re-running the same scope — by hand from Snapshots (↻ Re-Scan) or on a timetable via Scheduled scans — is what builds the series the comparison reads from. The full model of what counts as a change lives at Changes between scans.

“Identical scope” is strict: the same jurisdictions, topic areas and custom topics. Add one topic and you have started a new series — the next Change Monitor will have no baseline until that new scope has run twice. If you meant to widen your coverage permanently, accept the one-scan reset; if you only wanted a one-off look, run it as a separate scan and keep your recurring scope untouched.

Worked example: from cell to source in four clicks

Say your scan covers Digital Assets / Crypto and Operational Resilience across the EU and UK, and the EU × Digital Assets / Crypto cell prints 8.

  1. The cell is CRITICAL band. Hover: “score 8/10, 4 items” — high severity, modest volume.
  2. Click the cell. The detail panel opens with the four items; one is Confirmed · High with a Primary regulator source chip and “Underpins 3 editorial claims”.
  3. Read its summary; tap a citation marker to see the backing source, then View source → to open the regulator’s own document.
  4. Back on the Overview, the agenda shows the same instrument with T-62d — it has a compliance date inside your horizon. That is your finding: confirmed, high-impact, dated, and primary-sourced.

A non-obvious tip

The Change Monitor’s instrument focus is reachable from anywhere the detail panel opens. If a colleague asks “has anything actually happened on DORA since last month?”, open any DORA item’s detail card and click its instrument chip — the app jumps to the Overview with the Change Monitor open, filtered to that instrument’s confirmed events, each with its document link. It is the fastest evidence-backed answer in the app.

Where next

  • Briefing — the same scan as a narrative, with audio.
  • Timeline — the agenda’s dates plotted on a horizon.
  • Sources — the audit trail behind every chip and marker you saw here.
  • Changes between scans — the concepts behind the Change Monitor.
Last updated on