The client’s problem
Wojciech wrote two sentences and they contained everything that mattered: he needed his driving licence translated from Polish to English, and it was for the police, for a licence conversion.
The order form, meanwhile, recorded the document type as “Other” and the purpose as “Not Sure”. Both fields contradicted the message sitting next to them. The length field said “1 Pages/250 words”, which is two different units of measurement in one box and, for a credit-card-sized licence, substantially more words than the document contains.
We worked from the message. A client who writes a plain sentence naming the document and the authority has told us more than any dropdown will.
Why it was harder than it looked
Here is the thing about a Polish driving licence that makes it a different job from almost every other document this firm handles: most of it is not language.
Poland issues the harmonised European Union model licence – a plastic card on which the information is laid out in numbered fields under a scheme shared across the member states. The holder’s surname is in a numbered field. The given names are in another. The dates of issue and expiry, and the issuing authority, sit in a lettered series of their own. The categories of vehicle the holder may drive are listed as short alphanumeric codes rather than described in words. And the conditions attached to those entitlements are recorded as numeric codes in a further field.
What that means in practice is that a translator who approaches the licence as a text to be translated finds very little text. The field labels are in Polish, sometimes abbreviated; the content is largely numbers, dates and codes. A word-for-word approach produces a page of correctly translated labels attached to codes that remain opaque to the person reading it.
And the person reading it is a Singapore officer processing a conversion, who has no reason to know what any of those codes mean. The harmonised scheme is harmonised across Europe; it is not self-explanatory outside it.
This produces two specific risks, and they pull in opposite directions.
The first is omission. The conditions field is the dangerous one. Where a licence carries codes in that field, those codes are legal restrictions on the holder’s entitlement – the harmonised scheme uses them for things like a requirement for corrective eyewear or for an adapted vehicle. A translation that renders the licence’s visible prose and leaves the conditions field as a bare string of digits has handed the authority a document that understates the terms on which the holder is licensed. That is not a presentational failure. The restrictions are part of what the licence says.
The second risk is the opposite: invention. A translator who decides to be helpful may expand a category code into a description of what vehicles it covers, or expand a conditions code into a sentence about the holder’s circumstances. Both overstep. The code’s meaning is defined by the scheme, not by the translator, and a translator who paraphrases what a restriction means has started supplying content the document does not contain – and, in the case of a conditions code, content that may concern the holder’s health.
So the licence has to be rendered in a way that is complete without being inventive. That is the whole technical problem of this job.
There is a third point, and it is the one that most often determines whether a conversion goes smoothly: when the holder became entitled to drive.
A licence card carries a date of issue, and clients naturally assume that is the date their driving history begins. On an EU-model licence it very often is not. The cards are renewed and replaced on fixed cycles, so a long-standing driver may hold a card issued recently. The entitlement dates – the date each category was first obtained – are recorded separately, per category, in their own field on the same card.
This is good news, and it is worth saying clearly because the alternative situation is common and expensive. Where a licence does not carry per-category entitlement dates, a driver who needs to evidence a longer history has to produce a second document – the superseded licence, or a record from the issuing authority. On a harmonised EU licence, that history is already on the single card, provided the translator renders the per-category dates rather than collapsing them into the card’s issue date.
Fourth, the name. Polish uses diacritical marks that change both pronunciation and identity: a letter with a stroke or a tail is a different letter, not a decorated version of the plain one. Dropping them is not a simplification, it is a different name. And Polish surnames inflect, so the form on the licence may not be the form a Polish speaker would use in a sentence – which is irrelevant to us, because the licence’s form and the passport’s form are the only two that matter, and the passport governs.
How we approached it
We corrected the specification first, on the record: document type, a driving licence; receiving authority, the police, for a licence conversion. That took one line and it means anybody who opens the order later sees what the job actually was rather than “Other” and “Not Sure”.
Then we built the translation around the card’s own structure rather than against it. The numbered and lettered fields were reproduced as fields, each with its label translated and its content rendered exactly: surname, given names, date and place of birth as the card records them, the dates of issue and expiry, the issuing authority’s designation, the licence number, and the categories.
For the categories, each code was given exactly as printed, together with its per-category dates where the card carries them. No category code was expanded into a description of the vehicles it permits.
For the conditions field, every code present was reproduced in full and identified as a harmonised restriction code, with a note that the codes are defined by the scheme under which the licence was issued. Nothing was omitted and nothing was interpreted. Where a code might bear on the holder’s personal circumstances, the translation records the code and stops there, which is both the accurate course and the appropriate one.
Where the field labels on the card were abbreviated, we gave the full label in English and kept the Polish abbreviation visible, so a reader comparing the translation to the card can see which field is which.
Both sides of the card were translated. This is routine and it is routinely missed: on the harmonised licence the categories table and the conditions field are on the reverse, which means a client who photographs only the front has sent us the half of the document with the least information on it. We asked for both faces before starting.
The name was rendered with full Polish diacritics as they appear on the licence, and matched to the client’s passport spelling in the body of the translation, with both forms visible where they differ.
Dates were given with the month as a word.
Finally, certification: a signed statement that the English is a true and complete rendering of the licence produced to us, with the translator’s name, contact details and date, in the form a Singapore authority expects. The client’s form had notarisation switched off and that was right – for a licence conversion, a certified translation is what is called for, and we did not add a layer nobody had asked for.
What we delivered
One certified English translation of both faces of the licence, reproducing the card’s numbered field structure rather than flattening it into prose: every field label translated with the Polish abbreviation kept visible, every category code given exactly as printed with its per-category entitlement date, every restriction code reproduced in full and identified as a harmonised code without interpretation, the issuing authority and licence number rendered precisely, the name carrying its correct Polish diacritics and matched to the passport, dates unambiguous, and a certification statement in the form the receiving authority requires.
Delivered inside the deadline, with the specification corrected on the order record and no notarial layer added.
The result
The translation went in complete and on time, with nothing queried. The client’s full driving history was visible on the face of the translation because the per-category dates were rendered rather than collapsed, which meant no second document had to be found and no second order placed.
What an authority decides about a licence conversion is entirely a matter for that authority, and nothing here suggests otherwise. Our part was to make sure the document in front of them says everything the original says, including the parts written in code.
What a reader in the same position should know
Photograph both sides. On a European licence the categories and the restriction codes are on the back, and the back is the half that carries your driving history.
Do not assume the issue date on the card is when you started driving. Look for the per-category dates. If your card has them, your history is already on it and you do not need to find your old licence.
Expect the codes to be reproduced, not explained. A translator who writes a paragraph describing what each of your codes means has gone beyond the document. The codes are defined by the scheme that issued the licence, and an authority processing a conversion knows how to look them up.
Make sure your name keeps its Polish letters, and tell us how your passport spells it. Those are two different renderings of one name and both belong in the translation.
And write a sentence in the message box saying what the document is and who wants it, even if the dropdowns do not match. On this job that single sentence was more use than the whole form.
You can read about this work on our certified driving licence translation in Singapore page, and about the identity documents that often travel with it on our passport translation and personal document certified translation pages. If an authority has asked you for a notarised translation rather than a certified one, our notarised translation page explains the difference. Our FAQs answer the questions clients ask most, and you can hire a translator with photographs of both faces of your licence.
Ethan Lim
Hi, I’m Ethan Lim, a certified translator and language expert at CertifiedTranslationService.sg. I share clear and helpful articles about certified translation services in Singapore, covering ICA document needs, immigration papers, legal translation, and notarization. With my knowledge of industry standards and client needs, I guide readers through the translation process with trust and confidence.