The meeting starts in English. Everyone nods, the agenda gets going, and then someone asks a question in Dutch. The answer comes back in Dutch too. Within five minutes the whole meeting has switched, and your new colleague from Spain sits there, watches it happen and slowly tunes out. Nobody did anything wrong. It was just never agreed how things would go.<\/p>\n
That is exactly what a language policy prevents. A language policy is a deliberate agreement about which language or languages your organisation uses in which situations, and how you support your people in doing so. Not a thick document that disappears into a drawer, but a few clear choices everyone can fall back on.<\/p>\n
Many organisations do not have one. Not out of unwillingness, but because language rarely belongs to anyone. It falls between HR, L&D and management. And it is right there, in that no man’s land, that the problems start that you later see reflected in turnover, miscommunication and colleagues who do not feel heard.<\/p>\n
A language policy sets out which language is the norm in which situation. Which language you speak in meetings, which language you use for internal email, how you handle client contact, and what you do on the work floor where safety depends on understanding what is being said.<\/p>\n
What matters is the difference between the formal working language and the informal practice. On paper English can be the working language, while in reality the hallways, the coffee machine and half the meeting simply run in the local language. That gap is not a problem, as long as you made it consciously. “We just wing it” is not a policy. It is the absence of one, and that absence costs you more than you think.<\/p>\n
Language is often seen as something you sort out later. First the job content, then the language. But language touches precisely the things HR and L&D are measured on.<\/p>\n
Think of retention. An employee who cannot express themselves in meetings feels less part of the team and leaves sooner. Think of internal mobility. Talent that does not master the working language well enough does not progress, however good they are at the work itself. Think of inclusion. Whoever cannot follow the language misses not only information but also the informal moments where the real work gets aligned. And think of safety, because on a work floor where instructions are misunderstood, something goes wrong sooner or later.<\/p>\n
Language is not a side issue you arrange after onboarding. It is the infrastructure everything else runs on. We wrote earlier about why language is not a soft skill but a strategic strength<\/a>, and about how language is the biggest challenge in onboarding expats<\/a>.<\/p>\n Without agreements, a pattern emerges that you will probably recognise. Meetings unconsciously switch back to the mother tongue of the majority. Important information gets shared twice, once formally and once informally, and the informal version is often the real one. International colleagues ask fewer questions, not because they have nothing to say, but because the threshold is too high.<\/p>\n Those costs appear on no invoice, and that is exactly what makes them dangerous. Rework because something was misunderstood. A good hire who leaves again after a year. A project that slips because the alignment keeps faltering. Each of these can be expressed in money, and added together they are many times more expensive than the policy and support that could have prevented them.<\/p>\n This is the core choice, and it is rarely black and white. Many organisations think they have to choose between everything in English or everything in the local language. In practice a layered choice works better. English as the working language for formal communication and documentation, for example, and room for the local language where that strengthens connection.<\/p>\n Watch out for one common misconception. Introducing English as the working language does not mean nobody needs to learn the local language anymore. On the contrary. Whoever lives and works in a country needs the local language to truly belong, on the work floor and beyond. The working language handles collaboration. The local language handles the sense of belonging. Both deserve attention.<\/p>\n A language policy does not have to be a months-long project. These six steps get you to something that is sound and that works.<\/p>\n Want to know where your team stands before you make policy?<\/p>\n The Business English Team Scan objectively maps the actual language level of your team. A low-threshold starting point for step 4.<\/p>\n Take the Business English Team Scan \u2192<\/a><\/p>\n<\/div>\n Even with the best intentions, things sometimes go wrong. These are the five pitfalls we come across most often.<\/p>\n The first is a policy on paper that never lands in practice. A nice document nobody acts on changes nothing. The second is not accounting for different levels within one team. A single average hides large differences. The third is treating language as a one-off project instead of an ongoing part of your people strategy. The fourth is reserving no budget for support, so it stays at good intentions. And the fifth, perhaps the most stubborn, is the assumption that everyone “speaks English well enough”. Passively understanding and actively taking part are two very different things.<\/p>\n Introducing a language policy is one thing. Knowing whether it delivers is another. Do not only look at whether people completed a course, but at what changes in daily work. Do international colleagues take a more active part in meetings? Are there fewer misunderstandings? Does talent stay longer? We went into this in more depth in how you know if language training actually works<\/a>.<\/p>\n What is a language policy in the workplace?<\/strong> Is an employer required to have a language policy?<\/strong> Should you choose English or the local language as the working language?<\/strong> How do you determine which language level your team needs?<\/strong> Who is responsible for the language policy, HR or management?<\/strong> What does introducing a language policy cost?<\/strong> Ready to get started with language policy in your organisation?<\/p>\n Drawing up a language policy is step one. Knowing where your team actually stands is step two. We are happy to think along, with no obligation, about an approach that fits your people and your goals.<\/p>\nWhat goes wrong without a language policy<\/h3>\n
The hidden cost of no policy<\/h3>\n
English as the working language, or the local language as the connector?<\/h2>\n
6 steps to a workable language policy<\/h2>\n
\n
The 5 most common pitfalls<\/h2>\n
How do you measure whether the language policy works?<\/h2>\n
Frequently asked questions about language policy<\/h2>\n
\nA language policy is a deliberate agreement about which language or languages your organisation uses in which situations, and how you support your employees in doing so. It covers things like the working language in meetings, internal communication and client contact.<\/p>\n
\nThere is no legal obligation to draw up a language policy. However, an employer does have a duty of care, for example around safety. If instructions are not understood due to a language barrier, that can become a legal and practical problem. A clear language policy helps fulfil that duty of care.<\/p>\n
\nThat depends on your organisation and your team. Many international companies choose English as the formal working language and keep room for the local language in informal collaboration. English as the working language does not mean employees no longer need to learn the local language, because the local language stays important for integration and connection.<\/p>\n
\nStart by measuring instead of assuming. Map, per role or situation, which level is needed, and compare that with the actual level of your employees. An objective scan makes visible where the biggest gaps are.<\/p>\n
\nIdeally they carry it together. Management sets the strategic frameworks, HR and L&D translate those into concrete policy and support. Language often falls through the cracks precisely because nobody feels explicit ownership of it.<\/p>\n
\nDrawing up the policy itself mainly takes time, not a large budget. The costs sit in the support that follows, such as language training for those who need it. That investment usually outweighs the hidden costs of miscommunication, turnover and delay by a wide margin.<\/p>\n