Halo Translation Process

Overview

This article explains the Halo 360 translation process, including how static and dynamic text is handled, what review steps are required, expected timelines, and how translated content affects email delivery for users and raters.

Translation Workflow

Two categories of translation:

• Static text: UI elements like button labels, alerts (pre-translated by BTS)
• Dynamic text: Survey-specific content like questions, competencies, rating scales

Translation steps:

1. Language request: BTS requests languages needed for the client
2. Language check: Halo team confirms if the language exists in master package
3. Translation:
   • If language exists: AI translates dynamic text only
   • If language is new: AI translates both static + dynamic, followed by manual review
4. Approval & Launch: Reviewers sign off; Halo clears the project for launch

Note: No cohorts can launch until translations are complete and reviewed.

Review & Approval

• Reviewers are given login access to preview translated content live
• Each reviewer receives their own approval login
• Static text edits are handled via Excel, not editable via the platform
• Only static elements listed in Excel are editable

Timeline Estimates

• 4 business days: Initial delivery of logins + Excel
• 1–4 weeks: Review/edit window depending on complexity & language
• 3 business days: Post-approval, time to activate cohort

Translated Email Behaviors

• Default language: Set during upload or first login
• Changing interface language via dropdown also changes default language for emails
• Job Holders: Receive emails in their selected language
• Raters:
  • If new: inherit language from Job Holder
  • If existing: use pre-set system language