What Makes a Remote Standup Work
The standup format — what did you do yesterday, what are you doing today, any blockers — works when three conditions hold: it is short (fifteen minutes or less), it surfaces real blockers rather than status theater, and it does not duplicate information that is already in a shared tool.
On a remote team, the standup also serves a relationship function that in-office standups often provide through physical presence — a daily touchpoint that maintains team cohesion across distance.
Calendar Setup for a Lightweight Remote Standup
- Schedule for 15 minutes, not 30 — the time box enforces the format.
- Add a persistent Google Meet link to the recurring event so no one hunts for it daily.
- Include the standup format (what/doing/blockers) in the event description as a template.
- Set a no-agenda-no-meeting rule: if there are no blockers and everyone's work is visible in the project tool, consider cancelling.
- Choose a time that works for all timezones — or move to async if the team is too distributed for a shared standup time.
The Async Standup Alternative
For teams that are too distributed for a shared standup time, or for days when the synchronous format feels like overhead, an async standup — a shared document or Slack thread where each person posts their three sentences by a specified time — covers the same informational ground without scheduling coordination.
Some teams use the async format by default and escalate to a synchronous standup only when there are blockers that require live discussion. This hybrid approach reduces meeting time while preserving the option for real-time problem-solving when needed.
A standup that consistently runs over fifteen minutes is not a standup — it is a status meeting with a different name. Address the scope issue rather than extending the time box.
Maintaining Standup Quality Over Time
Standups decay. After a few months, the format gets ignored, the meeting runs over, and it becomes a check-in call without clear purpose. A monthly five-minute retrospective on whether the standup is serving its purpose — and what would make it more useful — prevents the accumulation of this decay. For related reading on managing recurring meeting quality, see our guide on when to kill a recurring meeting.
How Schedule Calendar helps
The daily standup appears in Schedule Calendar's popup with its recurring Google Meet link directly accessible. For remote team members, clicking the join link from the toolbar — without navigating to the calendar — reduces the friction of joining the standup on time. The countdown before the standup also signals when it is starting without requiring a separate reminder to check.
Frequently asked questions
Fifteen minutes is the target for teams of three to seven people. Each person takes roughly two to three minutes to share their three updates. Blockers that require discussion should be taken offline to a separate call or async thread rather than resolved in the standup. If fifteen minutes consistently runs over, the scope has expanded beyond the standup format.
Include: a persistent conference link (not generated fresh each time), the standup format in the event description (what did you do, what are you doing today, any blockers), the intended duration (15 minutes), and any relevant team documentation links. A persistent conference link is especially important — hunting for the daily meeting link wastes time and causes late starts.
Consider switching when: the team spans time zones with no natural overlap window, the synchronous standup consistently feels like overhead for a team with good tooling, or the meeting is primarily used for status updates rather than blocker identification. An async standup — written updates in a shared document or Slack — covers the informational purpose without the scheduling coordination.
Enforce the format strictly: each person answers the three questions and stops. Take blockers and extended discussions to a separate call immediately after or to a dedicated async thread. Cancel the standup on days with no real blockers and good shared visibility in the project tool. Run a monthly five-minute check on whether the standup is serving its purpose.
For most remote standups, recording adds overhead without commensurate value — the content is transient and its value is in the moment of sharing. For teams with significant timezone gaps where some members cannot attend live, a written async update is usually more accessible and useful than a recording. Record only if the specific content is valuable to review later, which is rarely the case for daily standups.
When creating or editing the recurring standup in Google Calendar, enable the Google Meet integration to add a conference link. This link is persistent across all instances of the recurring event — the same link works for every standup. Alternatively, create a standalone Google Meet meeting and copy the link into the recurring event description manually. Verify that the link persists across instances before the first use.