Client details are withheld. No name, certificate number, date or place appears in this account, and nothing is said about the client’s former nationality or their reasons for needing the document abroad. What follows is about the mechanics of taking a British public document outbound, and nothing else.
- An enquiry that ran the wrong way down our own site
- What a certificate of naturalisation actually is, for authentication purposes
- What a UK document going abroad actually needs
- The missing sentence: nobody had said what it was for
- Translating into Lithuanian: the name problem is the whole problem
- What we actually did
- What landed in the client’s inbox
- How it turned out
-
Questions people ask about taking a UK naturalisation certificate abroad
- Does my naturalisation certificate need to be notarised before it goes abroad?
- What does an apostille actually prove?
- Does the apostille go on the original or the translation?
- Is there an EU route that avoids all this?
- Should my name be adapted into Lithuanian form on the translation?
- Can I translate it myself, or get a relative who speaks Lithuanian to do it?
- I have lost my naturalisation certificate. Can you work from a copy?
- My document is going to a country that is not in the Hague Convention. What then?
- If you are taking a British document the other way
An enquiry that ran the wrong way down our own site
The message arrived early in the afternoon through the hire-a-translator form and ran to eleven words: a naturalisation certificate needed translating into Lithuanian. One page attached. Notarisation ticked. Purpose: not sure.
Everything on this website is built for documents coming in. Foreign certificates, foreign records, foreign judgments, arriving in English for a British reader — very often the Home Office itself. That is the brand, that is the traffic, and that is what nine out of ten enquiries are.
This one was the reverse, and it was the reverse in a particularly neat way. A certificate of naturalisation is the one document in this whole field that the Home Office issues rather than reads. It is the thing the Home Office hands you at the end of the process every other document on this site is trying to get through. And now it was going abroad.
Which meant that almost none of the usual answers applied, and the client’s one tick — notarisation — was pointing at the wrong layer.
What a certificate of naturalisation actually is, for authentication purposes
Start here, because everything follows from it.
A British certificate of naturalisation is a public document, issued by a government department, recording that a person has been granted British citizenship. It carries their identity details, a certificate number and a date. It is not a private deed, not a letter, not a contract, and not something a person executes themselves.
That single classification answers the client’s question before we get anywhere near Lithuania.
Private documents — a deed, a declaration, a company letter, an affidavit — generally cannot be authenticated as they stand. They have to be made notarially public first: a notary performs an act on them, and it is the notary’s signature and seal that the authentication layer then certifies. That is why so many outbound jobs genuinely do need a notary, and why clients who have been through one of those jobs arrive assuming every outbound job needs one.
A public document does not need that step. It is already issued by an authority whose signatures and seals the authentication layer holds on record. Adding a notarial act to it does not strengthen it; it inserts a private professional into a chain that was already complete, at the client’s expense.
So the first thing we said, before quoting, was that the notarisation the client had ticked was very probably not what they needed. We provide notarised translation and we were not trying to talk them out of a service. We were trying to stop them buying a layer that, on this document, does nothing — because the only thing worse than an unauthenticated document abroad is an expensively over-authenticated one that still lacks the stamp the receiving office actually asked for.
It is worth saying plainly what a notarial act does and does not do, since this is the single most persistent misunderstanding we encounter. A UK notary public is appointed by the Court of Faculties and regulated by the Master of the Faculties. The notarial act confirms a signature, the signer’s authority and their capacity. It does not attest the accuracy of a translation. A notary certifying a translator’s signature is confirming that the translator is who they say they are and signed in front of them — valuable when a foreign authority demands it, and an expensive irrelevance when it does not.
What a UK document going abroad actually needs
The layer that matters on an outbound British public document is an apostille, and in the United Kingdom it is issued by the Legalisation Office of the Foreign, Commonwealth and Development Office. It is a single certificate, issued under the 1961 Hague Convention, authenticating the origin of a public document so that another Convention country accepts it without any further consular step.
Both the United Kingdom and Lithuania are parties to that Convention. The practical consequence is simple and it is good news: no embassy appointment, no consular queue, one certificate.
Two refinements worth having, though, because they catch people.
One: the EU route does not help here. There is a European Union regulation on public documents that removes legalisation requirements for certain civil-status documents circulating between EU member states, and clients who have lived in the EU sometimes expect it to apply. It operates between member states. The United Kingdom is not one, so a UK-issued document gets nothing from it. The Hague route is the route.
Two: an apostille authenticates origin, not acceptance. It says the document is genuinely what it appears to be and was genuinely issued by the body named on it. It does not oblige any foreign office to accept the document, does not say the document is current, and says nothing whatever about the translation attached to it. Receiving authorities routinely impose their own requirements — how recent the document must be, whether a copy or an original is wanted, whether the translation must be produced in a particular way or by a particular kind of translator. Those requirements are theirs, they vary, and they change.
Which is where the purpose came back to bite.
The missing sentence: nobody had said what it was for
The form said “Not Sure”, and in this case that was an honest answer rather than a careless one. The client knew they had been asked for the document in Lithuanian. They did not know, or had not thought to say, which office had asked or why.
That matters more on this job than on almost any other, because the purpose determines whether there is any authentication step at all.
A naturalisation certificate might be wanted abroad for a long list of reasons — a residence or registration formality, a civil-status matter, a property or inheritance process, a bank or employer that needs evidence of nationality, a consular process at a Lithuanian mission. Some of those readers want nothing more than an accurate certified translation. Some want the original apostilled. Some want the translation itself brought into the chain. Some want a sworn translator in their own jurisdiction rather than a certified translation produced in the UK — which is a route we cannot provide from here and will tell a client so.
So we did not quote an authentication chain. We quoted the translation, explained the apostille route, explained that the notarial layer was probably unnecessary, and asked the client to put one question to whoever had asked them for the document: what do you need, in what form, how recent must it be, and does the translation have to be produced in a particular way. Our FAQs make the same point less politely, and it is the single most useful question anyone in this position can ask.
Translating into Lithuanian: the name problem is the whole problem
Now the linguistic half, and on this document it is almost entirely about one thing.
Lithuanian is a heavily inflected language. Nouns, including personal names, take grammatical endings that change according to their role in the sentence, and Lithuanian names have characteristic endings of their own. Rendering a foreign personal name into natural Lithuanian would ordinarily mean adapting it — giving it an ending so that it behaves like a Lithuanian word in a Lithuanian sentence.
On a document that evidences identity, a translator must not do that.
The reason is not stylistic. A certificate of naturalisation exists to say that a particular named person holds a particular status. If the translation renders that person’s name in an adapted or inflected form, the English document and the Lithuanian document now name two different strings of characters — and the reader’s job, which is to match this document against a passport and against whatever record is being created or updated, has been made impossible. The passport is not going to carry the adapted form.
So our rule on identity-evidencing documents into Lithuanian is fixed. The personal name is reproduced exactly as it appears on the source document and on the client’s passport, in its original Latin-character spelling, undeclined and unadapted. Where the surrounding Lithuanian sentence structure would ordinarily require an ending, the sentence is built so that the name can stand in its original form. Where that produces slightly stiff Lithuanian, the stiffness is correct: this is a legal instrument, not prose, and the name is data rather than language.
How foreign personal names should be recorded in Lithuanian official records has been a live legal question in Lithuania for many years, and it is precisely the kind of question a translator must not attempt to resolve on a client’s behalf. Our job is to make the chain back to the passport unbreakable and to leave any decision about how the name is entered in a Lithuanian register to the Lithuanian authority making that entry. Where the client has an existing Lithuanian-language document bearing their name in some form, we ask for it, and we flag any divergence in a translator’s note rather than picking a side.
The rest of the document gets the care any public instrument gets. The issuing department named accurately and not translated into an approximate local equivalent. The certificate’s own title rendered as what it is, with the English retained alongside, so a reader can see precisely which British instrument they are holding. The statutory framework referred to as the document itself refers to it — a translator does not add a citation the certificate does not carry, and does not map a British statutory provision onto a Lithuanian one. Every seal, stamp, signature block, security feature and reference field accounted for, with each described in a bracketed translator’s note giving its text and position. A seal left unmentioned reads, to a careful officer, as a seal that was ignored. And dates written out unambiguously, because a British date and a continental date can be the same eight characters meaning two different days.
What we actually did
- Classified the document before anything else. A public document issued by a government department — which immediately answered the notarisation question the client had asked and pointed at the apostille route instead.
- Told the client the notarial layer was probably unnecessary, and why. Against our own invoice. A notarial act confirms a signature, authority and capacity; it adds nothing to a document whose issuing authority is already on the authentication layer’s records.
- Explained the correct outbound route. An apostille from the FCDO Legalisation Office, available because both countries are Convention parties, and no consular appointment required.
- Ruled out the EU route explicitly. Clients who have lived in the EU often expect the public-documents regulation to apply; it operates between member states and does not assist a UK-issued document.
- Asked for the purpose, and did not quote the chain without it. The receiving authority decides whether the original needs an apostille, whether the translation enters the chain, and whether a sworn translator in Lithuania is wanted instead. We quoted the translation and left the chain open pending that answer.
- Fixed the name rendering in writing before translating. Original Latin-character spelling as it appears on the certificate and the passport, undeclined and unadapted, with the Lithuanian sentence structure built around it.
- Asked whether any existing Lithuanian-language document carried the client’s name, so that a divergence could be flagged rather than discovered.
- Translated the whole page, apparatus included. Issuing department, certificate title with the English retained, reference fields, every seal, stamp and security element described in bracketed notes, nothing omitted and nothing added.
- Mirrored the layout, so the English and the Lithuanian can be laid side by side and checked field against field by a reader who reads neither language fluently.
- Attached a certificate of accuracy built to the GOV.UK definition — written confirmation that it is a true and accurate translation of the original document, the date of translation, and the translator’s full name and contact details — bound to a copy of the source so the two cannot be separated.
What landed in the client’s inbox
A complete Lithuanian translation of the certificate, laid out to mirror the English; a certificate of accuracy carrying the three GOV.UK components; a copy of the source document bound to the translation; and a short plain-English note setting out what an apostille does and does not do, why a notary was not needed on this document, which route applies between the UK and Lithuania, and the one question the client needed to put to the office that had asked them for it.
Delivered inside the deadline the client needed, certified to the GOV.UK standard, with the name reproduced exactly as their passport carries it. Nothing came back to us as a query — no request to re-render the name, no challenge to the certificate of accuracy, no question about the absence of a notarial seal.
Certified English to Lithuanian translation is quoted per document once we have seen the pages, and the quote you are given is the price you pay. Standard turnaround is two to three working days, with a 24-hour express option. Home Office Translations UK is an ATC member company and many of our translators hold ITI membership.
How it turned out
The translation went out complete and on time, with the certificate attached, and the client confirmed afterwards that it did its job. What any Lithuanian authority decides is that authority’s business and the client’s — not ours to claim and not ours to publish. Our part was to make sure nothing in the Lithuanian page gave anyone a reason to come back and ask a question, and that the client did not pay for a notarial act that would have added nothing.
What stays with us is the shape of the enquiry. Eleven words, one tick in the wrong box, and a purpose field that honestly said “not sure” — and the single most valuable thing we did on the whole job was to tell the client not to buy something.
Questions people ask about taking a UK naturalisation certificate abroad
Does my naturalisation certificate need to be notarised before it goes abroad?
Usually not. It is a public document issued by a government department, so the ordinary route is an apostille from the FCDO Legalisation Office rather than a notarial act. Notarisation exists to bring private documents into the authentication chain. If someone has quoted you notarisation on a naturalisation certificate, ask them what exactly is going to be authenticated.
What does an apostille actually prove?
That the document is genuinely what it appears to be and was issued by the body named on it. It does not oblige a foreign authority to accept the document, does not certify that it is current, and says nothing about any translation attached to it. Confirm the receiving authority’s own requirements before you commit.
Does the apostille go on the original or the translation?
It depends on what the receiving authority asks for, which is why that question has to be asked first. Commonly the apostille goes on the public document and the certified translation accompanies it; some authorities want the translation brought into the chain as well, and some want a sworn translator in their own country instead. Each of those is a different job and a different cost.
Is there an EU route that avoids all this?
There is an EU regulation that removes legalisation requirements for certain public documents moving between EU member states. The United Kingdom is not a member state, so it does not apply to a UK-issued document. The Hague apostille route is the one that applies.
Should my name be adapted into Lithuanian form on the translation?
No — not on a document that evidences identity. Your name is reproduced exactly as it appears on the certificate and your passport, in its original Latin-character spelling, without grammatical endings. An adapted name breaks the chain back to your passport, which is the one thing the reader needs to be able to follow. How your name is eventually entered in a Lithuanian register is a decision for the Lithuanian authority, not for a translator.
Can I translate it myself, or get a relative who speaks Lithuanian to do it?
You can produce a Lithuanian version, but you cannot certify it in any way a careful reader will treat as independent, because the certificate of accuracy is a statement about the translation made by someone with no interest in the document. On a nationality document in particular, a self-made translation invites exactly the question you do not want asked. Our note on the hidden risks of free and self-made certified translations covers where this goes wrong.
I have lost my naturalisation certificate. Can you work from a copy?
We can translate from a legible copy, and we will say so on the certificate of accuracy — it describes exactly what we received. But an authentication layer acts on a document, and a receiving authority asking for an apostille will generally want the issued certificate rather than a photocopy. Replace the certificate first if that is the route you are on.
My document is going to a country that is not in the Hague Convention. What then?
Then the route is the older one: UK authentication followed by legalisation at that country’s mission in London, in that order. It takes longer and costs more, and it is worth confirming the mission’s current requirements before starting, because missions set their own and change them.
If you are taking a British document the other way
Tell us the destination country and the office that asked for it. Those two facts decide everything else: whether a notary is involved, whether an apostille is needed, whether the translation enters the authentication chain, and whether what is wanted is a UK certified translation at all.
Our certified legal translation services page covers official and authority-bound documents in both directions, and our sworn translation services page explains where that term fits and does not fit in UK practice — a distinction that matters a great deal on outbound work, because some countries want a sworn translator of their own. If your file also includes identity or civil-status records, see passport translation, birth certificate translation and marriage certificate translation. Where a document has to be executed for use before a foreign notary, our power of attorney translation page covers that class, and our guide to the UK government bodies that routinely ask for certified translations is the companion piece for documents coming the usual way.
When you are ready, hire a translator and put the destination country in your first sentence. On an outbound job it is worth more than every other field on the form put together.