Checking the draft

Bible translation checking software — find the problem, then let a person decide.

Bible translation checking software finds problems in a draft before anyone treats it as finished. Paratext’s Basic Checks and unfoldingWord’s translationCore are built for that job. Aquilla does not replace them: the team reviews in the browser, reads a back translation while drafting, and exports USFM when those checks still have to run.

The direct answer

What does Bible translation checking software do?

It looks for draft problems a person might miss: a broken verse number, odd punctuation, a key term that changed, or a source word with no rendering. Paratext does this with Basic Checks and the Biblical Terms tool. translationCore does it with notes, key terms, and alignment, including offline. Aquilla does not run those checkers. It keeps the draft, the team review, and a back translation in one signed-in workspace, then hands USFM to the tool that still owns the check.

Paratext’s checking tools page lists Basic Checks for chapter and verse numbers, characters, punctuation, capitalization, repeated words, and more, plus key terms, spell check, and parallel passages. The training manuals run those checks only after the project inventory says which characters and marks are valid.

translationCore is a separate desktop application from unfoldingWord. Teams open a project and check figures of speech, key terms, and alignment to the source languages. It is free, open source, and built to work offline. That is a different product from a browser workspace.

What the search is actually choosing

Bible translation checking is a job list — not one spell-check button.

Searchers mix Paratext’s inventories, translationCore’s alignment, and a team reading the draft aloud. Aquilla covers the browser review and is explicit about the rest.

JobAquillaTypical result for this search
Chapter, verse, and marker checksNo — not Paratext’s chapter/verse or marker checks.Yes — Paratext Basic Checks
Characters, punctuation, capitals, repeated wordsNo — Aquilla does not run those inventories.Yes — Paratext Basic Checks, after an inventory
Quotations, numbers, references, and footnotesNo — not Paratext’s remaining basic checks.Yes — Paratext Basic Checks
Figures of speech, key-term checks, word alignmentNo — Aquilla is not translationCore.Yes — translationCore: Translation Notes, Translation Words, alignment
Biblical Terms window and parallel passagesNo — keep that desktop suite in Paratext.Yes — Paratext Biblical Terms and parallel passages
A community checking campaignNo — Aquilla does not run community-checking campaigns.Scripture Forge, when a project uses that campaign
Review a draft with the team in the browserYes — comments, status, and a person who approves.Often still inside Paratext or Scripture Forge
A back translation you can read while draftingYes — an inspection aid, not the consultant check.A separate Paratext project, or Render’s audio tabs
Carry approved wording into later draftsYes — Living Memory learns from decisions you authorize.Paratext translation memory and Biblical Terms renderings

How to check a draft without pretending one tool does every check

A check is not a draft

Drafting proposes wording. Checking asks whether that wording is complete, consistent, and still the meaning of the source. Paratext and translationCore are built around the second job. Aquilla is a workspace for the draft and the review, not a replacement for those checkers.

What stays in the checking suite

Keep Paratext Basic Checks if the project depends on inventories for characters, punctuation, references, or markers. Keep translationCore if the team checks figures of speech, key terms, or alignment against the source, including offline. Export USFM/USX from Aquilla when that handoff is required.

What a person still decides

Software can flag a repeated word or a missing rendering. It cannot decide that a verse is faithful. Team checking, community testing, and the consultant meeting stay with people. Aquilla does not assign the consultant or run the meeting.

Related, and not this page

Back translation is one inspection aid, described on its own page. Key-term memory versus Paratext’s Biblical Terms tool is the translation-memory page. The eight quality stages are the workflow page. This page is only the checking software.

Software vs the stages

This page is the checker. The workflow page is the sequence.

Team checking, community testing, back translation, consultant review, and final software checks are stages. The workflow page describes them. This page says which program runs the software checks, and which of those programs Aquilla is not.

If you need the stage, use the workflow. If you need to know whether Aquilla is Paratext Basic Checks or translationCore, use this page.

Common questions

Bible translation checking FAQ

What is Bible translation checking software?

It is software that helps a team find problems in a Scripture draft before publication: chapter and verse numbers, characters, punctuation, key terms, references, or a place where the source is not reflected. Paratext’s Basic Checks and unfoldingWord’s translationCore are built for that. Aquilla does not replace them. It is a browser workspace where the team reviews a draft, reads a back translation while they work, and keeps approved wording consistent.

Does Aquilla replace Paratext Basic Checks?

No. Paratext checks chapter and verse numbers, markers, characters, punctuation, capitalization, repeated words, quotations, numbers, references, and footnotes, usually after a project inventory. Aquilla does not ship those inventories, does not install on Windows or Linux, and does not implement Send/Receive. If the project still runs Basic Checks, export USFM and run them in Paratext.

Does Aquilla replace translationCore?

No. translationCore is unfoldingWord’s desktop checking tool for figures of speech, key terms, and alignment to the source languages, including offline use, often with a translationStudio project. Aquilla does not provide those checking tools, does not work offline, and does not upload a project to Door43. Use translationCore when that is the check the team trusts.

Is team checking the same as a software check?

No. Team checking is people reading the draft together for flow, clarity, and consistency. A software check is a tool that flags patterns, such as punctuation or a missing key term. Aquilla can hold the team review in the browser. It does not run Paratext’s or translationCore’s checkers, and the review is not finished because a screen looks clear.

Can Aquilla run a community checking campaign?

No. Scripture Forge can run community checking against a Paratext project. Aquilla does not run those campaigns and does not sync into Paratext. Community testing is still a human step, described on the workflow page.

How is this different from the back-translation page?

A back translation is one way to inspect meaning, in the consultant’s language. This page is the broader checking job: Basic Checks, translationCore, and the team review. Aquilla shows a back translation as you work. That gloss is not a completed check, and it is not Paratext’s interlinearizer.

Do I still need a translation consultant?

Yes, when the project requires one. A consultant checks meaning with the team. Aquilla does not assign a consultant, does not replace the meeting, and does not decide that a book is ready to publish.

How much does Bible translation checking 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 checker you already trust.

Open a Free plan and review with your team. Bible-translation teams and ETEN affiliates can contact us for team-plan access at no cost. Aquilla will not replace Paratext Basic Checks or translationCore.