---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Requesting translations in Localization Workspace

# Requesting translations in Localization Workspace {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Requesting translations in Localization Workspace

Localization Workspace enables you to create and submit translation requests for various content types into multiple languages through a single interface.
You can save, modify, and submit translation requests, which then generate and package a project in Localization Framework.
Once packaged, the request is sent to your third-party translation service provider.
From version 3.0.0 onward, you can cancel translation requests post-submission but must notify the provider directly, as Localization Workspace does not handle cancellations with them.
Show full answer Show less  

## Creating Translation Requests

* **Languages:** Select target languages or language groups for translation.
* **Types:** Choose multiple content types from across your instance. The system retrieves all translatable documents for the selected types.
* **Scope:** Select or deselect specific documents per language from the retrieved content list.
* **Estimate and Due Date:** Generate an informational cost estimate to aid budget planning and optionally set a due date before submitting the request.

## Tracking and Managing Requests

All saved or submitted translation requests appear on the Localization Workspace home screen under **My Requests**. From there, you can edit, archive, or cancel requests. Due dates are suggested based on the type of service provider and can be accepted or adjusted using a calendar picker, with restrictions preventing dates earlier than the suggested due date.

## Due Date Calculation

Localization Workspace uses an industry-standard formula for intelligent due date suggestions when submitting requests through a Translation Management System (TMS):

* **For word-based languages:** Divide total word count by 1,500, add 2 days, then add to the current date.
* **For character-based languages:** Divide total character count by 15,000, add 2 days, then add to the current date.

Note that the system shows word counts during estimation, but uses character counts for due date calculations if the language is character-based. When translating into multiple languages concurrently, the language with the highest word or character count determines the due date. For machine translation providers, the default due date is the current date. Due dates in Localization Workspace align with those in Localization Framework projects.

## Practical Example

If the total word count is 62,453, the due date calculation is:

* 62,453 ÷ 1,500 = 41.6 (truncated to 41)
* 41 + 2 = 43 days
* The suggested due date is 43 days from the current date.  
Create and submit translation requests in Localization Workspace. Generate informational cost estimates for review and set a due date before submitting the request.

## Overview of creating translation requests {#requesting-translations-localization-workspace__cf-using-parent-workflow}

As a localization requester, you can create translation requests for multiple content types into multiple languages, all in one interface.  
You can save or modify a translation request before submitting it. When you submit the translation request, Localization Workspace creates and packages a project in [Localization Framework](https://www.servicenow.com/docs/e_WbB6fnk~E43boBQ1BSmQ "The ServiceNow Localization Framework application standardizes and enhances the translation process of artifacts across the platform through configurable workflows. Such artifacts include ServiceNow Service Catalog items, Virtual Agent topics, Natural Language Understanding models, and Document Templates of ServiceNow HR Service Delivery."). Creating the project might take several minutes depending on the number of documents. When the project is ready, Localization Workspace sends the translation request to your third-party service provider.  
Note:  
From version 3.0.0, you can cancel a [TMS](https://www.servicenow.com/docs/I2obvAhtW__oPncH5m5kvA "The Localization Framework supports integration with a translation management system to localize the content.") translation request after submitting it. However, Localization Workspace does not contact your service provider. You should notify your provider directly regarding any cancellations.

On the Localization Workspace home page, the Request Translation button opens a wizard displaying a four-step process.

1. [Request translations in Localization Workspace: Languages](https://www.servicenow.com/docs/id0eb4U1R~hYcsLPfbMoRQ "Add target languages to a translation request in Localization Workspace.")

   Start a translation request by selecting available target languages or language groups.
2. [Request translations in Localization Workspace: Types](https://www.servicenow.com/docs/XS5U7AYeLmbUWN~E11oIRA "Add content types to a translation request in Localization Workspace. Your translation request can include multiple types of documents from tables across your instance.")

   Add content types to a translation request. You can select multiple types of documents from tables across your instance. The system retrieves all available translatable documents for
   each selected content type.
3. [Request translations in Localization Workspace: Scope](https://www.servicenow.com/docs/a4POCiRvnXfmMFZvAIx5SA "Select specific documents to add to a translation request in Localization Workspace.")

   Select or deselect specific documents from the retrieved list of content. Different documents can be selected for each language in the request.
4. [Request translations in Localization Workspace: Estimate and Due Date](https://www.servicenow.com/docs/7_1BSHDxyq7Vi5yrn17DXg "As the final step in creating a translation request, you can review an informational cost estimate and optionally set a due date. The due date can be used to trigger email notifications.")

   Generate an informational cost estimate as the last step in the Request Translation wizard. Review the estimate to plan and control your localization budget. Optionally add a due date for the request.
{#requesting-translations-localization-workspace__cf-using-parent-steps-ol}

## Tracking translation requests {#requesting-translations-localization-workspace__section_is3_1cj_g3c}

When you save or submit a translation request, its record is displayed on the Home screen of Localization Workspace in the My Requests list. You can edit, archive, or cancel a translation request from My Requests. For more information, see [Localization Workspace Home and translation job status](https://www.servicenow.com/docs/6ayIyYKcv2L0RsTJAh2HmQ "Start a translation request and monitor the current status of your translation requests from the Localization Workspace Home screen.").

## Translation request due dates {#requesting-translations-localization-workspace__section_pxt_npv_33c}

In the Estimate step of a translation request, the system suggests due dates based on the type of service provider. You can optionally accept the suggested due date, or you can use the calendar picker to choose another date. You
can't choose a date that is earlier than the suggested date, however.  
From version 3.0.0, intelligent due dates are offered when requests are submitted through a [TMS](https://www.servicenow.com/docs/I2obvAhtW__oPncH5m5kvA "The Localization Framework supports integration with a translation management system to localize the content."). Localization Workspace suggests a due date based on the target language's word or character count, using the following industry-standard formula.{#requesting-translations-localization-workspace__table_hjz_5hc_j3c__entry__2}

| Target language type | Formula used |
|-|-|
| Words | Divide the total word count by 1500. Then add 2. The result is the expected number of days to complete the translation. Add that number to the current date. |
| Characters | Divide the total character count by 15,000. Then add 2. The result is the expected number of days to complete the translation. Add that number to the current date. |
[Table 1. Due Date formula]

{#requesting-translations-localization-workspace__table_hjz_5hc_j3c}  
Note:  
The Estimate step of a translation request displays Word counts, not Character counts, even when the target language has been configured as character-based. However, the intelligent due date suggestion uses the Characters formula for languages configured as character-based.

When using a TMS to translate into multiple target languages in one request, the formula assumes that the languages are processed concurrently, not sequentially. This means that the language with the highest word or character count
is used to calculate the due date suggestion.

For machine translation service providers, the default due date is the current date. Due dates in Localization Workspace correspond to the Localization Framework Project due dates.  

## Due date calculation for a TMS request {#requesting-translations-localization-workspace__example_xmj_2hc_j3c}

The following example illustrates the due date calculation when the word count is 62,453.

1. Divide the word count by 1500.62453 / 1500 = 41.6.

2. Truncate (round down or take the floor) to the nearest whole integer.41.6 becomes 41.

3. Add 2 days.41 + 2 = 43.

4. Add the number of days to the current date. The suggested due date is 43 days from the current date.

{#requesting-translations-localization-workspace__ol_omc_c1b_l3c}