Why Industry-Specific Business English Works Better

Two colleagues take the same placement test and both come out at B2. One runs client calls comfortably; the other goes quiet whenever the discussion leaves the prepared agenda. The difference is not the level. It is that one of them has rehearsed the conversations their job actually produces, which is the case for industry-specific business English in a single sentence.

Why does the same CEFR level produce different results at work?

Because a CEFR level measures general proficiency, while workplace performance depends on scenario familiarity. Two B2 speakers can perform very differently if one has rehearsed their role's recurring conversations and the other has only ever studied English as a general subject in general contexts.

This is not a criticism of the framework. The Common European Framework describes what a learner can do across broad language functions, and it does that job well enough to have become the international standard. But it deliberately abstracts away from context, and context is precisely what determines whether you can handle a supplier dispute or a patient handover under time pressure.

The practical consequence is that "improve my English" is the wrong goal statement for a working professional. It has no finish line, no feedback and no obvious first action. "Be able to run the Monday client call without losing the thread" is a goal you can practise against, and it is reached in weeks rather than the months a level change requires.

There is a second reason the same level diverges in practice. Familiar content carries a conversation a long way. When you know the subject matter deeply, you can predict what is coming, infer what you missed, and reach for a phrase you have used a hundred times. Take the same speaker into an unfamiliar domain and the apparent level drops immediately, because none of those supports are available.

That is why professionals often describe their English as inconsistent. It is not inconsistent. It is contextual, and the contexts you have rehearsed are the ones where you sound like yourself.

What does general business English cover, and where does it stop?

General business English gives you the shared register: meeting phrases, email structure, polite disagreement, presentation transitions. It stops at the point where your specific role begins, which is unfortunately where most of the difficult and high-stakes conversations are located.

The shared layer is real and worth learning first. Turn-taking signals, softeners for requests, and closing language work identically in a hospital and a shipping company, and they solve a large share of everyday difficulty. Our complete guide to business English for meetings covers that common ground in detail.

But look at what the shared layer does not include:

Profession	Weekly language a general course will not teach
Software engineer	Blocker reporting, pull request comments, incident and postmortem updates
Nurse	Structured handover, symptom questioning, discharge instructions
Cabin crew	Standard announcements, special assistance requests, disruption handling
Logistics manager	Delay notification, customs correspondence, damage claims
Consultant	Scope negotiation, findings presentation, stakeholder pushback
Lawyer	Contract drafting precision, cross-border terms, dispute correspondence
Banker	Client onboarding and compliance questioning, product explanation

Each of these is a recurring, high-consequence conversation for the person in that role. None of them appears in a general syllabus, and in several cases — logistics, freight, export documentation — there is almost no language-learning material of any kind, only sector glossaries and process guides written for people who already speak English fluently.

How much vocabulary does a profession actually need?

Less than most professionals fear. A focused core of a few hundred role-specific terms and set phrases covers the large majority of what someone says and writes in a normal working week, because job language is repetitive by nature and clusters tightly around a small number of recurring situations.

This is the good news buried inside the bad news. Learning "business English" as an open-ended field is demoralising because it has no boundary and therefore no possible completion. Learning the language of one role has a visible boundary, and you can see the end of it from the beginning.

The Worklish curriculum is structured to make that boundary explicit: eleven industries, each with ten workplace topics, each topic with ten specific subtopics. A tourism professional works through guest check-in, complaints and service recovery, food and beverage, and tours and activities. A finance professional works through client onboarding and compliance, financial products, and investment communication. You can see the full topic map for your own industry.

Two things make that core efficient to build. First, the terms repeat: a logistics manager writes about delays weekly, so twenty phrases about delay get retrieved constantly rather than decaying. Second, the terms come with context attached, and context is what makes vocabulary retrievable — you are not learning a word, you are learning what to say when a shipment is stuck at customs.

Building that core is the Word Bank step in the Worklish method: a personal, role-specific store of phrases assembled from your own work rather than copied from a generic list.

Does this matter more for some professions than others?

It matters most where the stakes of a misunderstanding are highest and the vocabulary is most specialised. Healthcare, aviation, maritime and legal work all combine technical precision with real consequences, which is exactly why each of those fields has developed its own formal communication protocols.

Some of those protocols are highly standardised. Aviation uses ICAO standard phraseology for radio communication; nursing handovers commonly follow the ISBAR sequence; maritime operations use standardised marine communication phrases. Learning the protocol is necessary and it is nowhere near sufficient, because the protocol covers the emergency and the exception.

The rest of the working day is not covered at all. A pilot's week includes crew coordination, delay explanations to passengers, and correspondence with the airline. A nurse's week includes conversations with anxious families, shift negotiation and supplier calls. A ship's officer deals with agents, port authorities and customs. None of that is scripted, all of it is consequential, and it is the gap between the standard phraseology and the actual working day where most industry-specific practice is needed.

