Horizon scanning
Track regulatory movement in your sector with implications attached, not just headlines.
— Risk & Compliance
Researches regulatory change in a defined area, classifies the findings, and states the implications for your specific business context.
1 day → ~10 minutes
Including the external research pass
No coding required
— USE CASES
Track regulatory movement in your sector with implications attached, not just headlines.
Scan the same question across markets and see where obligations differ.
Re-run the scan each quarter so change is visible against the last position.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Risks are sorted into your categories using the same rules each time, which is what makes a large volume of risk, control and policy documentation readable.
Your strategy, standards and prior work are loaded first, so conclusions about the risk universe in scope are anchored to your situation.
Current external sources on the risk universe in scope are researched during the run rather than recalled from training data, and every source travels with the output.
In risk & compliance work, regulation scan is one of those tasks that looks straightforward until you are three documents deep and the details stop agreeing with each other. Horizon scanning is the typical trigger — track regulatory movement in your sector with implications attached, not just headlines. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 1 day of manual work.
Here the same job runs as a Skill. Your material goes in; classified regulatory changes with sources comes out, alongside implications for your context. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. The practical effect: 1 day of manual work becomes a ~10 minutes run, held to an identical standard on the tenth engagement as on the first.
Regulation scan exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a data subject access request end to end and returns a governed decision on whether to fulfil it, fulfil it in part, refuse it with reasons or extend the deadline, having verified identity, mapped the request to the systems that actually hold the data and held the outcome for a data protection sign-off before anything is disclosed.
Fans multiple audit or review reports into individual findings, deduplicates repeats, and sorts them by severity into one consolidated register with sources retained.
Pairs a full evidence set against every audit assertion or PBC item to produce a coverage matrix, naming the assertions nothing supports and the documents supporting nothing.
Reads a submitted claim against the policy wording that governs it and returns a coverage assessment showing whether it appears covered, potentially excluded or in need of specialist review, mapped clause by clause and never issued without a handler's sign-off.
Assesses a reported incident against your response playbook and policies, assigns the severity band the evidence supports, and returns the matching response plan with the notifications, owners and timelines that band requires.
Assesses personal-data processing and cross-border transfers against privacy policy and jurisdiction rules, producing a documented approval outcome with conditions, policy evidence and grounds for referral.