Project Routing lets you create one set of files once and have wxrks automatically split it into a separate project for every Organizational Unit that needs it — each with its own workflows, target languages, and contact person — instead of creating and configuring those projects one at a time.
​

💡 Who is this for? This guide is for Account Admins and Project Managers who need to set up a Project Routing configuration and use it to create linked projects across multiple Organizational Units within the wxrks platform.

A regular project belongs to a single Organizational Unit. Project Routing is a second way to start a project: instead of picking one Organizational Unit, you pick a Project Routing Configuration that already lists several Organizational Units, upload your files once, and wxrks creates one linked project per Organizational Unit in that configuration — each pulling its own workflow, target languages, and per-unit settings from the configuration.

This is worth using whenever the same source content regularly needs to go out to several teams or departments at once — for example, one piece of marketing copy that three regional Organizational Units each need translated into their own target language. Set up the routing once, and every future batch of files reuses it.

A configuration is what Project Routing actually routes against — it links a set of Organizational Units to a workflow and target language(s) apiece, plus optional per-unit Translation Memory, Glossary, Price List, and Instructions. You need at least one configuration before you can create a project with Project Routing, and creating or editing one requires Account Admin access.

Go to Settings → Translation Settings → Project Routing, then click Create new Configuration.

On the new configuration, fill in:

For each Organizational Unit row, also set its Workflow and Target Languages, and — via the icons on the right of the row — optionally override that unit's default Translation Memory, Glossary, and Price List, or add unit-specific Instructions for whoever works the project. Any of these left unset falls back to the Organizational Unit's own defaults, the same way a regular project does — see Project's Translation Settings for how those settings behave once a project exists.

The lock icon between the Workflow and Target Language columns controls whether the same target language can be assigned to more than one Organizational Unit in this configuration. Locked (the default), picking a language already used by another row automatically bumps the new row to a regional variant instead — as in the screenshot above, where the second unit's French automatically became French (Africa) because the first unit already had plain French. Unlock it if you actually want two Organizational Units to receive the exact same target language.
​

Click Save once every row has a Workflow and at least one Target Language. Create a new configuration whenever you need a different combination of Organizational Units or language routing — a project created from a configuration doesn't stay linked to it afterward, so changing the configuration later has no effect on projects it already created.

Start a new project the normal way — the Start a new project button on your homepage, or Projects in the left sidebar — and you'll see two options side by side: Direct Project (a single Organizational Unit) and Project Routing. Hover More Info on either card for a quick visual reminder of what it does; click Create Project Routing to continue.

The rest of the wizard mirrors creating a regular project in three steps, with the differences called out below.

Pick the Configuration you set up earlier and give the project a Project Reference. The Org. Units and Source Language come from the configuration and can't be changed here — but you can still remove any Target Languages you don't need for this particular batch of files from the list the configuration prefilled.

Upload your files the same way as a regular project — drag and drop, or Browse — and wait for every file to finish importing before moving on. Each file's own parsing options (what gets extracted, how tags are handled, and so on) work exactly the same as a Direct Project; see How to configure file parsing options for your project's files for what each setting does.

Step 3 previews the projects Project Routing is about to create — one per Organizational Unit — as a set of cards you can page through if a configuration has more than a couple of units.

If a file isn't assigned to any Organizational Unit's card, a warning banner names it and explains it will not be translated — assign it to at least one card's Files field, or leave it out on purpose if that file genuinely doesn't apply to any of the units.

Each card also needs a Contact Person chosen manually — search by name if the person you're looking for isn't already in the dropdown — and lets you make one last change to that unit's Workflow or Target Languages before creating anything.

Click Create once every card has a Contact Person and at least one file assigned.

wxrks creates one project per Organizational Unit and lists them like any other project, each starting in the same Pending/quote-calculation flow a Direct Project goes through — see the Approve your project step in How to create a translation project in wxrks for what happens next.

Projects created together this way carry a small icon marking them as part of the same routing group. Clicking that icon on any one of them filters the project list down to just the projects from that same batch, so you can review or manage them together without hunting through your full project list.

[SCREENSHOT PLACEHOLDER]

How to create a translation project in wxrks — the full step-by-step for a Direct Project, which Project Routing's own wizard mirrors.
​How to configure file parsing options for your project's files — every per-file setting available in Step 2.
​Project's Translation Settings — how a project's Translation Memory, auto-translation, and Sous Chef Agent settings work once it's created.
​Project Overview — a map of every tab on a project's page, for managing the projects Project Routing creates.