A New Zealand Medical Certificate Translated into Arabic for an Employer Overseas

This case study is written at the level of process only. The client is not named – the surname is distinctive enough that naming it would identify them – and nothing about the content of the document, its subject matter or its findings appears anywhere in this piece. The document is referred to throughout simply as a medical certificate.

An enquiry that arrived at the wrong door, for the right reason

This one came in through our apostille services in New Zealand page, which told us something before we had read a word of the form. People who land on an apostille page are usually not shopping for a translation. They are trying to work out how to make a New Zealand piece of paper count for something in another country, and they have correctly guessed that there is a stamping step involved and incorrectly guessed which one.

The form said: one page, a medical certificate, English into Arabic, notarisation required, certification “Not Applicable”. The purpose field said the document was going to the client’s employer in Saudi Arabia.

Two things about that are worth pausing on, because they shaped the whole job.

The first is the direction. Almost everything we do runs inbound – a document in another language arriving in New Zealand to be read by a New Zealand authority. This ran the other way. A New Zealand document, in English, had to become an Arabic document that would be read in the Gulf. Outbound work is not harder in the sense of being more technically demanding. It is harder because almost every certainty you rely on going inbound evaporates going outbound.

The second is the reader. Every other job on our board that week had a named authority at the end of it: Immigration New Zealand, the Department of Internal Affairs, NZQA, a court. This one had an employer. And an employer, for a translator, is the hardest reader there is.

Why an employer is harder to translate for than a government department

Government bodies publish requirements. They are not always clear, and they change, but they exist: you can read what Immigration New Zealand expects of a translation, and you can build to it, and if you have built to it you can say so with a straight face.

No employer publishes a translation requirements checklist. There is no page anywhere that says what the human resources department of a particular company in Riyadh or Jeddah will accept. There is often an internal policy, and sometimes a government requirement sitting behind the employer that the employer itself is simply passing along, and the employee is rarely told which is which. The person who will actually open the file might be an HR administrator, a government relations officer, a line manager, or all three in sequence.

So you cannot build to the standard. You have to infer it, and then deliberately over-meet it, because the cost of being wrong is asymmetric. A translation that is more complete and more formally certified than the employer needed costs a little money. A translation that is less than the employer needed costs the employee a round trip through their own HR department from the other side of the world, and whatever the document was needed for does not happen on time.

That asymmetry is the whole design principle for a job like this, and it leads to a short list of decisions.

We assume the document will be escalated

The employer may not be the final reader. HR departments forward things – to a government relations officer, to a labour or licensing body, to a sponsor. A document built only to satisfy a colleague’s glance falls over the moment it is passed upwards. So the translation was built as though a government office would eventually read it: complete, formally certified, nothing summarised, nothing left out as self-evident.

Nothing is omitted, including the furniture

Letterhead, footer, the practice’s details, the signature block, the date line, every stamp and every reference on the page: all of it rendered or described. The temptation on a one-page document is to translate the substance and leave the surroundings, on the basis that the surroundings are obvious. They are obvious to a New Zealand reader. To a reader in another country and another script, the surroundings are how the document’s authority is established at a glance. Stamps and signatures cannot be reproduced, so each one is described in a translator’s note in its proper position on the page, with legible text transcribed and anything illegible marked as illegible rather than guessed at.

Certification goes on even though the form said “Not Applicable”

The client had completed the certification field as “Not Applicable” and ticked notarisation. That combination is contradictory, and it is one of the most common contradictions we see: it means “I don’t know what certification is, but I know I need the serious version”. A translation presented to a foreign employer with nothing attached to it is a Word document with Arabic in it, and any HR administrator is entitled to ask who produced it and on what authority. A Certificate of Accuracy, naming the translator and the direction of translation, costs nothing extra on a job of this size and removes the question entirely. It went on.

Writing a Latin-script name in Arabic so that it matches the passport

This is the part of outbound Arabic work that people do not anticipate, and it is the part most likely to cause a rejection.

A New Zealand medical certificate names the person in Latin script. An Arabic translation has to name them in Arabic script. There is no single correct way to do that – and the employer does not want the correct way. The employer wants the same way as every other document in the employee’s personnel file, starting with the passport and the residence permit.

The reason is mundane and absolute: in an Arabic-language filing system, two spellings of a name are two people. If the certificate says one thing and the residence permit says another, a clerk comparing them is not looking at a transliteration variant. They are looking at a mismatch, and a mismatch is something they have to escalate rather than resolve.

So the rule we apply is that we never invent an Arabic spelling of a name when an official one already exists. We ask for it. In this case that meant asking the client for the Arabic rendering of their name as it appears on their existing documentation, and using exactly that, character for character, even where a translator would have chosen differently.

Where a client genuinely has no prior Arabic spelling, the choices that have to be made are worth understanding, because each one is a place a mismatch can be born:

Arabic script has no capital letters, so the visual cue that marks a proper noun in English disappears entirely, and a name has to be unmistakable from context and placement alone. Short vowels are not normally written, so the same written form can be read several ways, and the written form is what matters for matching. Long vowels are written, which means a decision about whether an English vowel is long or short changes the letters on the page. Several English consonants have no exact Arabic equivalent and are conventionally mapped to the nearest letter, with more than one convention in circulation. The Arabic definite article can assimilate in pronunciation to the following letter while staying unchanged in writing, so a name that is pronounced one way is spelled another. Feminine name endings have their own letter, and whether it is used is a judgement about the name’s form. And Gulf naming conventions order given name, father’s name and family name in a way that may not match how a New Zealand document has laid the name out, so the order has to be preserved from the source rather than rearranged into local habit.

