Solutions
A contract is a document where the formatting carries meaning.
Legal documents are the clearest case for why layout preservation is not cosmetic. Clause numbering, defined terms and cross-references are part of the instrument, not decoration around it.
What makes these documents hard
Four failures that matter more here than anywhere else.
Numbering that shifts
If clause 7.2 becomes 7.3 in translation, every cross-reference in the document is now wrong. This is a layout failure with legal consequences.
Defined terms that drift
A defined term translated inconsistently is a different defined term. Consistency is not a style preference in this document class.
Tracked changes and comments
Working documents carry review state. Whether that state survives processing is worth testing on your own file rather than assuming.
Scanned filings
Court and registry documents are frequently scans. They have no text layer, so recognition has to run before anything else can.
The documents we get
These are the document types that come up most in this category.
Contracts and agreements
Numbered clauses, defined terms, cross-references, signature blocks.
Filings and registry documents
Often scans, often with strict formatting conventions, often with tables of parties and dates.
Correspondence and opinions
Letterhead, addressee blocks, firm-specific formatting that has to survive.
Terms and policies
Long, highly repetitive, and the case where a glossary earns its keep most.
Terminology and consistency
You supply the terms. We enforce them.
We do not supply legal glossaries. What we do is take the term list your work is judged against — TXT, CSV or XLSX, up to 2000 terms — and apply it during translation rather than as a correction afterwards.
Where a defined term must render identically everywhere it appears, that is exactly the kind of constraint a glossary enforces well and a reviewer cannot police reliably by eye.
What we do not do is give legal advice, verify legal effect, or certify a translation for filing. Those are your reviewer's responsibilities, and claiming otherwise would be dishonest.
How the work runs
Four steps, same pipeline for every industry.
- 01
You send one real document
The awkward one if you have it. It is evaluated on the same path your production work would take.
- 02
We run it end to end
Inspection, per-page routing, translation with your terminology applied, independent review, visual verification.
- 03
You judge the returned file
Layout, terminology, the pages that normally break. That is the evaluation.
- 04
Scope is agreed separately
Volume, language pairs, turnaround and integration. The sample tells you whether to have that conversation at all.
Questions
Do you provide certified or sworn translations?
No. We provide the translated document. Certification, swearing and notarisation are separate processes carried out by qualified people in the relevant jurisdiction.
How do you keep clause numbering consistent?
Translated text is written back into the original document rather than into a rebuilt one, so the numbering structure is the source's numbering structure.
Can you enforce our defined terms?
Yes — send the term list and it is applied during translation. Up to 2000 terms per glossary.
Do you handle scanned filings?
Yes. Pages without a text layer go down the optical recognition path, and in a mixed PDF that is decided page by page.
Is our material confidential?
We do not name clients, we do not publish documents, and engagement material is not used to train models. Terms are set per engagement — send your NDA and we will tell you plainly if there is something we cannot agree to.
Send us a contract and check the numbering.
It is the fastest way to see whether the structure survives — and the failure mode that matters most in this document class.
- No signup, no self-service portal — you send a file, we run it.
- You get the finished document back, not a screenshot of one.
- If it is not good enough, you have lost nothing.