Skip to main content
ع
Where a tender, a JV and an HSE library all pass through two languages

Oil & Gas Translation for the UAE Energy Sector — ADNOC Supplier Qualification, EPC Contracts and HSE Documentation

An energy project in the UAE is built on paper long before it is built in steel. A contractor earns the right to bid by qualifying as a supplier; it wins by submitting a tender pack that answers a technical specification clause by clause; it delivers under an EPC contract wrapped in method statements, risk assessments and permits-to-work; and it shares risk through a joint-venture agreement that some authority will one day read. Much of that paper is generated in English by international engineering firms, and much of it must be read, scored, notarised or filed by an Arabic-language authority — from the ADNOC Supplier Hub to an onshore notary. This page is about the translation that carries an energy document across that line.

  • The full supplier-qualification file prepared for the register — trade licence, audited financials for ICV, quality certifications and ownership papers
  • Long EPC and technical document sets kept terminologically consistent from the master contract to the last annex
  • HSE plans, method statements, risk assessments and incident reports rendered for the reader who must act on them
  • Onshore and free-zone versions handled for what each one is for — the ADGM English contract and its Arabic filing
  • Dubai-based, UAE-wide service
  • Arabic & English
  • Clear guidance on every document
  • Direct request, no middlemen
The controlling idea

In the UAE energy sector, translation is procurement and compliance infrastructure, not a finishing step

An oil and gas file is rarely a single document. It is a supplier-qualification pack lodged on a hub, a tender submission measured against a specification, a library of health-and-safety procedures that a site will run on, and a joint-venture or shareholders' agreement that binds companies across borders. Each of those has a different destination and a different reader. The ADNOC Supplier Hub scores a qualification. A principal or EPC contractor evaluates a bid. A safety officer works from a method statement. An onshore notary or court reads a joint-venture agreement. Translation is what lets one document satisfy readers who do not share a language.

It helps to keep three kinds of statement apart on this page. There is general information about how the sector procures and builds. There are official requirements set by authorities — that documents going before an onshore court or a UAE government body must be in Arabic, that a foreign-language document is only admissible with a certified legal translation, that attestation certifies a seal and not a translation. And there is what we, at MANJAZ, actually do: translate the whole instrument against its source, hold every term, unit and figure identical across a long set, and hand each document back prepared for the counter it is going to. When those three blur, a contractor relies on a promise that no authority ever made.

What sets energy work apart from a one-off certificate is scale and repetition. A single EPC package can run to thousands of pages across a contract, its schedules, drawings, data sheets and HSE annexes, and the same defined terms recur throughout. If a valve, a pressure rating or a party's name is rendered one way in the contract and another way in a schedule, the inconsistency itself becomes a commercial problem — a query at bid evaluation, an ambiguity in a claim, a mismatch a checker flags. The discipline the sector needs is less about any single sentence and more about keeping a large, evolving body of documents saying the same thing in both languages.

The sector's centre of gravity is Abu Dhabi, and that shapes where the language line falls. ADNOC and its group companies run the largest supplier and contractor ecosystem in the country; the energy free zones and the ADGM common-law jurisdiction sit in the same emirate; and Abu Dhabi's own courts have their own rules on when a foreign-language document must be translated. A contractor moving between an English EPC contract, an ICV certificate built on audited accounts, and an onshore filing is crossing between language regimes several times over. Knowing which document needs Arabic, which can stay English, and which needs both is half the work.

The documents an energy translation file runs on, and their Arabic names

