W45 – Route human reviews to specific decision pools
A decision pool is a named group of reviewers who check a localization engine's translations during human review. A pool can be your own team, reviewers from your agency, or professional translators. One localization engine can now send each language and folder to a different pool.
Send different content to different reviewers#
You could already limit human review to selected languages and to translations below a quality threshold. Decision pools choose where those reviews go. For example, one localization engine can be set up so that:
- German content under
docs/legalgoes to your legal reviewers. - Other German content goes to your German-speaking team.
- Portuguese goes to reviewers from your existing agency.
- All other languages go to professional external review.
A decision pool can be of two types:
- Internal pools are for your team and your agency's reviewers. Members get an email when reviews in their languages are waiting. In Queue, they approve the translation or edit it and approve, and the localization job continues. To include an agency, invite its reviewers to your organization and add them to a pool. Only pool members get the email, but the review isn't reserved for them: anyone whose role has the Review translations permission can approve it in Queue.
- External pools send reviews to professional translators, and the reviewed text returns to the localization job. Use Lingo.dev external review, billed per word through your Lingo.dev plan, or connect your BLEND account under Settings → Integrations and be billed by BLEND directly.
Set up decision pools#
- Create pools under Settings → Decision pools.
- In the localization engine's Pipeline tab, open the Human review step and choose the languages and directories each pool covers.
- Translations in a language or folder that no pool covers skip human review. To send every translation to review, add a pool with Any language and Any directory selected.
Reviews that nobody decides before the step's timeout continue with the translation they were given.
Decision pools work with human review on the Enterprise plan. See the Decision Pools documentation for routing rules, permissions, and costs.
The legacy CLI doesn’t support all the features of the new CLI, including your engine’s configured localization pipeline. Reach out to the Lingo.dev team for help migrating.