English for a Daily Stand-Up: A Three-Sentence Status Update

At 9:57, eight people join the same call. Fifteen minutes later everyone has to know three things: who finished what, who is doing what next, and where the team is stuck. The 2020 Scrum Guide calls the Daily Scrum a 15-minute event: inspect progress toward the Sprint Goal, adapt the plan. Fifteen minutes divided by eight people is under two minutes a turn, and once two people take three, the last person runs out of time.

So the stand-up is not a report to a manager. It is a hand-off to colleagues who need to know whether their own work depends on yours: the shape of your day, and any decision they have to make.

What the stand-up is actually asking you for

The format is deliberately thin. A round that stays under fifteen minutes only works when each turn carries three things and nothing else: a result, a next step, a constraint. Everything else — how hard the bug was, who reviewed the change, why the vendor is slow — is context one colleague needs and seven do not.

The three-sentence template

Three sentences, one job each.

1. What moved since the last stand-up.
2. What you will do before the next one.
3. What could stop you, and who can unblock it.

One sentence each, no preamble. Yesterday I finished the retry logic. Today I'm picking up the export bug. Nothing is blocking me. That is eleven seconds, and the team is up to date.

The three questions are a convention, not a rule: the 2020 Scrum Guide lets a team choose any structure that produces a plan for the next day. But a fixed shape is what makes a one-minute update possible — you stop deciding what to say and start filling slots.

Tense rules that keep each sentence true

Most unclear updates are not a vocabulary problem. They are a tense problem: the sentence says finished when the work is still running, or says next when the plan is only a hope.

Form	What it promises	Example
past simple	finished, with a time you can point at	I finished the retry logic yesterday afternoon.
present perfect continuous	started earlier, still running	I've been chasing the flaky test since Monday.
be going to	a plan you have already decided	I'm going to rewrite the export step this afternoon.
will	a decision or promise made now	I'll send the numbers right after this call.

Two rules cover most of it. If the work has an end, use the past simple with a marker: I finished, I shipped, I closed. If the work is a stretch of days with no end yet, use the present perfect continuous: I've been reviewing, I've been waiting. The second form says the item is not done without you saying "still working" three times.

The third sentence has its own trap: a blocker in the future tense sounds like a worry (It might be a problem), while the present simple sounds like a fact (The staging key is missing). Say the fact, then what you need.

Time markers that do the work of a whole sentence

A marker answers "when" before anyone asks, and it costs three words.

• since yesterday for anything that started at the last stand-up.
• by Thursday for a promise with a date.
• after the review for work that waits on another event.
• until the vendor replies for a real dependency.
• before the demo for a deadline other people care about.

Put the marker at the end: I'll have the draft ready by Thursday is easier to follow than By Thursday, I will have the draft ready, because the verb comes first and the deadline second. Until the vendor replies is the exception — it is the condition, so it comes first.

One warning: a marker with no number is a wish. Soon, later today and asap all produce a sentence nobody can check. If you do not know the date, say when you will know: I'll know by tomorrow whether Thursday is still possible.

Asking for help without sounding stuck

"Blocked" is a status, not an apology. Three phrasings, in rising urgency.

I'm waiting on the staging key — Ana, can you drop it in the thread after this?

I'm stuck on the migration — I need twenty minutes with someone who knows the old schema.

I can't ship without a decision on the audit log. Sam, can we settle that today?

Each names the thing, a person, and an ask small enough to answer in one line. What to avoid: I'm blocked by the backend team. A group instead of a person, no action, and the listener has to guess whether you need a meeting, a file or a decision. A version for the day you are not blocked but worried: If the vendor slips past Wednesday I'll need help on the client side. That buys help before the problem exists.

When someone asks a question mid-update

A question mid-turn is a good sign: someone is listening, and their work touches yours. Answer the smallest version, park the rest, and finish the third sentence you still owe.

Short answer: yes. Can I finish the third point and then take that?

Good question — the detail is in the ticket, and I'll come back to it after the round.

Then actually finish. An update that dies at sentence two leaves the team unsure whether you are blocked, and the next person opens by asking. If the question turns out to be bigger than your update — a design choice, a date that affects three teams — say so in one line and name where it goes: That needs fifteen minutes with Priya and me; I'll set it up after this. The stand-up keeps its fifteen minutes, and the question keeps its owner.

How to learn English quickly for work when the stand-up is your only practice

The stand-up is already a daily rehearsal with a real audience and a time limit, which makes it better practice than most apps. Three things turn it into practice rather than performance.

First, keep the same three openers for a week: I finished, I'm picking up, Nothing is blocking me. Fluency at this scale is repetition, not range.

Second, record yourself for forty-five seconds before the call, once. Listen for two things only: whether the tense matches the work, and whether each sentence has an end.

Third, write down the three sentences you actually said and fix one of them. That is a two-minute loop you can run every working day.

That is also where a tool earns its place: HiBay's AI speaking practice gives you a turn to speak and scores it against IELTS- and TOEFL-style criteria, so the feedback is about the sentence you built rather than your accent.

Six updates you can copy

The template survives most days. Here is how it sounds on the unusual ones.

Day	Sentence 1	Sentence 2	Sentence 3
Normal	I finished the retry logic yesterday.	I'm picking up the export bug today.	Nothing is blocking me.
Blocked	I finished the schema draft.	I'm starting the migration this morning.	I need the staging key from Ana before I can test.
Nothing done	I didn't merge anything yesterday — the review came back with three fixes.	I'm clearing those three fixes first, then the export.	No decision needed from you yet.
Cross-team	I finished our side of the API contract.	I'm writing the client against the mock while I wait.	I need the vendor's field names by Thursday or the date moves.
On-call	I spent yesterday on two pages and one incident.	I'm back on the export today unless another page comes in.	If the incident repeats, I'll need someone to cover the export.
Release day	I finished the checklist and the rollback notes.	I'm on deploy at three, then monitoring.	I need one person on standby for an hour after that.

Frequently asked questions

How long should a stand-up update be?

On a fifteen-minute stand-up with eight people, ninety seconds is a safe ceiling. If your third sentence is longer than your first two together, you have started explaining, and explanation belongs in the thread with the one person who needs it. Check yourself with a stopwatch once a week, and if you keep passing ninety seconds, cut the middle sentence first — the "what I did" story is usually in the ticket already.

What do I say in a stand-up if I finished nothing yesterday?

Say it in one clause, give the reason in a second, and spend the rest of the update on today. Nothing merged yesterday — the review came back with three fixes. Then: Today I'm clearing those three fixes first. Finish with what you need, even if it is nothing: No decision needed yet. Avoid a long account of why the day went wrong, and avoid "just", as in I just didn't get to it: it invites a follow-up question you have no time to answer.