- Using SafetyCulture
- Templates (managing)
- Manage multi-language templates
Manage multi-language templates
Localize your multilingual team's inspection experience by managing template translations.
How does a multi-language template work?
We understand that for a global organization, your staff might come from different backgrounds and speak different languages. With SafetyCulture, you can localize the inspection experience by adding translations to your templates, so your team members can do their work in a language they're comfortable with.
Take a look at this example of an inspection being started in English and Spanish using the same template:
What you'll need
This feature is currently in Early Access. If you're interested, please contact our customer support team or your customer success manager to check if your organization is eligible.
1. Download translations from a template
Select Templates from the menu on the left-hand side.
Click
on the template's right-hand side and select 
Translate template.In the pop-up window, click Download CSV and open the downloaded file.
If you want to update a template for all languages, please make sure to update it in the template editor first. Then, follow the manage multi-language templates instructions to update the translations.
2. Prepare translations
In the CSV file, you'll find that supported web app languages are visible as column headers.
As there's no way to determine the template's original language, copy the labels in the "default" column to the column of the language that it's in.
Add each label's translations for each language you want to support.
Save your changes.
If you want to add translations for languages outside of what's supported on the web app, you'll need to add additional columns and use groups to show these translations to your users.
Insert a new column and enter the language tag as the column header. For example, for Chinese (Simplified), use "zh-CN".
Add each label's translations for each language you want to support.
To show the relevant language for your users, create a group and add its "Group ID" to the language's "fallback_identifiers" row.
Save your changes.
3. Upload translations to a template
Go back to the web app.
In the pop-up window, upload your translation CSV file.
Click Publish template.
4. Conduct inspections
Now that your template is ready to be used in different languages, you can give template access to your team for them to start inspections.
Remember that translations are shown based on each user's language setting for the web app. Not the mobile app. If you have groups created for additional languages, make sure to add users to those groups for them to see their relevant languages in inspections.
5. View and export as reports
Once your team completes their inspections, they can also view the inspections as web reports in their preferred language or export them as a PDF or Word file.
Currently, only languages supported on the web app are available when viewing and exporting multi-language reports.
Limitations
Responses for questions using Global Response Sets, Sites, and Assets can't be translated.
Media attachments can't be translated.
Multi-language is not supported for exporting inspections as CSV or Excel.
Multi-language is not available in Analytics for response breakdowns and question filters.
Was this page helpful?
Thank you for letting us know.