How do we plan for leave without invading privacy?

Availability visibility gap

Record the availability information needed for planning, not unnecessary personal details. Use authorized calendars or agreed availability records and respect organizational access policies.

What to do now

  1. Collect relevant availability dates
  2. Avoid unnecessary personal explanations
  3. Adjust assignments and handoffs
  4. Confirm coverage for critical responsibilities
Recommended action flow for availability visibility gap: Collect relevant availability dates then Avoid unnecessary personal explanations then Adjust assignments and handoffs then Confirm coverage for critical responsibilities. Escalate when required coverage cannot be provided during an absence.

When to escalate

Escalate when

Required coverage cannot be provided during an absence.

Who decides

The resource owner and project manager

Example

A plan shows a reviewer unavailable for three days without revealing private reasons.

Mistake to avoid

Publishing sensitive leave details in a general project report.

Prevent a repeat

Review overload and bottlenecks at the person or skill level before adding more commitments.

Suggested ApprovedFlow setup

  • Resources
  • Tasks
  • Timesheets

Compare available capacity, assigned task work and actual recorded effort using the enabled resource and timesheet views. See the platform

Related cases

Practice references