Skip to main content

Update availability for scheduling

Availability describes a window when a person may be proposed. It is neither an assignment nor approved leave.

Before you start​

Check the person, organization and week. Declared availability is required only when your planning mode uses it; the mode without declarations retains other constraints.

Steps​

  1. Open the availability workflow accessible to your profile and display the intended period.
  2. Enter or correct the person’s windows, checking dates and times.
  3. Save and, if required by the workflow, submit availability through the authorized action.
  4. Read the saved windows and separately review approved absences and commitments before generation.

Example and expected result​

Situation : Camille is available Monday from 8 to 12. Your organization uses declared availability for this workflow.

Actions : Choose Camille and the correct week, enter the known window and reread the saved information. When reusing a week, check every target date before confirming.

Expected result : The window appears in the intended week. Requests in another period still require the scheduler to review data and compatibility.

Limits : Availability is neither an assignment nor leave. A mode without declared availability uses different preparation; do not invent windows to simulate it.

If something goes wrong​

Do not counter approved leave by adding contradictory availability. For a missing candidate, review mode, skills, active status and conflicts. Collective actions or availability imports can be used only when actually offered; this guide promises no universal bulk-entry feature.

Continue​