Skip to main content
MethodLegal, Risk & ComplianceContracts & regulationIntermediate

Map the regulations that apply to your business

A map of laws, regulators, licences and upcoming rule changes relevant to a product in a jurisdiction.

This is a practical, copy-paste process for launching in a regulated area (finance, health, ai, food, data).. Use it when you want a clear structure, then add your own details and the linked evidence.

Published by Deepstory Research. Reviewed Sep 2026.

How to use this method

  1. 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
  2. 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
  3. 3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.

The prompt

Paste it as-is. The AI will ask for anything still in [BRACKETS].

Download .md
# Map the regulations that apply to your business
Method by Deepstory Research: deepstoryresearch.com/method/regulatory-landscape-scan

You are a regulatory-affairs analyst. Follow the method below step by step. Goal: A map of laws, regulators, licences and upcoming rule changes relevant to a product in a jurisdiction.

## My inputs
- Product or activity: [PRODUCT_OR_ACTIVITY]  (example: AI hiring tool)
- Jurisdictions: [JURISDICTIONS]  (example: EU, UAE, India)
- Stage: [STAGE]  (example: pre-launch)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. List applicable regulations and regulators per jurisdiction.
2. Summarise key obligations.
3. Identify licences or registrations.
4. Flag pending changes with dates.
5. Produce a compliance to-do list to verify with counsel.

## Deliver the output in this structure
- Regulation map
- Obligations table
- Licences
- Upcoming changes
- Compliance checklist

## Quality rules
- Cite the law’s name and date; mark anything uncertain.
- Distinguish proposed vs enacted.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

What you need to give the AI

InputPlaceholderExample
Product or activity[PRODUCT_OR_ACTIVITY]AI hiring tool
Jurisdictions[JURISDICTIONS]EU, UAE, India
Stage[STAGE]pre-launch

Use it when

  • Launching in a regulated area (finance, health, AI, food, data).

What you get

  • Regulation map
  • Obligations table
  • Licences
  • Upcoming changes
  • Compliance checklist

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

  1. 1

    List applicable regulations and regulators per jurisdiction.

  2. 2

    Summarise key obligations.

  3. 3

    Identify licences or registrations.

  4. 4

    Flag pending changes with dates.

  5. 5

    Produce a compliance to-do list to verify with counsel.

Quality checks built into the prompt

  • • Cite the law’s name and date; mark anything uncertain.
  • • Distinguish proposed vs enacted.
  • • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].

Evidence to use with this method

Methods tell the AI how to think. Evidence gives it sourced numbers to think with. Download a context file and attach it with the prompt.

Run next

Methods that chain well after this one.

Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.