Snapshots

The Snapshots tab — My Snapshots — is your archive: every scan you have run, grouped by day, with scans still running maturing in place at the top. It is where you load past results back into the dashboard, rename them, re-run them, and — with care — delete them.

It is also where the app’s change-tracking story becomes visible as structure: re-runs of an identical scope fold into a series under their newest scan, and it is exactly those series that give the Change Monitor its baseline.

The masthead shows the archive’s range (OLDEST 03-02-2026 · NEWEST 20-07-2026), and on this tab the ticker strip counts the archive itself: SNAPSHOTS · SERIES · IN FLIGHT · ● LAST SCAN.

In flight

Scans that are still running appear as cards above the ledger:

Live scans show the scan’s title and scope, a Stage x of N tracker with a descriptive phase, a percentage and progress bar, the start time, and a live cost meter.
Batch scans show a steady bar and the promise: “Queued — running in the background, we’ll email you when it’s ready.”

When a scan finishes, its card settles into the ledger below — and the green Scan Ready pill in the top chrome offers to load it from anywhere in the app.

The ledger

The archive is a day-grouped ledger (TODAY — 20-07-2026, YESTERDAY — 19-07-2026, then weekdays), with columns:

Snapshot · Engine · Mode · Cost · Time · Scan ID

Each row carries the snapshot’s title, a Loaded pill when it is the one currently on the dashboard, a ⟳ chip when it was produced by a scheduled sweep, the engine it ran on, a LIVE or BATCH mode pill, its cost, its time, and its mono scan ID.

Click a row to reveal the actions:

Action	What it does
Load to Dashboard	Makes this snapshot the loaded one — every reading tab now shows it
Rename	Inline rename (double-clicking the title does the same)
↻ Re-Scan	Re-runs this snapshot’s exact configuration as a new scan
Delete	Two-step: the button arms to Confirm Delete on first click

Series — re-runs of the same scope

Snapshots that share an identical scope — the same jurisdictions, topic areas and custom topics — fold into one series under their newest scan. A ▸ 4 scans hint under the head row expands the older runs, each prefixed with its DD-MM date. Engines and time horizons may differ within a series; scope is what defines it.

Series are not cosmetic. The Change Monitor compares a scan against the previous scan of the same series; a scope with only one run has no baseline and nothing to compare. The habit that makes the product compound in value is therefore: settle a scope, then ↻ Re-Scan it (or schedule it) rather than composing a fresh scan each time. The full model is at Changes between scans.

Two cautions. Delete is permanent — it removes the snapshot and there is no undo beyond the two-step confirm. And editing scope forks the series: re-running with one extra topic starts a new series with no baseline, so the next Change Monitor will report nothing to compare against. Rename freely — titles are labels and do not affect series identity — but change scope deliberately.

Finding things

Search-by-title is the tab’s only narrowing tool; while active it shows x of n matched. Everything else is chronology — there are no facet filters here, because the archive is a ledger of scans, not a list of items.

Worked example: standing up a weekly series

You have settled on a scope — Digital Assets / Crypto and Operational Resilience, EU + UK, 18 months.

Run it once from the order form and rename the result to something durable: EU/UK crypto & opres — weekly.
The following Monday, open Snapshots, click the row, ↻ Re-Scan. A live card appears at the top, matures, settles into today’s group — and folds under the same series head with ▸ 2 scans.
Load the new run. The Overview’s Change Monitor now reads “compared with your scan 7 days earlier” and lists confirmed events with document links.
When the routine proves out, recreate it as a scheduled scan so the Monday run happens without you; snapshots born from the schedule arrive with the ⟳ chip and join the same series, provided the scope is identical.

A non-obvious tip

Every snapshot is directly addressable: ?snapshot=<id> on the app’s URL loads that snapshot on arrival. Combined with the scan ID pill on each row, that gives you permanent references for filing and sharing — a compliance memo can cite the exact snapshot it was written from, and anyone with access can reopen precisely that state of the world. Snapshots are also first-class API objects — see the Snapshots API.

Where next

Overview → Change Monitor — what a series buys you.
Changes between scans — the comparison model.
Scans and snapshots — the underlying objects.
Studio — turn any archived snapshot into artefacts.