Workflow
Bilingual Legal Documentation in the GCC: Challenges and Best Practices
A single GCC dispute can run in Arabic before an onshore court and in English before a tribunal, off the same documents. Most of the avoidable errors happen at that seam.
Arabic is the official language of the UAE under Article 7 of the Constitution, and the language of onshore proceedings under Article 5 of Federal Decree-Law No. 42 of 2022 on Civil Procedure. Foreign-language documents must be translated by a translator licensed by the Ministry of Justice before they will be accepted.
Meanwhile the DIFC and ADGM courts operate in English, and most institutional arbitrations seated in the region are conducted in English by agreement. So the same underlying facts, the same contract, and often the same bundle move between two languages depending on where they land — and the seam between them is where avoidable errors accumulate.
Key takeaways
- Decide the working language of the chronology on day one, and never let it drift.
- Build a party-name table early: one entity routinely appears under four or five spellings.
- Certified translation is a court requirement, not a quality guarantee — terminology still drifts between translators.
- Keep the original beside the translation with paragraph-level mapping, so a disputed word can be traced.
Where bilingual files actually break
Party names
Transliteration is not standardised. A single company can appear across one bundle as four or five different English spellings, none of them wrong, plus the Arabic original. Search misses documents. Chronologies double-count. Two entities in a group get merged because their transliterations converge.
The fix is unglamorous and effective: a canonical name table built during the indexing pass, listing every spelling encountered, the Arabic original, and the entity it maps to. Every downstream artefact uses the canonical form and nothing else.
Dates
Hijri and Gregorian dates coexist in the same file, sometimes in the same document. Numeric formats are ambiguous across conventions. Correspondence dated by reference to a stated event rather than a calendar date has to be placed by context. Every chronology entry needs its calendar recorded alongside the date, and inferred dates need marking as inferred — a distinction nobody remembers six weeks later.
Terminology drift
Certified translation gets a document admitted; it does not keep vocabulary stable. Two licensed translators can render the same contractual term differently, and across a large bundle translated in tranches, the same Arabic term may reach you as three different English terms. When the meaning of that term is the dispute, the translation has quietly taken a position.
Maintain a matter-level bilingual glossary of the terms that matter, fix the rendering once, and issue it to every translator on the matter. Where a term is genuinely contested, keep the original in brackets after the translation rather than choosing silently.
Governing language clauses
Bilingual contracts usually nominate a prevailing version. Read it before you build the chronology, because it determines which text you are actually construing — and it is common for the prevailing version to be the one nobody on the team has been working from.
Documents that break mechanically
Right-to-left and left-to-right text in one paragraph reorders unpredictably when copied between systems, and embedded figures and clause numbers are where it shows. Arabic OCR on a poor scan degrades faster than English, particularly with handwritten annotations and stamps. Both problems are worth catching during indexing rather than discovering in a submission.
A working practice
- 01Pick the working language for the chronology and evidence index, and record the choice in the file. Mixed-language artefacts cannot be reviewed by anyone who was not there.
- 02Index in the original language, so you can find a document by what it actually says rather than by what a translator later called it.
- 03Build the name table and glossary during indexing, not at the end. Retrofitting them means re-reading.
- 04Translate selectively and deliberately. Full-bundle certified translation is expensive and slow; translate what will be submitted, and work from the originals for everything else.
- 05Map translations to originals at paragraph level, so any assertion can be traced back to the source text in one step.
- 06Quote the original where the word is the issue. For a contested term, the Arabic belongs in the report next to the English.
One structural point worth stating plainly: translating a document and then extracting facts from the translation compounds two lossy steps, and the resulting reference points at the translation rather than at what the party actually wrote. Extracting from the original and translating the extracted facts keeps the citation honest.
Once the bilingual groundwork is done, the report itself follows the ordinary structure — see how to structure a legal case report.
This article is general information about professional practice and technology, not legal advice. Data protection and professional conduct rules differ by jurisdiction and change often — the position described here is as at August 2026. Check the rules that bind you, and your firm's own policies, before changing how you handle client material.
Keep reading
Workflow
How to Structure a Legal Case Report: A Step-by-Step Framework
Most case reports are rewritten not because the analysis was wrong, but because the structure was decided while writing. Here is a framework that settles it beforehand.
Workflow
5 Ways Paralegals Can Cut Case File Review Time Without Cutting Corners
Speed in file review comes from doing fewer passes over the same pages, not from reading faster. Five techniques that hold up when the file is 4,000 pages.