Standup Meeting English: What to Say Every Day

The exact phrases and sentence structures for daily standups — what you did, what you'll do, and how to report blockers clearly in English.

The daily standup is probably the most repeated conversation in a developer’s working life. You say roughly the same three things every morning — what you did yesterday, what you’ll do today, and whether anything is blocking you.

But for non-native English speakers, this seems simple but often isn’t. The standup combines past tense, future tense, technical vocabulary, and professional tone — all in under a minute, live, in front of your team.

Here is everything you need to do it confidently.


The Three Standard Questions

Every standup answers three questions. Memorise how to open each one:

QuestionStarter phrases
What did you do yesterday?”Yesterday I…”, “I spent yesterday…”, “Last week I…” (on a Monday)
What will you do today?”Today I’m going to…”, “I’m planning to…”, “My focus today is…”
Are there any blockers?”No blockers.”, “I’m blocked on…”, “I need help with…”

Describing Yesterday’s Work

Use simple past for completed work. Use present perfect if the work is finished but still relevant to today.

Examples

“Yesterday I finished the login API endpoint and wrote unit tests for the happy path.”

“I spent most of yesterday debugging the websocket disconnection issue. I narrowed it down to a race condition in the reconnect logic.”

“Yesterday I reviewed three PRs and attended the sprint planning session. I didn’t get to the ticket I planned because the planning ran long — I’ll pick that up today.”

“I was out sick yesterday. Today I need to catch up on the sprint board and check what changed.” ← Useful phrase if you missed the previous day.

Common mistakes to avoid

“Yesterday I was doing the login endpoint.” — Do not use past continuous for completed tasks.
“Yesterday I worked on / I finished / I completed the login endpoint.”

“I make the tests.”
“I wrote / created / added the tests.”


Describing Today’s Plan

Use present continuous (“I’m doing”) or going to + verb for plans. Both are natural.

“Today I’m going to start implementing the notification system.”

“I’m planning to finish the database migration script and open a PR for review.”

“My focus today is finishing the frontend form — I want to have it ready for QA by end of day.”

“Today I’m picking up [ticket number]. I’ll also join the design sync at 2 PM.”

“I’m continuing work on the search feature — I should be done by this afternoon.”

Useful expressions for estimating progress

“I’m about halfway through the task.” — progress midway
”I should have this ready by end of day.” — ETA
”This is taking longer than expected — I’ll give a better estimate once I’ve dug in.” — realistic update
”I’ll have a draft ready for review by tomorrow morning.” — committing to a deadline


Reporting Blockers

This is the most important part of the standup — and often the hardest to say, especially in a second language. Being blocked is not embarrassing. Reporting it clearly is a sign of seniority, not weakness.

No blockers

“No blockers.” — clear and professional; perfectly acceptable
”Nothing blocking me."
"All clear on my end.”

When you are blocked

“I’m blocked on the API access — I don’t have credentials for the staging environment yet.”

“I’m waiting on a response from [person/team] before I can continue.”

“I’m blocked on [ticket]. I’ve raised it with [person] — hoping to get unblocked today.”

“I hit a wall with the third-party library — it doesn’t support our use case. I need to discuss alternatives with the team.”

“I need a decision on the DB schema before I can move forward. Can we sync after standup?”

The phrase “Can we sync after standup?” is extremely useful. It signals that a topic needs discussion, but without derailing the standup itself.


Putting It All Together: Full Standup Examples

Scenario 1: Normal day, no blockers

“Yesterday I finished the user authentication flow and merged the PR. Today I’m starting on the password reset feature. No blockers.”

Scenario 2: Blocked, needs help

“Yesterday I worked on the notification service but got stuck on how to handle timezone differences in the scheduled emails. I’m still on that today. I’m blocked — I’d like to pair with someone who’s worked with this scheduler before.”

Scenario 3: Slower progress than expected

“Yesterday I was debugging a flaky test. Turns out it was a timing issue with the async setup — I’ve fixed it but it took most of the day. Today I’m catching up on the ticket I planned for yesterday. No blockers, but I’m behind on the sprint goal, so I’ll flag that here.”

Scenario 4: Reviewing and supporting

“Yesterday I reviewed two PRs — left comments on both, approved one. I also helped [name] debug a CI issue. Today I’m back on my own tasks — mainly the cache invalidation logic. No blockers.”


Standup Vocabulary Quick Reference

PhraseWhen to use it
”I’m blocked on…”Something is preventing you from progressing
”I need to sync with…”You need to talk to a specific person
”I’m behind on…”Progress is slower than planned
”I wrapped up…”You finished something (slightly more natural than “I finished”)
“I picked up…”You started working on a ticket/task
”I handed off…”You transferred work to someone else
”I’m waiting on…”You need something from outside your control
”I flagged this to…”You escalated or notified someone
”ETA”Estimated Time of Arrival — used informally: “ETA on that is tomorrow”

One Last Tip: Keep It under Two Minutes

Standups are time-boxed — usually 15 minutes for the whole team. Your update should take 30–60 seconds maximum. If something needs more discussion, say:

“I’ll follow up on that after standup."
"Let’s take that offline."
"Can we put 10 minutes on the calendar to discuss this?”

“Take it offline” is one of the most useful phrases in English meeting vocabulary. It means: “This is a longer conversation — let’s not have it in the standup.” It is not negative or dismissive; it is how experienced engineers keep meetings efficient.

Practice your standup update before the meeting if English is not your first language. Thirty seconds of preparation makes a noticeable difference.