Slack Standup Template
A reusable Slack standup post template with five filled-in examples ready to copy.
More from Social
What you get
Get a reusable Slack standup post template with five filled-in examples, using bold section headers and a plain, direct voice, ready to copy and paste.
Who it's for
- Scrum masters running daily standups
- Team leads managing async teams
- DevOps engineers coordinating daily updates
- Product managers overseeing project progress
- Remote work team coordinators
Use cases
- When you need to send a daily standup update to your team
- As a team lead, when you want to standardise your standup posts
- For async teams, when you need to keep everyone informed
- When you're onboarding new team members and want to set a good example
- When you want to improve team communication and collaboration
FAQ
what should be in a slack standup post?
A good Slack standup post should include brief updates on what you did yesterday, what you're doing today, and any blockers you're facing. This template provides a concise and scannable format with five example fills.
how do you write a good slack standup post?
Write your Slack standup post in a plain and direct voice, avoiding buzzwords and filler phrases. Use bold section headers like 'Yesterday', 'Today', and 'Blockers' to make it easy to scan.
how do you announce a product launch on slack?
While this template is specifically for standup posts, you can use a similar format to announce a product launch on Slack, keeping your message concise and to the point.
what makes a good slack shout-out message?
A good Slack shout-out message is brief and specific, recognising someone's achievement or contribution. This template can help you get started with writing clear and concise messages.
Sample output
**Template** *Yesterday:* I worked on [task/project name] and completed [specific task or milestone]. *Today:* I will be focusing on [task/project name] and aiming to [specific goal or deliverable]. *Blockers:* I am currently blocked by [specific issue or dependency]. **Example fills (Number 1-5)** 1. *Yesterday:* I fixed 5 bugs in the authentication module, *Today:* I will be optimizing database queries for the user profile page, *Blockers:* I am currently blocked by a pending database schema update. 2. *Yesterday:* I implemented API endpoints for the new payment gateway, *Today:* I will be integrating the payment gateway with the existing order processing system, *Blockers:* None 3. *Yesterday:* I reviewed and merged 2 PRs for the team, *Today:* I will be working on a new feature to improve error logging, *Blockers:* I am waiting for feedback from the QA team on the current build. 4. *Yesterday:* I refactored the code for the search function to improve performance, *Today:* I will be testing the new search function with a large dataset, *Blockers:* I am currently blocked by a dependency on the updated search index. 5. *Yesterday:* I investigated and resolved a production issue with the caching layer, *Today:* I will be implementing a monitoring system to detect similar issues, *Blockers:* None
Last updated: 2026-06-28