How Legal Translation Works in Dubai: Steps and Turnaround
Most translation websites reduce their process to three icons and a promise. This page walks through what actually happens between the moment you send a document and the moment the finished translation reaches you — the staged checks you never see, the ones that cannot be skipped, and what you should expect from us at every step.
- Every translation is compared line by line against the source by a second linguist
- Nothing on the page is silently dropped — seals, stamps, footers and margins included
- Names are locked to the spelling on your passport, Emirates ID and trade licence
- Confidential handling aligned with the UAE Personal Data Protection Law
- Dubai-based, UAE-wide service
- Arabic & English
- Clear guidance on every document
- Direct request, no middlemen
Getting a legal translation in Dubai takes four steps: send clear scans of your documents through the request form; receive a fixed quote and an expected turnaround; the translation is prepared and reviewed by a legal translator; you receive the stamped translation as a PDF and, when needed, a hard copy. Urgency, volume and language pair are what change the turnaround.
Why we publish our working process
Ask a translation office how it works and you will usually get a version of the same answer: we translate, we check, we deliver. That answer hides everything that matters. Quality in legal translation is not a talent living in one person's head; it is a sequence of separate checks, done by different people, in a fixed order. A skipped stage is invisible in the file you receive — and very visible at the counter where you submit it.
This page contains three different kinds of statement, and it keeps them apart deliberately. Some things here are official requirements set by UAE authorities — for example, that documents presented to UAE courts must be in Arabic or be translated by a legal translator approved by the UAE Ministry of Justice. Some are published professional models the industry works to. And some are simply how we run our own workshop. Where a rule comes from an authority, we say which one; where something is our own practice, we say that too.
We publish the pipeline for a simple reason: the difference between a translation accepted first time and one sent back rarely lies in the elegance of the language. It lies in whether a name matches an Emirates ID, whether a faded stamp was described or guessed at, whether the certification block carries what the receiving authority expects, and whether a second linguist actually compared the target against the source. Those are process questions, and a process can be shown.
From intake to delivery: nine stages
Intake and scoping
We read before we quote. The team identifies the document type, the direction of translation and — most importantly — the receiving authority, because the recipient defines what a compliant deliverable looks like. Legibility is checked page by page now, so a missing annex or a cropped stamp is raised with you today, not on deadline day.
Written terms and confidentiality
Scope, delivery format and data handling are agreed in writing before work starts. Where your documents contain personal data this is more than courtesy: UAE data-protection law contemplates written terms between the party who owns the data and the party who processes it. Confidentiality undertakings are signed where the matter calls for them.
Reference capture: names and terminology
Before a word is translated we collect the fixed points: personal names exactly as spelled on passports and Emirates IDs, company names exactly as on the trade licence, prior approved translations, and defined terms from earlier documents in the same matter. These go into a matter glossary that binds everyone who touches the file.
Translation, by one accountable linguist
A qualified translator works the document in full and performs their own check. Where the destination is a UAE court, notary or government body, the law shapes this stage: the profession is regulated by federal decree-law, the translator is registered per language pair, works personally, and their name and registration number accompany the document.
Revision: the second linguist
A different linguist compares the translation against the source, line by line — figures, names, clause references and omissions included. This is the stage the industry's published standard makes mandatory, and the one we treat as untouchable: the drafting translator never revises their own work, because a self-check is not independence.
Subject review, where the matter needs it
Some documents carry a register of their own — medical reports, audited financials, technical exhibits. Where the subject matter warrants it, a monolingual reviewer reads the finished translation for fitness in that domain: does this read the way a clinician, an auditor or an engineer would write it?
Layout and bidirectional typesetting
The translation is set to mirror the structure of the source — headings, tables, stamps and their positions — so a receiving officer can check page against page. Then every number, date, case reference and Latin-script name inside Arabic text is re-read, because mixed-direction text can silently reorder them.
Final verification against your specifications
Before release, the deliverable is checked against what was agreed at intake: completeness, page correspondence, the certification block the destination requires, and the agreed file formats. This is a checklist pass, not a re-read — its job is to catch the gap between a good translation and a compliant deliverable.
Delivery, records and retention
You receive the translation in the agreed form, with the translator's declaration where the destination calls for one. Afterwards the file does not drift: registered translators are required to keep proper work records, and beyond that statutory layer, retention and deletion follow what we agreed with you in writing.
Translate, revise, verify: the staged model we work to
There is a published international answer to the question of what a professional translation service looks like. ISO 17100, issued in 2015 as the successor to the European standard EN 15038, describes translation as a staged process with named human roles — translator, reviser, reviewer, proofreader, project manager — rather than one undifferentiated job.
The sequence matters more than the labels. First, translation with the translator's own check. Then revision: a bilingual, line-by-line comparison of the target against the source, carried out by a second person — the step the standard makes mandatory. Then review, a monolingual assessment for the agreed domain, and proofreading, both optional under the standard. Finally, verification that the deliverable matches the agreed specifications before release. The detail buyers rarely hear is the important one: the translator's self-check does not substitute for independent revision.
We describe this model because it is the model our workflow follows — and we describe it plainly, without wrapping it in a badge. This page makes no claim to any certificate. It also helps to separate two questions that get blended in Dubai: whether a translation is admissible before UAE authorities is a licensing question, answered by the Ministry of Justice roll; whether it was produced by a disciplined process is a quality question, answered by how the provider actually works. A serious provider must answer both, and neither answer substitutes for the other.
One more boundary, stated honestly: work delivered under that staged model is human translation. Raw machine translation with post-editing sits outside the scope of the standard — a separate framework, ISO 18587, exists for it. So when a provider tells you a document went through translation and revision, machine output with a cleanup pass is not what those words mean.
Want this checked for your own document?
A legal translation is finished when a second linguist has compared every line against the source — not when the first draft reads well.
The vocabulary of the workshop
- Revision
- A bilingual comparison of the translation against the source by a second linguist, covering meaning, omissions, figures and terminology. The mandatory quality step in the staged model.
- Review
- A monolingual read of the finished translation by someone who knows the domain, asking whether the text is fit for its agreed purpose — clinical, financial, technical or legal register included.
- Proofreading
- A narrower, pre-delivery check of surface mechanics: spelling, punctuation, typography. Useful, but never a substitute for revision against the source.
- Final verification
- The last gate before release: confirming the deliverable matches the agreed specifications — completeness, format, certification block and page correspondence.
- Matter glossary / termbase
- The approved terminology for your matter: defined terms, entity names as registered, spellings locked to identity documents, and terms that must not be translated at all.
- Translation memory
- A bilingual store of previously approved sentence pairs from your own files. Its value in legal work is continuity: the fifth contract in a series speaks the same language as the first.
- Transliteration
- Rendering a name in the other script rather than translating it. The highest-risk operation on the page: one letter away from the passport spelling is enough for a counter to send a document back.
- Translator's declaration
- The signed block confirming the translation is accurate, with the translator's identifying details. What it must contain is set by the receiving authority, not by the translator.
- Bidirectional text
- Text mixing right-to-left Arabic with left-to-right digits and Latin names. Its display order is governed by a formal Unicode algorithm — which is why it needs its own check.
Terminology control: the same clause stays the same clause
Legal documents rarely travel alone. A shareholder agreement follows a memorandum of association; a judgment cites the contract it rules on; the fifth amendment must echo the first four. The fastest way to manufacture doubt in a reader — a judge, a counterparty, a registrar — is to let one defined term arrive in three different Arabic renderings across documents that belong together.
Our answer is unglamorous and effective: a glossary per client and per matter, built at intake and enforced at revision. It records how each defined term is rendered, which entity names must appear exactly as the trade licence prints them — the registered legal name, never the marketing name — and which elements are not translated at all, such as trademarks or statutory titles with fixed renderings.
Personal names get the strictest treatment, because transliteration is where most counter-level rejections are born. There is no single correct Arabic spelling of a Latin-script name, or vice versa; there is only the spelling already on your passport, Emirates ID or residence file. We capture that spelling before translation begins, the glossary locks it, and both the reviser and the final verification confirm it survived every page.
Translation memory sits behind all of this as a continuity asset, not a discount lever. For repeat legal clients it means the wording your counterparties accepted last year is the wording they will see this year. It also raises a question we answer plainly when asked: memories and glossaries are data about your matters, so where they are stored and who can open them is a confidentiality decision, handled under the same rules as the documents themselves.
When the source is not clean: five real situations
A twenty-year-old certificate arrives as a dark phone photo, with a faded circular seal
What is usually neededWe ask first for a flat, complete scan of the original at proper resolution — most illegibility is created by the capture, not the document. Where the original genuinely cannot be improved, we translate what is legible, describe what is not, and tell you before submission that the receiving authority may query it. What we never do is guess.
The fifth agreement in a series lands, and the first four used carefully negotiated defined terms
What is usually neededThe matter glossary and translation memory are loaded before drafting starts, so party names, defined terms and recurring clauses reuse the wording your earlier documents established. The reviser then checks consistency in two directions: against the source, and against the earlier files.
A document set contains medical records and family-court papers
What is usually neededAssignment narrows to the people who must see the file, transfer moves off open email into a secure channel, and written confidentiality and processing terms are put in place with a defined retention position. Health data carries its own federal legislation in the UAE on top of the general data-protection law, and we treat it accordingly.
An Arabic contract must be produced alongside the English original, for signature by both parties
What is usually neededThe Arabic mirrors the original clause numbering and structure so both columns read in parallel; clause cross-references, figures and Latin-script party names get the bidirectional check; and the parties should record which language prevails — a point to settle with your legal advisers before signature, not after a dispute.
A litigation bundle needs to move faster than the calendar allows
What is usually neededWe are honest about what compresses and what does not. Setup, sequencing and parallel handling of independent documents compress well. Independent revision and final verification do not — removing them does not speed the process up, it moves the delay to the courtroom. If a deadline cannot be met with the checks intact, we say so at intake.
What we do with what cannot be read
If a stamp, seal or signature cannot be read, the translation says so — in a bracketed note that describes the element instead of inventing its content. An invented name on a court document is a serious defect; an honest note is a professional statement. This notation is our professional practice, not a wording any UAE authority prescribes, and where an illegible element matters to your submission we flag the risk before you file, so the receiving authority's questions never take you by surprise.
The same principle covers everything else on the page: seals, stamps, letterhead, footers, handwritten margin notes, barcodes and the back of every sheet are accounted for in the translation — rendered where legible, described where not. And one related boundary: we do not reproduce signature or seal images in a way that could make the translation pass for an original document. A translation represents the source; it must never impersonate it.
Have a question about your case?
Layout mirroring and the direction problem
Here is an honest sentence you will rarely find on a translation website: no UAE authority we can cite publishes a rule requiring a translation to visually replicate the layout of the source document. We mirror layout anyway, and the reason is practical. A translated document whose headings, tables and stamp positions correspond page for page to the original lets the officer receiving it verify one against the other in minutes. Lose that correspondence and you have handed a stranger a puzzle — and puzzles get sent back.
The second half of typesetting is invisible until it fails: direction. Arabic runs right to left, but the digits inside it run left to right, and English names, case numbers and abbreviations keep their own direction inside an Arabic sentence. The order all of this displays in is not a matter of the typist's care — it is governed by a formal specification, the Unicode Bidirectional Algorithm, and text that ignores how that algorithm behaves can reorder itself between the file you wrote and the file the court opens.
The casualties are always the items that matter most: passport numbers, IBANs, dates, case references, plot numbers, Latin-script party names. Numbers and punctuation are directionally ambiguous — they take their direction from context — and paired brackets are notorious for flipping in mixed-direction runs. A scrambled case reference in a memorandum is not a cosmetic blemish; it points the court at the wrong file.
Dates deserve their own sentence. UAE documents move between Hijri and Gregorian calendars, and between day-month and month-day conventions. A careless reformat that swaps day and month produces a date that is perfectly plausible and entirely wrong. Our rule is that every date is transcribed, not recalculated, and the revision stage re-reads each one against the source.
This is why the pipeline gives typesetting its own stage with its own check. After layout, a linguist re-reads every figure, reference and name in final form — in the file format you will actually submit — because direction problems have a habit of appearing only in the final rendering.
Stage one begins the moment your documents arrive. Send them with the receiving authority named, and we will come back to you with a scoped, written plan.
Request a translationWhat to send us, to get it right the first time
- Flat, complete scans rather than cropped phone photos — with every edge, stamp, barcode and QR code inside the frame
- Both sides of every page, and every schedule, annex or attachment that belongs to the document
- Personal names exactly as spelled on passports and Emirates IDs — a photo of the ID page beats a typed guess
- Company names as printed on the trade licence, plus the licence itself where entities appear in the document
- The receiving authority and country, because the certification block and format are defined by the recipient
- Any prior approved translations, glossaries or defined-term lists from the same matter
- The attestation status of the document, so translation and attestation happen in the right order for your destination
- Your deadline and preferred delivery format — including whether a signed hard copy is needed
The short list of things that actually get translations rejected
The mistakeA name transliterated differently from the passport, Emirates ID or trade licence — the single most common counter-level rejection.
The fixSpellings are captured at intake from the identity documents themselves, locked in the matter glossary, and re-checked at both revision and final verification.
The mistakeA translation destined for a UAE court or notary produced by someone not registered on the Ministry of Justice roll.
The fixCourt- and notary-bound work is produced under a registered legal translator whose name and registration number accompany the document, as the profession's law requires.
The mistakeOnly the body text translated — stamps, seals, footers, marginal notes and the back of the page silently missing.
The fixEvery element on every side of every sheet is rendered or described. Illegible elements are marked as such — never invented, never dropped.
The mistakeA certification block that does not carry what the destination requires — formats differ between authorities and countries.
The fixThe block is built to the recipient's stated rule. DIFC Courts service rules, for instance, require the translator's statement of correctness with name, address and qualifications; other destinations ask for different elements, so we confirm per destination.
The mistakeTranslation and attestation done in the wrong order, so the translation no longer reflects the final attested original.
The fixSequencing is confirmed at intake against the destination's requirements. Attestation validates signatures and seals, translation renders content — two different steps whose order depends on where the document is going.
The mistakeFigures, dates and case references scrambled inside Arabic paragraphs by unhandled bidirectional text.
The fixA dedicated typesetting check re-reads every number, reference and Latin-script name in the final file format before release.
The mistakeAn error in the source document quietly corrected in the translation — a well-meaning act that misrepresents the source.
The fixThe translation reflects the source as it stands. Discrepancies we notice are flagged to you separately, so you can correct the original with its issuer where needed.
Confidentiality as an operating system, not a sentence
The documents that reach a legal translator are among the most sensitive things a person or company owns: divorce papers, medical files, shareholder disputes, unannounced transactions. A sentence on a website promising discretion is not a control. Controls are specific: files are assigned on a need-to-know basis, so the people who can open your documents are the people working on them; transfer happens over secure channels rather than long open email chains; and retention ends in deletion on the schedule we agreed, not in an archive that outlives its purpose.
Confidentiality is also a statutory matter in this profession, in two distinct layers. The law regulating translators in the UAE places a duty of confidentiality on the registered translator personally, alongside the duties to work accurately and to perform assignments personally. Separately, the UAE has a federal Personal Data Protection Law — Federal Decree-Law No. 45 of 2021, in effect since early 2022 — governing the processing of personal data through electronic systems, inside and outside the country, with conditions for consent, correction, restriction of processing and cross-border transfer. A federal Data Office stands behind it as regulator.
That law shapes how a translation engagement should be papered. When you send us documents containing personal data, you are — in the law's vocabulary — the controller, and the provider processes that data on your instructions. The framework contemplates written processing terms between the two, covering what is processed, why, for how long, and with what security. We treat that paperwork as part of the service, not an exotic extra, and you should expect the same from any provider who handles your files.
One more honest wrinkle: the UAE runs more than one data-protection regime. Alongside the federal law sit the DIFC's own Data Protection Law of 2020, Dubai's data legislation, and a dedicated federal law for health data in ICT systems. Which regime governs your documents can depend on where your entity is established, so we confirm the applicable rules for each engagement rather than assuming one law fits all.
And the question more clients ask every year: are the files put into AI tools? Our position is a data-handling position. Client documents are not pasted into public machine-translation or public AI services, because doing so is a disclosure to a system whose storage, access and reuse you have not agreed to. Any technology that touches your text must pass the same three questions as any subcontractor: where is the data stored, who can access it, and what has been agreed with you.
What UAE authorities require, and what good practice adds
Set by authorities: the admissibility layer
- Documents presented to UAE courts must be in Arabic or be translated by a legal translator approved by the UAE Ministry of Justice
- The translation profession is regulated by federal decree-law: registration per language pair, personal performance of the work, and a statutory duty of confidentiality
- The registered translator's name and registration number accompany the documents they produce
- Registered translators take a legal oath and carry professional liability insurance under the profession's rules
- Where a recipient defines a certification format, that format is binding — DIFC Courts service rules, for example, specify the translator's statement, name, address and qualifications
Added by professional practice: the quality layer
- Independent revision of every translation by a second linguist, following the staged model of the international standard
- A matter glossary that locks names to identity documents and defined terms to earlier filings
- Layout mirroring, so the receiving officer can verify translation against source page by page
- A dedicated bidirectional typesetting check on figures, dates, references and Latin-script names
- Documented final verification against your agreed specifications before release
- Need-to-know assignment, secure transfer, and an agreed retention and deletion position
Not sure which route applies to your document?
Questions clients actually ask about the process
Yes, and not as a courtesy skim. Revision is a distinct stage in which a second linguist compares the translation against the source line by line, including figures, names and omissions. The drafting translator never revises their own work. On urgent jobs we compress preparation and run independent documents in parallel — the revision stage itself is not negotiable.
No. Client files are not pasted into public machine-translation or public AI services. Pasting a confidential document into a public tool is a disclosure to a system whose storage and reuse you never agreed to. Where technology assists our workflow, it must satisfy the same tests as any subcontractor: known storage, controlled access, and terms agreed with you.
The assigned team only: the translator, the reviser, and where needed a domain reviewer and a project coordinator. Sensitive matters are staffed on a need-to-know basis, and confidentiality is not only our policy — the law regulating the profession places a personal duty of confidentiality on the registered translator, and health data carries its own federal legislation.
It will mirror the original's structure — headings, tables, stamp positions, page breaks — because that makes verification faster for the officer receiving it. We say plainly that this mirroring is professional practice rather than a rule any UAE authority publishes. What is added on top is whatever the destination requires: typically the translator's declaration and identifying details.
Every seal, stamp and signature is accounted for: translated where legible, described in a bracketed note where not. We do not guess at faded text, and we do not reproduce signature or seal images in a way that could let the translation pass for an original. If an illegible element could matter to your submission, we tell you before you file.
Sometimes, and we will tell you when it is not enough. The recurring problems with phone photos are cropped edges, cut stamps, glare over security features and unreadable QR codes — defects usually discovered at the submission counter, which is the worst place to discover anything. Where the photo endangers acceptance, we ask for a flat scan before we begin.
No — and that answer protects you. A translation must reflect the source as it stands; silently improving it makes the translation misrepresent the document it certifies. What we do instead is flag the discrepancy to you separately, so you can have the issuing authority correct the original where it matters.
We ask for the identity documents at intake and copy the spelling from them, character by character, into the matter glossary. The reviser checks every occurrence against that glossary, and final verification checks it again. One inconsistent letter across a set of documents is exactly the kind of defect this pipeline exists to catch.
Two layers again. The profession's rules require registered translators to keep proper records of their work, and we honour that layer. Beyond it, retention is what we agree with you in writing: how long files and translation memories are kept, and when they are deleted. UAE data-protection law gives personal data defined protections, and our retention terms are written to respect them.
Parts of it, honestly, yes: intake, preparation and typesetting can be compressed, and independent documents can move through translation and revision in parallel with more hands. What we do not do is drop the second linguist or the final verification to buy speed — the time saved reappears, with interest, at the receiving authority's counter. We would rather tell you at intake what is achievable.
Turnaround depends on the document's length, the language pair, formatting and whether attestation steps must precede translation. A short standard certificate moves faster than a multi-page contract or court bundle that needs terminology research and a second review. When you request a quote, MANJAZ confirms a delivery estimate for your specific file before work begins, so plan ahead when a filing deadline is involved.
Urgent handling can be requested, and MANJAZ will tell you frankly at intake whether your document can be prioritised and what delivery estimate is realistic. Feasibility depends on length, language pair, translator availability and the review step, which is never skipped for legal work. Share the deadline and the receiving authority when you send the file so scheduling reflects the actual filing date.
For most translations a legible, complete scan or photo is enough, because the translator works from the document's content and reproduces its stamps and seals as they appear. Some receiving authorities, however, ask that the translation be attached to the original or a certified copy, or that the original be sighted. Tell us the destination and we will advise before you visit.
Both are available. Legal translations for onshore courts and government departments are normally delivered as stamped, signed hard copies attached to a copy of the source document, since that is what most authorities file. A PDF scan of the stamped translation can be sent for your review or for authorities that accept electronic submissions. Confirm which format the receiving body requires before ordering.
Yes. Stamped hard copies can be delivered by courier to offices and homes across Dubai, including Business Bay, or collected in person, and a scanned PDF is usually sent ahead so you can check the file. Delivery timing depends on the courier and location and is confirmed when the job is scheduled. Deliveries to other emirates and abroad are arranged on request.
Official references
- u.ae — The Official Platform of the UAE Government: Civil cases
- u.ae — Data protection laws
- UAE Ministry of Justice — services for experts and legal translators
- DIFC Courts — Rules of the DIFC Courts, Part 9: service of documents
- UAE Ministry of Foreign Affairs — attestation of official documents
- Unicode Consortium — UAX 9: the Unicode Bidirectional Algorithm
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.
Ready to translate your document?
Send the document and we confirm the exact certification the receiving authority expects.