Legal Translation for Law Firms and In-House Counsel in the UAE
A law firm does not translate its own filings; it instructs. This page is written to the partner, the associate and the knowledge-management lead who send a matter out for translation and need it to come back admissible, confidential and consistent. The work you outsource — litigation bundles, disclosure sets, due-diligence rooms, enforcement files — is your clients' work, carried into another language under someone else's professional responsibility. We treat it that way: as your matter, translated to be filed and relied on, not merely rendered.
- A translation your firm can file — certified by a translator on the Ministry of Justice roll, not an internal draft
- Confidentiality built for privileged and NDA-covered matters, not bolted on afterwards
- One terminology across a whole matter — contracts, pleadings, exhibits and judgments in a single voice
- Work scoped to the file: litigation bundles, disclosure sets, due-diligence rooms and enforcement
- Dubai-based, UAE-wide service
- Arabic & English
- Clear guidance on every document
- Direct request, no middlemen
Admissibility is a status your firm cannot confer on itself
Most firms that instruct us have Arabic-English capability in the room. A senior associate reads a contract in both languages; a paralegal drafts correspondence in Arabic without a second thought. So the question is rarely whether the firm can understand the document. It is whether the version the firm produces can be filed. In the UAE, translation for the courts and government bodies is a licensed profession, and admissibility is tied not to accuracy alone but to the person who signs the rendering. A translation prepared by a bilingual member of your team, however faithful, is not something an onshore court, a notary or a registry will treat as a certified translation.
The framework behind that is recent and specific. The profession is governed by Federal Decree-Law No. 22 of 2022, in force since 2 January 2023, which replaced the older 2012 law. It builds a two-layer system: a translator must be registered on the roll held at the Ministry of Justice and separately licensed by the competent authority in the emirate. Registration is granted per language pair, runs in fixed terms, and requires the translator to take a legal oath before undertaking work. Since 2024, professional indemnity insurance is mandatory for translators and translation houses, and a 2025 schedule of administrative penalties attaches personal fines to breaches — practising after a registration lapses, working outside the licensed language pair, omitting the translator's name and registration number, or disclosing confidential information. The status, the oath, the insurance and the liability sit with the individual, not with any firm that instructs them.
Read as a procurement decision, this changes the shape of the choice. You are not buying language skill, which you already have. You are selecting a provider whose translators hold a status your filings require and your team cannot self-confer, and who will carry that status — and the personal responsibility that comes with it — on the documents you send into a court, a ministry or a deal. That is why in-house language ability and an outsourced certified translation are not substitutes. One helps you understand and negotiate; only the other lets you file.
Three things stay separate throughout this page, because a firm that blurs them ends up relying on an effect the system does not grant. There is general information about how translation works in the UAE. There are official requirements set by the authorities — Arabic as the language of the onshore courts, admissibility only with a certified translation, the licensing regime. And there is what we, at MANJAZ, actually do for the firms that instruct us: translate the full document through a registered legal translator, hold one terminology across the matter, and handle the file under confidentiality controls appropriate to privileged material. Where a requirement is emirate-specific or recently changed, we say so, and we point you to the receiving authority rather than presenting one court's practice as a national rule.
The vocabulary of an outsourced legal-translation relationship
- Registered legal translator
- A natural person entered on the roll held at the Ministry of Justice and licensed in the emirate, authorised to produce translations the courts and government bodies accept. The authority is personal: the translator signs, stamps and is accountable for the rendering.
- Translation house (dar tarjama)
- A licensed legal person registered on the same roll. It must work through registered translators and may not outsource certified work to unregistered ones. When your firm engages a house, the individual translator's registration still matters — it is what makes the document admissible.
- Per-language-pair registration
- A translator's authority is tied to specific language combinations, not granted in general. A translator registered for English-Arabic is not thereby authorised for French-Arabic. For a multi-language matter, the pair coverage of the people on your file is a question worth asking up front.
- The legal oath
- Under the executive regulations, a translator takes a legal oath before undertaking assigned duties. It is part of what distinguishes a certified legal translation from a private one: the rendering is produced under a sworn professional obligation, not merely a commercial promise.
- Professional indemnity insurance
- Since 2024, translators and translation houses must carry professional indemnity insurance covering losses from errors in their work, including breaches of confidentiality. For a firm, it means the translator's accountability is not only professional and disciplinary but financially backed.
- Certified vs sworn translation
- International clients often ask for a "sworn" translation. The UAE analogue is a registered legal translator who has taken the legal oath; "certified" abroad can mean only a signed statement of accuracy. When a foreign court or counterparty specifies a form, tell us — the two are not always equivalent.
- Translation memory and glossary
- A controlled record of how each defined term, party name and recurring phrase is rendered, reused across every document in a matter. It is the mechanism that keeps a thousand-page bundle internally consistent — and, for a firm, the reason a large matter reads as one instrument rather than many.
- NDA and data minimisation
- The contractual and operational spine of a confidential engagement: signed non-disclosure covering everyone who touches the file, and the discipline of sending only the material actually needed for the translation. Both matter more in the UAE because privilege, as common lawyers know it, is not recognised here.
- Prevailing language
- Where a bilingual contract diverges, the clause — or the law — that decides which text governs. Before the onshore courts, the Arabic version prevails regardless of a prevailing-language clause, which makes the accuracy of the Arabic a matter of legal effect, not presentation.
- Admissibility
- Whether a court, notary or registry will accept a document as filed. For foreign-language material it turns on a certified Arabic translation by a registered translator, the whole document rendered, names and figures consistent. Admissibility is what a firm is really buying — not words, but a document that will not be turned away at the counter.
The workstreams law firms send out, and the discipline each one needs
| Workstream | What is in the bundle | The translation discipline it needs |
|---|---|---|
| Litigation bundles and pleadings | Statements of claim and defence, memoranda, exhibits, correspondence relied on as evidence. | Certified Arabic for the onshore court; one glossary so party names and defined terms stay stable across the file. |
| Disclosure and discovery sets | High-volume, multilingual document sets for review and production, often under a deadline. | Consistent terminology at volume, controlled handling of privileged material, and no open machine translation. |
| Due diligence and M&A data rooms | Memorandum and articles of association, resolutions, licences, contracts, litigation and regulatory histories. | NDA-covered workflow, Arabic versions ready for any onshore filing, and terminology aligned to the deal documents. |
| Corporate and transactional | MOA and AOA and their annexes, board and shareholder resolutions, share transfers, financing documents. | Legal Arabic where a registry requires it — with annexes never dropped, since authorities ask for the document "and its annexes". |
| Enforcement and cross-border | Foreign and DIFC/ADGM judgments, arbitral awards, finality certificates, powers of attorney. | The whole judgment translated, the operative part matched term for term, seals and annexes reproduced. |
| Regulatory and investigations | Regulator correspondence, compliance submissions, internal-investigation records and interview notes. | Tight confidentiality, careful register, and terminology that does not shift between the regulator's language and yours. |
| Powers of attorney and authority documents | Litigation, corporate and property POAs, board authorisations, signatory mandates. | Exact scope of authority preserved; often notarised and attested in their own right before translation. |
| Expert reports and witness statements | Court-appointed and party expert reports, affidavits, and witness statements used in evidence. | Technical terms fixed once and reused; register kept faithful so a translated statement reads as the witness's own. |
Want this checked for your own document?
Your firm can read the document in both languages. What it cannot do is sign the version the court will accept — that signature belongs to a registered translator, and so does the responsibility.
Confidentiality without privilege: why the controls have to be contractual
For a firm trained in a common-law system, the first thing to understand about outsourcing sensitive material in the UAE is that legal professional privilege, as you know it, is not recognised here. There is no doctrine that shields lawyer-client communications from disclosure in the same way. What exists instead is a duty of professional secrecy, protected across several instruments — the Civil Code, the Penal Code, the Labour Law, the cybercrime rules and trade-secret protections — and, for personal data inside a legal matter, the Personal Data Protection Law of 2021. Confidentiality is real and enforceable; it simply rests on statute and contract rather than on a privilege you can assert.
That distinction has a practical edge. If a member of your team drops an NDA-covered draft into an open cloud translation tool, the exposure is not softened by a privilege that would keep the content out of reach — because there is no such privilege, and the act itself may breach the confidentiality obligations your firm owes its client. This is precisely why serious legal work is not run through consumer machine translation. The controls that replace privilege are contractual and operational: non-disclosure agreements binding everyone who touches the file, data minimisation so only what is needed is sent, controlled access, and vetted linguists rather than an anonymous pool.
So the confidentiality question a firm should ask a provider is not "do you keep things confidential" — everyone says yes — but "how." How far down the chain does the NDA reach; whether any subcontractor sees the file at all; how the material is transferred and stored; whether privileged content ever passes through an open engine; and who, by name and status, will actually work on the matter. Those are answerable, verifiable questions, and they are the ones that separate a controlled legal-translation workflow from a general commercial one.
Send us the matter — the languages, the volume, the deadline and the confidentiality terms — and we will come back with a scope, a terminology plan and the people, by status, who would work on it.
Brief us on a matterTerminology management is where a large matter is won or lost in translation
A single contract can be translated well by one careful linguist. A matter cannot. Once a file runs to a shareholders' agreement, a dozen resolutions, a bundle of pleadings and a stack of exhibits, the risk stops being the quality of any one sentence and becomes the consistency of all of them. The same defined term must render the same way on page 5 and page 500. A party's name, transliterated one way on the passport and another on the trade licence, must be reconciled to a single form. A statutory phrase with a fixed Arabic rendering must not drift into a loose paraphrase halfway through. Inconsistency is not an aesthetic flaw in a legal file; it is an opening.
It is an opening because the other side reads for contradictions. Where your Arabic renders a defined term two different ways, opposing counsel can argue the two documents mean two different things — that the obligation in the pleading is not the obligation in the contract, that the party named in the exhibit is not the party named in the claim. Courts, faced with an internal inconsistency in a translated file, do not resolve it in your favour by default. So the discipline that holds a matter together is not glamorous, but it is decisive: a glossary agreed at the outset, a translation memory that reuses approved renderings, and a review layer that checks the file against itself, not just against the source.
For a firm, there is a further payoff that outlasts the single matter. The glossary you build with a provider on one case becomes an asset for the next: your house style for entity names, your preferred renderings of recurring clauses, the client-specific terms you have already settled. A provider who keeps that record, and who applies it under the confidentiality terms you set, is not just translating documents; it is maintaining a shared terminology memory that makes each subsequent instruction faster, cheaper in effort and more consistent than the last. That continuity is one of the real reasons firms consolidate translation with a provider rather than spreading it across whoever is cheapest that week.
Three language regimes in one country — and the moments a document crosses between them
Onshore courts — Arabic, civil law
- Arabic is the language of the courts by statute. Practitioners cite the Civil Procedure Law for the rule that pleadings, evidence and judgments are in Arabic, and that a foreign-language document is admissible only with a certified Arabic translation by a registered translator.
- In a bilingual Arabic-English contract, the Arabic prevails onshore if the two diverge — regardless of a prevailing-language clause. Translation accuracy is therefore load-bearing on the substance of the deal, not on its presentation.
- Mainland proceedings can exceptionally run in English, but only by a specific decision under Article 5(2) of the 2022 Civil Procedure Law — not on request. The default remains Arabic, and firms plan for it.
DIFC and ADGM — English, common law
- These common-law courts conduct proceedings in English and require documents filed in English. ADGM applies English common law directly; the DIFC rules state plainly that proceedings and filings are in English.
- But Arabic returns at the boundary. Where a DIFC judgment is to be served outside the centre within the UAE, an agreed Arabic translation must be lodged within a short window, and enforcement outside the centre requires the judgment translated into Arabic for the Dubai execution judge.
- Even inside the free zone the Arabic requirement can reappear: the ADGM Notary Public requires documents in dual-language Arabic and English, the translation certified by a licensed legal translator. The lesson for a firm is to map the crossing points in advance.
Have a question about your case?
How an outsourced matter runs, from intake to version-controlled delivery
Intake and confidentiality framework
The engagement opens with your confidentiality terms, not ours: your NDA or one we sign, the scope of who may see the file, and any client-specific handling instructions. Nothing substantive moves before that frame is in place.
Secure transfer and data minimisation
You send the material through a secure channel, ideally only the pages actually needed for the translation. We confirm formats, identify what is in scope, and flag anything that should be attested or finalised before translation begins.
Scoping the bundle
We map the file: which documents, which language pairs, which need certified Arabic and which are for understanding only, and where the deadlines actually bite. For a large matter this scope is agreed with your team before work is committed.
Glossary and terminology sign-off
Before volume translation, we settle the terms that must stay fixed — defined terms, party and entity names, recurring clauses, client house style — and, where you wish, put the glossary to your team for sign-off. This is what keeps the whole file in one voice.
Translation by a registered legal translator
The work is carried out by a translator on the Ministry of Justice roll for the relevant language pair, personally responsible for the rendering, applying the agreed glossary and translation memory across every document in the matter.
Independent revision
A second linguist reviews the rendering against the source and against the rest of the file, checking that terminology is consistent, names and figures match, and the operative language of any judgment or contract is exact. Process standards such as ISO 17100 make this second-person step a defining feature.
Certification and assembly
The certified translation is stamped and signed by the registered translator, carrying the name and registration number the authorities look for, and assembled with the source so the file presents as one coherent instrument — seals, annexes and all.
Delivery and version control
You receive the file with clear versioning, so a later amendment to one document does not silently desynchronise the rest. For an ongoing matter, the glossary and memory are retained under your confidentiality terms for the next instruction.
Privileged material and open machine translation do not mix
It is worth stating plainly, because it is the most common quiet exposure in a busy practice: pasting NDA-covered or sensitive client material into a public machine-translation engine can itself breach the confidentiality obligations your firm owes. In many consumer tools, submitted text may be retained or used to improve the service, and once it leaves your control the exposure cannot be recalled. In the UAE this bites harder than in a privilege jurisdiction, because there is no privilege to keep the content out of reach if a dispute arises over how it was handled.
This is not an argument against technology. Translation memories, terminology tools and secure, access-controlled systems are exactly how a large matter is kept consistent. The line is between controlled tools operated under your confidentiality terms and open, public engines that treat your client's file as training data. A firm's diligence question is simple and answerable: does anything privileged ever pass through a public engine, and if not, how is that enforced across everyone on the file?
How to vet a legal-translation provider — a diligence checklist for the firm
- Confirm the individual translator on your file is on the Ministry of Justice roll — not merely that the agency holds a trade licence. An agency stamp over an unregistered translator's work is not what the courts accept.
- Check that the registration covers your language pair and is live at the moment of filing. Registration is per pair and runs in fixed terms; a lapsed or out-of-scope registration is a rejection risk.
- Ask about professional indemnity insurance. Since 2024 it is mandatory, and it is part of what makes the translator's accountability more than a promise.
- Require a signed NDA that reaches every person and any subcontractor who will touch the file — and ask, explicitly, whether the work is ever subcontracted at all.
- Ask how privileged and NDA-covered material is handled, and get a clear answer on whether anything passes through open machine translation.
- Probe the terminology process: is there a glossary and translation memory, agreed with you, applied across the whole matter and retained for the next one?
- Confirm that the whole document is translated — seals, stamps, signatures and annexes included — not just the body, since authorities read the whole file to accept it.
- Ask who carries personal liability for the rendering, and whether a second linguist independently revises it. A named, responsible translator and a review layer are the marks of a legal workflow.
Where firms slip when they outsource translation
The mistakeTreating an agency stamp as sufficient without confirming the individual translator is on the Ministry of Justice roll for your language pair.
The fixVerify the person, the pair and the live registration up front — the admissibility rides on the individual, not the letterhead.
The mistakeAssuming a bilingual associate's careful draft is filable, and discovering at the counter that it is not a certified translation.
The fixUse the in-house draft to understand and negotiate; route the filing version through a registered translator.
The mistakeRunning NDA-covered or privileged material through a public machine-translation engine to save time.
The fixKeep sensitive files inside a controlled workflow under your confidentiality terms; there is no privilege here to soften the exposure.
The mistakeFragmenting one matter across several providers, so the same term and party name drift apart between documents.
The fixConsolidate a matter with one provider holding one glossary and translation memory across the whole file.
The mistakeLeaving personal and entity names inconsistent across passport, Emirates ID, trade licence and translation.
The fixReconcile every name to one agreed form at the glossary stage, before volume translation begins.
The mistakeTranslating a document before it is final or attested, so a later change forces the translation to be redone.
The fixFinalise and, where needed, attest the source first, so the certified translation reproduces the document that will actually be filed.
The mistakeAssuming a DIFC or ADGM matter in English never needs Arabic, and being caught out at onshore enforcement or a notary.
The fixMap the crossing points in advance; plan the Arabic for the moment the document moves onshore or before a notary.
The mistakeForgetting that in a bilingual contract the Arabic prevails onshore, and treating the English as the operative text.
The fixHave the Arabic checked with the same rigour as the English — onshore it is the version that governs.
Which of these matters is on your desk?
A litigation partner is filing a commercial claim onshore where the contract, correspondence and evidence are all in English.
What is usually neededCertified Arabic translation of the pleadings and every foreign-language exhibit by a registered translator, held to one glossary, mindful that in a bilingual contract the Arabic prevails onshore if the versions diverge.
A corporate team is running cross-border M&A due diligence out of a DIFC entity, under a strict NDA.
What is usually neededA confidential, NDA-covered workflow for the data room — memoranda of association and their annexes, resolutions and contracts — with a shared glossary and Arabic versions prepared for any onshore filing that follows.
A disputes team holds a DIFC or ADGM judgment in English and needs to enforce it against assets onshore.
What is usually neededAn Arabic translation of the judgment and its supporting documents for the onshore execution track, prepared to the timing the rules require, the operative part matched exactly against the English original.
In-house counsel wants to standardise terminology across a portfolio of bilingual contracts for one client group.
What is usually neededA single glossary and translation memory built with your team and applied across the portfolio, so defined terms, entity names and standard clauses read the same in every contract and in any later dispute.
A dispute has produced a high-volume, multilingual disclosure set to review and produce under a court deadline.
What is usually neededA scoped, confidential workflow that separates what needs certified Arabic from what is for understanding only, keeps terminology consistent at volume, and never routes privileged material through an open engine.
A firm wants a standing confidentiality and terminology framework in place before the next urgent matter lands.
What is usually neededAn engagement set up in advance — signed NDA, secure transfer, an agreed glossary and named linguists whose registration you can confirm — so that when a deadline arrives, the framework is already there and only the file is new.
The language pairs behind a UAE firm's matters
- English ↔ ArabicThe core pair. English contracts, pleadings and evidence into Arabic for the onshore courts and registries; Arabic judgments, statutes and official documents into English for foreign clients, counsel and boards.
- French → ArabicContracts and litigation files from francophone civil-law jurisdictions arrive with their own legal vocabulary, reconciled into the UAE's Arabic terms for the onshore court.
- Russian → ArabicCommercial agreements, corporate records and litigation documents involving Russian-speaking parties, brought into consistent Arabic for filing and enforcement.
- Chinese → ArabicTrade, investment and corporate documents from Chinese-language counterparties, rendered into Arabic for UAE registration, banking and dispute work.
Not sure which route applies to your document?
Outsourcing legal translation: a firm's questions
Because admissibility in the UAE is tied to the person who signs, not to accuracy alone. Translation for the courts and government is a licensed profession, and only a translator registered on the Ministry of Justice roll — and licensed in the emirate — can produce a certified translation the courts, notaries and registries accept. Your associate's draft is invaluable for understanding and negotiating the document; it simply is not the version an onshore authority will treat as certified. Use the in-house reading to run the matter, and route the filing version through a registered translator.
Ask for the individual translator's Ministry of Justice registration and confirm three things: that it is the person who will work on your file, that it covers your specific language pair, and that it is live at the time of filing. An agency's trade licence is not the same as an individual's registration, and registration is granted per language pair and runs in fixed terms — a translator authorised for English-Arabic is not thereby authorised for another pair. Where you need certainty on a particular filing, confirm the requirement and the acceptable form of certification with the receiving authority.
With contractual and operational controls, because the UAE does not recognise common-law privilege — confidentiality here rests on statute and contract, protected across the Civil Code, Penal Code, Labour Law, cybercrime rules and, for personal data, the 2021 data-protection law. In practice that means a signed NDA reaching everyone who touches the file and any subcontractor, data minimisation so only what is needed is sent, secure transfer and storage, named and vetted linguists, and no privileged content passing through open machine translation. We put the framework in place before the first document moves, and we are happy to work under your NDA rather than only our own.
That is the core of doing legal translation at scale rather than one document at a time. We agree a glossary at the outset — defined terms, party and entity names, recurring clauses, your house style — and apply it through a translation memory across every document, with a review layer that checks the file against itself as well as against the source. The point is that a shareholders' agreement, the resolutions, the pleadings and the exhibits all read as one instrument, so the other side cannot argue that two of your documents mean two different things. The glossary is retained under your confidentiality terms, which makes each later instruction more consistent than the last.
Inside those courts, everything is in English — proceedings and filings alike. Arabic returns at the boundary. Where a DIFC judgment is to be served outside the centre within the UAE, an agreed Arabic translation must be lodged within a short window; and enforcing a free-zone judgment against onshore assets requires it translated into Arabic for the Dubai execution judge. Even the ADGM Notary Public requires dual-language Arabic and English documents. So choosing a free-zone forum reduces the Arabic requirement inside the case; it does not remove it at the points where the matter touches the onshore system. Mapping those crossing points early is part of what we help with.
Before the onshore courts, the Arabic prevails where the two texts diverge, and it does so even if the contract contains a clause naming English as the governing language. That is a direct consequence of Arabic being the language of the courts. The practical implication for a firm is that the Arabic side of a bilingual contract is not a courtesy translation — it is the text that will govern in an onshore dispute, and it deserves the same review rigour you give the English. We translate and, on request, review both sides so a divergence does not surface for the first time in litigation.
Yes, and the challenge there is as much management as language. A large multilingual set has to be triaged — separating what genuinely needs certified Arabic from what is translated for understanding and review only — kept consistent in terminology at volume, and handled so that privileged material never leaves a controlled workflow. We scope the set with your team, agree the glossary before volume work begins, and keep clear version control so a late amendment to one document does not silently desynchronise the rest. Deadlines are planned around the court's timetable rather than promised in the abstract.
We plan the work around your deadline rather than quoting a fixed turnaround in the abstract, because the honest answer depends on the volume, the language pairs and the state of the source documents. What we commit to is a clear scope up front, an agreed sequence for a large bundle so the time-critical documents are ready first, and early flags on anything — an unattested source, a missing annex — that could delay the file. Tell us the deadline and the bundle when you brief us, and we will tell you what is realistic and how we would sequence it.
Yes. Many firms prefer to put their own NDA and engagement terms in place, and to set up a standing arrangement so that the confidentiality framework, secure transfer channel and agreed glossary already exist when an urgent matter lands. That way each new instruction is just a new file on a ready track, not a fresh negotiation. We are comfortable operating under your paper, and the retained glossary and translation memory make the relationship more efficient over time.
No — they answer different questions, and a serious provider should be clear about both. ISO 17100 is an international standard for translation-service processes; it addresses how the work is organised, including mandatory revision by a second person. Ministry of Justice registration is a UAE legal-admissibility question: whether the translator is authorised to produce a certified translation the courts and authorities will accept. A process standard does not substitute for registration, and registration says nothing about process. For a firm, the first controls quality; the second controls whether the document can be filed at all.
The registered translator carries personal, professional responsibility for the accuracy of the rendering — they sign and stamp it, their name and registration number appear on it, and since 2024 they must hold professional indemnity insurance covering losses from errors in their work, including breaches of confidentiality. The recent penalty regime also attaches personal administrative fines to specific breaches. This personal accountability is one of the practical reasons the certified-translation system exists: responsibility rests with an identifiable, insured, sworn professional, not diffused across an anonymous process. Acceptance by any particular authority is a separate matter and can never be guaranteed in advance, but a registered translator translating the full document removes the most common grounds for rejection.
Official references
- UAE Ministry of Justice — Translator Registration (Experts & Legal Translators services)
- u.ae — The Official Portal of the UAE Government: Civil cases
- DIFC Courts — Rules of the DIFC Courts, Part 2
- ADGM — Courts Frequently Asked Questions (incl. Notary Public)
- UAE Ministry of Foreign Affairs — Attestation of Official Documents and Certificates
- UAE Legislation — Federal Decree-Law No. 22 of 2022 Regulating the Translation Profession
This page is general information about translation services, not legal advice. Requirements are set by the authority receiving your document and can change — always confirm with the receiving authority or ask us to check for your specific case.
Request Legal Sector Translation
Send the document and we confirm the exact certification the receiving authority expects.


