Regulatory Change Impact Assessment Planner

Assess how a new regulation affects teams, policies, products, vendors, timelines, and operational risk.

Prompt Template

You are a compliance operations advisor helping a business respond to a new regulatory change. Build an impact assessment and readiness plan.

**Regulation or policy change:** [name and short description]
**Jurisdiction:** [country/region/state]
**Effective date:** [date]
**Business type:** [SaaS / ecommerce / healthcare / fintech / agency / marketplace / other]
**Products/services affected:** [list]
**Current compliance posture:** [unknown / partially compliant / audited / certified]
**Teams involved:** [legal, product, engineering, finance, support, sales, HR, vendors]
**Known gaps or concerns:** [data handling, disclosures, contracts, reporting, training]
**Risk tolerance:** [low / medium / high]
**Resources available:** [budget, owners, outside counsel, timeline]

Create:
1. **Executive summary** — what changed, why it matters, and deadline pressure.
2. **Applicability check** — assumptions, affected entities, exemptions to verify, and legal questions to ask counsel.
3. **Impact matrix** — business area, requirement, current state, gap, severity, owner, due date.
4. **Readiness roadmap** — phases from discovery to implementation to audit evidence.
5. **Policy/process updates** — documents, customer-facing disclosures, internal SOPs, vendor contracts, and training needed.
6. **Product/technical changes** — data, reporting, consent, retention, audit logging, UI copy, or workflow updates.
7. **Stakeholder communication plan** — internal update, customer notice, vendor request, and board/executive summary.
8. **Evidence checklist** — artifacts to retain for audit or regulator questions.
9. **Risk register** — top risks, mitigation, contingency, and escalation triggers.
10. **30/60/90-day plan** — concrete actions by owner.

Do not provide legal advice; clearly mark items that require qualified legal review.

Example Output

Executive Summary

The EU Digital Operational Resilience Act (DORA) introduces stricter ICT risk, incident reporting, and third-party oversight expectations for financial entities and key technology providers. Our fintech reporting platform may be indirectly affected through customer contract obligations and vendor risk reviews. The priority is to confirm applicability, map customer obligations, and prepare evidence before procurement renewals begin in Q3.

Impact Matrix

| Area | Requirement | Current State | Gap | Severity | Owner | Due |

|---|---|---|---|---|---|---|

| Vendor management | ICT provider register | Vendor list exists in finance sheet | Missing risk tier and contract clauses | High | Ops | May 15 |

| Incident reporting | Faster incident classification | Security incidents tracked in Jira | No regulatory severity mapping | High | Security | May 30 |

| Customer contracts | Resilience commitments | Ad hoc security exhibit | DORA-ready addendum needed | Medium | Legal | Jun 10 |

30/60/90-Day Plan

**30 days:** Confirm applicability with counsel, appoint DORA owner, inventory ICT vendors.

**60 days:** Update incident classification workflow, draft customer FAQ, begin contract addendum review.

**90 days:** Run tabletop exercise, collect evidence pack, brief leadership on residual risk.

Tips for Best Results

  • 💡Separate applicability questions from implementation tasks so legal uncertainty does not stall obvious prep work.
  • 💡Regulatory changes usually create vendor and contract work, not just policy work.
  • 💡Create an evidence folder from day one; proving readiness later is much harder than collecting artifacts as you go.
  • 💡Use severity and effective date together — low-effort/high-deadline gaps should move first.