The file check

Translation quality assurance software — the check before you deliver the file.

Translation quality assurance software flags rows in a bilingual file: an untranslated segment, a number that changed, a tag that moved, a required term that was missed. Xbench and Verifika run that check. Aquilla does not. It shows support evidence in the draft, and a person still decides the release.

The direct answer

What is translation quality assurance software?

It loads a bilingual file and looks for problems a reviewer might miss. ApSIC Xbench checks untranslated segments, inconsistent translations, numbers, tags, and key terms. Verifika runs the same kind of pass and is used when the team needs a report. Aquilla does not run that file check. It shows inspectable support evidence on each cell, in text and in audio, and a person still decides what is good enough to release.

People searching for translation quality assurance software already have a CAT package. They want a second program to scan it. A browser workspace that can show support on a verse has not become that scanner.

Xbench’s own guide lists the checks: untranslated segments, the same source with different targets, number and tag mismatches, terminology against a list, and spell-check if you download a dictionary. Aquilla does not implement that list.

What the search is actually choosing

Translation quality assurance software is a job list — not “someone reviews it.”

Searchers mix a rule check on a package, a report for the client, and a reviewer looking at the draft. Aquilla is only the last setting, and it does not pretend to clear the file.

JobAquillaTypical result for this search
Untranslated segments, number mismatches, and tag mismatchesNo — Aquilla does not run that file check.Yes — Xbench and Verifika
Terminology check against an imported glossaryNo — no glossary file, and no forbidden-term rule.Yes — Xbench key terms, Verifika terminology
Same source translated two ways, or the reverseNo — not a segment-consistency report.Yes — Xbench
A QA report you hand the clientNo — Aquilla does not produce that report.Yes — Verifika is built to document the pass
Spell-check the bilingual fileNo — no spell-check dictionary on a package.Yes — Xbench, with a dictionary you download
See where support for a cell is thinYes — inspectable support evidence on text and audio.Not the job of a file QA tool
Paratext Basic Checks or translationCoreNo — those checkers stay in their own tools.Paratext and translationCore, not Xbench

Run the file check in the tool that reads the file

A file check and a review surface are different jobs

Translation quality assurance software loads a bilingual file and runs rules across it. Xbench and Verifika are that pass. Aquilla is the workspace where the draft is written. Showing support on a cell is not the same as scanning a package for tag errors.

What stays in Xbench or Verifika

Keep a QA tool when the delivery is a Trados or memoQ package and the client expects a list of untranslated segments, number or tag mismatches, or terminology misses. Verifika is the one sold for a report you can hand over. Aquilla does not open those packages and does not write that report.

What the reviewer sees in Aquilla

Each cell can show inspectable support evidence, for text and for audio, so a reviewer can start where support is thinner. Agents can flag an issue. A person still decides what is good enough to release. That signal does not replace a bilingual-file QA pass.

Related, and not this page

Bible translation checking software is Paratext Basic Checks and translationCore. Professional translation tools is the editor, including where to get memory with AI. This page is only the QA tool.

Agency QA vs Scripture checks

This page is Xbench and Verifika. The checking page is Paratext.

Bible translation checking software compares Basic Checks and translationCore with what a browser workspace does not run. This page is the other search: a QA tool on a CAT package. Aquilla is not the answer to either search when the job is the automated check.

The quality stages of a Bible translation — team check, community review, consultant check — are the workflow page. Those stages are people and questions. They are not an Xbench report.

Common questions

Translation quality assurance FAQ

What is translation quality assurance software?

It is the program that checks a bilingual file before delivery. ApSIC Xbench loads the ongoing translation and looks for untranslated segments, inconsistent translations, number and tag mismatches, and terms that miss a glossary. Verifika runs a large set of the same kinds of checks and is used when the team needs a report of what was found. The software flags the row. A person still decides whether the translation is right.

Is Aquilla a replacement for Xbench or Verifika?

No. Xbench and Verifika read bilingual files from desktop CAT tools and run rule checks across the file. Aquilla does not open those packages, does not run those checks, and does not produce their report. If that pass is required, run it in the tool that already does it. Aquilla is the workspace where the draft and the review happen.

Does Aquilla check numbers, tags, and untranslated segments?

No. Those are file-level QA checks. Xbench documents them: untranslated segments, number mismatches, tag mismatches, unpaired punctuation, and terminology misses against a list. Aquilla does not claim that list. It does not spell-check a package either.

How is this different from Bible translation checking software?

Bible translation checking software is Paratext’s Basic Checks and unfoldingWord’s translationCore: chapter and verse, characters, references, key terms, and alignment. This page is the agency QA tool that runs on a CAT package. Aquilla does not replace either one. The checking page is the Scripture comparison. This page is Xbench and Verifika.

What does Aquilla show a reviewer instead?

Inspectable support evidence on the cell, for text and for audio, so a reviewer can spend time where support is thinner. Agents can flag an issue. Living Memory carries forward wording the team has already approved. None of that is a client QA report, and none of it clears a file the way Xbench does.

Can I hand a client an Xbench-style report from Aquilla?

No. Aquilla does not export a QA report of error categories, severities, or segment hits. If the delivery includes that report, produce it in Verifika or Xbench from the bilingual file those tools can read.

Does quality assurance software replace the reviewer?

No. Xbench and Verifika find rows that match a rule. They do not know whether the meaning is right. Aquilla’s support evidence does not know that either. A person still authorizes the release.

How much does this cost in Aquilla?

Anyone can start on the Free plan with a weekly allowance of AI assistance. Bible-translation teams and ETEN affiliates get team-plan access at no cost — contact us to activate your organization’s workspace.

Related topics

Review the draft. Keep the QA tool that reads the package.

Open a Free plan and review with support evidence on the cell. Bible-translation teams and ETEN affiliates can contact us for team-plan access at no cost. Aquilla will not replace Xbench or Verifika.