Skip to main content
A good handoff identifies the content, the reviewer, and the release it belongs to. Use project access and a reproducible queue filter so reviewers know exactly what to inspect.

​
Prepare the batch

  1. Finish source uploads and generation for the intended release.
  2. Confirm the target locales and source paths.
  3. Invite reviewers and give them access to the project through the appropriate team.
  4. Share the guideline, glossary, and relevant product context.
  5. Record which reviewer owns each locale or file.
Use roles and permissions to distinguish drafting from approval. A translator can prepare target text; approval requires an authorized role.

​
Review in Platform

Open the Content Editor, select the locale, and start with Needs review. Check Untranslated and Has issues separately so a narrow review filter does not hide missing work. Use Board for unresolved product or terminology decisions. For repeated source text, project settings can group exact duplicates. Inspect context before choosing shared wording: identical source text can serve different purposes in different screens.

​
Hand off a spreadsheet

Export the filtered queue as XLSX or CSV when a collaborator needs an offline reference. Record the source revision, locale, and filters with the export. Split batches larger than 5,000 matching segments. A spreadsheet export is a review artifact. It does not itself apply edits or approvals back to Platform. Have an authorized reviewer apply agreed changes in the editor and verify the final saved result.

​
Complete the release

Resolve outstanding issues, check untranslated strings, and download full target files. Test representative screens, long labels, and placeholder substitutions in the application. Keep the reviewed source revision with the delivered files so later source changes are easy to identify.