---
name: regulatory-change-brief
description: Summarizes supplied regulatory updates and maps each change to affected policies, processes, data, contracts, controls, owners, and implementation dates. Use for compliance monitoring, obligation tracking, impact assessment, regulatory briefs, or change registers.
license: Apache-2.0
metadata:
  adlass.categories: "legal-compliance/regulatory-monitoring"
  adlass.industries: ""
  adlass.tags: "regulatory-update,impact,compliance,obligations,change-tracker,monitoring"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Regulatory change brief

## Purpose

Convert supplied regulatory notices and internal compliance materials into a source-cited change register and an impact brief for the responsible owners.

## Scope

Extract effective dates, transitional dates, scope, defined terms, obligations, prohibitions, reporting duties, recordkeeping requirements, and enforcement language, then map each obligation to internal policies, processes, data, contracts, and controls.

**Excluded:** jurisdiction-specific legal advice, a conclusion that the company is compliant, contacting regulators, and changing policies or controls.

## Data basis

- Official notice, rule, guidance, consultation, or supplied regulatory summary.
- Internal policy library, control register, process maps, data inventory, contract register, and prior change assessments.
- Company applicability statement and compliance calendar.

## Result

A brief for decision owners and an obligation tracker with source quote, effective date, applicability, impacted asset, gap, owner, priority, and open question.

## Quality criteria

- Each obligation cites article, section, page, or paragraph in the supplied source.
- Effective, compliance, and transition dates are not conflated.
- Applicability is “confirmed”, “possible”, or “not assessed” with its basis.
- A mapped control is not called effective unless the source provides evidence.
- Overlapping changes retain separate source rows and relationships.

## Instructions

Read definitions and scope before extracting duties. Separate mandatory wording from explanatory examples. Use the internal applicability statement before assuming a process is affected. Record date conflicts verbatim and flag them for legal review. Map one obligation to multiple policies or controls with separate rows. Prioritize only with the supplied severity rule; otherwise show impact dimensions without a numeric score.

## Adapt before use

The tracker records an assessment trail; it is not a substitute for counsel’s interpretation of the supplied source.

- Add the regulatory source, internal policy library, control register, and applicability statement.
- Map obligation, policy, process, data, contract, owner, and due-date fields.
- Define priority labels, escalation roles, legal-review boundary, and compliance-calendar conventions.