A Russian-Language Birth Record for a New Zealand Citizenship Application

The client’s problem

Ihor needed one page translated for a New Zealand citizenship application: his birth certificate. He told us so twice. He submitted the job through our site at twenty past four in the morning, and again twenty minutes later, and the two records that came through to us disagreed with each other about something fundamental.

The first said the document was in Russian. The second said it was in Ukrainian. Same client. Same purpose. Same certificate. Two different answers to the question of what language it was written in.

Most translation jobs begin with the language pair settled and everything else uncertain. This one began the other way round: we knew exactly what the document was for and who would read it, and we did not know what language we were being asked to translate from.

Why it was harder than it looked

It would be easy to read that as a client being careless with a form. It is not, and understanding why is the whole point of this piece.

A birth certificate issued in Ukraine before 1991, or in the first years after independence, is very often written in Russian. Many are bilingual, with Russian and Ukrainian running in parallel or with pre-printed Ukrainian headings filled in by hand in Russian. Some are on Soviet-era stock that was still in circulation years after the state that printed it had ceased to exist. The document is Ukrainian in the sense that a Ukrainian authority issued it and a Ukrainian authority holds the register behind it. Its text may nonetheless be Russian.

So when a client fills in a language field and hesitates between “Russian” and “Ukraine”, they are not confused about their own paperwork. They are accurately reporting that the honest answer has two parts, and that the form has room for only one. The field is asking what language the text is in; the client is also trying to tell us where the document came from. Both facts matter, and a form with one box makes them compete.

This has a direct consequence for the translation. The language of the text determines who should translate it and how the handwriting is read. The issuing state determines what the document is, which register sits behind it, what the seals and the series markings mean, and which authority a receiving official would contact if they wanted to verify it. Get the first right and the second wrong and you produce fluent English that misdescribes the document. Get the second right and the first wrong and you hand the work to a translator reading a language the document is not in – and Russian and Ukrainian are close enough that a confident guess can survive a long way into a document before it breaks.

There was a second problem, quieter but more likely to cost the client. The form recorded the receiving authority as the Department of Internal Affairs, and that is correct. New Zealand citizenship is administered by the Department of Internal Affairs, not by Immigration New Zealand. Those are different agencies with different functions: Immigration New Zealand deals with visas and residence, the Department of Internal Affairs with citizenship, passports and the civil register. Clients very reasonably assume that anything to do with coming to New Zealand and staying there is one process handled by one agency, and a document prepared with the wrong reader in mind can be prepared to the wrong standard. Here the form had it right, and part of our job was simply not to undo that.

And then the name. The client’s name exists in Cyrillic on the certificate and in Latin characters in his travel document, and those two renderings were produced by different systems at different times for different purposes. A citizenship file is, among other things, an exercise in showing that a series of documents all refer to one person. Every time a name is rendered a new way, that chain gets one link weaker.

How we approached it

We did not pick one of the two language entries and proceed. We read the document and let it answer the question.

That meant examining it as an object before translating it as a text: the pre-printed headings and what language they are in; the language of the entries written or typed into those headings; the seals, and what is impressed or printed on them; the series and number markings; the issuing office named on the face of it. Those features, together, establish both facts the form could not hold at once – the language of the text, and the issuing authority behind it. Once both were settled from the document, the job had a specification, and we recorded that specification against the order so that nobody downstream would have to re-derive it.

Where the document carried text in more than one language, we translated all of it and said so, rather than silently selecting one layer. A reader looking at the English should be able to see the shape of the original, including the fact that it has more than one language on it.

On the name, we applied the rule we apply to every identity document without exception: the spelling in the client’s current travel document governs. Not the spelling a transliteration standard would produce, not the spelling that looks most natural in English, and not the spelling used on a different document from a different decade. Where the certificate’s Cyrillic form transliterates to something other than the passport spelling, we use the passport spelling in the body of the translation and record the original Cyrillic form as it appears, so the reader can see both and the difference is on the page rather than hidden. The chain of identity is then visible and checkable instead of being quietly asserted.

Dates, series numbers and the handwritten elements were handled with the same discipline: rendered exactly, with anything genuinely illegible marked as illegible rather than reconstructed. On a document whose purpose is to prove a fact about a person, a plausible guess is worse than an admitted gap, because a gap invites a question and a guess invites a wrong answer.

We then prepared the certification. A certified translation for New Zealand official use is the translation plus a signed statement from the translator confirming it is a true and complete rendering of the document supplied, with the translator’s name, the date and contact details. The client’s form had notarisation switched off, and that was the right setting: for a civil-status document going to the Department of Internal Affairs, certification by a competent and independent translator is what is required. Notarisation answers a different question, about the execution of an instrument, and buying it here would have added cost and time without adding anything the reader was asking for. We left it off and said why.

What we delivered

One certified English translation of the birth certificate, prepared from a settled specification: the language of the text established from the document itself rather than from the order form, the issuing authority correctly identified, every language layer on the page translated, the name rendered to match the client’s travel document with the original Cyrillic form shown, all seals and series markings accounted for, illegible elements marked as illegible, and a signed certification statement in the form New Zealand officialdom expects.

Delivered inside the deadline, certified exactly as the receiving department requires, with the two duplicate order records reconciled into one job so the client was quoted and invoiced once.

The result

The translation went into the citizenship file complete and on time, with nothing queried and no follow-up request for clarification. The language ambiguity that arrived with the order was resolved before any work was done, which is the only place it can be resolved cheaply.

The decision on a citizenship application belongs to the Department of Internal Affairs and to nobody else, and this piece makes no claim about it. What was in our hands was narrower and entirely achievable: that the document in the file says what the original says, that it is certified in the right form, and that the name on it matches the name on everything else.

What a reader in the same position should know

If you hold a birth certificate issued in Ukraine, or anywhere else in the former Soviet Union, do not worry about getting the language field right. Send us the document and let us establish it. If the form makes you choose between the language of the text and the country that issued it, say both in the message box – that is the most useful sentence you can write.

Check which agency is actually going to read your document. Citizenship is the Department of Internal Affairs. Residence and visas are Immigration New Zealand. Preparing a document for the wrong one is a common and avoidable waste.

Give us the spelling of your name exactly as it appears in your passport, before we start. It is the single piece of information that most often prevents a query later, and it costs you one line of typing.

And before you pay for notarisation, ask whether anyone has requested it. For a civil-status document going to a New Zealand government department, a properly certified translation is normally what is needed. We would rather tell you that than sell you a layer you do not need.

You can read how we handle this work on our birth certificate translation and citizenship document translation pages, and about the authentication step some documents need on our DIA authentication page. If you are not sure whether you need notarisation, our notarised translation page explains what it is for, and our FAQs answer the questions clients ask most. When you are ready, hire a translator or contact us with a photograph of the document and we will tell you what it is and what it needs.