The Working Language: A Business Standard for Scots and Gaelic Beyond Display
Photo by Photo by Arpita Ghosh on Unsplash on Unsplash
On a wet Tuesday in Glasgow, a campaign team reviews a new poster. The English line is crisp. Below it, a Gaelic phrase has been added in a decorative script, chosen because it looked distinctive. No one in the room speaks Gaelic. The phrase is grammatical, but the accent is missing, and the placement suggests ornament rather than address. A Gaelic speaker will notice within seconds. The poster will still communicate, but it will also communicate something else: that the language was added as a signal, not as a service.
That is the risk facing any UK organisation that wants to use Scots or Gaelic in business messages. The intention is usually good. The execution often stops at the visual. A language is not a texture. It is a working system of meaning, with grammar, pronunciation and register. If it appears in a campaign, a sign or a public message, it should meet the same standard as the English text beside it.
Begin with the service question
Before commissioning a translation, ask what changes for the audience. Bilingual messaging earns its place when it helps someone understand a notice, use a service, feel addressed in a public setting or take part in a consultation. In those cases, the second language is not a gesture; it is part of the access standard. Gaelic language plans in parts of the public sector already make this operational, and Scots can play a similar role where local audiences use it.
For a corporate slogan or a seasonal campaign, the service case is weaker. That does not make the use illegitimate, but it does change the burden of proof. If the language is there to signal commitment to place, the organisation must show that commitment elsewhere: in recruitment, in staff training, in customer materials and in the accuracy of the text. A single line of Gaelic on a homepage cannot carry that weight alone.
Pronunciation is part of proofreading
Spoken content exposes errors that print can hide. A recorded greeting, a radio advertisement, a conference welcome or a video voiceover will be heard by speakers who know how the language should sound. Gaelic has pronunciation rules that are not intuitive from the spelling to an English-speaking eye. Scots has varieties and local norms; a phrase that sounds right in Aberdeen may sit differently in Ayrshire.
The practical answer is not to guess. Commission a pronunciation check alongside the translation. Ask a first-language speaker or a qualified language coach to record the line. Give spokespeople a written phonetic guide and a short audio reference. Build time for rehearsal into the production schedule. This is not an exotic extra; it is the same discipline an organisation would apply to a product name or a legal term.
Translation is a review process
Machine translation has its uses, but it is not a sign-off. For Gaelic, commission a qualified translator with experience of the register you need. For Scots, agree the variety and the orthography before work begins. Scots has no single standard, and a generic version can read as neither one place nor another. A glossary of recurring terms, approved by the language lead, prevents drift across campaigns.
The review should happen in context. A translator working on a standalone paragraph may produce accurate prose that becomes clumsy when it meets a headline, a button or a tight layout. Ask for a second review after design. Check that meaning survives, that tone matches the English, and that nothing has been added or removed to fit the space. Record who approved it and when. This is basic quality control, not bureaucracy.
Design that does not decorate
Bilingual design fails when one language is treated as illustration. Common mistakes include placing Gaelic in a decorative script, adding tartan borders, using a saltire as a substitute for a layout idea, or setting the second language so small that it cannot be read. These choices turn a working language into a symbol of Scottishness. They also make the text harder to use.
Treat the languages as typographic equals. Keep the same size, contrast and placement logic. Check accents, line breaks and text expansion. If the Gaelic line is longer, adjust the layout rather than shrinking the type. Avoid using Alba as a brand flourish unless the context genuinely calls for it. A simple test: if the same design approach were applied to French or Polish, would it look absurd? If so, it is decoration, not communication.
The tartanry test
Tartanry is the habit of reducing Scottish identity to a set of visual cues: shortbread, claymores, misty glens and a sprig of tartan on every surface. It is not harmless. In business messaging, it signals that the organisation sees Scotland as a theme rather than a place where people live and work. Scots and Gaelic deserve better than that.
A useful test has three questions. Does the language say something useful to the audience? Has it been reviewed by someone who knows it? Would a speaker feel addressed rather than used? If the answer to any of these is no, the text is not ready. The aim is not to remove personality from the message. It is to make the personality credible.
A small protocol that holds
Organisations do not need a large language department to get this right. They need a one-page protocol. It should state the purpose of using Scots or Gaelic, the approved translator and reviewer, the pronunciation check for spoken content, the design rules, the approval route and the review date. It should also say who is responsible for the final sign-off.
That protocol should be shared with agencies, designers and event producers. It should be revisited after each campaign. Over time, it becomes a record of decisions rather than a set of vague good intentions. The result is not a perfect performance of Scottishness. It is something more valuable: language that is ordinary, accurate and useful.
Clear voices build trust. In this area, trust is built by treating Scots and Gaelic as working languages, not as a sprig of tartan.