Horizon scanning
Track regulatory movement in your sector with implications attached, not just headlines.
— Risk & Compliance
Regulation scan
Researches regulatory change in a defined area, classifies the findings, and states the implications for your specific business context.
- Risk & Compliance
- Traceable reasoning
- Runs anywhere
2–3 days → ~10 minutes
Including the external research pass
No coding required
- Input
- The regulatory area and jurisdictions in scope
- Output
- Classified regulatory changes with sources
- Runs in
- Skillsize · ChatGPT · Claude · Copilot
- Export
- SKILL.md · MCP
- Time saved
- ~2–3 days per run
— USE CASES
What people use Regulation scan for
Jurisdiction comparison
Scan the same question across markets and see where obligations differ.
Periodic compliance updates
Re-run the scan each quarter so change is visible against the last position.
What it works from
- The regulatory area and jurisdictions in scope
- Your business context
- Any classification you want applied
What you get back
- Classified regulatory changes with sources
- Implications for your context
- A repeatable scan for the next cycle
— HOW IT BEHAVES
How Regulation scan produces its result
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Consistent classification
Items are sorted into your categories using the same rules each time, which makes volume readable.
Live external research
Current external sources are researched during the run rather than recalled from training data, and the sources travel with the output.
Synthesis into a deliverable
Findings are pulled together into a written output ready for review.
Why this is expensive by hand
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 2–3 days of manual work.
How this Skill produces it
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: 2–3 days of manual work becomes a ~10 minutes run, held to an identical standard on the tenth engagement as on the first.
Who it's for
- Independent consultants codifying their own methodology
- Strategy and transformation teams standardising delivery
- Internal advisory functions under pressure to produce faster
- Operators who need defensible output, not a one-off chat answer
Run it in Skillsize — or export it anywhere
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.
ChatGPTClaudeCopilotAI Products (MCP)
More Risk & Compliance Skills
Browse the full library →Risk & Compliance
Control gap assessment (SOC 2 / ISO 27001)
Extracts documented controls and framework requirements, then grades every requirement covered, partial or absent for SOC 2 or ISO 27001 readiness.
Risk & Compliance
Audit evidence mapping
Maps an uploaded evidence set against a list of assertions or PBC items to produce a coverage matrix, flagging unsupported assertions and orphaned documents.
Risk & Compliance
RCSA questionnaire → risk register
Runs a scored risk and control self-assessment questionnaire and calculates residual risk identically every time, producing a register comparable across teams and quarters.