A good calendar title tells people what they’ll do and what it’s about: “Decide: May launch date,” “Workshop: billing flow,” or “Unblock: analytics handoff.” The title should still make sense when somebody reads it on their phone three minutes before the call.

This is a step up from “Quick Sync,” a title that tells you precisely two things, both of which are up for negotiation.

What the calendar would say if it could

  • “Quick Sync” → “We’re trying to find the one person who knows why this is late.” Try “Unblock: analytics handoff,” and name the missing input in the invite.
  • “Touch Base” → “I’d like to know whether anyone has read the document.” Try “Review: onboarding draft by Thursday” in a message with the link and two questions.
  • “Stakeholder Alignment” → “We are about to discover that ‘ready’ has three definitions.” Try “Agree: launch readiness criteria,” with each definition written down before the call.
  • “Brainstorm” → “Please invent something on camera at 9 a.m.” Try “Workshop: three checkout ideas.” Ask for ideas in writing first and spend the live time comparing them.
  • “Weekly Status” → “We will take turns reading the board.” Try a weekly written update with a separate slot for the blocker that needs a decision.

Use the title to test the invitation

Start with a verb that describes the work. Add the specific topic. If the event is for a decision, put the decision in the title and the options in the description. Put preparation and the decision owner in the description, too; the title doesn’t have to carry the whole meeting.

Some meetings are for listening, feedback, or building a relationship. “One-on-one: how the role is going” is honest and useful. You don’t have to invent a deliverable to justify giving somebody your attention.

Decide: keep or cut the May beta? Read before joining: the open issues and the two release options. Leave with: a decision and an owner to share it.

If the most honest verb is “read,” try sending the thing to read.