What is async calendar etiquette, and why does it matter?
Async calendar etiquette is the set of shared habits a remote team uses to signal availability, protect focus time, and schedule meetings without forcing people to be online at the same moment. Without it, a shared calendar turns into a free-for-all where anyone can drop a 30-minute hold on someone else's morning, regardless of time zone or workload.
Remote team scheduling breaks down for a predictable reason: a calendar app shows blocks of time, not context. It doesn't show that the block at 7 a.m. for one teammate is 9 p.m. for another, or that the "quick sync" conflicts with someone's only two hours of deep work that day. Teams that write down a few rules — and actually enforce them — cut down on the back-and-forth rescheduling that eats into the day. For background on why reminders alone don't solve this, see the guide on notification blindness.
How should you write a meeting invite so it doesn't waste everyone's time?
A good meeting invite answers three questions before anyone clicks accept: why this meeting exists, what's expected of each attendee, and what happens if someone can't make it. Invites that just say "Sync" with no agenda force attendees to guess, which is how optional meetings quietly become mandatory.
Meeting invite best practices for distributed teams include a one-line purpose in the title, a linked doc for pre-reading, and an explicit decision on whether the meeting is sync-required or can be resolved async instead. GitLab's public communication guidelines, built for an all-remote company, put it directly: GitLab frames its communication handbook around written-first collaboration precisely because undocumented meetings don't scale across time zones. If you're still building the habit of prepping before you join, the five-minute meeting checklist covers what to confirm before every call.
What's the right way to block time on a shared calendar?
Block time the same way you'd block a conference room: with a clear label, an honest status, and a block that matches how long the work actually takes. A calendar entry titled "Busy" with no context gets overridden by the next person who needs a slot; a block titled "Focus: client proposal draft, DND" rarely does.
Three habits make blocks stick. First, set working hours and a working location in your calendar settings so invites outside your day are flagged automatically — Google's own documentation on working hours explains how this signals unavailability to anyone trying to book you. Second, leave buffer between calls instead of scheduling them edge to edge; the guide to back-to-back meeting buffers covers how little slack most calendars actually have. Third, run a short weekly pass to catch blocks that no longer reflect reality — the ten-minute weekly calendar review is built for exactly this.
| Habit | Gets overridden | Holds up |
|---|---|---|
| Block title | "Busy" | "Focus: Q3 deck, do not book" |
| Buffer between calls | None, back-to-back | 10-15 min pad on each side |
| Working hours set | Not configured | Enabled, auto-flags off-hours invites |
| Recurring hold review | Never revisited | Checked weekly, dropped if stale |
How do you handle time zones without creating confusion?
Always display the meeting time in a format tied to each invitee's local clock, never a single reference zone written in the title. "3pm EST" in an invite title is only correct for whoever set the meeting; everyone else has to do mental math, and mental math is where double-bookings and no-shows come from.
Calendar apps convert times automatically when invites are sent through Google Calendar, Outlook, or iCloud — the problem shows up when someone manually types a time into an event description instead of using the actual date/time fields. That's also the usual cause of the issue covered in why calendar reminders show the wrong time zone. For teams juggling a work calendar against a personal one across regions, keeping both in a single alarm list instead of two disconnected apps removes a layer of error — Pealo's work and personal calendar setup is built around that exact problem.
When should a meeting actually be an async message instead?
Default to async whenever the goal is sharing information, gathering input on a document, or making a decision that doesn't require real-time debate. A meeting is justified when the topic needs live back-and-forth, there's a conflict to work through, or the group genuinely benefits from everyone reacting in the same moment.
Before sending an invite, a useful filter is whether a written update, a recorded loom, or a comment thread would get the same outcome without pulling six people off their work blocks at once. Teams that get this right still keep a smaller set of calendars — for recurring standups, deadlines, and the handful of calls that truly need everyone live — and rely on alarms rather than silent notifications to make sure those don't get missed. The guide on why people keep missing meetings breaks down why notification-only reminders fail quietly on a muted phone, and why an actual alarm app like Pealo's iPhone alarm rings through Focus and Silent mode when the stakes are higher than a routine sync.
Alarms your calendar sets for you
Connect Google, Outlook or iCloud. Pealo arms a real alarm before every event.
Download on the App Store