Within about ten minutes one November afternoon, three requests arrived from the same person. George, a client based in the UK, was putting together Catalan and Spanish documents for a UK visa application and had done what most busy applicants do: scanned everything, merged it into one file per language, and sent it off. The first upload was a 14-page Catalan PDF with notarisation ticked. The second was an 8-page Spanish PDF without it. The third was the Catalan set again, with a short message: he had redone the request because the translation did not need to be notarised.

On paper this looks like admin noise. In practice it is a very common pattern, and the way it is handled decides whether the applicant ends up with a clean, usable set of translations or a pile of paperwork that costs more than it should and is harder for a caseworker to follow. This is how we read the three uploads as one job and what we set out to prepare.

What George sent, and the one question he asked

Each lodgement told us something slightly different, so it is worth laying them side by side.

Upload Source language Pages Notarisation Note from the client
First Catalan 14 Requested All documents in one PDF; asked whether to upload them separately
Second Spanish 8 Not requested Again, all documents combined into one PDF
Third Catalan 14 Not requested Resubmitted because notarisation was not needed

All three named the Home Office (UKVI) as the certification standard and a visa application as the purpose. The form recorded the document type as “Other”, which tells you the bundle is not a single certificate but a mix of records. We are not going to describe what those records are here; the point of this case study is the shape of the job, not the contents of someone’s file.

George asked one direct question: did he need to upload the documents separately? That question deserved a straight answer, and we come back to it below. The quieter question inside the three uploads was different. Which of these requests is the real one?

Why a Catalan bundle is not just “more Spanish”

Applicants outside Spain sometimes assume that Catalan is a regional flavour of Spanish and that any Spanish translator can handle it. It is not, and they should not. Catalan is a separate Romance language with its own grammar, vocabulary and official terminology. It is co-official with Spanish in Catalonia and, in its local forms, in other parts of Spain, which is why public bodies in those areas regularly issue records in Catalan, in Spanish, or in both on the same sheet.

That has three practical consequences for a visa file.

Two languages, one country, sometimes one page

A bilingual page is the trap. If a certificate prints every heading in Catalan and Spanish side by side, a careless approach translates both columns and doubles the word count for no benefit. A sensible approach renders the content once, notes that the original is bilingual, and translates any part that appears in only one of the two languages. The reader at UKVI gets one clear English version, and the translator’s certificate states exactly what was translated.

Terms that look familiar and are not

Catalan official vocabulary can look close enough to Spanish to tempt a guess. Office names, registry references, the wording of stamps and the terms used for family relationships or employment status need to be read in Catalan, not inferred from Spanish. A visa caseworker will not know the difference, which is exactly why the translator has to.

The split between the two PDFs may not be clean

George sorted his scans into a Catalan file and a Spanish file. That is helpful, but a person sorting documents by eye can easily put a mostly-Spanish page with a Catalan heading into the Catalan pile, or the other way round. Part of our check was to confirm, page by page, that each sheet sat with the right language before anything was quoted as final.

Reading three lodgements as one job

Our order system gives every upload its own code, and on screen George’s three requests looked like three separate orders: 14 notarised pages, 8 certified pages and another 14 certified pages. Taken literally, that would mean quoting the Catalan bundle twice, once with a notary and once without, and adding the Spanish set on top.

That is obviously not what he wanted. The third message makes the intent plain: it replaces the first. So the working file became a single combined job:

  • 14 pages of Catalan into English, certified to the Home Office standard, no notarisation.
  • 8 pages of Spanish into English, certified to the same standard, no notarisation.
  • One client, one visa application, one set of translations designed to sit together.

The first Catalan request, the notarised one, was treated as superseded rather than as a second order. The resubmission carried no file of its own, so the PDF from the first upload remained the source for the Catalan work. Merging the three into one story matters for the client in a plain way: he should receive one quote and one coherent set of documents, not two overlapping ones.

Did he actually need a notary?

George changed his mind about notarisation within minutes, and he was right to question it. For UK immigration, the Home Office asks for certified translations of documents that are not in English or Welsh. GOV.UK’s visitor visa guidance, for example, says simply that you must provide certified translations of any documents that are not in English or Welsh. The certification comes from the translator or translation company: a signed statement that the translation is a true and accurate rendering of the original, dated, with the translator’s name and contact details. Check the current guidance for your own visa route, because the detail can differ.

