Pointspoken

What to say in a daily standup, in clear English

Reviewed 19 Sept 2026

A standup update should take about half a minute. It exists so that teammates can spot overlaps and unblock each other, not so that everyone can prove they were busy.

The hard part in a second language is speed. Everyone speaks quickly, there is no time to plan, and it is tempting to fill the silence. A fixed three-part pattern removes the planning, so you can spend your attention on saying it clearly.

The structure: yesterday, today, need

  1. Yesterday

    One result, in one sentence. Pick the item a teammate is most likely to care about.

  2. Today

    The one thing you intend to finish, not everything you might touch.

  3. Need

    A named person and a specific request. If you need nothing, say “no blockers” and stop talking.

Before and after

A team of six, standing meeting, each person speaks in turn.
Before

“Yeah so yesterday I was looking at the login bug, and I tried a few things, I thought it was the cache but it wasn't, so then I looked at the session stuff, still not sure, and also I had some meetings. Today I'll keep looking at it, and, yeah, maybe I'll ask someone if I get stuck.”

  • The investigation is told step by step, which nobody else needs.
  • “Maybe I'll ask someone” hides a real blocker. The standup is the place to ask.
  • There is no result and no plan that a teammate could react to.
Clearer

“Yesterday I ruled out the cache as the cause of the login bug. Today I'm testing the session timeout, and I expect an answer by lunch. Sam, I need fifteen minutes from you on how sessions are refreshed. Can we talk straight after this?”

Scripted example, not a real user's recording.

Phrases you can use

Yesterday
  • “Yesterday I finished…”
  • “I ruled out…, so the cause is probably…”
  • “The pull request for… is ready for review.”
Today
  • “Today I'm aiming to finish…”
  • “My one goal today is…”
  • “I'm picking up… next.”
Need
  • “I need ten minutes with… about…”
  • “I'm blocked until… is merged.”
  • “No blockers.”

Common mistakes

Narrating the debugging

Give the conclusion: what you ruled out or confirmed. Offer the detail after the meeting.

Listing meetings

Nobody needs your calendar. Mention a meeting only if it produced a decision that affects the team.

Asking nobody in particular

Use a name. “Sam, can I have fifteen minutes?” gets an answer; “I might need help” does not.

Solving it in the standup

When a discussion starts, say “let's take that after standup” and move on.

A ten-minute drill

  • Before your next standup, say your three sentences out loud once. Time it: aim for 20 to 30 seconds.
  • Record the same update as a practice answer and read the transcript. Cross out every word that a teammate would not miss.
  • Record again without those words.

Questions people ask

What if I made no progress yesterday?

Say what you learned or what stopped you: “No progress on the export yesterday. I was pulled onto the incident. Back on it today.” That is a complete and respectable update.

Is it rude to be this short?

No. In a standup, brevity is a courtesy to the other people waiting to speak. Being short and specific is read as competence.

How do I handle a standup that is not in my first language?

Prepare your three sentences two minutes before. A fixed pattern means you only choose the content, not the structure, which frees attention for pronunciation and pace.

Related situations