Client details are anonymised. First names only, no document numbers, no addresses.
A two-line enquiry with a much longer question inside it
Bohdan’s enquiry reached us early on a Tuesday morning and said almost nothing. Ukrainian into English. Certified translation. Two pages. Certification required for the Home Office (UKVI). And then one short sentence in the message box: required for a UKVI Home Office visa application.
Attached were two photographs. Not scans — photographs, taken on a phone, saved as JPEGs with the long machine-generated file names that a web form gives a file when it has no name of its own. Between them they carried one Ukrainian birth certificate.
On paper this is the most ordinary job in our business. A birth certificate, one language pair, a visa file. We do this every week. But the ordinary jobs are the ones where a small inconsistency does the most damage, because nobody is watching for it. The entire value of a certified translation of a civil-registry document is that it lets a caseworker match one piece of paper to another without having to think. The moment it makes them think, you have a problem — and for a Ukrainian applicant in the UK in 2026, there are three different places where that can happen.
Why the name was the real job
Ukrainian is written in Cyrillic. Bohdan’s birth certificate records his name, his parents’ names and his place of birth in Cyrillic characters, and every one of those has to arrive in English in Latin characters. That conversion is transliteration, not translation, and it is the single most common point of failure in documents from Ukraine, Russia, Bulgaria, Serbia and Greece.
The problem is that there is more than one defensible answer. Ukraine has used more than one official romanisation standard in living memory, and the system adopted for passports in 2010 does not always produce the same result as the systems used before it. A given Ukrainian given name can appear as Bohdan or Bogdan. A surname can carry an -iy, an -yi or an -y ending depending on which table the clerk was working from and which year it was. Place names move too: the same city is Kyiv in current UK government usage and Kiev in older documents and older transliteration habits.
Now add the thing that makes an applicant’s file different from a textbook exercise. By the time someone applies to UKVI from inside the UK, their name already exists in English, in writing, on documents issued by somebody else. A biometric residence document. A Ukraine Scheme grant letter. A share code, a payslip, a GP registration, a bank account, an application form they filled in months ago. Those spellings were fixed by whoever typed them first, and they are not necessarily the spelling a translator would choose from scratch.
So the question for us was never “what is the correct transliteration of this name?” It was “which English spelling of this name is already in the Home Office’s hands, and does this certificate now have to agree with it?” Those are completely different questions, and only the second one is useful to the person paying us.
The other two things that were harder than they looked
The second was the certificate itself. Ukrainian birth records are not one document family, they are several, stacked up by history. There are Soviet-era certificates issued before 1991, printed in Russian, bearing the arms and the registry wording of a state that no longer exists. There are the independent-Ukraine booklet and form certificates issued through the 1990s and 2000s. There are the later machine-printed forms, and since 2016 there are re-issues and duplicates produced through Ukraine’s digitised civil registry, which look nothing like the older paper. A person born in one era may well be submitting a document issued in another, because the original was lost, left behind, or replaced with a duplicate.
Each of those variants carries a different issuing authority, a different seal, and different wording for what is effectively the same legal fact. A translation that silently smooths all of that into a generic British-sounding “Birth Certificate — Registry Office” has thrown away the information a caseworker uses to decide whether the document is what it claims to be. The issuing body has to come through as what it actually is, in its own name, with a plain English rendering beside it.
The third was the photographs. Two phone images of a certificate are not a defect — most of our work arrives that way now, and for a certified translation the question is not whether the source was a scan but whether every element on the page can actually be read. Seals are where this bites. A Ukrainian registry seal is a circular impression, often struck in violet or blue ink, frequently overlapping the printed text, and on a phone photograph taken at an angle under a kitchen light it is the first thing to go. So is handwriting in the margin. So is the faint pre-printed serial text.
We would rather raise that at the start than guess at it in the middle. A certified translation has to be complete — every stamp, every seal, every handwritten annotation, every line of pre-printed boilerplate, including the parts that look like decoration. If something genuinely cannot be read, the honest move is to mark it as illegible in the translation and say so, not to invent a plausible word. But it is far better to get a second photograph.
How we worked through it
We started by asking Bohdan two questions, before anyone translated a word.
First: how is your name spelled, in English, on the documents you have already given the Home Office, and on your passport or travel document? Not how you would spell it — how it is already written. Second: can you send one more photograph of the lower part of the certificate, flat, in daylight, so the seal and the registry details are legible?
Both came back quickly. That gave us the anchor spelling for the applicant’s own name and let us read the issuing registry cleanly.
From there the work was disciplined rather than difficult. We transliterated consistently across the whole document, using the anchor spelling for the applicant and a single coherent system for every other name on the page — his parents, the registrar, the place of birth — rather than mixing systems line by line. Where our transliteration of the applicant’s name differed from the spelling already in use, we did not quietly pick one. We rendered the document faithfully and added a translator’s note recording that the certificate’s Cyrillic form corresponds to the Latin spelling used in his existing paperwork. That note costs nothing and removes the exact doubt a caseworker would otherwise have to resolve on their own.
We described the issuing authority as it appears on the document rather than as a British equivalent. We reproduced the layout so the English version maps onto the Ukrainian one field by field, which matters when somebody is holding both side by side. We described each seal and stamp in place, in brackets, saying what it is and what it reads, instead of leaving a silent gap where a purple circle sits on the original. Dates were given in an unambiguous order. And because this is a UKVI file, the whole thing was produced in UK English.
Then the certification. The translation carries our statement of accuracy, the date, the translator’s and the company’s details, and confirmation that it is a complete and accurate translation of the attached document — which is the form UK government bodies, including UKVI, generally expect for a certified birth certificate translation. Bohdan had not ticked notarisation, and he did not need it. For a Ukrainian birth certificate going into a visa application, certification is the normal requirement; notarisation is for the smaller set of cases where a receiving body, usually a foreign one, specifically asks for an oath. Adding it here would have added cost and delay and bought him nothing, so we said so.
What was delivered
Bohdan received the certified English translation of his Ukrainian birth certificate, formatted to mirror the original, with every seal and annotation accounted for, the issuing registry named as the document names it, the applicant’s name spelled to match the paperwork the Home Office already held, and a short translator’s note explaining the Cyrillic-to-Latin correspondence. It went out inside the deadline he had asked for, as a PDF he could attach to his online application without reformatting anything.
Nothing came back to us queried. His file went in complete and on time, with the birth certificate no longer being the thing he had to worry about. The decision on the application is UKVI’s and is theirs alone to make — we do not know it and would not claim it. What we can say is that the document did the job it was there to do, which is to be unambiguous.
If you are in the same position
A few things are worth knowing before you order anything.
Find your anchor spelling first. Before you commission a translation of any Cyrillic-script document, write down exactly how your name appears in Latin letters on the documents the UK authorities already hold, and give that to your translator. This is the single most useful thing a client can do for us, and it takes two minutes.
Expect a complete translation, not a summary. UK authorities generally want the whole document rendered, seals and stamps included, not the headline facts. If a quote looks unusually cheap because somebody is only translating the filled-in boxes, that is not the same product.
Know which version of your certificate you are sending. If you hold a Soviet-era certificate in Russian, say so, because the source language on the document may not be the language you expect. If you hold a recent duplicate from Ukraine’s digital registry, that is fine, but mention it.
Photograph it properly. Flat, in daylight, the whole page in frame including the edges, and a separate shot of anything with a seal on it. Two good photographs beat ten poor ones.
And be clear about the reader. A birth certificate for a visa application, a passport document translation, and a certificate going to a foreign authority are not interchangeable jobs, because the certification each one needs is different. Tell your translator who is going to read it. If you are unsure, our guide to certified translations for UK immigration documents sets out who asks for what, and the same logic applies across our certified legal translation work.
Ukrainian is one of the languages we handle most often, and almost every file has a name question in it somewhere. If you have a Ukrainian certificate to submit and you are not sure whether the spelling on it will line up with the rest of your application, send it over through our translator request form and tell us who it is for. We would rather sort the name out before we start than explain it afterwards.