A notary adds something different. A notary public confirms the identity and signature of the person signing the translator’s declaration. That is useful when a foreign authority, a court or a specific institution asks for it. For a standard UK visa file it is usually an extra layer nobody has requested. Our page on notarised translation services in the UK explains when that layer genuinely earns its place.

So the honest advice was: do not pay for notarisation on 14 pages unless the visa route or a specific instruction asks for it. If a later step does ask, a certified translation can be notarised afterwards without being redone.

The answer to “should I upload them separately?”

For us, one PDF per language is perfectly workable. We split the file internally, identify each document within it and count pages properly. George did not need to start again.

The output is a different matter, and this is where we planned the work around the person who will eventually read it. A UKVI caseworker looks at a document and its translation together. If 22 pages of mixed records come back as one long English file, the caseworker has to hunt for which translated page belongs to which original. So the plan was to return each document as its own translation, each carrying its own certification, named so it can be matched to the original at a glance. George could then upload them in pairs, original and translation, in whatever order his application portal asks for.

We took a similar approach in an earlier file where a Belgian visa file arrived in Dutch and French; the languages were different, but the lesson about matching each translation to its own original carried straight across.

What we prepared to deliver

At the point this case study was written, the job was at the quote and scoping stage. The plan we set out for George covered:

  1. A page-by-page check of both PDFs to confirm the language of each sheet and flag any bilingual Catalan and Spanish pages.
  2. Translation of the Catalan pages by a translator working from Catalan, and of the Spanish pages by a Spanish translator, both into English.
  3. Complete translations: headings, body text, stamps, seals, handwritten notes and marginal entries rendered or described, with nothing summarised away.
  4. Names, dates and reference numbers carried across exactly as they appear in the originals, with Spanish and Catalan naming conventions (two surnames, particles and accents) kept intact.
  5. A signed certification on each translated document, meeting the Home Office expectation for certified translations, without notarisation.
  6. Files named to mirror the originals, so each translation can be uploaded next to the document it belongs to.

Where it stands: one merged job, two languages, 22 pages in total, certification only. The earlier notarised request is treated as superseded, so it should not be quoted or processed alongside the new one.

A short checklist if your documents are in Catalan, Spanish or both

  • Sort your scans by language if you can, but do not worry about perfection; a good translation team will check each page anyway.
  • Tell the translator if some pages are bilingual, so they are not translated twice.
  • Read the guidance for your specific visa route before ticking notarisation. Most UK visa files need certification, not a notary.
  • If you change your mind after submitting, say clearly which request replaces which. One line is enough, and George’s was exactly that.
  • Keep the original documents to hand. The translation supports the original; it does not replace it.
  • Ask for each document to be translated and certified as a separate file, so the caseworker can match every page.
  • Check that names are spelled the same way across all your translations and your passport, accents included.

Questions applicants ask about Catalan and Spanish visa documents

Can one translator do both the Catalan and the Spanish pages?

Sometimes, if they genuinely work from both languages. What matters is that whoever translates the Catalan pages reads Catalan properly rather than relying on Spanish. We assign each language to a translator who works from it.

My certificate has Catalan and Spanish on the same page. Will I pay for both?

Not if the two columns say the same thing. We translate the content once, note that the original is bilingual, and translate anything that appears in only one language.

I ticked notarisation by mistake. Is it too late to change?

No. Tell us before work starts, as George did, and the quote changes to certification only. If an authority later asks for notarisation, it can usually be added to the existing certified translation.

Will UKVI accept a translation of a document issued in Catalan?

The Home Office rule is about the target language, not the source. Any document not in English or Welsh needs a certified English translation, whatever language it started in. Whether a particular document supports your application is a separate question for your route’s guidance.

Do I need to send the original paper documents to the translator?

No. Clear scans or a well-lit PDF are enough for us to translate from. Keep the originals safe for your application, since the visa process may ask you to provide them or copies of them.

Should I translate every page in my bundle?

Translate every page you intend to submit. If a page is not going into the application, there is no need to translate it, but do not leave out parts of a document you are submitting, such as the reverse side or an attached stamp.

Sending us a mixed-language bundle

If your visa file mixes Catalan and Spanish, or any two languages, send it as it is. We will read the pages, tell you what each one is, and quote one job rather than several. You can upload it through our hire a translator order form. For another Spanish file prepared for a UK visa, see how we handled Spanish Bachillerato certificates for a student visa.

Related case studies