This article is part of our Business English Hub — explore workplace vocabulary, email writing, presentations, and more.
- Video call phrases like “You’re on mute” and “Can everyone see my screen?” are essential survival vocabulary for remote workers.
- Asynchronous communication requires clearer, more structured language than face-to-face conversation because there is no immediate feedback loop.
- Choosing the right register—email for formal records, Slack/chat for quick updates—prevents miscommunication and maintains professional relationships.
- Time zone awareness is a professional skill: always specify the time zone when scheduling and show consideration for colleagues in different regions.
Ready to practise? Start Flash Cards →
Remote work has transformed the English needed in professional settings. Whether you join a distributed team for the first time or you are an experienced remote worker looking to polish your communication, the vocabulary and phrases in this guide will help you sound confident, clear, and professional in every channel—from Zoom calls and Slack threads to project update emails and cross-time-zone scheduling.
This guide covers the full spectrum of remote work English for B1–C1 learners: the phrases that keep video calls running smoothly, the vocabulary of asynchronous communication, how to write clear project updates, when to use email versus chat, and how to handle time zones without causing friction. A vocabulary table covers ten essential terms with meanings and example sentences, and a full FAQ section addresses the questions remote workers most commonly ask about professional English.
1. Why Remote Work English Is Different
In an office, much communication happens informally—a quick question at someone’s desk, a glance across the room to check understanding, body language that signals confusion or agreement. Remote work strips away those informal cues and forces everything through written text or video. The result is that language must work harder: messages need to be more explicit, updates more structured, and tone more carefully managed. A message that would be perfectly clear in person can cause confusion or even offence when read on a screen without context. This is why remote work has developed its own vocabulary and conventions—and why learning that vocabulary gives you a significant professional advantage.
2. Video Call Etiquette and Key Phrases
Video calls are the closest thing to face-to-face communication in a remote team. Knowing the standard phrases makes you sound confident and helps meetings run efficiently.
- “You’re on mute.” — The most common phrase in remote work. Said when someone is speaking but their microphone is off.
- “Can everyone see my screen?” — Used when sharing your screen during a presentation or demo.
- “Let’s wait a moment for everyone to join.” — A polite way to delay starting until latecomers arrive.
- “Sorry, I had some connection issues.” — A neutral, professional way to explain technical problems without over-apologising.
- “Sorry to jump in, but…” — A polite way to interrupt without seeming rude.
- “Could you repeat that? You broke up for a moment.” — Asking someone to repeat themselves when the audio was unclear.
- “Let’s take this offline.” — Suggesting that a topic is too detailed for the current meeting and should be discussed separately.
- “I’ll drop the link in the chat.” — Sharing a URL or resource in the meeting chat window.
- “Can we get a quick round of updates?” — Asking each person to give a brief status report.
3. Asynchronous Communication Vocabulary
Async (asynchronous) communication is any message that does not require an immediate response—email, Slack, project management comments, recorded video updates. Knowing the vocabulary helps you describe and navigate this style of working.
- async — Short for asynchronous. “We work async across three time zones.”
- thread — A chain of related messages. “I’ll reply in the thread so everyone can see the update.”
- loop in — To add someone to a conversation. “Loop in Maria—she’s handling the design side.”
- ping — To send a quick message. “Ping me when it’s ready and I’ll review it.”
- EOD / EOP — End of day / end of play. “I need this by EOD Friday.”
- TL;DR — Too long; didn’t read. A short summary placed at the top of a long message. “TL;DR: the launch is delayed by one week.”
- action item — A specific task assigned to a person. “The action item for you is to update the brief by Thursday.”
- deliverable — A finished piece of work that can be submitted or handed over. “The deliverable for this sprint is the MVP prototype.”
In async communication, assume your reader may not have the same context as you. Start messages with the key point (TL;DR style), give enough background for someone reading it twelve hours later, and be explicit about deadlines and ownership.
4. Project Update Language
A well-structured project update uses a consistent template so readers can scan it quickly. The most common structure is Status / Progress / Next Steps:
- Status: “On track / At risk / Blocked.”
- Progress: “This week we completed the user testing phase and identified three key issues.”
- Next Steps: “Next steps: fix the login bug (owner: Dev team, due: Wed), share revised mockups (owner: Design, due: Fri).”
Use passive voice for completed actions (“the report has been sent”) and active voice for next steps (“Ana will review the copy by Tuesday”). This makes it immediately clear what is done and who owns what is coming next.
5. Email vs Chat: Choosing the Right Register
- Email — Use for: formal requests, legal or contractual matters, communicating with external clients or partners, messages that need a permanent record. Tone: structured, professional, full sentences.
- Chat (Slack, Teams, etc.) — Use for: quick questions, informal team updates, sharing links, real-time coordination. Tone: brief, conversational, contractions are fine.
- Project management comments (Jira, Asana, Notion) — Use for: status updates, task-specific discussion, attaching files. Tone: factual, concise, action-focused.
6. Time Zone and Scheduling Expressions
- “Let’s schedule this for 10:00 GMT / 11:00 CET — does that work for you?”
- “I’ll be offline during those hours as it’s outside my working day.”
- “I’ll send this async so you can review it in your morning.”
- “Could we find a time that works across both time zones?”
- “I’m in BST (UTC+1) — happy to take the early slot so the team in APAC can join at a reasonable hour.”
- “There’s a Calendly link in my email signature — feel free to book a slot that suits you.”
7. 10 Essential Remote Work Vocabulary Terms
| Term | Meaning | Example |
|---|---|---|
| stand-up meeting | A short daily team meeting (typically 15 minutes) where each person shares progress and blockers | “Our stand-up is at 9 am every day — keep it to 15 minutes.” |
| async | Communication that does not require an immediate response | “We work async, so replies within 24 hours are fine.” |
| bandwidth | Available capacity or time; being ‘low on bandwidth’ means being too busy | “I don’t have the bandwidth to take on another project this week.” |
| loop in | To add someone to a conversation or email thread | “Let me loop in the project manager — she’ll know the answer.” |
| take this offline | To move a detailed discussion out of the current meeting | “This is getting complex — let’s take it offline after the call.” |
| EOD / EOP | End of day / end of play — the deadline is before close of business | “I need the draft by EOD Wednesday at the latest.” |
| ping | To send a quick message to someone via chat | “Ping me when you’ve pushed the update and I’ll test it.” |
| follow up | To send a message checking on progress after an initial contact | “I’ll follow up with the client if we haven’t heard back by Friday.” |
| circling back | Returning to a topic that was postponed or left unresolved | “Just circling back on the proposal — have you had a chance to review it?” |
| deliverable | A finished piece of work that must be completed and submitted | “The key deliverable this sprint is the onboarding flow prototype.” |
8. Practical Tips
- Over-communicate context. In async work, assume the reader does not have the background you have. One extra sentence of context saves hours of back-and-forth.
- Use TL;DR summaries. For messages longer than a paragraph, put the key point at the top. “TL;DR: we need to push the deadline to 28 June.”
- Be explicit about ownership and deadlines. “Can someone look at this?” is weak. “Tom, could you review the brief by Thursday EOD?” is clear and actionable.
- Mirror the register of your team. If your team uses informal language in Slack, match that. If email threads are formal, maintain that standard.
- Test your tech before a call. Join five minutes early, check your audio and camera, and have a backup (phone number, chat message) ready if your internet fails.
When writing async messages to a global team, put a TL;DR at the top of anything longer than three sentences. It respects your reader’s time and ensures the key information lands even if they skim. Example: “TL;DR: launch moved to 28 June — details below.”
Practise Business English Vocabulary
Drill remote work vocabulary with free Flash Cards — no account needed, start immediately.
Start Flash Cards →9. Frequently Asked Questions
What English phrases are most useful for video calls?
The nine phrases that cover the vast majority of video call situations are: “You’re on mute,” “Can everyone see my screen?,” “Let’s wait a moment for everyone to join,” “Sorry, I had some connection issues,” “Sorry to jump in, but…,” “Could you repeat that? You broke up for a moment,” “Let’s take this offline,” “I’ll drop the link in the chat,” and “Can we get a quick round of updates?” Practise these until they feel automatic.
How formal should business English emails be?
It depends on the context. In a startup with a flat hierarchy, “Hi James, quick question…” is perfectly professional. In a traditional corporate or legal context, “Dear Mr Harrison, I am writing to…” is more appropriate. The safest strategy when you are new is to mirror the register of the emails you receive: if your contact writes informally, you can match that; if they write formally, maintain that standard until the relationship becomes more established.
How do I handle time zones professionally?
Always specify the time zone when scheduling: “10:00 GMT / 11:00 CET” removes any ambiguity. Show consideration for colleagues in distant regions by offering early-morning or late-evening slots rather than always defaulting to your own convenience. Tools like Calendly or World Time Buddy let others book slots in their own time zone automatically. In signatures and messages, consider adding “(London, GMT)” so people know your base without having to ask.
What does “circling back” mean?
“Circling back” means returning to a topic that was postponed, left unresolved, or where you are following up after not receiving a response. It is extremely common in remote work emails and chat: “Just circling back on the proposal I sent last week — have you had a chance to review it?” It is a polite, non-pushy way to re-open a conversation. In email subject lines, you often see: “Re: Proposal [circling back].”
How do I write a professional project update?
The most effective structure is Status / Progress / Next Steps. Start with a one-word or one-phrase status: “On track,” “At risk,” or “Blocked.” Follow with a brief summary of what was completed this period. Then list the next steps with a clear owner and deadline for each item. Use passive voice for completed work (“the draft has been sent to the client”) and active voice for upcoming actions (“Ana will review copy by Tuesday”). Keep the update scannable rather than written as flowing paragraphs.
What is the difference between async and sync?
Synchronous (sync) communication requires both parties to be present at the same time — video calls, phone calls, and live chat are all sync. Asynchronous (async) communication does not require simultaneous presence — email, Slack messages, project management comments, and recorded video updates are all async. Remote teams that span multiple time zones rely heavily on async communication so that no single time zone is always disadvantaged.
How do I politely interrupt in a video call?
The most natural and professional phrases for interrupting in a video call are: “Sorry to jump in, but…,” “If I could just add something here…,” “Can I come in on that point?,” and “Just to build on what [Name] said…” Raise your hand (either physically or using the video platform’s raise-hand feature) before speaking if the group is large. Avoid simply talking over people — in a video call where audio lags, this causes confusion rather than clarity.
What is “bandwidth” in business English?
“Bandwidth” in business English means the available capacity, time, or energy that someone has to take on tasks. It comes from the technical meaning (internet bandwidth = data capacity) but is now widely used metaphorically. “I don’t have the bandwidth for another project this month” means “I am already too busy.” It is common in tech companies and distributed teams. If someone says “Do you have bandwidth for this?,” they are politely asking whether you have capacity to help.
How do I professionally decline a meeting?
Decline politely and briefly: “Thank you for the invite — I won’t be able to join this one, but please share the notes and I’ll follow up with any questions.” If the meeting is recurring and you feel it is not a good use of your time, you can say: “I’d like to discuss whether my attendance adds value here or whether an email update would work just as well.” Always offer an alternative (reading the notes, a quick async message) so you do not appear disengaged.
What abbreviations are used in remote work chat?
The most common abbreviations in remote work chat are: OOO (out of office), WFH (working from home), EOD (end of day), EOP (end of play), LGTM (looks good to me — used as approval), TL;DR (too long; didn’t read — used before a summary), ASAP (as soon as possible), FYI (for your information), NRN (no reply needed), and IMO / IMHO (in my opinion / in my humble opinion). Learning these saves time and helps you sound like a natural member of a remote team.
Conclusion
Remote work English spans a remarkably wide range: the casual brevity of a Slack ping, the structured clarity of a project update, and the polished formality of a client email can all be required within the same working day. The key is knowing which register fits which channel, and having a core set of phrases ready for the situations that arise most often — video call interruptions, async updates, scheduling across time zones.
The best way to make this vocabulary stick is to use it immediately in real contexts. Load the terms from the vocabulary table into Flash Cards and review them over the next few days. Write one project update using the Status / Progress / Next Steps structure. Try one of the video call phrases in your next meeting. Small, deliberate practice in real contexts is what moves vocabulary from “I recognise this” to “I use this naturally.”