Explore
HomeFeaturesSolutionsPricingDocsContact
Account
Start freeContact usLogin
Appearance

Purpose

What this page is for

  • Capture time-away requests and status.
  • Keep planners informed about real availability before building a week.
  • Support both admin tracking and schedule clarity.

Workflow

Recommended workflow

  1. Record or review requests as early as possible.
  2. Approve or deny them with enough lead time for planning.
  3. Confirm balances and settings for the relevant absence types.
  4. Check the weekly schedule after approvals so the coverage picture is still realistic.

Detailed guidance

How this page fits into the product

Why absence visibility matters

An absence that is tracked in one part of the app but invisible to the planner is almost worse than no absence system at all. The schedule must reflect who is actually available or the weekly grid becomes misleading.

How requests, balances, and history support each other

Requests are the operational intake. Balances answer whether a request is supported. History provides auditability and context when someone asks why a week looked thin or why a member did not appear eligible for a period.

Absence roles versus absence records

The record says someone is away. The role or schedule label explains that absence clearly when looking at the week. Both pieces matter if you want the schedule to be readable instead of mysterious.

Practical tips

What helps in real use

  • Approve or record absences before weekly scheduling begins whenever possible.
  • If the week looks understaffed, check the absence calendar and history before assuming the scheduler failed.
  • Use clear absence labels so both dashboard and public pages stay interpretable.

Common questions

Frequently asked questions

Why do approved absences matter to scheduling?

Because they change who is actually available to cover required roles during the week.

Should absence information appear on public pages?

Only in the way your workflow needs for visibility. The goal is clarity, not exposing unnecessary admin detail.