A Work Package sends a translation project — including its current segment confirmations and a copy of the relevant Translation Memory and Glossary — from one wxrks account directly into a project in a different wxrks account. It replaces the older process of manually exporting a loc-kit, emailing it to a partner, and re-importing the result.
💡 Who is this for? This guide is for Account Admin and Project Manager users who need to send translation work to, or receive it from, another wxrks account within the wxrks platform.
What Work Packages are for
Work Packages exist for cases where the work itself — not just a review or a comment — needs to move to a completely separate wxrks account: sending overflow or specialized work to a partner LSP's account, or an agency sending work into a client's own account. The connection is always one-way: the sending account decides what gets sent and when, and the receiving account cannot send anything back through the same connection.
This is different from Project Routing, which creates multiple copies of one project for different Organizational Units inside the same account. Both settings live on the same page, on separate tabs, but they solve different problems — Project Routing never leaves your account.
Before you start
You need the receiving account's account UUID — ask the other account's Account Admin for it, or share yours with them if you're setting up the receiving side.
A project can only be sent as a Work Package once it's in Approved status.
Setting up the connection and sending or receiving packages all require the Account Admin or Project Manager role.
Step 1: Connect the two accounts (the Handshake)
Before any project can be sent, the sending and receiving accounts need a one-time connection called a Handshake. Go to Settings > Translation Settings > Project Routing, then switch to the Handshake tab.
Send the invite (sending account)
Click Invite Handshake.
Paste the receiving account's UUID and click Confirm.
The connection shows as Pending until the other account accepts it. You can delete a pending invite at any time.
Accept the invite (receiving account)
On the Handshake tab, find the pending invite and click Accept.
Optionally enter a Project Name Prefix — this text is added to the start of every project reference this account receives through the connection. If you leave it blank, wxrks uses WP as the default prefix.
Select the Authorized Org Units — only these Org Units can be used as the destination when the sending account sends work. This selection is required.
[SCREENSHOT PLACEHOLDER]
You can revisit an accepted connection at any time from the edit icon in the Actions column to change the prefix or the authorized Org Units.
Step 2: Send a Work Package
Once the connection is accepted, the sending account can start sending work from any Approved project — from either the project's Overview or Tasks tab, once a Handshake exists:
On the Overview tab, open the Import/Export dropdown — a Work Package section there offers Send Work Package for selected work units (only the items you've checked in the list) or Send Work Package for all project work units (the entire remaining scope).
On the Tasks tab, the same action is its own Send Work Package button, offering Whole project at workflow or Selected tasks.
Either option opens the Send Work Package modal. Choose the Destination Account (only accounts with an accepted Handshake appear here) and the Destination Org Unit (limited to the Org Units that account authorized), then click Send.
Sending doesn't happen instantly — wxrks replicates the selected work units and their Translation Memory/Glossary context into the destination account in the background, so the new project may take a few minutes to fully appear.
What the receiving account sees
A new project is created automatically, named Prefix - Original Project Reference - Project Name (using the prefix set when the Handshake was accepted, or WP if none was set).
The project carries a visual indicator showing it originated from a Work Package.
It uses the destination Org Unit's own default settings — its Price List, Contact Person, and workflow sequence carry over from that Org Unit, not from the sending account.
wxrks creates a temporary Translation Memory and Glossary in the destination account, seeded from the sender's context (including fuzzy matches), and attaches them to the new project so the receiving team has the same resources the sender was working with.
[SCREENSHOT PLACEHOLDER]
Step 3: Deliver the work back
There's no separate "deliver" action to remember in most cases: as soon as the destination project's status changes to Delivered, wxrks automatically pushes the completed translations back into the original project's work units.
If that automatic delivery doesn't happen — for example after a temporary server issue — the project's execution status area shows a manual fallback:
Deliver Work Package: appears while a transfer is ready to go out but hasn't delivered yet. Use it to trigger delivery manually.
Retry Work Package: appears if a delivery attempt failed. It reimports the source project's translations into this project's work units, overwriting any existing content there — wxrks asks for confirmation before running it.
While a delivery is running, the same area shows a live progress indicator (for example, Delivering 4/10), and updates to Delivered 10/10 once complete. Delivery also supports partial progress: if only some work units come back, sending or delivering again later won't overwrite the ones already marked Delivered.
[SCREENSHOT PLACEHOLDER]
Troubleshooting
The Work Package section doesn't appear in the Import/Export menu. Confirm a Handshake has been accepted with at least one destination account, and that the project is in Approved status — the sending options stay disabled until both are true.
Delivery shows as interrupted or failed. Use Retry Work Package from the project's execution status area (see above). If it keeps failing, contact [email protected] or search the wxrks Community for similar reports.