Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
- Overview
FAQs
- Can an Australian employer ban employees from speaking another language at work?
- Is speaking another language at work discrimination?
- Can we require English for customer service roles?
- What if other employees feel excluded when co-workers speak another language?
- Should this be covered in contracts or just in a policy?
- Key Takeaways
- Official Sources to Check
A lot of business owners run into this issue when a team becomes more diverse, a customer complains they felt excluded, or a manager wants everyone to use English on the floor. The problem is that employers often get this wrong in two ways. First, they assume they can simply ban other languages at work because it feels more professional. Second, they ignore language-related conflict until it turns into a discrimination complaint, bullying allegation, or unfair policy dispute.
The short answer is that speaking another language at work is not automatically unlawful or inappropriate in Australia, and a blanket rule is often risky. What matters is why the rule exists, when it applies, whether it is genuinely needed for the job, and how it affects employees from different cultural or ethnic backgrounds. This guide explains where Australian businesses can set communication expectations, where they can get into trouble, and what a practical workplace language policy should actually say before you roll one out.
Overview
Australian businesses can usually set reasonable communication standards at work, but they should be careful about broad English-only rules. If a language requirement is not connected to safety, operational needs, customer service, or another legitimate business reason, it may create discrimination risk.
- why employees are using another language, and whether it affects safety, performance, supervision, or customers
- whether any proposed rule is genuinely necessary for the role, shift, task, or setting
- how the rule could affect staff from particular racial, ethnic, or national backgrounds
- whether managers are applying the rule consistently, not selectively or emotionally
- what your policies, contracts, and complaint processes say about respectful communication
- whether you need a more limited direction instead of a workplace-wide ban
What Is It and Appropriate to Speak Another Language at Work Means For Australian Businesses
For most employers, this issue is really about balancing lawful management directions with anti-discrimination obligations and day-to-day team culture.
Australian law does not generally prohibit employees from speaking a language other than English at work. At the same time, employers are not powerless. A business can give lawful and reasonable directions about how work is performed, including communication standards, if those directions are connected to the job and are not discriminatory in effect or application.
This is where founders often get caught. A rule can sound neutral on paper but still create legal risk if it unfairly targets workers from a particular race, nationality, or ethnic background. In Australia, race discrimination laws at both federal and state or territory level can become relevant if a workplace policy disadvantages people because of race, colour, descent, national origin, ethnic origin, or related attributes.
That does not mean every English-at-work rule is unlawful. It means the business should be able to explain, in practical terms, why the rule exists and why a narrower option would not work.
When a workplace language rule may be easier to justify
A language requirement is more likely to be defensible when it is tied to a clear business need. Common examples include:
- safety instructions in a warehouse, factory, construction setting, or other higher-risk environment
- customer-facing roles where the business requires staff to communicate with most customers in English
- team meetings where all attendees need to understand what is being discussed
- handovers, incident reporting, or compliance records that must be understood by supervisors or regulators
- training sessions where consistent language use is necessary so everyone receives the same information
Even in those situations, the safest approach is usually a limited rule. For example, requiring English during a safety briefing is very different from banning private conversations between co-workers in another language during breaks.
When a workplace language rule becomes risky
The main risk is a policy that is broader than necessary or enforced in a way that singles out particular employees.
Red flags include:
- a blanket English-only rule that applies at all times, including breaks and personal conversations
- a manager reacting to discomfort or suspicion rather than a real workplace issue
- staff being told not to speak their first language even when no customers are present and no operational issue exists
- rules applied only to some cultural groups but ignored for others
- complaints framed as “it feels rude” without any evidence of exclusion, misconduct, or disruption
There is also a practical point. A heavy-handed language ban can damage morale, retention, and trust. For many businesses, especially in software, IT, ecommerce, hospitality, logistics, and healthcare-adjacent operations, multilingual staff are an asset. A policy should not treat language skills as a problem unless there is a clear workplace reason.
Lawful and reasonable directions still matter
Employers can still direct employees to communicate in a particular way in certain contexts. The key question is whether the direction is lawful and reasonable.
In practice, that usually means asking:
- what specific problem are we trying to solve
- is the direction connected to the employee’s role and duties
- is there a less restrictive way to achieve the same outcome
- have we considered the impact on affected employees
- have we documented the reason for the rule before we enforce it
If you cannot answer those questions clearly before you update a handbook or instruct a manager, the policy probably needs more work.
When This Issue Comes Up
This issue usually surfaces in ordinary founder moments, not in a formal legal review.
A team lead may overhear staff speaking another language and assume they are gossiping. A customer may tell reception they felt uncomfortable because they could not understand what two workers were saying. A manager in a fast-growing business may want one communication rule across all teams because it feels simpler. These are common situations, but they do not all justify the same response.
Customer-facing roles
If employees regularly deal with customers, your business can usually require clear communication in English when serving customers who expect to be addressed in English. That is often a legitimate service standard.
But that does not automatically justify a wider rule for every moment of the shift. If two staff members briefly speak another language while restocking shelves or resolving a task together, you should still ask whether there is a real operational issue.
Safety and compliance settings
Safety is one of the strongest reasons for a more prescriptive communication rule. Where workers need to understand warnings, emergency procedures, equipment directions, or compliance instructions instantly, a business may require a shared working language for those tasks.
This is especially relevant if misunderstanding could lead to injury, reporting failures, or regulatory problems. The more concrete the safety or compliance reason, the easier it is to explain and defend the rule.
Remote teams and tech businesses
Software, IT and ecommerce businesses often have multilingual teams, remote contractors, offshore support functions, or mixed local and overseas staff. Here, the issue is less about overheard conversations and more about documentation, meetings, support logs, and team inclusion.
A sensible policy may require project records, customer communications, or internal tickets to be in English so everyone can collaborate. That is very different from telling bilingual employees they cannot chat to each other in another language on a call before a meeting starts.
For startups, this is also where contracts and policies need to line up. If employment contracts, contractor agreements, onboarding documents, and internal policies all say different things about communication standards, managers tend to improvise. Improvisation is where inconsistent treatment starts.
Complaints about exclusion or bullying
Sometimes a complaint is not really about language at all. It is about a worker feeling isolated, left out, or worried they are being discussed in front of them. Those concerns should not be dismissed, but the answer is not always a language ban.
You may need to address:
- team conduct and respectful behaviour
- bullying or gossip if there is actual evidence of it
- meeting practices that exclude some participants
- manager capability and conflict resolution
Focusing on the behaviour often works better than policing language itself.
Recruitment and job requirements
This issue can arise before you hire someone. If a role really needs fluent written or spoken English, state that carefully and only where it is genuinely inherent to the position. For example, a role handling Australian customer complaints, safety documentation, or regulated records may need a higher level of English than a back-end technical role with limited local interaction.
Overstating language requirements in job ads can create discrimination concerns and may also shrink your talent pool unnecessarily.
Practical Steps And Common Mistakes
The safest approach is to create a targeted communication policy, not a broad cultural rule.
Step 1: Identify the real business reason
Before you spend money on setup, policy updates, or manager training, define the problem in plain English. Is it customer service consistency, safety, team inclusion, documentation quality, or something else?
If the reason is vague, such as “it looks unprofessional” or “people might be offended”, stop there and test whether there is actual evidence of harm.
Step 2: Limit the rule to the situations that need it
A narrow rule is usually easier to justify and easier for staff to follow. For example, you might require English in:
- customer interactions where the customer does not share another language
- formal team meetings attended by staff who need a common language
- written internal records, support tickets, or incident logs
- safety briefings, emergency procedures, and regulated communications
You might avoid regulating:
- private conversations during breaks
- casual discussions between bilingual co-workers when no operational issue exists
- social team chat that does not affect service, safety, or inclusion
Step 3: Put the expectation in writing
If a communication standard matters, write it down. A workplace policy should explain what is expected, when the rule applies, why it exists, and how concerns can be raised.
A useful policy often includes:
- the business reason for any language requirement
- examples of situations where English is required
- confirmation that the business respects cultural diversity and multilingual staff
- a statement that private conversations and breaks are treated differently unless there is a specific reason
- how managers should handle concerns or complaints
- how the policy interacts with anti-discrimination, bullying, and code of conduct policies
For many SMEs, this policy should sit alongside employment contracts, contractor terms where relevant, handbooks, and complaint procedures.
Step 4: Train managers before enforcement starts
A legally sensible policy can still cause problems if managers enforce it badly. This happens when a supervisor tells one group to “speak English” on the spot, but ignores the same conduct from someone else, or uses the rule to control workplace relationships rather than performance.
Managers should know:
- the specific reasons behind the policy
- when they can give a direction and when they should escalate
- how to separate language issues from misconduct or bullying concerns
- how to avoid comments that sound targeted at race or national origin
- how to document incidents factually
Step 5: Deal with complaints case by case
One of the biggest mistakes is reaching for a business-wide rule because of a single complaint. Investigate what actually happened.
Ask practical questions such as:
- was a customer unable to receive service
- did staff miss a safety direction
- was someone being mocked, isolated, or bullied
- did a meeting exclude participants who needed to understand it
- is this a one-off issue or a repeated pattern
The answer may be coaching, a meeting protocol, or a conduct warning rather than an all-staff language policy.
Common mistakes businesses make
Most legal risk comes from overreach, inconsistency, or poor drafting.
- using a blanket English-only rule without a task-specific reason
- relying on customer preference alone when there is no real business need
- confusing discomfort with misconduct
- failing to consider discrimination risk before introducing the rule
- applying stricter standards to some employees than others
- writing a policy but not updating contracts, onboarding materials, or manager guidance
- disciplining an employee too quickly before the facts are clear
What to review before you sign off on a policy
Before you sign a contract, issue a handbook update, or start disciplinary action, review the documents and processes around the issue. Depending on your business, that may include:
- employment agreements and contractor agreements
- workplace policies and staff handbooks
- anti-discrimination, equal opportunity, and bullying policies
- performance management and disciplinary procedures
- customer service scripts or operational manuals
- health and safety procedures
If your business uses online collaboration systems, ticketing tools, or ecommerce support platforms, make sure your documented expectations reflect how the team actually communicates day to day.
FAQs
Can an Australian employer ban employees from speaking another language at work?
Not as a general rule just because the employer prefers it. A business may be able to require English in specific situations where there is a genuine operational, safety, service, or compliance reason, but a blanket ban is much riskier.
Is speaking another language at work discrimination?
No, not by itself. The discrimination risk usually arises when an employer restricts language use in a way that unfairly disadvantages workers from certain racial, ethnic, or national backgrounds, or applies the rule selectively.
Can we require English for customer service roles?
Often yes, if the role genuinely requires staff to communicate effectively with customers in English. The requirement should be connected to the role and should not automatically extend to every private or non-customer-facing conversation.
What if other employees feel excluded when co-workers speak another language?
You should look at the actual behaviour and context. If the problem is exclusion from meetings, rude conduct, or bullying, address that directly. Do not assume language itself is the misconduct.
Should this be covered in contracts or just in a policy?
Usually both, depending on the business. Core obligations may sit in employment contracts, while the practical detail belongs in workplace policies and manager guidance so expectations can be applied consistently.
Key Takeaways
- Speaking another language at work is not automatically unlawful or inappropriate in Australia.
- Employers can set communication standards, but the direction should be lawful, reasonable, and connected to a real business need.
- Blanket English-only rules are more likely to create discrimination risk than narrow, task-based requirements.
- Safety, customer service, team-wide meetings, and formal records are common situations where a shared working language may be justified.
- Private conversations, break times, and casual exchanges usually need a more cautious approach.
- The best protection is a clear written workplace policy, aligned employment contracts, trained managers, and case-by-case handling of complaints.
If your business is dealing with is it and appropriate to speak another language at work and wants help with workplace policies, employment contracts, discrimination risk, or staff complaint processes, you can reach us on 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.
Official Sources to Check
Rules and regulator guidance can change. Check the current official material most relevant to this issue before relying on the article:







