🗣️ Daily Standup Phrases
30 ready-to-use English phrases for your daily standup — progress, plans, and blockers — with a note on when to use each one. Free, no signup.
"Yesterday I…" — reporting progress
Open with what you actually finished. Lead with the outcome, not the activity.
- Yesterday I finished the login flow and opened a PR for review. Clean, complete update — done + next step.
- I wrapped up the payment refactor and it's now in QA. "Wrapped up" = finished. Common in standups.
- I got the caching layer working — response times dropped noticeably. Pair the task with its impact when you can.
- I made good progress on the migration script but it's not done yet. Honest mid-task update; sets up "today".
- I spent most of yesterday debugging the flaky test. Fine to report investigation, not just shipped code.
- I picked up the ticket about the broken webhook and started digging in. "Picked up" = took ownership of a task.
- I paired with Sam on the search feature for a couple of hours. Mention collaboration; credit teammates.
- I reviewed two PRs and left some comments. Reviews count as work — say so.
"Today I'll…" — sharing your plan
State your intent for the day. Keep it to one or two concrete things.
- Today I'll address the review comments and get the PR merged. "Address" = act on feedback. Sounds professional.
- I'm planning to finish the migration script and test it on staging. "On staging" — note the preposition.
- My focus today is the rate-limiting bug. Naming one focus signals clear priorities.
- I'll pick up the next ticket once this one is merged. Shows you have a queue and a sequence.
- I want to wrap up the API docs before lunch. Optional time hints help the team plan.
- I'll be heads-down on the perf work most of the day. "Heads-down" = focused, fewer interruptions.
- After standup I'll sync with Maria about the schema change. "Sync with" = have a quick chat to align.
"I'm blocked by…" — flagging blockers
Raise blockers clearly and early. Say what you need and from whom.
- I'm blocked — I need access to the staging database to test this. State the blocker, then the exact need.
- I'm waiting on the design before I can finish the UI. "Waiting on" = depending on something not ready.
- I'm stuck on the OAuth integration — could someone with auth experience help? Ask for help by name or by skill.
- The deploy is blocked until the security review is done. Blockers can be process, not just code.
- No blockers on my side. The standard "all clear" phrase.
- I might be blocked later today if the API spec isn't finalised. Flag a risk before it becomes a hard blocker.
- Can we take this offline? It's blocking me but it's a longer conversation. "Take it offline" = discuss after standup.
Clarifying, handing off & wrapping up
Phrases for when you need detail from someone, or to pass work on cleanly.
- Quick clarification — is this for the next release or the current sprint? Ask scope questions in one short sentence.
- Just to confirm, you want me to prioritise the bug over the feature? "Just to confirm" — polite priority check.
- I'll hand this off to Alex since I'm out tomorrow. "Hand off" = transfer ownership.
- Can someone take over the deploy while I'm on the call? Ask for coverage clearly.
- I'll add the details to the ticket so it's easy to pick up. Promise written context for async teammates.
- That's everything from me. Standard close — keep it short.
- Nothing to add — same as yesterday. Honest and brief when there's little to report.
- Let's grab five minutes after this to go over it. Move detailed topics out of the group meeting.
How to use this cheatsheet
- Skim it for two minutes before your standup and pick one phrase per topic.
- Follow the three-part rhythm: yesterday → today → blockers.
- Swap in your real tasks — the phrases are just the scaffolding.
- Save your favourites; after a week they become automatic.
Cultural notes
- Concise beats complete. A standup is a 60–90 second update, not a status report. Two sentences is plenty.
- Flag blockers early. Saying "I\'m blocked" is expected and valued — it is not a sign of weakness. Silence on a blocker is the real problem.
- Take detail offline. If a topic needs more than a sentence or two, say "let\'s take this offline" and discuss it after.
- Lead with outcomes. "I shipped the login fix" lands better than "I worked on login."