Skip to content

Guide

Casual vs formal English at work: how to pick the tone

Most work writing sits somewhere between the two. Here’s how to match the tone to the person and the channel, with the same message written both ways.

Updated October 24, 2026

Native speakers switch tone without thinking: a two-word Slack reply to a teammate, a careful email to a new client. If English isn’t your first language, the switch takes more effort, and the usual result is writing that’s more formal than it needs to be. It isn’t wrong, but it can sound distant, or like a template.

Here’s how to decide, what actually changes between the two, and what “too formal” looks like.

How to choose

  • Casual: teammates, people you talk to every day, Slack, quick replies in a thread you’re already part of.
  • Formal: first contact, clients and partners you don’t know yet, senior people outside your team, anything about money, contracts or complaints, job applications.
  • Mirror the other person. If a client signs off with “Thanks, Sam”, you can drop the “Dear Mr. Smith”.
  • When unsure, aim for the middle: full sentences, contractions, no slang, no emoji. That works almost everywhere.

Formal in modern workplace English doesn’t mean old-fashioned. It means complete, precise and polite. Casual doesn’t mean sloppy. It means short and direct.

The same message, two ways

Six situations that come up every week, each written for a teammate and for a client or a senior stakeholder.

Asking for something

Casual

Could you take a look at the deck when you get a chance?

Formal

Would you be able to review the deck by Thursday? I’d especially appreciate your thoughts on the pricing section.

Formal requests use Would you be able to or Could you please and give a specific date. Casual ones can leave the timing open.

Reporting a delay

Casual

Heads-up: the report’s going to be a day late. You’ll have it Friday morning.

Formal

I wanted to let you know that the report will be delayed by one day. I will send it to you on Friday morning.

Both give the new time. The formal one just spells everything out, without contractions.

Saying no

Casual

Sorry, I can’t take this on this week. Could it wait till Monday?

Formal

Unfortunately, I won’t be able to take this on this week. I could start on Monday, if that works for you.

In either tone, a no lands better with an alternative attached. Unfortunately does a lot of the softening in formal English.

Following up

Casual

Just bumping this. Any thoughts on the draft?

Formal

I’m following up on my email from last Tuesday. Have you had a chance to review the draft?

Avoid “As per my last email” in both. Native readers hear it as irritation.

Apologizing

Casual

Sorry, my bad! I sent the old version. Here’s the right one.

Formal

Apologies for the confusion. I sent an earlier version by mistake, and the correct file is attached.

Keep apologies short. One clear sentence and the fix reads as more professional than a paragraph of regret.

Giving feedback

Casual

Looks great! One thing: could we cut the intro a bit?

Formal

This is a strong draft. My main suggestion is to shorten the introduction so the key results come first.

Formal feedback gives the reason for the change. Casual feedback can just ask for it.

What actually changes

Contractions

Casual English uses them everywhere: I’m, we’ll, it’s, don’t. They’re also normal in most work email, including email to clients. “I do not have the file” in Slack reads as stiff, or even annoyed. Leave contractions out in legal text, formal letters and documents meant to sound official.

Phrasal verbs vs single verbs

Casual English prefers phrasal verbs: a short verb plus a small word like up, off or out. Formal English often uses a single verb from Latin instead. Both are correct. They just set a different tone.

CasualFormal
put off, push backpostpone
set uparrange
find outdetermine
look intoinvestigate
go overreview
sort outresolve
get back torespond to

If your first language is Spanish, Russian or German, the Latin-based verb often feels more natural, because it looks like a word you already know: posponer, проинформировать, informieren. That’s a big reason non-native email sounds formal even when it’s meant to be friendly.

Sentence shape

Formal English wraps a request in a few extra words: Would you be able to, I was wondering if, Could you please. Casual English gets to the point: Can you. Exclamation marks, emoji and a quick “thanks!” belong to casual writing. In a formal email, one exclamation mark is plenty.

What “too formal” looks like

Some phrases show up in non-native work email far more than in native writing. They come from textbook business English, or from translating formal phrases in other languages word for word. Most can simply be deleted.

deleted: I would like to inform you thatinserted: Just a heads-up: the server will be down tonight.

Start with the news. “Heads-up” is casual; in a formal email, just state it.

deleted: Please be informed that theinserted: The office is closed on Monday.

Delete the announcement and say the thing.

deleted: Kindly revertinserted: Please reply with your comments.

“Revert” meaning reply is common in Indian English, but elsewhere it means to go back to an earlier state. “Kindly” sounds dated in US and UK email.

deleted: Please findinserted: I’ve attached the report.

Still common in formal email, but stiff between teammates.

deleted: Dear colleaguesinserted: Hi all, the meeting deleted: isinserted: has moved to 3 pm.

“Dear colleagues” sounds like a company-wide announcement. “Hi all” or “Hi team” works for internal email.

Slack vs email

Slack

  • Short messages, contractions, no “Dear” and no sign-off.
  • Don’t send “Hi” on its own and wait for a reply. Put the question in the same message: “Hi Sam, do you know who owns the billing service?”
  • An emoji reaction is a fine way to say “seen” or “done”.
  • Formal messages are fine for announcements in big channels. Elsewhere they read as cold.

Email

  • A greeting and a sign-off, even in a quick reply to a teammate: “Hi Sam,” and “Thanks,”.
  • A subject line that says what you need: “Review needed: Q3 pricing deck by Thursday”.
  • One clear ask per email, near the top.
  • Start formal with someone new, then match their tone once they reply.

More on both: writing clear, polite email and fixing Slack messages before you send them.

US vs UK notes

  • Directness. American work English is usually more direct and more upbeat (“Love this!”, “Awesome, thanks!”). British English hedges more (“I was wondering if you might be able to…”), and understatement is common: “not bad” can be real praise.
  • Quite. In the US, “quite good” means very good. In the UK it often means fairly good.
  • Sign-offs. “Best” and “Thanks” are the safe US choices. “Kind regards” is more British but fine anywhere. “Cheers” is casual, and to American readers it sounds British or Australian.
  • Titles. American English writes “Mr.” and “Dr.” with a period. British English usually leaves it out: “Mr Smith”.

Switching tone with one shortcut

AI Grammatic, a Mac menu bar app, gives every language two versions of its shortcut. Select your text in any app and press ⌘⌥E for a natural, casual rewrite, or add ⇧ for a formal one. Either way it fixes grammar and phrasing, keeps your meaning, names and links, and replaces the text in place in about a second. ⌘Z brings back what you wrote.

sorry, report will be late, i send it tomorrow morning

Casual ⌘⌥E

Sorry, the report’s running late. I’ll send it tomorrow morning.

Formal ⇧⌘⌥E

Apologies, the report is running a little late. I will send it to you tomorrow morning.

Try both on one of your own sentences in the live demo. If English isn’t your first language, the guides to mistakes Russian, Spanish and German speakers make are a good next read.

Try it in your next message

Free for 10 rewrites a day. No account, no card.

Download for Mac