This article walks you through creating a translation project in wxrks, from opening the project wizard to approving the project once it's ready to start.
💡 Who is this for? This guide is for Account Admins and Project Managers who need to create a new translation project within the wxrks platform.
Requirements
Before creating a project, make sure the following already exist in wxrks:
Translation Memory (optional, but recommended if you want to reuse past translations)
Glossary (optional, but recommended for consistent terminology)
1. Create a new project
From the sidebar, click Projects, then New Project.
2. Choose Direct Project or Project Routing
wxrks offers two ways to start a project: Direct Project, for a single Organizational Unit, or Project Routing, which creates multiple projects at once and routes each target language to the right Organizational Unit in a single step.
This article uses Direct Project as the example. To learn more about the other option, see How to use Project Routing in wxrks.
3. Configuration
This is the first step of the project wizard. wxrks pre-fills several fields based on your user and Organizational Unit setup, and you can override any of them.
At the top of the screen, click Import Project Template to upload a previously exported project settings file (JSON) and prefill the form automatically instead of entering everything by hand.
The following fields are required (marked with *):
Organizational Unit - the unit this project will be created under. If you belong to multiple Organizational Units, pick the one where this project should live (this is meant for companies with several units, like departments or cost centers, that need to separate costs, billing, and invoices).
Contact Person - the person who will receive project notifications.
Project Reference - the name you'll use to find this project later. We recommend following your internal naming convention or content codes here.
Source Language - the source language of your uploaded files. All files in a project must share a single source language.
Target Languages - every language you want your files translated into. You can assign different target languages to individual files in a later step.
You may also fill in or override:
Project Manager - the person responsible for the project. This field only appears if your role can assign one.
Project Notes - instructions or guidelines for anyone involved in the project.
Continuous project (toggle) - a project that never closes: files can be re-imported and work is priced per import batch, with no fixed project cost or due date. Also only available to some roles.
Translation Memory - the Translation Memory (or Memories) to use for this project, if you already have one set up. This appears greyed out if your role can't change it, though a default may already be applied.
Glossaries - the Glossary or Glossaries to use for this project's terminology, if any. Same permission behavior as Translation Memory.
Prices - the price list used to calculate this project's costs. wxrks selects the Organizational Unit's default price list automatically when one is set.
Invoice Info - purchase order information for this project's future invoicing.
Click Next once you're done to move to the Upload Files step.
4. Upload Files
Click Browse to select files from your device, or drag and drop them onto the upload area. A Google Drive button also appears here, once wxrks finishes loading the Google Drive integration a moment after the page opens, letting you import files directly from a connected Google Drive account instead.
Wait for every file's progress bar to reach 100% before clicking Next. wxrks accepts a wide range of file formats — see Supported and Unsupported File Extensions for the current full list.
⚠️ Tip: if you handle a lot of content, think ahead about how you want to group files into a project. wxrks lets you send different files to different languages and workflows within the same project, so you may prefer to group files by the workflow, languages, or content type they share, instead of one project per deliverable.
Click a file's row to expand its settings inline — which content should be extracted for translation, how tags and formatting are handled, and other options specific to that file's type. Click the row again to collapse it.
Below, the expanded options for a JSON file:
...and for a DOCX file — other file types show their own set of options:
5. Workflows
wxrks recommends a workflow and carries over the target languages for each file automatically, based on the file type and your Configuration step settings. You can adjust the target languages or workflows for individual files here if a specific file needs to differ from the rest of the project — check several files and click Edit to change them together.
Click Create once every file has the languages and workflows you want.
6. Approve your project
If Quote Automation is enabled (an account-wide setting that calculates project costs automatically — see My Account Configurations), the project moves to Pending status on its own. Otherwise, set it to Pending manually to calculate its costs. From there, the project can be approved.
Once approved, if the feature is enabled, pre-translation begins — populating segments from your Translation Memory and/or machine translation.
Note: You can't change a project's foundational creation details after the fact, such as its parent Organizational Unit. wxrks doesn't support moving these elements between units, to protect user data and comply with our SOC 2 Type 2 certification requirements.