In-Country Value (ICV)
A supplier-scoring programme in the Abu Dhabi energy ecosystem, introduced by ADNOC in January 2018. A supplier's ICV certificate is built from its audited financial statements and reflects local spend, manufacturing, investment, Emiratisation and related components. A supplier without a certificate is scored zero for ICV in the tender, so the certificate — and the accounts behind it — sit at the centre of the qualification file.
ADNOC Supplier Hub and prequalification
The portal through which a company registers to supply ADNOC and, for relevant categories, passes a prequalification stage assessing technical, HSE, financial and operational capability. Trade licence, quality certifications, tax registration, audited accounts and ownership details are typical supporting documents — several of which arrive for translation.
EPC contract
Engineering, Procurement and Construction — the backbone agreement of a large energy project, under which one contractor designs, buys and builds. It rarely travels alone: schedules, technical specifications, drawings, a scope of work and HSE requirements are annexed to it, and the defined terms must be rendered identically across the whole set.
Tender / bid pack
The documents a contractor submits to win work: a technical proposal answering the specification, a commercial offer, compliance statements, and supporting certificates. A bid is read clause against clause, so a translated proposal that drifts from the specification's wording invites queries and can cost marks.
Technical specification and data sheet
The clauses and tables that define what must be supplied and to what standard — materials, tolerances, pressure and temperature ratings, testing regimes. Numbers and units carry the meaning here, and a single misplaced decimal or loosely converted unit is a substantive error, not a stylistic one.
Method statement and permit-to-work
Site-level safety documents: a method statement sets out how a task will be done safely, and a permit-to-work authorises a specific job under stated controls. They are working instruments a crew acts on, so clarity and exact terminology matter more than elegance.
HSE management system and OSHAD framework
Contractors in the Abu Dhabi energy sector are expected to run an HSE management system aligned to the emirate's Occupational Safety and Health System Framework (OSHAD-SF) codes of practice and to ADNOC's own HSE standards. Delivery generates a continuous stream of plans, risk assessments, permits and incident reports — a recurring translation workload.
Joint venture / shareholders' agreement
The agreement by which an international company and a local partner share ownership and risk in a project vehicle. It may be governed by the law of a common-law free zone and stay in English there, yet still need a certified Arabic version when it is registered, notarised or litigated onshore.
Audited financial statements
The accounts an external auditor has examined and signed. Beyond their ordinary corporate uses, they are the basis of an ICV certificate, and a new certificate is expected after new audited figures — which is why their translation recurs on a schedule rather than once.
Certificate of origin and commercial invoice
For long-lead equipment brought into the country, procurement generates customs paperwork — a certificate of origin from the exporting chamber of commerce and a commercial invoice among them. Where these arrive in a foreign language, a certified Arabic translation is what lets them clear and match the rest of the file.
General information

Qualifying as a supplier: the ICV certificate and the accounts behind it

Before a company can win energy work in Abu Dhabi, it usually has to qualify as a supplier. Registration runs through the ADNOC Supplier Hub, and for many categories a prequalification stage follows, testing whether the company is capable technically, financially and on health and safety. The supporting documents an applicant assembles — a trade licence, quality certifications, a tax registration number, audited financial statements and ownership details — are the same documents that, when they exist only in a foreign language, need a certified Arabic rendering to sit correctly in the file.

The In-Country Value certificate is the piece most particular to this sector. ADNOC introduced the ICV programme in January 2018 to measure and reward the value a supplier keeps inside the national economy, and a supplier without a certificate is scored zero on that dimension of a tender. The certificate is built from the company's audited financial statements — which is why the accounts, and any translation of them, matter beyond the finance department. Reporting around the programme indicates a certificate is valid for a limited period and that a revised certificate is expected after fresh audited figures, so the exercise repeats rather than settling once. The exact validity window and revision timing are best confirmed against ADNOC's own published material.

Two cautions belong here. First, ADNOC evaluates bids on a combination of price and ICV, but the precise weight given to the ICV score is something to confirm against ADNOC's own published material rather than a figure repeated second-hand. Second, qualifying with ADNOC is not the end of it: a contractor working under a principal or an EPC contractor must also satisfy that party's requirements, which cascade the same technical, financial and HSE expectations down the supply chain. The translation demand follows the same cascade — a subcontractor often has to present, in the principal's language, documents originally written in its own.

Want this checked for your own document?

