wxrks' Quality section is where you see how a translation changed as it moved through your workflow. Every edit a reviewer makes gets recorded, labeled with a reason, and rolled up into reports you and your vendors can revisit later.
​

💡 Who is this for? This guide is for Project Managers and Vendors who need to review quality reports and understand how translation changes are tracked and categorized throughout the workflow.

From the sidebar, click Quality to expand three pages: Dashboard, Reviews, and Reports.
​

Two more pieces of the same quality system live inside the Editor itself rather than under the Quality sidebar item, and are documented separately: the rule-based QA Check Tool (tag, length, spelling, and formatting checks a linguist runs before delivering), and QA Confidence Score and Smells (an AI review that flags likely quality problems and scores each segment's confidence).

When a linguist reviews someone else's translation and edits a segment, wxrks prompts them to label the edit with a change category — Grammar, Fluency, Terminology, Incorrect Translation, or a Preferential change. This categorization is what powers the Reviews and Reports screens below, and it also feeds into the translator's quality metrics on their vendor profile.
​

See Translation changes categories in wxrks for what each category means, and How to configure custom review categories if you want to replace or add to the default list.

Open Quality > Reviews to see every task that has been through a review step, grouped by project. Vendors only see reviews for tasks they were personally involved in (translating or reviewing); Project Managers see every review for the Organizations and Organizational Units they're associated with.
​

Each row is one project, showing its Status, Organizational Unit, Overall Changes percentage, total segments changed, creation date, how many reviews it has, and a General Feedback score where one has been given.
​

Click the arrow next to a project to expand it into its individual tasks:

The expanded table lists each File Name, its status and Workflow step, the Translator and Reviewer involved, the Language Pair, the percentage of segments changed, and a feedback score. Click a file name to open its Work Unit Review:
​

At the top, meta chips repeat the Project, Organizational Unit, Project Manager, last reviewer, Language pair, Workflow, and File. The Changes Summary panel quantifies the review: percentage of changes, how many segments changed, repeated segments, confirmed segments, locked segments, and total words/segments. Below that, a breakdown table shows how many occurrences of each change category (Grammar, Fluency, and so on — see Translation changes categories in wxrks) were found, and what share of changed and confirmed segments they represent.
​

Further down, each numbered segment shows its Source, Target, and exactly what was Changed — with the edit highlighted inline — tagged with its category. Use Show comments to read any reviewer notes on that segment, or Open in Editor to jump straight to it.

Open Quality > Reports for a different view of the same underlying data: instead of one review per task, a report consolidates every workflow step's changes for one file and target language into a single record. A report's status is Finished once every workflow step's review is complete, or Pending while at least one is still in progress.
​

Each row shows the project, status, Organizational Unit, File Name, Language Pair, the date of the First Review, and a general feedback score. Click a project name to open its Full Quality Report:
​

Each segment is laid out across columns: the original Source, the initial Translation, and then one column per subsequent workflow step (labeled Review, Review 2, and so on). A step that changed the segment shows the edit with its change category badge; a step that didn't shows a No Changes label instead — so you can see exactly which workflow step introduced (or didn't introduce) each change, not just the final result.

Reviews and Reports are the record-keeping side of quality in wxrks. The rest of the system lives in these related articles: