By default, wxrks calculates a project's cost and a vendor's task payment from the Source word count — the original, untranslated content. You can instead base either calculation on the Target word count, taken after the content has already been pre-translated with Machine Translation, Translation Memory, or Context Sensitive translation.
​

This article covers where that setting lives, what it changes, and what to check before you switch to it.

💡 Who is this for? This guide is for Account Admins and Project Managers who need to configure or apply Target-based word counts for project cost and vendor payment calculations within the wxrks platform.

Source word counts come from the original content, before any translation happens. Target word counts come from that same content after pre-translation — segments already filled in by Machine Translation, Translation Memory, or Context Sensitive translation (see Translate in the Actions/Options Bar article).
​

Basing a calculation on the Target instead of the Source gives a more accurate picture of what still needs manual translation work, since content already matched from Translation Memory or machine-translated is no longer counted as if it were untouched.

Both settings live in Organizational Unit settings, under the Net Rate tab — visible only to Account Admins.

Pre-analysis and Post-analysis refer to the two kinds of logfile a project can generate — see All about Logfiles for what each one shows. In short: pre-analysis estimates the effort before translation starts, and post-analysis measures the actual effort afterward, compared against that pre-analysis baseline.
​

The Net Rate tab also has a separate coefficient table selector and a Pay by Hours option, both unrelated to Source/Target — see Net Rate Coefficients and Managing Hourly Rates.

A cost or payment can only be calculated from the Target once the content actually has a Target — otherwise there's nothing to count.
​

If Quote Automation is turned on for the project (recommended), wxrks pre-translates automatically as part of approving the project, so no extra step is needed. If it isn't on, pre-translate the content yourself first — see Translate in the Actions/Options Bar article.

⚠️ Segments that are still empty at calculation time aren't counted at all, which can understate the cost or payment if pre-translation hasn't finished yet.

The Net Rate tab sets the org-wide default, but you can also choose Source or Target for one logfile when you create it manually.

A whole-project logfile is always a pre-analysis logfile — the Pre-analysis/Post-analysis choice only appears when generating a logfile from selected Work Units. See All about Logfiles for what each logfile type includes.

Each part of a split Work Unit gets its own logfile once one is created for it, so a Source/Target choice applies per part rather than to the whole original file. See Split a Work Unit into Multiple Parts for how that affects cross-file leverage matches.