Standups
Use standups to collect completed work, planned work, and blockers before the meeting starts.
How standups work
Each standup starts from current work context. Participants review what they completed, what they plan to work on, and what is blocked before or during the meeting.
The goal is a short alignment loop, not a manager-facing status performance. Source work stays attached so the team can move quickly and follow up on the records that need attention.
Standup list
The standups page shows standups you are involved in and standups run by other teams you can observe. Each standup shows the team, schedule, and active state.
Configuration
Team admins configure which days the standup runs, what time it runs in the team's timezone, and whether it syncs with a Google Calendar recurring event. Setup can adopt an existing event time, create a new calendar event, or link an existing one.
The configuration page also shows team members with icons for connected integrations so admins can see whether anyone is missing a key connection.
Standups can be enabled, disabled, or deleted from team settings. When Google Calendar is connected, we can keep the recurring event and Meet link aligned with the standup schedule.
For team ownership and admin controls, see Teams. For calendar setup, see Google Calendar.
Waiting room
The waiting room shows when the standup starts, who is expected, who has joined, and the time zones of attendees. Use it to review planned work, mark completed work, and document blockers before the live meeting starts.
Any team member can start the meeting when the team is ready.
Running the standup
The live standup view shows one participant at a time in the same three-column recap format: worked on, planned, blockers. The sidebar collapses automatically so the current speaker has focus. When the organizer finishes, other participants are redirected back to the standups list.
The current speaker view can include completed team journal tasks, in-flight issues from connected issue trackers, pull requests, calendar events, and blockers.
Planned todos can appear in the planned column. Planned issues are filtered to keep stale issue tracker work out of the standup.
Todos can be made private. Synced integration items follow the source app's visibility, so do not rely on a workspace privacy toggle for work already visible in Jira, Linear, GitHub, or GitLab.
After the meeting, the end view shows completion context such as meeting duration and attendance, then the team can follow up on blockers or action items from the source work.
For async teams, use Slack Standups; for live calls, use Google Meet.