English for Standup Meetings: Phrases That Work

The daily standup is one of the shortest meetings on the calendar and one of the highest-stakes for non-native English speakers. You have 60 to 90 seconds to communicate clearly, sound confident, and not accidentally alarm your manager with poorly chosen words. English for standup meetings follows a specific structure that, once you internalize it, makes the whole thing significantly easier. This guide covers the phrases and patterns for live standups and written async updates — with special attention to how to report blockers without sounding incapable. For the broader context of professional English at work, see our guide for non-native English professionals.

The Standup Formula and Why It Helps Non-Native Speakers

The standup format — yesterday, today, blockers — is one of the most predictable structures in professional English. That’s good news if you’re working in your second or third language: predictable formats mean you can prepare language in advance rather than improvising under pressure.

The three-part structure exists because it covers the full picture quickly:

Yesterday: What did you complete or work on?
Today: What are you working on or planning to finish?
Blockers: What is preventing you from moving forward?

When the format is this clear, your job is not to fill it with elaborate sentences — it’s to fill it with accurate, concise information in natural-sounding English. The phrases below give you the language to do that in every scenario.

Yesterday Phrases for English Standup Meetings

The past reporting section has one job: tell the team what you actually accomplished or worked on. Use past simple tense for completed work. Use past continuous or “working on” for in-progress items.

Completed work:

“Yesterday I finished the API integration for the payment flow.”

“I completed the design review and shared feedback with the team.”

“I wrapped up the data migration for the staging environment.”

In-progress work (not yet complete):

“Yesterday I was working on the authentication module — I made good progress but it’s not finished yet.”

“I spent most of yesterday on the refactor. Still in progress, but the core logic is done.”

“I continued work on the dashboard redesign. I’m about 70% through the mockups.”

If you worked on meetings or reviews rather than direct output:

“Yesterday was mostly meetings — I attended the sprint planning and had a one-on-one with my manager. I also reviewed two pull requests.”

That last one is important. Non-native speakers sometimes feel like “just meetings” is not a legitimate standup answer. It is. Being honest about how you spent your time is always better than padding with vague phrases.

Today Phrases for English Standup Meetings

The today section uses present continuous (“I’m working on”) for things already in progress, and present simple (“I plan to”) or “going to” for things you intend to do.

Starting something new:

“Today I’m going to start the unit tests for the authentication module.”

“I’m planning to kick off the performance analysis this morning.”

“Today I’ll focus on reviewing the open tickets from last sprint.”

Continuing something:

“I’m continuing work on the payment integration — I expect to have a PR ready by end of day.”

“Today I’ll be finishing up the mockups and sharing them for review.”

When you have a specific deliverable:

“My main goal for today is to get the staging deployment done before the 3 p.m. review.”

“I’m aiming to complete the documentation and have it merged by EOD.”

Giving a specific deliverable or time target — “by EOD,” “before the review,” “by noon” — is one of the fastest ways to sound more confident in a standup. It replaces vague “I’ll be working on it” energy with concrete commitment, which reads as professional competence regardless of your English level.

How to Report Blockers in English Standup Meetings Without Sounding Incapable

Blockers are where non-native speakers hesitate the most. In many cultures and languages, reporting that you are stuck carries a strong implication of failure or incompetence. In English-speaking engineering and product teams, the opposite is true: reporting a blocker promptly is considered professional, responsible behavior. Hiding a blocker is the problem, not having one.

The key is in how you frame it. The goal is to state the blocker clearly, explain why it’s a blocker, and signal that you are either actively working on a solution or you need a specific form of help.

Simple blocker:

“I’m blocked on the API credentials — I’m waiting for the DevOps team to grant access before I can continue.”

Blocker with what you’ve already tried:

“I’m blocked on a dependency issue with the build. I’ve checked the documentation and tried two approaches, but I need a second set of eyes. Could someone with Gradle experience take a look?”

Blocker that is unclear or ambiguous:

“I have a question that’s holding me up — the requirements for the export feature aren’t clear on whether we need to support CSV and Excel, or just CSV. Can we clarify that today?”

When you’re not fully blocked but slowed down:

“I’m not fully blocked, but I’m moving slower than expected on the database queries — the performance is worse than I expected and I’m investigating.”

That last example shows nuance that sounds very natural in English: distinguishing between “blocked” (cannot continue) and “slowed down” (continuing, but with difficulty). Many non-native speakers either overclaim being blocked or underclaim it to avoid appearing stuck. This phrasing thread — “not fully blocked, but…” — splits the difference cleanly.

Hedging vs. Clarity: When to Qualify and When to Be Direct

Non-native speakers sometimes overuse hedging language in standups because they’re not 100% certain of what they’ll accomplish in a day. This is understandable, but too many hedges make you sound less reliable than you are.

Over-hedged (avoid):

“I might try to possibly work on the testing if I have time and things go okay.”

Clear commitment with appropriate qualification (use this):

“I’m planning to finish the testing today — I’ll flag it if something unexpected comes up.”

The second version commits to a goal while leaving a professional door open. That’s the balance standups are looking for: directness with honesty about uncertainty, not directness alone and not endless qualifications.

Hedging is appropriate when you genuinely don’t know the answer, when you are reporting something uncertain, or when you are making a prediction about external factors. It is not appropriate as a general anxiety-reduction strategy for every sentence.

For broader guidance on natural professional English phrasing and eliminating over-hedging patterns, see how to improve your business English fast.

If you write async standup updates in Slack or Jira, over-hedging shows up in writing even more visibly than in speech. NotchTutor is particularly useful for catching awkward hedges and tense errors in written updates — and it explains why each correction matters, which means the same mistake is less likely to appear next Monday.

Async Standup Updates for Slack and Jira

Many teams now run standups asynchronously — you write your update in a Slack channel, a Jira ticket, or a dedicated tool like Geekbot or Range instead of attending a live meeting. The written format follows the same yesterday/today/blockers structure, but the written medium changes a few things.

In async updates, write in short sentences. Avoid long paragraphs.

A readable async standup in Slack:

Yesterday: Finished the payment flow integration and opened a PR for review.

Today: Working on the unit tests for the checkout module. Goal is to have the test suite running by EOD.

Blockers: None.

If you have a blocker, be specific about what you need:

Blockers: Waiting on API credentials from DevOps (ticket #1423). Can’t proceed with the integration tests until I have access.

Tagging the ticket number is optional but useful when your team works in Jira or a similar tool — it gives colleagues a direct path to context without you having to explain the full background every time.

For Slack specifically, avoid writing your async update in a single dense paragraph. The format above — with bold labels — is readable in a channel thread in a way that paragraph updates are not. For more on professional Slack writing in English, see how to write professional Slack messages.

The daily standup rewards prepared language. You know exactly what will be asked, you know the three-part format, and with the phrases in this guide you have the vocabulary to fill all three sections confidently — in live meetings and in async written updates. Preparation doesn’t make your English sound scripted; it makes it sound fluent.