How linguists track their own progress per job
When several people work on the same content across different steps (translation, revision, a final review), each step needs its own clear view of whether that content is ready. Per-job status gives every person that view: each linguist can clearly see when their own assignment is done, and that individual clarity adds up to better quality in the final text. This is the status behavior users coming from other CAT tools already know.
In Wordbee, this is the segment status per job setting: every job keeps its own private status on each segment, so one step's review never changes what another step sees. It is the recommended setup for teams running multi-step workflows where each step tracks its own progress. To use it, a platform owner activates it by contacting Wordbee, and it then takes effect immediately across every project on the platform. Until it is activated, Wordbee keeps today's default: a single status shared by all jobs on a segment, where teams coordinate through that shared status (see Management of project workflows).
With it on, teams get:
Accurate per-step progress: each step reflects its own real state, not another step's.
Protected work: a project-level check no longer resets the statuses a linguist set in their job.
A clean starting point: each job begins aligned with the content's current shared status.
Clear accountability: every step owns a separate, traceable picture of readiness.
How Job Statuses Work
Every segment has a status you can set to grey (not started), green (validated), or red (problem). What changes is whether that status is shared across all jobs or kept per job. Consider a typical two-step workflow: one linguist translates the content in a translation job, and another revises it in a revision job.
With the setting off (default) | With the setting on | |
|---|---|---|
Status | One status, shared by both jobs on the segment | Each job keeps its own status per segment |
What the translator sees | The single shared status | Their translation job's status |
What the reviser sees | The same shared status, so the translator's changes show through | Their revision job's status, separate from the translation job's |
A change in one job | Changes the status everyone sees | Updates that job only; the other job is unaffected |
A segment a linguist has not yet touched in their job | — | Shows the current shared status until the linguist sets a status in that job; after that, the job keeps its own and later shared-status changes no longer affect it |
Bottom line: Project-level work stays on the shared status. Only when this new feature is enabled, if a manager runs project QA, pushes a Flex update, or brings in a new document version, the shared status changes, but each linguist's job status stays as they left it.
Working with Statuses in the Editor
Visually, nothing changes: the status flag is in the same place and works the same, and clicking it cycles through grey, green, and red. Only the behavior is adjusted by the setting, so which status your change updates depends on where you are working:
If you are working on a job, the status you set (by hand or by running a QA check) updates that job's status only.
If you are working on a project or a Flex container, the status you set (including a project-level QA check) updates the shared status, leaving job statuses untouched.
Turning It On
Segment status per job is turned off by default and is controlled at the platform level. Platform owners can activate it at any time by contacting Wordbee. Once enabled, the change takes effect immediately across every project on the platform, so there is no per-project or per-user switch to set. Keep the default if a single shared status per segment fits how your teams work.
Because it changes how statuses behave inside jobs for everyone, brief your teams before activating it: inside a job they will see that job's status rather than the shared one, and each job starts from the segment's current shared status.
Learn More
Management of project workflows: How teams coordinate with the shared segment status in a translation-revision workflow (the default, feature-off way of working).
The Segments: The segment status values and how to cycle them.
QA Panel: Run and review quality checks in the Editor.
QA Profiles: Configure which rules a QA check applies.