A Net Rate Coefficient is the set of rules wxrks uses to turn a raw word count into what a vendor actually gets paid, based on how much of the work was already done for them by Translation Memory, Machine Translation, or the platform's AI-assisted suggestions. This article explains what each coefficient controls, the platform's default effort percentages, and how to build and assign a custom coefficient set.
💡 Who is this for? This guide is for Account Admins who need to understand how wxrks weights Translation Memory, Machine Translation, and AI-assisted matches into a vendor's Net Rate, and build a custom coefficient set for their account or Organizational Units.
What is Net Rate?
A project's Logfile counts every segment in a job and buckets each one into a match tier — how closely it already matched something in your Translation Memory, whether it came from Machine Translation, or whether it needs to be translated from scratch. See All about Logfiles for how that breakdown is built.
Net Rate Coefficients turn that breakdown into money: each match tier gets its own effort percentage, and a vendor's final pay for a segment is their per-word rate multiplied by that percentage. A brand-new segment with no useful match is charged at (or near) 100% effort — full price. A segment that's a 101% match to something already in the Translation Memory needs essentially no editing, so it's typically weighted at 0% — no pay for that word. Everything in between is a judgment call your account makes about how much a partial match actually reduces a linguist's work.
The same coefficients also drive project cost estimates — heavier use of Translation Memory, Machine Translation, and AI assistance lowers both what a vendor is paid and what the job costs to run, since both numbers come from the same weighted word count.
The three columns: TM, MT, and NT
Every coefficient table has three percentage columns, and it's easy to assume they map one-to-one onto "Translation Memory," "Machine Translation," and "AI" — they don't quite. Based on how the platform's Logfile calculation actually assigns each match type to a column:
TM — applies to Translation Memory matches, and also to AI-assisted (Context Sensitive) matches and repeated segments. All three are weighted by the same percentage for a given range.
MT — applies only to segments that came from a connected Machine Translation engine.
NT — applies only to Non-Translatable content: segments your account's rules (for example a Regular Expression setting on the Organizational Unit) exclude from translation entirely, such as tags or placeholders. It is not an "AI" column, despite sitting next to TM and MT.
This matters when you're deciding how generously to weight AI-assisted suggestions: there's no separate slider for that. Whatever you set the TM percentage to at a given match range is also what a Context Sensitive AI match gets charged at, at that same range.
Where to find Net Rate Coefficients
Go to Settings > Translation Settings > Net Rate Coefficients. This page (labeled Edit Coefficients on screen) lists every custom coefficient set your account has created, with its name, its match ranges, and whether it's marked as your account's Default.
If your account hasn't created any custom set yet, or hasn't marked one as Default, wxrks falls back to its own built-in default coefficients — see below. See All about Settings for how this tab fits into the rest of Translation Settings.
The platform's default coefficients
wxrks ships with a built-in default coefficient set that applies whenever an account (or Organizational Unit) hasn't selected a custom one. This default isn't editable, and isn't visible from any account's own Settings — it lives outside any single account's configuration. Its match-range breakpoints are confirmed in the platform's backend code: 0%–49%, 50%–74%, 75%–84%, 85%–94%, 95%–99%, 100%, and 101%, plus a separate Repetitions row. Every custom coefficient set you create starts from these same seven breakpoints, though you can add more of your own.
The specific effort percentages the default set uses for each range aren't stored anywhere this project's code access could confirm directly — they're configured as platform-level data, not hardcoded logic. The table below reflects wxrks' own published default values; treat it as the most reliable available answer, but if you need to confirm the exact current default for a specific range, contact [email protected].
Translation step
Range | TM | MT | NT |
Repetitions | 0% | — | — |
0% – 49% | 100% | 100% | 100% |
50% – 74% | 50% | 80% | 80% |
75% – 84% | 25% | 70% | 70% |
85% – 94% | 15% | 50% | 50% |
95% – 99% | 10% | 40% | 40% |
100% | 1% | 20% | 20% |
101% | 0% | 0% | 0% |
Review step
Range | TM | MT | NT |
Repetitions | 0% | — | — |
0% – 49% | 100% | 100% | 100% |
50% – 74% | 50% | 50% | 50% |
75% – 84% | 40% | 40% | 40% |
85% – 94% | 30% | 30% | 30% |
95% – 99% | 20% | 20% | 20% |
100% | 0% | 0% | 0% |
101% | 0% | — | — |
Ranges follow the same seven breakpoints for every workflow step, but the platform lets the percentages themselves differ by step — a Review step generally needs less re-work than a Translation step, so its defaults are less steep.
An unfilled range is charged at full price, not zero
When you build a custom coefficient set, it's not mandatory to fill in a percentage for every range on every workflow step. It's worth knowing exactly what happens if you don't: a range or workflow step left without its own percentage is calculated at 100% effort — full price — confirmed in the platform's backend calculation logic (works/src/main/java/com/bureauworks/works/accounting/netrate/service/NetRateSettingsService.java and the matching database query in NetRateWorkflowItemRepository, both of which fall back to 100% whenever a coefficient value is missing). In other words, an unfilled range behaves as if no TM/MT/AI discount applied at all — the safer default from a vendor's point of view, since it never accidentally pays someone $0 for real work.
The safest approach is still to assign every workflow step your projects actually use to a coefficient table with real values — that way nothing is left to the fallback.
Building a custom Net Rate coefficient set
Click Create Edit Coefficient on the Net Rate Coefficients list. Creating a set is a two-step process.
Step 1: Ranges
The first screen defines your match-range breakpoints. It starts pre-filled with the same seven default ranges described above (0%–49%, 50%–99%, 100%, 101%). Click Add Range to insert an additional starting point — the platform automatically fills in the end of the previous range for you. Click Next once your ranges are set.
Step 2: Name it and build Coefficient tables
Give the set a Name, then assign your account's workflow steps (Translation, Review, or any custom step) to one or more Coefficient tables. Every workflow step assigned to the same table shares one set of TM/MT/NT percentages across your ranges — this is how a Translation step and a Review step end up with different effort percentages even though they share the same set's name. Click New table to create another table with different values for a different group of steps; wxrks automatically groups workflow steps together if their tables end up with identical ranges and values.
Fill in a percentage for each range in the TM, MT, and NT columns — remember TM also covers AI-assisted matches and repetitions, per the column breakdown above. Click Save when you're done.
Choosing which coefficient set applies
A custom set does nothing until it's selected somewhere:
Account default — toggle Mark as Default on a set from the Net Rate Coefficients list (or from the set's own page) to make it your account's fallback for every project that doesn't have a more specific Net Rate selected.
Organizational Unit override — open the Unit and use its own Net Rate tab's Edit Coefficients field to pick a specific set for that Unit instead of the account default. See All about Organizational Units for that tab's other settings — Payment Type (Pre-analysis vs. Post-analysis), Pay By (Words vs. Hours), Count Words From, and Quoting Type — which work alongside the coefficient set you choose here but are configured independently of it.
If neither an account default nor a Unit override is set, wxrks uses its own built-in default coefficients described above.
How this shows up in payment and cost
A project's Pre-analysis Logfile uses your coefficients to estimate what a job should cost and pay before any work starts. Once a linguist or reviewer finishes, the Post-analysis Logfile recalculates the same weighted breakdown based on the actual editing effort — this is what vendor payables and final invoicing are based on. See All about Logfiles for how to read that breakdown on an actual project, including the Net Rate Factor column that shows exactly which percentage from your coefficient set was applied to each match tier.
The same weighting is also what makes an account's investment in Translation Memory, Machine Translation, and AI-assisted translation pay off financially: the more segments land in a well-discounted range, the less a job costs to run and the faster it can be delivered.
Related articles
All about Organizational Units — the Net Rate tab that selects which coefficient set applies to a Unit, plus Payment Type, Pay By, and Quoting Type.
All about Settings — where Net Rate Coefficients fits among the rest of Translation Settings.
All about Logfiles — reading the match-tier breakdown and Net Rate Factor on an actual project.