Create a Calendar Rule for Declining or Releasing Team Time

Separate the three decisions

A decline means you will not attend an invitation. It does not, by itself, mean the event is cancelled for everyone. Use it when the meeting still makes sense but your own availability has changed. If your absence affects the purpose of the meeting, tell the organizer rather than assuming a decline communicates the full situation.

A cancellation means the shared event will not go ahead as planned. The person responsible for organizing it should make that call, after checking whether the group still needs the meeting or can continue without them. A release is different again: it removes a hold on time that was reserved for a task, focus period, or possible work session. The team should agree whether those blocks are personal or shared before treating them as available to others.

Agree on a release threshold

Choose a simple test that colleagues can apply consistently. For example: release a block when its stated purpose is complete, no longer needed, or cannot happen in the reserved window. If the work is only delayed, keep the time only when there is a clear reason to protect it; otherwise, release it and arrange a new time separately.

Set expectations for blocks that are hard to interpret. A title such as “Project work” may not tell colleagues whether the time is flexible. Encourage people to include a short purpose or a note about whether the block is open for others to use. Do not assume that an unlabelled or private block is available simply because it appears unused.

Make cancellation a deliberate group decision

Before cancelling a meeting, ask whether the goal can still be met, whether attendees need the time for another task, and whether a replacement is actually required. If the meeting is no longer useful, cancel it rather than leaving an obsolete invitation on everyone’s calendar. If only one attendee cannot make it, a decline and a note to the organizer may be enough.

For a recurring event, clarify whether the change applies to one occurrence or future meetings as well. A team rule should tell organizers to state the scope plainly in their notice. When the calendar controls available to you do not make the intended scope clear, pause and check the event details or ask an authorized colleague rather than risking a broader change.

Notify people with the information they need

A useful notice says what is changing, which date and time are affected, and whether anyone needs to do something next. Send it to the attendees or colleagues who rely on the block, using the event’s normal communication method when appropriate. Avoid assuming that a calendar change alone will reach everyone’s attention in time.

Keep the explanation brief and factual. You do not need to share private details to explain that a meeting is cancelled or a work block is released. If the group should reconvene, name the next step—such as proposing another time—without implying that a replacement has already been scheduled.

Example: “The project review on [date] at [time] is cancelled because the review is not ready. Please release the time. I’ll suggest a new slot after [next step].”
For a personal decline: “I can’t attend [event] on [date]. The meeting can still go ahead; please contact me about [specific input] if needed.”

Use a small checklist before changing time

A consistent pause prevents accidental cancellations and silent releases. Before acting, answer these questions:

• Is this my invitation to decline, a shared event to cancel, or a block to release?
• Does the decision affect one time slot or a recurring series?
• Who will lose the time, and who needs a direct update?
• Have I stated whether there is a next step or replacement plan?

Confirm the change reached the right people

After making the calendar change, review the event or block from your calendar and check that the date, time, and intended scope match the decision. For a shared event, confirm that the cancellation or update is reflected in the event information. For a personal decline, verify that you declined the invitation rather than removing or cancelling it for others.

Then check that your notice went to the people who need it and that any follow-up is clear. If someone still treats a released slot as reserved, clarify directly; calendars and notifications do not guarantee that every colleague has seen an update. BITTU Mail includes calendar features, while available controls can depend on role, plan, and provisioning. Follow the controls available to your account, and ask an authorized workspace administrator if you cannot make a change you are responsible for.