A certified translation case study from our UK Home Office work. The client is identified by first name only and no document is described in a way that could identify her or anyone else whose papers were in the set.
The enquiry came in through our hire a translator form and, on the face of it, it was ordinary. Nancy, writing from Belgium, needed a certified translation for a Home Office (UKVI) visa application. Source language: Dutch. Target language: English. Nine pages. Notarisation: yes. Document type: Other. Nothing uploaded.
Then the message field, which is where the truth usually lives: “Some documents are in French and others in Dutch.”
That one sentence changed the whole job. The form had recorded a single source language, because almost every form in this industry assumes an order has one. What Nancy actually had was a nine-page Belgian set split across two source languages, going into one UKVI visa file, with nothing attached for us to look at and no indication of what the documents were. Everything that followed came out of that mismatch.
Why a Belgian set legitimately arrives in two languages
The first thing worth saying, because it is the thing applicants most often get wrong about themselves, is that Nancy had done nothing unusual. Belgium has three official languages – Dutch, French and German – and the language a public document is issued in follows the region and the issuing authority, not the person holding it.
A gemeente in Flanders issues in Dutch. A commune in Wallonia issues in French. The Brussels-Capital Region is bilingual and will issue in either, depending on how the register entry and the request were made. The German-speaking Community in the east issues in German. So a person born in one region, married or registered in another, and employed or resident in a third ends up holding a stack of documents in two or three languages, every one of them a perfectly valid original.
Nobody in that position has been given a reason why. It is not a mistake, it is not a sign that a document is unofficial, and it is not something the holder chose. We say this early to clients because the usual instinct is to assume something is wrong with the papers and to go back to the Belgian authorities asking for a re-issue “in the right language” – which wastes weeks and, in most cases, is not available anyway. The documents are right. It is the translation plan that has to absorb the complexity.
The part that made it harder than nine pages of Dutch
If all nine pages had been Dutch, this would have been a straightforward piece of work. Two source languages made three separate problems appear at once.
UKVI’s requirement lands on each document, not on the order
This is the single most expensive misunderstanding we see, and it is worth setting out carefully. The Home Office does not ask for “a certified translation of your application”. It asks for a translation of each document that is not in English or Welsh.
The Immigration Rules put it directly. Appendix FM-SE, in its general provisions, requires that where a specified document is not in English or Welsh the applicant supplies the original plus a full translation that can be independently verified by the Entry Clearance Officer, Immigration Officer or the Secretary of State. That translation must be dated, and must contain confirmation that it is an accurate translation of the document, the full name and signature of the translator or of an authorised official of the translation company, and the translator’s or company’s contact details. For leave to remain and indefinite leave to remain applications it must additionally be certified by a qualified translator, with details of the translator’s or the company’s credentials.
GOV.UK’s own plain-English guidance on certifying a document says the same thing in shorter form: the translator must confirm in writing that it is a true and accurate translation of the original document, state when the translation was completed, and give their full name and how to contact them.
Read that as an instruction about quantity and the operational consequence falls out immediately. A nine-page bundle containing, say, four or five distinct documents is not one translation with one certificate at the front. It is four or five certified translations, each one carrying its own certification, each one independently verifiable on its own terms. We have seen applicants assemble nine translated pages, staple a single certification sheet to the top and submit it in good faith – and submit something short. The caseworker is checking documents, one at a time, against a checklist. A certificate that covers “the enclosed” does not tell them that the page in front of them has been certified.
Two source languages means two competences
The second problem is one the industry is often coy about, so we will be blunt. A translator qualified to produce a certified French-to-English translation of a Belgian civil document is not automatically qualified to do the Dutch one. Some linguists work in both. Most do not, and the honest answer to “can one person handle this?” is usually no.
That is not a difficulty in itself – it is a planning problem, and it is the real planning problem in a job like this. Who translates the French pages. Who translates the Dutch pages. Who reviews each half, in the language it was written in, by someone competent in that language. And then the question that actually decides whether the bundle holds up: who owns the set as a whole, so that the same name, the same date, the same town and the same registry office come out identical on both halves.
Accuracy within one language is the easy half. Consistency across two is where mixed sets fail.
The same Belgian town has two names, and so does its registry
Here is the trap, and it is specific to exactly this kind of order. Belgian municipalities frequently have a Dutch name and a French name: Kortrijk is Courtrai, Mons is Bergen, Antwerpen is Anvers, Brussel is Bruxelles. The issuing office has two names too – a dienst burgerlijke stand in one language is a service de l’etat civil in the other, and a translator working page by page will often render the Dutch one as “civil registry department” and the French one as “registry office of civil status” without ever noticing they have just described the same institution twice.
Multiply that across nine pages and the caseworker opens a bundle in which the same person appears to have been registered in two different towns by two different authorities. Nothing in it is wrong. All of it looks inconsistent, and inconsistency in an immigration file is the thing that generates questions.
So the rule we work to is: decide once, apply everywhere, and say what you decided. Place names and authority names are settled before translation starts, not negotiated page by page. Where a town carries two official forms, the form printed on that source document is kept as the primary rendering and the other form is given once in a short translator’s note, so the reader can see for themselves that Kortrijk and Courtrai are one place. What we do not do is silently pick one and hope. A note costs two lines; a caseworker’s query costs weeks.
The first real move was finding out what the nine pages were
Because nothing was attached and the document type said “Other”, we could not plan anything until we knew what we were looking at. “Nine pages” is not a document set – it is a page count, and nine pages for a visa file could be civil-status records, employment or financial evidence, or a mixture of both. Each of those changes the certification wording, the order of work and who needs to review what.
So the opening conversation was not a quote. It was a short, specific list of questions:
- How many separate documents make up the nine pages, and which pages belong to which document? This is the question that converts a page count into a certification count.
- What is each document, and which authority issued it? The issuing authority tells us the region, and the region usually tells us the language before we have even seen the page.
- Which pages are French and which are Dutch? Asked explicitly, because clients who have lived with bilingual paperwork all their lives sometimes stop registering which is which.
- Is any page an extract or an abbreviated certificate rather than a full copy? Belgian registries issue several forms of the same record, and a translation must represent the document actually in front of it.
- Does any page carry an apostille, legalisation stamp or official annotation – and what language is the stamp in? Stamps, seals and marginal notes are part of the document and have to appear in the translation. A French apostille attached to a Dutch certificate is its own small mixed-language problem.
- Has anything already been translated? Part-translated sets are common and are usually best redone, because a certification we did not issue is a certification we cannot stand behind.
- What does the document list for the application actually ask for? We translate what the file needs, not everything in the drawer.
Those questions took one exchange. They saved the job. Once we knew how the nine pages divided, we knew how many certified translations the bundle required – and that number, not the page count, is what the client needed to understand before anything else was agreed.
Where notarisation fits, and where it does not
Notarisation had been ticked on the form. We did not simply bill for it.
What UKVI asks for in respect of a translated document is the certification described above: the accuracy confirmation, the date, the translator’s or the company’s name, signature and contact details, and – for the in-country routes – a qualified translator and their credentials. A notary’s involvement is a different act. The notary is attesting to a signature and an identity, not reading the Dutch and confirming that the English matches it. On the published requirement for translated documents in a UKVI application, notarisation is not what is being asked for.
That does not make it pointless. Notarised translation is genuinely required by plenty of other receiving bodies – foreign registries, some overseas authorities, certain commercial and court processes – and if a document from this same set is going on to one of those afterwards, having it notarised in the same run is sensible and saves a second job. So we explained the distinction, asked where else the papers were going, and left the decision with the client rather than quietly adding a service because a checkbox had been ticked. Clients remember being told they did not need something.
How we built it
With the set mapped, the work ran in a deliberate order.
The set was split by language and assigned to linguists working in the right direction for each half, each with a reviewer competent in that source language – the French pages reviewed in French, the Dutch pages in Dutch. Many of our translators hold ITI membership, and Home Office Translations UK is an ATC member company.
Before either half was translated, we built the set’s term sheet: every personal name as it appears on each source document, every place name with both its Dutch and French forms, every issuing authority with a single agreed English rendering, and one date convention for the whole bundle. Belgian documents in both languages write dates day-first, but the month names differ, and a bundle that mixes numeric and written dates reads as careless. That sheet was the contract between the two halves of the job.
Each document was then translated in full – every seal, stamp, marginal annotation, pre-printed form text and signature block represented, with illegible elements marked as illegible rather than guessed. A partial translation of an official record is not a certified translation of it.
Each document then received its own certification, carrying the elements UKVI’s requirement specifies, dated, signed and traceable to us. Not one certificate for the bundle. One per document.
Finally, the whole set was cross-read by one person whose only job was consistency across the two languages: does the same name appear identically on the French pages and the Dutch pages, is the same municipality the same municipality throughout, is the registry office called one thing, do the translator’s notes agree with each other. We also laid the delivered file out so that each translation sits with its own original and the pagination makes clear which belongs to which, which is a small courtesy to the person who has to check it and a real reduction in the chance of a query.
Delivered inside Nancy’s target date.
How it turned out
The file went in complete and on time. Every document in the set was certified exactly as UKVI’s requirement for translated documents specifies – each one individually, each one dated, each one naming and contactable back to us. Names, places and authority names read identically across the French pages and the Dutch ones, with the dual-name question answered openly in the translation rather than decided behind the reader’s back. Nothing came back to us as a query about the translations.
Nancy confirmed the set did its job: the bundle she submitted was the bundle the checklist asked for, and she was not left explaining her own paperwork to a caseworker. What happens next in the application is the Home Office’s to decide, and we make no claim about it – our side of it was complete, correct and in her hands before the date she needed it.
What a two-language file taught us to say first
If your own papers have arrived in more than one language, the useful thing to take from Nancy’s set is not reassurance – it is a reordering of the questions.
Stop counting pages and start counting documents, because the certification count follows the documents and that is the number the Home Office is working from. Expect a separate certified translation for each document that is not in English or Welsh, and be suspicious of any arrangement that offers you one certificate for the lot. Ask who is reviewing each language, not just who is translating. And ask what happens to the names – the names of people, of towns and of the offices that issued the papers – across the two halves, because that is the join where a perfectly accurate set still manages to look wrong.
Mixed-language sets are not rare and they are not a problem with your documents. They are a problem with the assumption that an order has one source language. We plan around that assumption on every Belgian, Swiss and Canadian set that crosses our desk, and on anything else where the language of a document follows the authority that issued it rather than the person who holds it.
If you are putting a visa file together and some of it is not in English, our guide to translating documents for a UK visa sets out the ground rules, and our notes on certified translations for UK immigration documents go further into what the certification itself has to say. For the documents themselves, we handle certified birth certificate translation and marriage certificate translation for UK use, and where a set needs the formal legal treatment, our certified legal translation service covers it. Send us a page count and, more importantly, tell us how many documents are in it and what languages they are in – that is the sentence that lets us plan the job properly.
Requirements for translated documents are set by the Home Office and can change. The wording described here reflects the published Immigration Rules and GOV.UK guidance at the time of writing; always check the current document list for your own application before you submit.
