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.

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 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.

The connection shows as Pending until the other account accepts it. You can delete a pending invite at any time.

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.

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:

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.

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:

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.

The Send Work Package modal requires only Destination Account and Destination Org Unit. Everything below them is optional, and controls what travels with the work — and, on Pre-Analysis projects, which vendor your own account pays for it.

What each option does:

Select Send Reference Files to copy the reference files attached to your project — style guides, past deliveries, screenshots — into the destination project. Without it, the receiving team gets only the translatable content plus the temporary Translation Memory (TM) and Glossary described above.

ℹ️ Note: The checkbox is cleared every time the modal opens, so select it on each send. Sending part of a project now and the rest later means selecting it twice.

ℹ️ Note: Selecting the option later does not backfill a package already sent. Share the files with the receiving account directly, or select the option when you send the remaining work units.

💡 Tip: Use the editor to strip anything that only applies to your own account — internal deadlines, client names, references to your workflow — and to add context the receiving team can act on.

ℹ️ Note: Editing the text here does not change the instructions on your own project. It only sets the instructions on the project created in the destination account.

On projects whose payment type is Pre-Analysis — where cost is calculated from the analysis logfile rather than a flat or per-word amount — you can record which vendor your account pays for the sent tasks, so the task budget is calculated from that vendor's rate instead of being left empty.

ℹ️ Note: The selected user is used only to calculate this account's payment and profit margin. It is not sent to the destination account — the receiving team assigns its own linguists.

ℹ️ Note: Only users who can handle every language pair in the send are offered. A vendor missing one pair would fail the whole send, so they are filtered out of the list. To use a different vendor per language pair, send each pair in its own Work Package.

⚠️ Warning: Assigning a vendor here replaces any assignee already on those tasks in your project, and the replaced assignment's budget is discarded. Send with Assigned to empty to leave existing assignees untouched.

If Advanced Settings is not in the modal, the project's payment type is not Pre-Analysis. Send without it and handle the vendor's payment through your usual process for that payment type.