The daily standup was supposed to take five minutes. Somehow it eats twenty, drags in six people to hear updates meant for two, and still leaves the actual blockers unspoken. If your team is remote or spread across time zones, the meeting is even more expensive — someone's always joining at 7am or 11pm.
Async standups fix this. Instead of everyone stopping work to say the same three things out loud, each person replies to a prompt on their own time. The alignment survives; the interruption doesn't. And you don't need a paid Slack bot or a standup SaaS to run one — you need a recurring email and three good questions.
Here's how to set it up.
What Is an Async Standup?
An async standup replaces the live daily meeting with a written check-in that people answer whenever they start their day. The classic three questions stay the same:
- What did you do yesterday?
- What are you doing today?
- Is anything blocking you?
The difference is timing. Nobody blocks 15 minutes on a calendar. The prompt goes out every morning, replies trickle in over the first hour or two, and the whole team can skim them in the time it takes to drink a coffee. For distributed teams, this is the only version of standup that respects everyone's working hours.
Why Email Beats a Bot for This
Dedicated standup bots exist, but most teams don't need one. Email already has everything the ritual requires:
- Everyone has it. No new tool to adopt, no per-seat cost, no onboarding.
- Replies thread naturally. A reply-all creates the exact record you want — everyone's update in one place.
- It's searchable forever. Yesterday's blockers are one search away.
- It works across every time zone and device. No "did you install the app?"
The only missing piece is the part a human keeps forgetting: actually sending the prompt every single morning. That's the job you automate. With a tool like Recurrr, you write the prompt once and it goes out on schedule — every weekday, byte-for-byte, without you touching it.
Step 1: Write One Fixed Prompt
The key insight that makes email standups work: the email never changes. You're not writing a fresh message each day. You're sending the same prompt, and the fresh content lives entirely in the replies.
A simple daily standup prompt looks like this:
Subject: Standup — reply with your 3
Morning team 👋
Reply-all with:
- what you did yesterday,
- what you're doing today,
- anything blocking you.
Keep it short.
That's it. Because the message is identical every day, it's a perfect fit for a scheduled recurring email. See the full version on our Daily Standup Prompt example.
Step 2: Schedule It for Every Weekday Morning
Set the prompt to send automatically on weekday mornings — before most people start deep work, so their reply frames the day. In Recurrr you'd:
- Write the subject and body above.
- Set the schedule to every weekday at, say, 9:00am.
- Let it run. You never have to remember standup again.
The recurrence engine handles weekends, holidays you skip, and the "did I send it today?" anxiety. Your only job from here on is reading replies.
Step 3: Make Blockers the Point
Most of a standup's value is in one of the three questions: what's blocking you. The "did / doing" parts are mostly ceremony — useful context, but rarely actionable.
If your team's updates are getting long and no one's reading them, strip the ritual down to the signal that matters with a daily blocker check-in: a one-question email that asks only "is anything blocking you today?" Reply if yes, stay silent if no. You unblock people faster and reclaim the time everyone spent narrating work the group already knew about.
Step 4: Route Replies Where the Team Lives
Reply-all works beautifully for teams up to about eight people. Past that, the thread gets noisy. Two easy fixes:
- Send to a shared address that forwards into a Slack or Teams channel, so replies land where the team already talks.
- Keep reply-all but shorten the prompt — three bullets, one line each — so volume stays manageable.
Either way, the recurring email is still the heartbeat. It's just pointing the replies at the right room.
Beyond the Daily: The Rest of Your Rituals
Once the daily standup runs itself, the same pattern — one fixed prompt, sent on a cadence, answered in the replies — covers almost every recurring team ritual:
- A weekly team update prompt that asks what everyone shipped.
- A weekly retro prompt that gathers keep/drop/change input before the meeting.
- A weekly demo prompt where everyone drops a screenshot of what they built.
- A monthly team health check that quietly tracks morale.
Browse the full set on our examples for managers and engineering teams pages.
The Bottom Line
You don't need a meeting to run a standup, and you don't need a bot to run it async. You need a good prompt, a fixed cadence, and something to press "send" every morning so you don't have to. Write the prompt once, schedule it in Recurrr, and let your standup run itself — while everyone keeps their morning.