Quick summary: When a name is written in another script, there is rarely one correct English spelling — there are several defensible ones. If different documents in the same application use different ones, you have created an identity discrepancy that somebody will ask about. The fix is simple and has to happen before you order: decide the spelling, anchor it to your passport, and give it to every translator in writing.
This is the quiet problem in certified translation. Nothing is wrong with any individual document, and the bundle still raises a question.
A birth certificate translated as Mohammed, a degree translated as Muhammad, and a passport reading Mohamad are three reasonable renderings of the same name. To an assessor working through a file, they are three spellings that need reconciling.
Why transliteration has no single right answer
Transliteration converts a name from one writing system into another by sound and convention rather than by lookup.
Arabic, Chinese, Cyrillic, Devanagari, Thai, Amharic and many other scripts contain sounds and distinctions English does not map cleanly. Competing romanisation systems exist, regional conventions differ, and the same name can be rendered several ways by translators who are all working competently.
So the goal is not to find the correct spelling. It is to use one spelling, consistently, and to make it the one your other records already use.
The passport is the anchor
Your passport is the document nearly every Australian process treats as the identity reference point, and it is usually the one the receiving authority already has.
So the working rule is straightforward: the spelling in your passport is the spelling every translation should use for you.
This is not the translator's choice to make in isolation. Given a document in another script, a translator produces a defensible transliteration; given your passport spelling, they can use the one that matches the rest of your file.
Which means you have to supply it.
Tell the translator, in writing, up front
When you place an order, give:
- your name exactly as it appears in your passport, including spacing, hyphens and the order of names
- the same for every person named in the documents — spouse, children, parents where they appear
- any previous or alternative spellings that appear on older records, so they can be recognised rather than treated as a different person
- any name changes, and the document that evidences them
Home Affairs requires translator details to be supplied in English with every translation, and the same principle serves you here: the identity information a reader needs should not have to be inferred.
Where inconsistency usually creeps in
Ordering from different providers over time. A birth certificate translated two years ago by one translator and a police check translated last week by another will diverge unless somebody told the second one what the first did.
Documents from different countries. The same family name transliterated in the country of birth, the country of study and the country of last residence may already differ before any translation happens.
Family members handled separately. A shared family name rendered one way on the applicant's documents and another way on a child's creates a question about whether they are the same family.
Long employment histories. An employment reference spanning several employers may show the name written differently by each of them.
Name order. Where the source document places the family name first, a translation that reorders it silently — or does not — can look like two different people across a bundle.
What a translator will and will not do
What they will do
Use the spelling you provide, where it is a legitimate transliteration of the name on the document. And note where the source document itself shows a different spelling, so the connection is visible rather than hidden.
What they will not do
Translate a name into a different name. Transliteration carries sound across scripts; it does not substitute an English equivalent, so a name is not "translated" into Michael because it sounds similar.
Nor will they silently correct a spelling on the source document. If the original is wrong, that is a matter for the issuing authority — the translation reflects what the document says.
When older documents genuinely differ
Sometimes the source documents themselves carry different spellings, and no instruction to the translator can change that. An old certificate says one thing; the passport says another.
That is not a translation problem, and trying to solve it in the translation makes it worse. The translation should show what each document actually says.
What resolves it is a linking explanation — the same approach used for any name change: a document connecting the names, or a statement setting out the history, provided alongside. The point is that the discrepancy is disclosed and explained rather than discovered.
A practical sequence
- Open your passport and write your name exactly as printed, character for character.
- List every other person who appears in your documents, with their passport spelling where they have one.
- Collect what you already have translated, and check the spellings used.
- Give all of it to the translator when you order, not after.
- Check the returned translation against your passport before you lodge — first name, family name, spacing, order.
- Keep the list for the next document you order, so future translations match.
That last step is the one that pays off. Most inconsistency comes from ordering documents months apart with nobody holding the thread.
Before you order
Decide the spelling once, and treat it as fixed. Every hour spent getting this right before ordering is an hour you do not spend explaining an identity discrepancy afterwards.
NAATI publishes its practitioner identification guidance and Home Affairs its translation requirements. If you are ordering several documents, LodgeHQ Translate can take your preferred spellings once and apply them across the set.