An async standup template is a fixed set of prompts each person answers in writing once a day, on their own schedule, instead of meeting on a call. The reliable core is three prompts: what I finished since my last update, what I'm focused on today, and what's blocking me (and who I need it from). Post it in a dedicated channel by a consistent cutoff time, tag people in the blockers line, and keep each update to roughly 4 to 8 lines so teammates can scan it in under a minute. The rest of this guide gives you copy-paste templates for Slack, an outcome-based variant that beats the generic 'yesterday/today' wording, and the posting rules that keep async standups from going quiet after three weeks.

The basic async standup template (copy and paste)

Start here if you're setting this up for the first time. This is the classic three-part format, lightly adapted so it reads well in a chat thread rather than spoken aloud. Replace the bracketed parts and post it as a single message.

The fourth line is optional, but it's the one most teams are missing. A status meeting exists mostly so a lead can sense whether a deadline is in trouble; an explicit confidence signal recreates that without a call. If three people in a row post 'At risk,' that's a conversation worth having the same day, not next sprint.

Outcome-based standup updates (the upgrade most teams need)

The most common failure mode is updates that list activity instead of progress. 'Worked on the API' tells nobody anything. 'Reviewed the PR' is a task, not a result. Rewrite each line so it describes what changed and how it moves a shared goal. The fix is concrete and easy to coach into a team.

Activity vs. outcome, side by side

A quick gut check before you post: would a teammate know whether your day moved the project forward or just kept you busy? If your update could have been written this morning before you did any of the work, it's describing a plan, not an outcome. Name the deliverable, the state it's in, and what it unblocks.

Slack standup message examples

Here are three filled-in examples for different roles, written the way they'd actually land in a Slack thread. Notice they're short, they tag people in blockers, and they lead with the result instead of the effort.

Engineer

Designer

Marketing / generalist

How to run async standups (setup in 30 minutes)

You don't need a paid tool to start. A dedicated Slack channel and a pinned template will carry a team of 5 to 15 people just fine. Add tooling later, and only if reminders or roll-ups become a real chore.

Tool prices and limits change, so check the current plan before committing. As of 2026 several of these advertise a free tier for small teams (Geekbot, for example, lists a free plan for up to 10 users), but confirm the numbers on the vendor's own site rather than trusting a figure you read once.

Daily posting rules that keep it alive

Async standups rarely fail because the template is wrong. They fail on fuzzy expectations — people don't know when to post, whether anyone reads it, or what happens if they skip a day. Make these rules explicit and the habit holds.

Async vs. live standups: when to use which

Async is the default for teams spread across more than two or three time zones, because no single meeting time is fair to everyone. It also leaves a searchable written record — six weeks later you can find the exact day a blocker first showed up. Live standups still win in two cases: a brand-new team that needs to build trust and shared context fast, and a team mid-incident, where real-time back-and-forth resolves things in minutes that text would drag out for hours. A lot of teams split the difference: async daily, plus one short live sync each week for the higher-bandwidth conversation text handles poorly.

A remote-team update template for weekly summaries

Daily standups answer 'what's happening right now.' Once a week, a slightly wider update keeps managers and neighboring teams oriented without pulling anyone into a meeting. Keep it to five lines.

Common mistakes to avoid

Start with the basic three-line template tomorrow, rewrite each line as an outcome instead of a task, and enforce just two rules: one posting cutoff and a visible reply from a lead. That alone is enough to replace a daily call this week. Add a tool or a weekly summary only once the daily habit is solid — the format is simple on purpose, and it's the discipline, not the software, that makes it stick.