English Phrases for Engineering Stand-ups

The daily stand-up is a cornerstone of agile engineering teams. It is short, focused, and follows a predictable structure — which makes it an excellent opportunity to build English communication habits. But even in a familiar format, non-native speakers often feel uncertain about the right phrasing. This guide gives you natural, professional English phrases for every part of the stand-up.

The Three Classic Questions

Most stand-ups are organised around three questions:

1. What did you work on yesterday?
2. What are you working on today?
3. Do you have any blockers?

Some teams add a fourth question: “What will you pick up next?” Let’s cover each in detail.

Reporting Yesterday’s Work

Use the simple past tense to describe completed work.

Basic phrases:

“Yesterday I worked on the authentication refactor.” “I finished the database migration script.” “I reviewed three pull requests and left comments.” “I spent most of yesterday investigating the memory leak in the worker service.”

When you didn’t finish something:

“I was working on the API rate limiting implementation — it’s taking longer than expected. I’ll continue today.” “I got partway through the test coverage improvements. Still in progress.”

When you attended meetings or did non-coding work:

“Yesterday was mostly meetings — the sprint planning session and two design reviews. I’ll be coding today.” “I spent the afternoon on documentation for the new onboarding flow.”

Reporting Today’s Plans

Use the present continuous or going to future tense.

Basic phrases:

“Today I’m working on the payment integration.” “I’m going to finish the unit tests for the order service.” “My focus today is the performance issue in the search endpoint.” “I’m picking up the task for the notification service — it’s been in the backlog for a while.”

Specifying tasks:

“Today I’m working on two things: the database schema update and a code review for Laura’s PR.” “I’m going to pair with Marcus on the deployment pipeline issue.”

When your plan is uncertain:

“It depends on how quickly I can resolve the blocker, but ideally I’ll start on the front-end integration this afternoon.”

Reporting Blockers

A blocker (or impediment) is anything preventing you from making progress. Be specific about what the blocker is and — if known — what help you need.

Reporting a blocker:

“I have a blocker: I’m waiting for access to the production logs to investigate the bug.” “My blocker is the dependency on the payments team’s API — it’s not ready yet.” “I’m blocked on a design decision. I need a fifteen-minute conversation with someone to unblock me.”

When you don’t have a blocker:

“No blockers on my end.” “Nothing blocking me today.” “I’m unblocked and making good progress.”

When something is slowing you down but not fully blocking:

“I don’t have a hard blocker, but I’m moving slowly on this — the legacy code is more complex than expected.” “I could use a second pair of eyes on the database schema design at some point today.”

Asking for Help

The stand-up is a moment to signal that you need help. Be direct but concise — detailed discussion happens after the stand-up or asynchronously.

“I need help with the Terraform configuration — could someone take a look after the stand-up?” “Is anyone familiar with the webhook retry logic? I have a question.” “I’d appreciate a quick pairing session today if anyone has capacity.”

Handing Off or Picking Up Work

“I’ll pick up the task for the error reporting dashboard — it’s been deprioritised but it’s next in my queue.” “I’m handing off the API documentation to Tom — he’ll be taking it from here.” “I’ll be picking up the ticket for the accessibility audit.”

Useful Transition and Closing Phrases

“That’s it from me.” “That’s all I have — no blockers.” “Happy to discuss the blocker in more detail after the stand-up if anyone has time.” “I’ll send an update in Slack if anything changes.” “Over to you, Priya.” (when passing to the next person)

Common Mistakes to Avoid

Over-explaining: The stand-up is a status update, not a design discussion. If you catch yourself explaining more than two or three sentences, stop and offer to continue after the meeting.

“I can go into more detail after the stand-up if anyone is interested.”

Using the wrong tense for completed work:

Incorrect: “Today I’m reviewing pull requests yesterday.” Correct: “Yesterday I reviewed pull requests.”

Forgetting to mention blockers: If you are stuck, say so. The stand-up exists precisely to surface blockers early.

A Full Example Stand-up Update

“Yesterday I worked on the authentication token refresh logic — I got the core implementation done and merged. Today I’m writing integration tests for it and then picking up the session expiry task from the backlog. I have one blocker: I need someone from the security team to review the token storage approach. Is there anyone who can help with that today or tomorrow?”

This covers all three questions clearly, mentions what needs to happen next, and makes a specific request for help — in under 60 seconds.

The stand-up is a simple meeting, but it is one where clear English makes a real difference. Consistent, concise updates build trust with your team, surface blockers early, and demonstrate professional communication skills. The phrases in this guide will help you feel confident and prepared every morning.