None of that is exotic linguistics. It is the practical reason a name should be copied from an existing official document rather than translated afresh.

The other things that change when the page turns right to left

An Arabic page reads right to left, and that is not only a typographic preference. It changes the layout: the signature block, the date line and the letterhead all move, and a translation that keeps the English arrangement looks, to an Arabic reader, like a form someone has filled in sideways.

Mixed-direction text is the practical hazard. A New Zealand practice name, a registration number, a web address or an email address stays in Latin script inside an Arabic sentence, and when left-to-right content sits inside right-to-left content, punctuation and brackets can visually jump to the wrong end of the string. It looks like a typing error and it can make a reference number appear to be a different number. Every mixed-direction element on this page was checked visually in the final PDF rather than trusted from the editor.

Numerals need a decision made on purpose. Both Western and Eastern Arabic-Indic digits are in everyday use across the Arabic-speaking world, and the two are not interchangeable to a reader scanning for a reference. We keep identifiers in the same digits as the source so that they can be matched character for character, and set out that choice in a translator’s note rather than leaving the reader to wonder.

Dates get the same treatment. A date in the Gregorian calendar may be read in a setting where the Hijri calendar is also in daily use, so the calendar is stated explicitly instead of assumed, and the day and month are never left in a numeric order that could be read either way.

The legalisation question the client was actually asking

The client arrived on our apostille page because they suspected a stamping step existed. They were right, and the step is not the one most people expect.

Here is the chain, and the fork in it. A New Zealand document going overseas can be signed and sealed by a New Zealand Notary Public, as set out on our notarised translation page, and the notary’s signature can then be authenticated by the Department of Internal Affairs. What DIA issues depends entirely on the destination. If the destination country is a party to the Hague Apostille Convention, DIA issues an apostille. If it is not, DIA issues an authentication instead, and the document then has further steps to go – through the foreign affairs ministry and, in many cases, the destination country’s embassy. That longer route is what our DIA authentication for non-Hague countries page exists for.

This is the single most useful thing we can tell anyone sending a New Zealand document into an Arabic-script destination: find out which of those two routes applies to your destination, as at today, before you pay for anything. Convention membership is not static – countries join, and the date they join matters – so a route that was correct in a forum post two years ago may not be correct now, and the reverse is equally true. We treated this as a question to be verified against the current position rather than answered from memory, and we would tell any client to do the same.

There is a second fork that almost nobody anticipates, and it is the one that most often sends a document back. Authentication attests to a signature or seal. It says nothing about whether the facts in the document are true. So the question becomes: whose signature does the receiving side want authenticated?

If the employer wants the translation vouched for, the signature in the chain is the translator’s, witnessed by a notary. If the employer wants the certificate itself vouched for – that it was genuinely issued by a New Zealand practitioner – then the signature that needs to travel up the chain is the practitioner’s, and that is a different document going through a different sequence. Those are not the same request, and discovering at the embassy counter that you have authenticated the wrong signature is an expensive way to find out. We flagged the distinction, set out both chains, and asked the client to put the question to their employer in those terms, because it is the employer’s answer and not ours.

Confidentiality, with a document like this one

Our standard access rule is that the assigned translator and one internal reviewer see your document, and nobody else. On a job like this we also apply a restraint that is not about access at all: we do not discuss the content of a medical document with anybody, including in our own correspondence with the client, beyond what is strictly needed to produce an accurate translation.

That restraint is the reason this case study tells you a great deal about Arabic script, employer expectations and the legalisation chain, and nothing whatsoever about what the certificate said. There is a version of this piece that would be more vivid. We are not going to write it, and if a translation provider offers to write it about your document, that tells you something.

What was delivered

A complete English to Arabic translation of the single page, laid out right to left to match the conventions of the receiving language, with every element on the source page rendered or described, the client’s name in the Arabic spelling their own existing documentation already uses, identifiers carried across character for character, and translator’s notes covering the stamps, the signature and the numeral and calendar conventions used. A signed Certificate of Accuracy was issued naming the translator and the direction of translation. The file was delivered inside the agreed window, and the legalisation route was set out in writing as two clearly separated options with the verification step the client needed to take before choosing between them.

The client confirmed receipt and confirmed that the document went to their employer complete and on time. Nothing came back to us with a query. We make no claim about any decision the employer took, because that is the employer’s to take and it is not ours to report.

If you are sending a New Zealand document into an Arabic-script country

Four things, in the order they will save you the most trouble.

Ask your employer, in writing, what they actually need: a translation, a notarised translation, or an authenticated document – and whose signature they want authenticated. Then send us the answer rather than your guess at it.

Send us the Arabic spelling of your name from your own existing documentation. Do not let anyone, including us, invent one.

Confirm your destination country’s current Hague Convention status before you buy any stamping step, because that one fact decides whether your document needs two steps or four.

And budget for the fact that outbound work has more moving parts than inbound work. Our medical translation services in New Zealand page sets out the certification levels and what each one includes, and the Arabic and English translation page covers the language pair in both directions. If the document is being read inside New Zealand rather than overseas, the answer is completely different and usually cheaper – we work through exactly that distinction in our case study on a French civil-status record prepared for Immigration New Zealand, where a client had paid for notarisation she did not need. And where the receiving body is a New Zealand court rather than an authority or an employer, the wrapper changes again, as the case study on Mandarin judgments affirmed in a High Court affidavit sets out.

The short version of all of it: when nobody publishes the standard, the only safe standard is the highest one you can justify. That is not an upsell. It is the cheapest thing you can do, counted properly.