Daily Standup in English: Example Sentences You Can Use

You join the daily standup, your turn comes, and your mind goes blank. The content is simple: what you did, what you will do, and what is in your way. In a standup meeting in English, the hard part is rarely the content. It is building sentences quickly in front of a group.

This article gives you daily standup update example sentences that are short and easy to say, ways to report blockers and delays, a fill-in template, and three complete standups for a developer, a designer, and a freelancer. All sentences use plain, everyday English.

The three parts: yesterday, today, blockers

Almost every team uses the same pattern. You answer three questions:

1. Yesterday. What you finished or moved forward.
2. Today. What you will work on.
3. Blockers. What is in your way, or "no blockers".

A standup is not a full report. Its purpose is to show the team where you are. Technical details belong after the meeting, not inside it.

Sentences for "yesterday"

Start with a past-tense verb and name the result.

Yesterday I finished the login page.

I fixed the bug in the payment form.

I reviewed two pull requests.

I made progress on the report, but it's not done yet.

I spent most of the day testing the new API.

If little got finished, say so plainly. Do not circle around it.

I was mostly in meetings yesterday, so I only started the task.

Sentences for "today"

Name one or two priorities. Do not read out your whole task list.

Today I'll work on the checkout flow.

My main goal today is to finish the API tests.

I'll start the new design after lunch.

I plan to send the draft to the client today.

After that, I'll help with code review if I have time.

Notice "I'll" and "I plan to". Both sound natural and sure enough, without overpromising.

How to say you are blocked and ask for help

This is the part where many people hesitate. But naming blockers is the main reason a standup exists. Say what the problem is, then what you need.

I'm blocked on the database access.

I'm waiting for the design files from Sara's team.

I need a review on my pull request before I can continue.

Can someone help me with the deployment error after the standup?

I don't have any blockers right now.

A pattern you can reuse: blocked on + problem, then need + help. For example: "I'm blocked on the API key. I need access from the admin."

Avoid vague lines like "I have a small problem." The team does not know how to help. If the technical issue is too long for now, offer a separate chat, and see explaining technical trade-offs in English.

How to report a delay without over-apologizing

One "sorry" is enough. Your team needs information more than regret. Build it in three parts: the fact, a short cause, and the plan.

The task is delayed by one day.

The delay is because the test environment was down.

I'll finish it by tomorrow afternoon.

I'll update you if that changes.

Read in order, that is four calm, clear sentences. Compare it with "I'm so sorry, I'm really sorry, I should have done it earlier." The second version makes others comfort you instead of helping you.

If you do not know when it will be done, say so and give a time to check.

I don't know the new date yet. I'll know after I test it this afternoon.

How to keep your update under 30 seconds

Three short sentences take about 15 to 20 seconds. A few habits help:

• One sentence per part. Add a second only if it really matters.
• Results, not process. "I finished the form" is more useful than the steps you took.
• Write notes before standup. Three short lines are enough. Say them once in your head before your turn.
• Save the details. Say "I can explain after standup" if someone asks too deep.

Short sentences are also easier to say smoothly. See why short sentences make answers clearer.

Async standup in chat

Many remote teams do written standups in Slack or Teams. A tidy three-line pattern is enough.

Yesterday: Finished the signup form. Today: Writing tests for the form. Blockers: None.

If you have a blocker, also name who you need.

Blockers: Waiting for the API key. @Dimas, can you share it today?

Keep the sentences as short as you would say them out loud. Written standups are also good practice for spoken ones.

Fill-in template

Copy this and replace the parts in brackets.

Yesterday I [finished / fixed / reviewed / started] [task].

Today I'll [work on / finish / start] [task].

I'm [blocked on / waiting for] [thing]. I need [help or access].

Or: I have no blockers.

This template covers almost every daily standup.

Three complete standups

Developer

Yesterday I finished the user profile API.

I also fixed two small bugs in the search page.

Today I'll write tests for the profile API.

I'm blocked on the staging server. It's been down since this morning.

Can someone from DevOps check it today?

Designer

Yesterday I finished the first version of the onboarding screens.

I sent them to the team for feedback.

Today I'll update the screens based on the comments.

I'm waiting for the final logo from the brand team.

No other blockers.

Freelancer

Yesterday I completed the homepage layout for the client.

I started the contact form, but it's not done yet.

Today I'll finish the form and send a preview link.

The client's feedback is delayed by one day, so I'll start the next page first.

I'll share the update this afternoon.

Common mistakes

• Too much detail. A three-minute technical explanation makes the standup run long. Save it for a separate session.
• Hidden blockers. Staying quiet when you are stuck makes the problem show up late.
• Promising too firmly. If you are not sure, use "I plan to" or "I hope to".
• Repeating apologies. Say it once, then move to the plan.
• Mispronounced tech words. Words like "cache" or "queue" can sound different from what you expect. See commonly mispronounced tech terms.

Summary

A daily standup in English needs only three parts: yesterday, today, blockers. Use one short sentence per part, around 15 words at most, and you finish in under 30 seconds. State blockers clearly and name the help you need. Report a delay as a fact and a plan, not a string of apologies. Write three lines of notes before your turn, and the habit gets easier fast.

Repartee is a Windows desktop app with a Meeting mode (Rapat) that listens to the meeting audio, shows the transcript with an Indonesian translation and the gist of the question, and drafts short English replies based only on your own meeting notes and profile. It never invents experience or progress, and you still speak in your own words.