Use casesStandups & rituals
For distributed teams☕ A Slack standup calendar without the app switch.
A Slack standup calendar pinned in the channel running the standup. Daily standups, async standups, design crits, retros — visible to the whole channel, with a Slack standup reminder the moment it's about to start.
The workflow
Before & after Scalendar.
Without Scalendar
Recurring standup. Friday retro. Monthly all-hands. Each one lives in a different person's calendar, with subtly different times, and the link in the invite expired six weeks ago.
- ✕Two timezones, three meeting times, infinite confusion
- ✕The "who hosts retro this week?" Slack message, every Friday
- ✕Zoom link in the invite, agenda in a doc, notes in a thread
With Scalendar
One Slack standup calendar, pinned in the channel that runs the meeting.
- Standups, retros, all-hands pinned in the channel — open it any time, see who's hosting, see what's coming up
- Slack standup reminder 15 minutes before, posted in the channel — no one DMs "starting now" anymore
- Every event card shows its creator — the "who's hosting today's standup?" question answers itself
On a standup calendar
What goes on a Slack standup calendar.
Think of it as a Slack standup template — the daily standup, the design crit, the sprint retro, the all-hands, the rolling 1:1s. Each one pinned in the channel that actually runs it, with a Slack standup reminder before it kicks off.
Daily standups
The daily standup, pinned in the channel that runs it — with a Slack standup reminder before it kicks off.
Design crits
A weekly design review with the design team — pinned in #design where the feedback lives.
Sprint retros
Retros on the calendar, pinned in the channel running the sprint. Set the cadence; the team sees it.
All-hands
The all-team meeting, pinned in #general — with a channel reminder before it starts.
1:1s & skip-levels
Bookable office hours with managers, calendared right in the team channel.
For distributed teams
Async standups for distributed teams — without the daily call.
Async standups skip the daily live call. The team writes their update within a window — say 9 to 11am local time — and reads everyone else's when they're back at their desk. No timezone math, no "sorry I missed it" DMs, no waking up at 6am for a 9am Pacific standup.
Scalendar handles the calendar layer of an async standup: when the window opens, when it closes, who's on point this week, and a channel reminder when it kicks off. The team writes their updates wherever your async standup already happens — in a Slack thread, a doc, or wherever fits your flow.
Multi-timezone teams use it differently from single-timezone ones. A wide async window for a globally distributed team is the use case Scalendar was built for: stack a reminder at the start of the window and a soft ping near the end, and let everyone fill in their update in their own working hours.
Other ways teams use it.
All use casesLaunches & deadlines
Keep ship dates, code freezes, and demos visible to everyone.
Community events & meetups
AMAs, workshops, office hours. Members RSVP from inside Slack.
Annual leave for teams
A shared #team-ooo calendar — who's off, when, and for how long.
Ready to try Scalendar for your standups, sync or async?
Install in 30 seconds. Free for up to 2 calendars. No card required.
Join waitlist