The document journey from registering as a supplier to signing a contract

  1. Register and prequalify

    The company registers on the supplier hub and, where required, prequalifies. The trade licence, ownership papers, quality certifications and audited accounts are gathered; any that exist only in a foreign language are translated so the file reads consistently.

  2. Build the ICV certificate

    The audited financial statements are certified into an ICV score by an approved certifying body. Where the accounts or supporting records are foreign-language, their certified translation is prepared to accompany the exercise, and the same is repeated when new audited figures arrive.

  3. Respond to the tender

    The technical proposal is drafted to answer the specification clause by clause, alongside the commercial offer and compliance statements. Translated bid text is aligned to the specification's own terminology so the two read as one conversation, not two.

  4. Attach technical and HSE annexes

    Data sheets, drawings, method statements, risk assessments and HSE plans are annexed. A shared glossary keeps a valve, a rating or a hazard named the same way from the master document to the last appendix.

  5. Negotiate the contract and the JV

    On award, the EPC contract and any joint-venture or shareholders' agreement are settled. Where a bilingual contract is agreed, the two versions are reconciled so they say the same thing before signature, not after a dispute.

  6. File or notarise onshore where needed

    If the arrangement is registered, notarised or litigated before an onshore authority, a certified Arabic version is prepared for that step — even when a parallel English version governs inside a free zone.

A long EPC set is not judged sentence by sentence but as a whole: the test is whether a valve, a party and a pressure rating are named the same way on page nine and page nine hundred.

The terminology principle behind energy-sector translation

Health, safety and environment: the document set that never stops

Health, safety and environment is where the translation workload is heaviest and most continuous. A contractor in the Abu Dhabi energy sector is expected to run an HSE management system aligned to the emirate's OSHAD framework codes of practice and to ADNOC's own HSE standards, and prequalification itself looks for a safety policy, incident records and a working management system. Once a project starts, the system produces documents daily: HSE plans, job safety analyses, method statements, risk assessments, permits-to-work, toolbox-talk records and incident reports.

The reason this matters for translation is the audience. A method statement or a permit-to-work is not read for pleasure; it is acted on by a supervisor and a crew, often on a multinational site where the working language of the engineering firm and the language of the local workforce differ. A phrase that is merely approximate in a safety instruction is not a stylistic lapse — it is an operational risk. So the register here is plain, exact and consistent, and a term defined in the HSE plan is carried unchanged into every permit and report that depends on it.

Incident and investigation reports add a second dimension, because they can end up before more than one reader. An internal report informs the contractor and the principal; a serious event may be reported to an authority; and where a dispute or a claim follows, the same report can be read in a legal setting where an Arabic version is required. Preparing the report accurately in both languages from the start avoids a rushed, adversarial translation later, when the wording is under scrutiny.

Have an energy file in front of you — a tender pack, an EPC contract, an HSE library or a JV agreement? Tell us the documents and where each one is going, and we will map what needs Arabic, what can stay English, and the order to prepare it.

Start a request

Where the contract stays English, and where it needs Arabic

Onshore UAE — courts, ministries, notaries

  • Arabic is the official language of the onshore courts; a foreign-language document is admitted only with a certified legal translation.
  • Registration, notarisation and government filings before onshore authorities generally require an Arabic version.
  • A JV or EPC agreement litigated onshore is read in Arabic, whatever language it was drafted in.
  • Customs paperwork for imported equipment in a foreign language needs a certified Arabic translation.

ADGM and DIFC — English common-law zones

  • ADGM applies English common law directly and DIFC runs in English; proceedings and filings inside the zone are in English.
  • An EPC or JV agreement governed by the zone's law can stay in English for the zone's own courts.
  • But the ADGM notary requires documents in dual-language Arabic and English, certified by a licensed legal translator.
  • And the same agreement usually needs a certified Arabic version the moment it is used onshore — for registration, notarisation or enforcement.

What an energy file contains, and where each part is going

