Cross Regulatory Impact Analyzer Patrick Munro
Analyzes how multiple regulations interact for a specific product, service, or business...
Install
npx skills add lawve-ai/awesome-legal-skills --skill cross-regulatory-impact-analyzer-patrick-munro -g -a claude-code -y- Repository
- lawve-ai/awesome-legal-skills919
- Category
- Business
- Updated
- 16d ago
- License
- See repository
- Context cost
- Mediumabout 2,850 tokens
- Runs scripts
- No, instructions only
What it does
Analyzes how multiple regulations interact for a specific product, service, or business model. Identifies where obligations overlap, reinforce, complement, duplicate, or conflict; builds a priority matrix; produces an integrated compliance timeline; and estimates the total compliance burden. Use when (1) scoping a new product or service against the full regulatory landscape before launch, (2) conducting M&A due diligence on a target's multi-regulation exposure, (3) building a strategic compliance roadmap where single-regulation analyses miss the interactions, (4) advising on complex situations where regulations touch the same conduct from different angles, or (5) estimating budget and resourcing for multi-regulation compliance. Primary coverage of EU digital regulation (GDPR, Data Act, AI Act, CRA, NIS2, DORA, DMA, DSA, ePrivacy) and national implementations; the framework extends to any jurisdiction where overlapping regulatory regimes apply to the same activity.
Cross-Regulatory Impact Analyzer
Purpose
Most regulatory analyses treat regulations one at a time. This is fine when a business is subject to one regulation. It stops being fine the moment multiple regulations reach the same activity, because the real compliance questions live in the overlap: which obligation is stricter, which deadline comes first, what satisfies both, and what conflicts. This skill produces the analysis that single-regulation guides do not.
When to use
- New product or service launch where more than one regulation plausibly applies
- M&A due diligence on a target with multi-regulation exposure
- Strategic compliance planning where a siloed, regulation-by-regulation approach has hit its limits
- Complex client advisory on regulatory interactions
- Budget and resourcing estimation for multi-regulation programmes
- Triaging incident response playbooks where multiple reporting regimes trigger simultaneously
Analysis framework
The analysis proceeds in six phases. Each phase produces an output that feeds the next.
Phase 1: Scope determination
Identify which regulations apply based on:
- Product or service type: hardware, software, SaaS, IoT, AI system, platform, financial service
- Sector: financial services, healthcare, critical infrastructure, public sector, consumer, etc.
- Entity size: headcount, revenue, balance sheet (matters for NIS2, DORA size thresholds, SME carve-outs)
- Data processing: personal data types, volumes, special categories
- Geographic scope: EU-wide, specific Member States, third-country targeting
- Risk profile: safety, security, fundamental rights implications
- Designation status: VLOP/VLOSE (DSA), gatekeeper (DMA), critical ICT TPP (DORA), critical entity (NIS2/CER)
Document the inclusion rationale for each regulation. Document the exclusion rationale too, because "we considered X and concluded it does not apply because Y" is half the value of the analysis.
