NotchTutor Blog
Formal vs Informal English at Work: When to Use Which
July 1, 2026
One of the most common — and least discussed — communication challenges in English workplaces is register: the level of formality in your writing. Use formal English when informal would feel natural, and you come across as stiff or distant. Use informal English when formal is expected, and you risk seeming careless or disrespectful.
For non-native English speakers, this challenge is doubled. You may have learned formal business English in school, which means informal professional English — the kind used in most modern offices — feels uncertain territory. At the same time, you may not have learned the social signals that tell a native speaker when to shift registers.
This guide gives you a concrete framework, a comparison table, and real examples to make the decision automatic.
For a broader foundation in professional writing, see our business English writing guide.
What Is “Register” in English?
Register is the style of language you choose based on context — who you’re talking to, what the situation requires, and what the relationship allows. It’s not about correct versus incorrect; it’s about appropriate versus inappropriate.
English has a wide range, from highly formal (“I would be grateful if you could consider the attached proposal at your earliest convenience”) to very informal (“Hey, take a look when you get a sec?”). In a workplace context, you’ll mostly operate somewhere in the middle — professional but not stiff.
The three registers you need in most business contexts:
- Formal — for external communications with senior contacts, legal and regulatory documents, official announcements, and written materials with a long shelf life
- Professional/neutral — for most day-to-day business communication: emails to colleagues, meeting notes, reports, project updates
- Informal — for internal chat, casual team conversations, messages to colleagues you know well
Most people overuse formal English in contexts that call for neutral, and underuse it in contexts that call for formal. The mismatch creates friction.
Formal vs Informal English: The Comparison Table
| Situation | Formal | Neutral/Professional | Informal |
|---|---|---|---|
| Email to new external contact | ✓ | ||
| Email to regular client | ✓ | ||
| Email to close colleague | ✓ or ✗ | ✓ | |
| Slack/team chat | Possible | ✓ | |
| Job application cover letter | ✓ | ||
| LinkedIn post | ✓ | Avoid | |
| Business report | ✓ | ||
| Meeting notes | ✓ | ||
| Company-wide announcement | ✓ | ||
| Quick internal update | ✓ | ✓ | |
| Legal or contract document | ✓ | ||
| Performance review | ✓ |
Side-by-Side Language Examples
The same message can be expressed across the full range. Here’s the same request in three registers:
Formal:
“I am writing to respectfully request your consideration of the revised proposal attached hereto. Should you require any clarification or wish to discuss any aspect in detail, please do not hesitate to contact me at your convenience.”
Professional/neutral:
“Please take a look at the revised proposal attached. Happy to answer any questions or set up a call if that would be helpful.”
Informal:
“Hey — attached is the updated proposal. Let me know if anything looks off or if you want to chat through it.”
All three are correct English. None is inherently better. The professional version works in 80% of business situations. The formal version is right when writing to a senior external contact you’ve never met. The informal version is right when messaging a colleague you talk to every day.
How Do You Know Which Register to Use?
Four factors determine the right register:
1. Your relationship with the reader How well do you know this person? Have you met them? Do you interact daily, occasionally, or never? The stronger the existing relationship, the lower the register can go.
2. Their seniority and role Writing to your CEO, a board member, a client’s legal team, or a government official? Default to formal until they signal otherwise. Writing to a peer or direct report? Professional neutral is almost always appropriate.
3. The document’s purpose and shelf life A message that will be read once and archived? Neutral is fine. A document that will be shared widely, kept as a record, or read by multiple stakeholders over time? Lean formal.
4. The culture of your organization Some companies are formal; others are relentlessly casual. Pay attention to how senior people write internally. That’s the baseline your organization actually uses, regardless of what the style guide says.
Register Mistakes That Are Easy to Fix
Too formal in internal communication
Before:
“Dear James, I hope this communication finds you in good health. I am writing to inquire whether the weekly status report for the Henderson project has been completed. Please advise at your earliest convenience.”
After:
“Hi James — has the Henderson project status report been finished? I need to include it in this week’s summary.”
The first version is not wrong, but it wastes James’s time and creates distance where none is needed.
Too informal in formal contexts
Before:
“Hey Sarah — just wanted to follow up on the contract. Any update? We’re kind of waiting on this lol.”
After:
“Hi Sarah, I’m following up on the contract from March 15. Could you let me know where things stand? We’re ready to proceed on our end.”
The informal version is fine for a colleague; it’s damaging to the business relationship when sent to an external contact.
Mixing registers inconsistently
A single document that swings between “It is hereby noted that…” and “Basically, what we’re saying is…” undermines both authority and readability. Pick a register and maintain it throughout.
How Non-Native Speakers Can Build Register Awareness
Native speakers acquire register intuitively through years of exposure. Non-native speakers have to build it more consciously, which is entirely possible — but takes deliberate attention.
Read native-speaker examples in the same context. Before writing a formal letter you’ve never written before, find a model. Before writing a casual Slack message in an unfamiliar culture, notice how your colleagues write.
Notice what you receive. How does your manager write to you? How does your manager write to their manager? What differences do you observe?
When in doubt, go one level more formal than you think. It’s easier to relax a relationship that started with formality than to recover from appearing careless. Formal signals care; informal signals assumption.
Edit specifically for register. After drafting, ask: which sentences are too formal or too casual for this audience and purpose? Make a pass just for that.
This is exactly the kind of pattern-level feedback that NotchTutor’s English writing assistant is designed to provide. Most grammar tools flag errors; NotchTutor identifies register mismatches — when formal language appears in informal contexts or vice versa — and explains why the mismatch creates friction. Non-native writers who use it regularly start to internalize the signals that govern register choices, building that awareness faster than passive exposure alone.
Special Cases: When the Rules Bend
Writing to someone who writes informally to you If your senior contact consistently writes to you in casual, friendly English, matching their register shows attentiveness and social intelligence. Responding formally to an informal message can feel stiff or even passive-aggressive.
Emotionally sensitive situations When delivering difficult news, feedback, or criticism, a slightly warmer and more formal register can reduce the sting. “I need to let you know that your performance on this project did not meet expectations” lands differently than “Your work on this wasn’t what we needed.”
Cross-cultural situations Some business cultures (Germany, Japan, many parts of the Middle East) use significantly more formal language in professional contexts than a typical American or British tech company. When writing across cultures, mirror the formality level of the messages you receive rather than assuming your own default is universal.
Quick Reference Guide
Use formal English when:
- Writing to someone you’ve never communicated with before
- The reader is significantly more senior than you and the relationship is new
- The document is official, legal, or will be widely distributed
- The stakes are high (a complaint, an official request, a legal notice)
Use professional/neutral English when:
- Writing to colleagues, regular clients, or known contacts
- Sending project updates, meeting notes, status reports
- In doubt about the right level
Use informal English when:
- Messaging colleagues you work with daily
- Using internal chat tools (Slack, Teams)
- The relationship is established and casual communication has been normalized
Putting It Together
Register is one of the subtler skills in professional English, but it’s also one of the most rewarding to develop. When your tone matches the situation consistently, readers stop noticing your language and focus on your content — which is exactly where you want their attention.
For more on the specific formats where these decisions play out, see how to write professional emails and professional Slack messages. The underlying principle — match your language to your audience and context — is the same in every channel.