Daily Standup Update Template for Engineering Teams (2026)
The daily standup update is the most common status update in engineering teams — and the most commonly done poorly. Generic updates like 'worked on the feature' waste everyone's time. A great standup update is specific, scannable, and takes under 2 minutes to write. This template gives your team a consistent format that captures meaningful progress, surfaces blockers early, and provides context that actually helps the rest of the team. Use it for async Slack standups, email updates, or as prep before synchronous meetings.
2-minute setup • No credit card required
When to use this template
Post daily at the start of your work day (async) or use as talking points during a synchronous standup. For distributed teams, post by end of your local morning so teammates in other time zones can read updates before their standup.
Template Variations
Pick the format that fits your context.
Yesterday / Completed
What you accomplished since the last update. Be specific — reference ticket numbers, PR links, or feature names so teammates can find context if needed.
**Done:** - [TICKET-123] Merged PR for user auth flow — added token refresh logic - Reviewed [teammate]'s PR on payment processing (#456) - Deployed hotfix for the email rendering bug (prod confirmed ✓)
Today / Planned
What you plan to work on today. This helps the team anticipate review requests, collaboration needs, and potential conflicts.
**Today:** - [TICKET-789] Start API endpoint for team invitations - Write integration tests for the auth flow I merged yesterday - Pair with [teammate] on database migration strategy (2pm)
Blockers / Risks
Anything preventing progress or at risk of delaying delivery. Name the blocker AND who can help unblock it.
**Blocked:** - Waiting on API docs from [external team] for the integration — pinged [contact] yesterday, following up today - CI pipeline flaky on test-suite-X — 3 retries needed to get green (/cc @platform-team) **No blockers** ← use this if you're clear
Context / FYI
Optional section for information that doesn't fit the other categories but is useful for the team to know.
**FYI:** - Taking a half day Friday for an appointment — will be offline from 1pm - The staging environment is running the new auth flow if anyone wants to test - Found a good library for rate limiting — will share in #engineering later
Expert advice
Write your standup update first thing in the morning — it takes 90 seconds and sets your intention for the day
If your updates look the same 3 days in a row, something is stuck — flag it even if it doesn't feel like a 'blocker'
Reference PR numbers and ticket IDs so teammates can get full context without asking follow-up questions
Use automated git-based updates (like Gitmore) for the 'Done' section and only manually add blockers — this saves time and ensures accuracy
Read your teammates' updates daily — async standups only work if people actually read them
Common questions
How long should a standup update take to write?
Under 2 minutes. If it takes longer, you're adding too much detail. The goal is a scannable summary, not a comprehensive work log. Use ticket numbers and PR links so readers can find details themselves.
What if I didn't finish anything yesterday?
That's fine — report progress honestly. 'In progress: auth flow at 60%, debugging token refresh edge case' is a perfectly valid update. If this happens multiple days in a row, it might indicate the task needs to be broken into smaller pieces or there's a hidden blocker.
Should standup updates replace synchronous meetings?
For status sharing, yes — async updates are more efficient. But keep a weekly synchronous meeting for discussion, blockers that need real-time collaboration, and team bonding. The goal is: async for information, synchronous for conversation.
How do you ensure people actually read async updates?
Three techniques: (1) Keep updates short and scannable — walls of text don't get read, (2) Use a dedicated Slack channel with no other noise, (3) Have the engineering manager reference standup updates in discussions ('as [name] mentioned in their update...'). This signals that updates are actually being read.
More free templates
Copy-paste templates for every stage of the engineering workflow.
Weekly Sprint Report Template
Sprint goals, completed work, carry-over, metrics, blockers, and next sprint preview.
View template📋Product Changelog Template
Keep-a-Changelog format for public releases, internal builds, and GitHub releases.
View template🚀Developer Onboarding Plan Template
30-60-90 day onboarding plan from pre-boarding through full ramp-up.
View template💼Freelance Developer Weekly Report Template
Professional weekly reports for freelance developers to send to clients.
View templateAutomate Your Git Reporting
Stop filling in templates manually. Connect your git provider and let Gitmore generate reports automatically — daily, weekly, or on demand.
Get Started FreeNo credit card • No sales call • Reports in 2 minutes