Scheduled scans

A scheduled scan is a scan configuration on a rota: it runs itself — every Monday at 09:00, weekdays at 06:00, the 1st of the month — and each run lands as a fresh snapshot, exactly as if you had pressed Start scan yourself. This is how Regulatory Snapshot goes from a tool you remember to open to a briefing that is there when you arrive.

You reach it from More ▸ Scheduled in the navigation. The page is the Planner — a calendar-first view of everything on the rota — plus a builder for creating and editing schedules.

The Planner at a glance

Zone	What it shows
Month calendar	Mon-first grid; each schedule projects colour-coded pills onto the days it will run. Past days are faded, today is ringed. Click a day to see exactly what ran, or will run, and when.
Next-run hero	The single next thing due across all enabled schedules, with a relative countdown and a Run now → button. Shows “Nothing due.” when the rota is empty or paused.
Schedule manager	One row per schedule: an enable/pause toggle, its cadence and next-run line, last-successful-run date, and a kebab menu with Edit, Run now, and a two-step Delete (“Tap again to confirm” — there is no undo). A dashed New recurring sweep row starts the builder.
Recent activity	A feed of past runs, newest first, including runs the scheduler made up after downtime (labelled as catch-up runs).

Run now is worth internalising: any schedule can be fired immediately, off-rota, without touching its cadence. It is the quickest way to test a new schedule end to end.

Creating a schedule

Open New recurring sweep. The builder has two columns — timing on the left, configuration and delivery on the right.

Name, cadence, and time

Name it something you will recognise in a list (“EU Crypto & AML Weekly”).
Cadence presets cover the common rhythms: Every day · Weekdays · Mon + Thu · M-W-F · Weekly (Mon) · Fortnightly · Monthly (1st) · Monthly (1st + 15th). Or ignore the presets and toggle the day circles (M T W T F S S) directly.
Time is local, 24-hour, with quick-pick chips for 06:00, 08:00, 12:00, and 17:00.

A preview line keeps translating your choices into plain language (“Every Monday at 9:00 AM”) with the concrete next run stamped beneath it — if the preview reads wrong, the schedule is wrong.

Configuration source

Every run needs a scan configuration. Two options:

Current dashboard scan — the schedule reuses whatever configuration produced the scan you currently have loaded. The card shows its areas and jurisdictions so you can confirm it is the one you mean.
Custom configuration — an inline mini order form: jurisdiction chips, entity types, regulatory areas, an engine selector, an analysis-model choice, a horizon (6/12/18/24 months), and — for engines that support it — a Batch mode (≈50% off) checkbox. Selecting Custom pre-fills from the current dashboard scan, so you usually only nudge one or two chips.

Scheduled runs default to the batch lane where the engine allows it: unattended scans rarely need live progress, and batch costs roughly half.

Delivery

Email when a run completes — one toggle. Batch runs deliver by email on completion, so a Monday-morning schedule with this on means the briefing is in your inbox before you open the app. Either way, every run also appears in My Snapshots and in Recent scans on the order form.

Press Save schedule. It appears in the manager, projects onto the calendar, and the next-run hero updates if it is now the soonest thing due.

A concrete rota

The classic setup for a compliance team watching EMEA:

On the order form, build and run the scan once — EMEA preset, your areas, 12-month horizon — and check the result reads right.
More ▸ Scheduled ▸ New recurring sweep — name it, preset Weekly (Mon), time 08:00, source Current dashboard scan, email on completion on. Save.
Press Run now once from the kebab to confirm the whole loop — run, snapshot, email — behaves before Monday does it unattended.

Pitfalls

Pausing is not deleting. The row toggle pauses a schedule (its pills leave the calendar’s future); Delete removes it permanently after the “Tap again to confirm” second tap. There is no undo on Delete.
“Current dashboard scan” is captured, not live. The schedule stores the configuration as it was when you saved. Changing your dashboard scan later does not silently retune the schedule — edit the schedule if you want it to follow.
Times are local. The time field follows your device’s timezone. A schedule built at 08:00 in London runs at 08:00 London time, not UTC.
Missed windows become catch-up runs. If the service was down over a scheduled slot, the run may be made up afterwards and labelled as a catch-up in the activity feed — expect the odd off-schedule timestamp rather than a silent gap.

Tip — the order form’s ticket has a one-tap “Make this a weekly scan” shortcut with a fine-grained control → Scheduled scans link. Start there when the scan you have just built is the one you want weekly; come here when you need any other cadence, custom configuration, or delivery control.

Where next

Your first scan — build the configuration a schedule will reuse.
My Snapshots — where every scheduled run accumulates.
/v1 scans API — trigger and fetch scans programmatically instead.