DocumentUsually drafted inTypical destinationWhy it is translated
ICV supporting accountsEnglishCertifying body / Supplier HubThe audited figures behind the ICV score
Trade licence and ownershipArabic or EnglishPrequalificationTo complete the supplier file
Tender / technical proposalEnglishPrincipal or EPC evaluatorScored against the Arabic/English specification
EPC contract and schedulesEnglishParties, and onshore if filedThe governing terms and annexes
Method statements and permitsEnglishSite crews and HSE officerActed on by a mixed-language workforce
Incident / investigation reportEnglishContractor, principal, authorityMay be read by an authority or in a dispute
JV / shareholders' agreementEnglishFree-zone or onshore registryArabic for onshore registration or notarisation
Certificate of origin and invoiceForeign languageCustomsCertified Arabic to clear equipment

Have a question about your case?

Technical accuracy

Numbers, units and defined terms: accuracy across a document set

Two things distinguish accuracy in energy translation from accuracy in most other work: the density of numbers and the length of the document set. A technical specification is largely a structure of figures — dimensions, tolerances, pressure and temperature ratings, flow rates, material grades and test thresholds. In that setting a number is not decoration around the meaning; it is the meaning. A loosely converted unit, a decimal in the wrong place or a transcribed digit are substantive errors that change what is being promised, and they are the errors a technical checker is trained to catch.

The length of the set is the second problem. When a contract, its schedules, its data sheets and its HSE annexes together run to thousands of pages, consistency cannot be left to memory. The working method is a shared bilingual glossary: the defined terms, the party names, the equipment tags and the project-specific vocabulary are fixed once and applied everywhere, so the same source term is never rendered two ways. This is exactly the discipline the international translation-services standard ISO 17100 addresses when it makes revision by a second linguist part of the process — a second reader checks not only sense but consistency against the agreed terms.

None of this replaces the roles the sector's own specialists play. The engineers own the technical truth of a specification; the lawyers own the meaning of a contract clause; the HSE team owns the safety judgement in a method statement. The translation carries their decisions faithfully across the language line without adding to them or softening them. Where a source document is ambiguous, the honest response is to flag the ambiguity rather than resolve it silently in the target text — because a silent resolution can quietly change what a party thought it had agreed.

I need to… — energy-sector cases we prepare files for

Bid on an ADNOC-linked project as an international EPC contractor

What is usually neededA translated tender and technical proposal aligned to the specification, bilingual HSE documentation aligned to the ADNOC and OSHAD standards, and the ICV supporting documents — the audited financial statements behind the certificate.

Form a joint venture with a UAE partner for a project filed onshore

What is usually neededA certified Arabic translation of the JV or shareholders' agreement for onshore registration or notarisation, reconciled with any English version that governs inside a free zone.

Push a full HSE management system onto a multilingual site

What is usually neededHSE plans, method statements, risk assessments and permits-to-work rendered plainly and consistently for supervisors and crews, from a fixed glossary tied to the framework.

Renew an ICV certificate after a new financial year

What is usually neededThe freshly audited financial statements translated to accompany the revised certificate, matched to the company details already on file so nothing reads inconsistently.

Clear long-lead equipment through customs

What is usually neededCertified Arabic translation of the certificate of origin, commercial invoice and supporting documents where they arrive in a foreign language, with names and figures matched to the rest of the procurement file.

Prepare a contract claim or dispute file

What is usually neededThe contract, variations, correspondence and technical records translated as a consistent set, so the Arabic before an onshore tribunal matches the English the project ran on.

Abu Dhabi's own rules: a numerical-data exemption, and a notary that pulls Arabic back in

Because the sector sits in Abu Dhabi, two emirate-specific rules are worth knowing. The Abu Dhabi Judicial Council issued Circular No. 8 of 2023, which exempts bank statements and invoices containing only numerical data from the requirement to be translated into Arabic before the emirate's courts, on the reasoning that figures speak for themselves. The exemption is narrow: where English narrative text accompanies the numbers and could affect comprehension, the court keeps its discretion to require an Arabic translation, and this is an Abu Dhabi measure that should not be assumed to apply in Dubai or the other emirates.

