# Translation Change Log

Record source changes, affected locales, semantic risk, translation owners, review status, dependencies, release completion, and deferred work.

## Usage note

Create a log entry when a source change affects translated content, even when the source edit appears small. Negation, placeholders, labels, numbers, and conditions can carry high semantic risk. Keep untranslated or stale locales out of publication where the change would mislead users. This log supports coordination but does not replace your translation-management, version-control, QA, or release system.

## How to use this template

1. Capture the source change, version, reason, before/after text, dependencies, and semantic risk.
2. Enumerate active locales and every content or media surface that inherits the meaning.
3. Assign translation, linguistic, functional, subject, and release owners with deadlines.
4. Define safe staging or blocking behavior for incomplete locales.
5. Verify live releases, record deferred work, and update terminology or workflow lessons.

## Blank template

### Source change

- **Change ID:** [Stable identifier]
- **Source locale and version:** [Locale; commit/release]
- **Component or page:** [Location]
- **Before:** [Exact source text]
- **After:** [Exact source text]
- **Reason:** [Correction, feature, policy, style, terminology]
- **Semantic risk:** [Low, medium, high, critical with reason]
- **Related strings/assets:** [IDs and surfaces]
- **Release target:** [Date or version]

### Locale status

- **Target locale:** [Locale code]
- **Translation owner:** [Person or vendor]
- **Status:** [Not started, translating, review, QA, released, deferred]
- **Terminology impact:** [Terms or memory changes]
- **Placeholder/plural risk:** [Details]
- **Linguistic reviewer:** [Owner and decision]
- **Functional/visual QA:** [Owner and result]
- **Subject/compliance review:** [If required]
- **Live verification:** [URL/build and date]

### Release checks

- [ ] Active locales and non-page assets are inventoried.
- [ ] Semantic risk determines review depth.
- [ ] Placeholders, plurals, variables, and formatting remain functional.
- [ ] Mixed-language or stale fallback is handled safely.
- [ ] Deferred locales have explicit status and owner.
- [ ] Live content is checked after deployment.
- [ ] Metadata, schema, sitemaps, and downloads match locale status.
- [ ] Terminology and source guidance capture lessons.