# Editorial Policy Change Log

Record policy revisions, rationale, authority, affected workflows, migration work, communication, training, effective dates, and evidence of adoption.

## Usage note

Create a log entry for every approved change that alters an obligation, decision right, definition, exception path, or operating control. Preserve prior versions and effective dates. This record supplements the policy; it does not replace clear current text, formal approval, or targeted communication to people whose work changes.

## How to use this template

1. Identify the approved policy, previous version, exact clauses changed, and evidence motivating the revision.
2. Summarize substantive additions, removals, and meaning changes in language affected contributors can understand.
3. Map dependent workflows, systems, templates, training, contracts, and in-progress work.
4. Record approval, version, effective date, migration owners, communication, and any transition rule before release.
5. Verify adoption with real work and retire obsolete guidance, then append outcomes and future review triggers.

## Blank template

### Change identity

- **Policy title:** [Official name]
- **Policy owner:** [Accountable role]
- **Previous version:** [Version and effective date]
- **New version:** [Version and effective date]
- **Approval date:** [YYYY-MM-DD]
- **Approver:** [Name and authority]
- **Change entry ID:** [Durable identifier]
- **Authoritative policy URL:** [Current source]
- **Archived version location:** [Protected history]

### Rationale and decision

- **Trigger:** [Incident, evidence, law, repeated exception, or another reason]
- **Problem with previous rule:** [Describe observed effect]
- **Clause changed:** [Section reference]
- **Meaning before:** [Plain-language summary]
- **Meaning now:** [Plain-language summary]
- **Alternatives considered:** [Options and reasons]
- **Decision rationale:** [Why this change is proportionate]
- **Unresolved question:** [Owner and resolution date]

### Impact and rollout

- **Affected roles:** [Who works differently?]
- **Affected content:** [Channels, regions, products, and in-flight work]
- **Dependent documents:** [RACI, templates, briefs, and procedures]
- **System changes:** [Forms, permissions, automation, or reports]
- **Training or acknowledgment:** [Method and audience]
- **Transition rule:** [Which version applies during migration?]
- **Migration owner:** [Role and date]
- [ ] Required pre-effective-date changes are complete.
- [ ] Obsolete links and copies have retirement owners.
- [ ] Emergency and exception paths reflect the new rule.

### Adoption review

- **Communication record:** [Audience, channel, and date]
- **Understanding check:** [Scenario, acknowledgment, or assessment]
- **Work sampled:** [Items and result]
- **Questions or exceptions:** [Pattern observed]
- **Corrective action:** [Owner and date]
- **Next policy review:** [YYYY-MM-DD or event]