The second rule runs the other way. Even inside ADGM — an English common-law jurisdiction where the courts work in English — the notary public requires documents in dual language, Arabic and English together in the same instrument, with the translation certified by a licensed legal translator. So an energy JV structured in ADGM does not escape Arabic simply by being there: the moment it is notarised, or used before an onshore authority, the Arabic version is needed. The practical lesson for the sector is to decide early which documents will touch an onshore or notarial step, and to prepare their certified Arabic before the deadline rather than under it.

Where an energy file stalls

  • The mistakeLetting defined terms drift across a long EPC set, so a valve, a rating or a party is named one way in the contract and another in a schedule.

    The fixFix a bilingual glossary at the start and revise the whole set against it, so the same source term is rendered the same way everywhere.

  • The mistakeTranslating a draft of a contract or specification, then signing a later version — so the Arabic no longer matches the document that governs.

    The fixTranslate the final, agreed version, and re-issue the translation if the source changes after it, rather than carrying an out-of-date rendering.

  • The mistakeAssuming an ADGM or DIFC English contract never needs Arabic, then meeting a wall when it is notarised or filed onshore.

    The fixDecide early which documents touch an onshore or notarial step, and prepare their certified Arabic in advance.

  • The mistakeTransliterating the company name differently across the trade licence, the ICV certificate, the tender and the contract, so a checker cannot confirm it is one entity.

    The fixFix one rendering of every company and party name at the outset and reuse it across the whole file.

  • The mistakeUsing a translator who is not registered with the Ministry of Justice for a document destined for an onshore court, notary or authority.

    The fixFor anything going before an onshore court, notary or government body, use a legal translator registered with the Ministry of Justice, whose registration covers the language pair.

  • The mistakeTranslating a technical specification approximately, so a unit is converted loosely or a tolerance is rounded, changing what is being promised.

    The fixTreat every number and unit as substantive, and have a second reader check the figures against the source, not just the prose.

What to send us to scope an energy translation

  • The kind of file — supplier qualification, ICV pack, tender, EPC or JV contract, HSE library, or a claim file — and the reader it is going to.
  • Whether the destination is the ADNOC Supplier Hub, a principal or EPC contractor, an onshore authority, or a free-zone counterparty — this decides whether certified Arabic is required.
  • Clear copies of the documents in hand, including the schedules, data sheets and annexes, not only the master contract.
  • Any existing bilingual glossary, style guide or previous translations, so new work stays consistent with what your project already uses.
  • For an ICV or qualification file, the audited financial statements and the licence and ownership documents in whatever language they exist.
  • Any deadline you are working to — a tender close, a certification renewal, a notarisation appointment or a hearing — so the work is sequenced to meet it.
  • The direction you need: a foreign or English document into Arabic for an onshore step, or an Arabic document into English for the international team.

The language pairs behind an energy file

  • Arabic ↔ EnglishThe core pair. Tenders, contracts and technical documents move into Arabic for onshore steps and back into English for the international engineering team — often both directions within one project.
  • French → English / ArabicFrancophone engineering and equipment firms bring specifications, data sheets and correspondence whose technical vocabulary is carried into English for the project and into Arabic where an onshore step requires it.
  • Korean / Japanese → English / ArabicMajor EPC contractors from East Asian markets deliver contracts and technical packs in their own languages; these are rendered for the project's working English and, where filed onshore, into certified Arabic.
  • Italian / German → EnglishEuropean contractors and vendors supply technical and commercial documents whose terminology is reconciled into the project's English so the whole document set reads as one.

Not sure which route applies to your document?

Energy-sector translation in the UAE: your questions

The trigger is the destination, not the document type. Anything going before an onshore court, a UAE government body or a notary generally needs a certified Arabic translation, because Arabic is the official language of the onshore system and a foreign-language document is admitted only with one. A document that lives entirely inside an English common-law free zone — an ADGM or DIFC matter heard in that zone's courts — can stay in English. The same JV or EPC agreement can therefore need Arabic for an onshore filing while its free-zone version does not. Map each document to where it is going before deciding.

Next step

Request Oil & Gas Translation

Send the document and we confirm the exact certification the receiving authority expects.