A calendar block can look like a meeting even when nobody has agreed to attend. That confusion can leave colleagues protecting time for a discussion that may never happen—or assuming a decision has already been made. Treat a tentative hold as a planning signal, not an invitation that settles the details. A clear title, honest description and review deadline help everyone understand what is known, what is still pending and what action to take. The same conventions work whether your team coordinates in a shared workspace or communicates the hold directly.
The useful bits
- Put “HOLD” or “TENTATIVE” at the start of a provisional event title.
- Record the purpose, decision-maker and deadline for confirming or releasing the time.
- Review open holds regularly and update or remove them when their status changes.
Make the title carry the status
Use a consistent label at the beginning of the title, such as “HOLD — planning discussion” or “TENTATIVE — project review.” Put the subject after the label so a colleague scanning a busy calendar can tell immediately that the event is not settled. Avoid titles such as “Project review” when the time is only being reserved; they read like a confirmed commitment.
Keep the label until the meeting is agreed. When it is confirmed, replace it with a direct event name. If the plan is dropped, remove the hold rather than leaving a stale block behind. A short, shared naming convention is more useful than relying on colleagues to infer intent from color or a private note.
Explain what is—and is not—decided
In the description, state why the time is being held and what remains undecided. For example, the topic may be known while the attendees, format or final time are still pending. Name who will confirm the plan and give a date or clear checkpoint for reviewing it. This prevents a tentative block from silently becoming permanent.
Do not list people as though they have accepted unless they have actually agreed. If you need to reserve time for a group, tell the relevant people separately that the block is provisional and explain whether they should protect the time or simply wait for confirmation. A calendar entry alone may not make that expectation clear.
Choose the smallest useful hold
Reserve only the time and people needed for planning. If a discussion might take an hour but could be handled in a shorter slot, avoid blocking a large group for the maximum possible duration before the scope is known. Where the calendar allows you to indicate availability or tentative status, use the option that accurately reflects your team’s convention; do not assume every calendar presents that status the same way.
Be especially careful with recurring holds. A series can occupy many people’s calendars long after the original uncertainty has passed. If you only need to protect one possible date, create a single hold rather than a recurring event.
Keep the hold visible to the right people
A hold is useful only if affected colleagues can interpret it. Use the calendar your team relies on, and make sure the title and description are understandable to its intended viewers. Avoid putting sensitive details in a broadly visible event; a neutral subject and a direct message to the necessary participants may be more appropriate.
BITTU Mail includes calendar functionality, and workspace calendars are available within BITTU Mail’s workspace offering. What actions are available can depend on role, plan and provisioning state. If your account does not offer the calendar control you need, follow your organization’s established process rather than assuming a setting exists or that another person can see the block.
Review before the deadline
At the stated checkpoint, decide among three outcomes: confirm the event, move the hold while explaining why, or release it. If the meeting is confirmed, update the title and details and communicate the agreed plan to participants. If the time changes, make the old and new status clear so nobody protects both slots by mistake.
For a team, assign one person to own each hold. That person should check unresolved holds during a regular planning review and remove blocks that no longer serve a purpose. A calendar entry without an owner or review point is easy to forget, especially when the original organizer becomes unavailable.
A quick check before you save
Use this checklist for each provisional block. Then check the calendar view colleagues actually use: the label should be visible, the purpose and review point should be understandable, and the time should appear only where intended. Ask a colleague who needs the information to confirm they can distinguish the hold from a confirmed event. That verifies the communication, not anyone’s agreement to attend.
- Does the title begin with HOLD or TENTATIVE?
- Does the description say what is pending and who will decide?
- Is there a specific review date or checkpoint?
- Have you told affected colleagues what to do while the plan is unsettled?
- Is the hold limited to the necessary time and people?
HOLD — [topic] Purpose: Reserve time to discuss [specific decision]. Pending: [attendees, format or other unresolved detail]. Owner: [person responsible for confirming]. Review by: [date or planning checkpoint]. Until confirmed: Treat this as provisional, not an agreed meeting.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction