# Regulatory Change Impact Assessment - TheAICommand skill file

Name: Regulatory Change Impact Assessment
Version: 1.0
Date: 2026-08-15
Source: https://theaicommand.com/library/skills
Article: https://theaicommand.com/grc/reg-change-impact-assessment-skill-file
Platforms: ChatGPT (Skills or a project), Claude (skills or project instructions), Microsoft 365 Copilot (Agent Builder)
Tested against: Claude Fable 5 (Anthropic), 15 August 2026 - pass. All other platforms: not yet tested.
Changelog:
- v1.0 (2026-08-15): Initial library release. Extracted from the published article.
Licence: Free to use and adapt internally. Attribution appreciated. No warranty. Educational purposes only.
Disclaimer: General information and education only. Not legal, compliance, financial, or professional advice.

---

# Skill: Regulatory Change Impact Assessment

## Purpose
Turns a regulator release (letter, standard, guidance or consultation paper) into a
structured draft impact assessment for [ORGANISATION]. The output is a draft for a
human obligation owner to validate, never a final compliance position.

## When to use
Use when a new regulator release needs a first-pass impact assessment. Do not use
for legal interpretation or for drafting submissions. If the full release text has
not been supplied, stop and ask for it.

## Inputs required
- The release, pasted or uploaded in full: [RELEASE_TEXT]
- Release name and date: [RELEASE_NAME], [RELEASE_DATE]
- Organisation context file (business lines, licence types, obligation register
  categories, control framework names): [ORG_CONTEXT]
- Date of this assessment: [DATE_CHECKED]

## Method
1. Summarise the change in plain language, including who it applies to and any
   dates or deadlines stated in the release.
2. Identify which obligation register categories in [ORG_CONTEXT] the release
   touches. List only categories supported by the release text.
3. Map each affected obligation to the impacted control categories in [ORG_CONTEXT].
4. Classify each affected area as exactly one of: no impact, monitor, or change
   required, with a one-sentence reason.
5. Draft actions for every area classified monitor or change required. Mark all
   owners TBD.
6. Cite the release section, paragraph or page for every claim in steps 1 to 5.
   If a claim cannot be cited, delete it and record the gap instead.

## Output format
Exactly these sections, in order: Change summary / Affected obligations /
Impacted controls / Gap assessment / Draft actions / Sources. Stamp the header:
DRAFT. Assessed against [RELEASE_NAME] dated [RELEASE_DATE]. Checked
[DATE_CHECKED]. Requires human validation before any register entry.

## Guardrails
- Every statement must be traceable to the release text. Never fill gaps with
  general knowledge of the regulator or of other releases.
- No legal conclusions. Describe what the release says, never what the law requires.
- Nothing enters the obligations register, a risk system or a board paper until a
  human obligation owner validates it.
- If the release appears incomplete, superseded or unclear, say so and stop.
- Keep the draft stamp on every version of the output.