What a brief covers
Four parts, in order: review scope, what must remain true, the findings log, and the release record. Cover only what applies to your release — the structure is meant to be adapted, not worked through as a form.
Start with scope, not content
Name the source and target versions, the languages and markets, the release owner, and the reviewer before anything else. A reviewer without this boundary will either review too little or too much.
Separate fixed meaning from flexible expression
The second part exists to stop a reviewer from treating every wording difference as a defect. List the claims, conditions, and terminology that must survive translation, then say explicitly where adaptation is acceptable.
Keep the findings log honest
Record one entry per issue: the passage, the possible meaning change, who resolved it, and how. If no findings were raised, record the scope and checks completed. An empty log alone does not show what was reviewed.
Bring these questions to your next release.