The pattern holds in less regulated fields too, just with lower stakes and less obvious structure. A designer defending a creative decision, a consultant reframing a client's scope request, a marketer explaining why a campaign underperformed — each is a recurring conversation with its own conventions that nobody has ever written down for them.

What does industry-specific business English look like in practice?

In practice it means replacing the topic with the scenario. Instead of a lesson on "telephoning", a logistics manager rehearses telling a customer that a container is held at customs, in the words that situation actually requires, with the objections that customer will actually raise.

The difference shows up in three places. The vocabulary is narrower and deeper: twenty phrases about delay, used until they are automatic, rather than two hundred general business terms used once each. The structure is borrowed from the job rather than from grammar: a handover follows the handover sequence, not a tense sequence. And the success test is behavioural: you either handled the call or you did not.

Consider two versions of the same practice session for a nurse at B2. The general version asks her to describe a daily routine using the present simple. The industry version asks her to hand over four patients in three minutes, using the structure her hospital expects, while a colleague interrupts twice with questions. Both take twenty minutes. Only one of them will be recognisable on Monday morning.

There is a further benefit that is easy to miss. Practising your own scenarios surfaces gaps you did not know you had. Most professionals discover that the vocabulary is fine and the sequencing is not — they know every word in a handover and have never had to produce them in order, under time pressure, without notes.

The same principle governs written practice. A consultant does not need "formal writing" in the abstract; she needs a scope-change email that declines an extra request without souring the account, and that is a specific document with specific conventions.

Does the profession matter more than the level?

They interact, and the practical answer is to hold both at once. The right unit of practice is a specific scenario at a specific level: a patient handover at B1 is a materially different exercise from the same handover at C1, and practising the wrong one wastes the session entirely.

This is why every Worklish scenario exists at five levels — Trainee (A1–A2), Associate (B1), Professional (B2), Senior (C1) and Expert (C2). The B1 version of a client complaint gives you a structured, predictable exchange where the customer states the problem clearly and accepts the first solution. The C1 version gives you an escalating customer who changes the subject, disputes the facts and threatens to leave.

Getting the level right also matters for motivation, which is the resource that actually runs out. Practising above your level produces failure without learning, because you cannot extract the pattern from something you did not follow. Practising below it produces confidence without change, which feels good for a fortnight and then stops working.

Our guide to CEFR levels for working professionals describes what each level looks like in observable workplace behaviour, which is the fastest way to place yourself honestly rather than optimistically.

The interaction also changes what counts as a hard scenario. A patient handover is linguistically simple and cognitively demanding, so it stays difficult at C1 for reasons that have nothing to do with vocabulary. A client dinner is linguistically demanding and cognitively simple, and it becomes easy the moment small talk stops feeling risky. Knowing which of the two you are facing tells you whether to drill phrases or to drill composure.

One practical note on sequencing: start one level below where you think you are. The first session should feel slightly easy. That gives you a clean baseline and it removes the discouragement that ends most self-directed practice in the first two weeks.

Why is speaking the skill that industry practice fixes?

Because speaking is the weakest skill for most learners, and it is the one that only improves through production in realistic conditions. Reading and listening improve passively at work; speaking does not, because most professionals gradually arrange their week to avoid the moments that demand it.

EF's English Proficiency Index 2025, which assessed speaking and writing for the first time across 123 countries and 2.2 million test takers, found speaking to be the weakest area for most learners. Meanwhile Microsoft's 2025 Work Trend Index, surveying 31,000 knowledge workers across 31 markets, found that 57% of working time goes to communication and that employees are interrupted roughly every two minutes. The skill under the most pressure is the one that gets the least practice.

There is a further reason industry practice is the right vehicle for fixing this. Speaking practice on an unfamiliar topic loads you twice — once with the language and once with the content — so you fail for reasons that have nothing to do with English. Practising a conversation you already understand professionally removes the content load entirely, leaving only the language, which is the thing you are trying to train.

Ethnologue's 2025 rankings put worldwide English speakers at around 1.53 billion, with roughly 390 million first-language speakers, so most of the people you will speak to are also working in a second language. The target is not native fluency. It is being clear and confident in the twenty conversations that make up your working year.

Start with one scenario rather than a plan. Pick the conversation you handled worst in the last month, write out how it should have gone, and say it aloud three times before the next occurrence. That single exercise teaches you more about your real gap than any assessment will, and it produces a result you can feel within a fortnight rather than a level you might reach within a year.

For how to structure that practice around a full-time job, see how to learn business English as a working professional.