Every meeting deserves a written agenda shared in advance, stating the purpose, the decisions needed, and any pre-reading, because attendees who know what is expected can prepare, and those who are not needed can decline without guilt. Invite only people whose input or approval is genuinely required, and consider whether the meeting could be an async document instead; a surprising number of recurring meetings survive purely from habit. State the meeting's time in each attendee's local zone or use a scheduling tool that displays it correctly, and rotate awkward times fairly when a team spans many zones, so the same people are not always waking at dawn.

For recurring meetings, review them quarterly and cancel or shorten those that no longer earn their time. A meeting that exists because it existed last quarter is a cost disguised as a routine, and remote teams, where calendar time is the scarcest resource, should audit it ruthlessly. If an agenda item needs only one or two people, handle it separately rather than holding a whole group hostage to a bilateral discussion.

Camera norms should be explicit and kind: cameras on helps connection and trust, but mandating them for every call penalises people with poor internet, shared living spaces, or fatigue, so agree a norm, such as cameras on for small team meetings and optional for large updates. Mute when not speaking, especially in large calls, and use the raise-hand feature or chat to avoid talking over colleagues, which is far more disruptive on video than in person, where body language signals turn-taking.

The facilitator's job is to keep the meeting on track: open with the purpose and the desired outcome, invite quieter participants by name, summarise decisions as they are made, and end on time even if discussion is unfinished, parking overflow items for async follow-up. Multitasking during calls is visible and corrosive, so keep meetings short, ideally 25 or 50 minutes rather than 30 or 60, giving attendees a real break between calls, and discourage back-to-back scheduling that leaves no time for notes or water.

A meeting without written notes is a meeting that will be repeated, because decisions fade and attendees remember different versions of what was agreed. Assign a note-taker, or rotate the role, and circulate a short summary within a day listing decisions, owners, and deadlines, stored where the whole team can find it later. Action items belong in the project tracker, not in chat messages that scroll away, and the next meeting should open by reviewing the previous actions, which creates gentle accountability without micromanagement.

Good remote meeting etiquette is ultimately respect made visible: respect for time through agendas and punctuality, respect for attention through short, purposeful calls, and respect for colleagues in other zones through fair scheduling and written follow-ups. Teams that practise it find meetings become rarer and better, because people trust that a called meeting will be worth attending, and that trust is the foundation of remote collaboration.

The ultimate test of meeting etiquette is whether people leave a call with more clarity than they entered it with, and whether the meeting's output survives in writing. If your team consistently achieves that, meeting load tends to shrink naturally, because well-run meetings resolve issues instead of generating follow-up meetings about the same topic. Audit your own meetings against that standard once a quarter, and you will find the calendar gradually empties of low-value calls, leaving time for the deep work that remote teams exist to do.

One habit that improves every meeting immediately is starting with a one-sentence purpose statement, spoken aloud, so late joiners and distracted attendees instantly know why they are there. It costs five seconds and prevents the most common meeting failure, which is a group of people unsure what decision they are meant to make.