Absences
Absences keep the schedule honest. They explain why people are unavailable and make sure approved time away is visible to planners and public viewers where appropriate.
Roster | Mon 17Covered8 / 8 | Tue 181 open7 / 8 | Wed 19Covered8 / 8 | Thu 202 open6 / 8 | Fri 21Covered8 / 8 |
|---|---|---|---|---|---|
| 1st Shift | 1st Shift | 1st Shift | 1st Shift | 1st Shift | |
Team Alpha 4shown4 assigned | |||||
Alex Morgan | SITE-A | FIELD | SITE-A | STDBY | OFF |
Jordan Lee | FIELD | SITE-A | FIELD | SITE-A | OFF |
Taylor Reed | SUPPORT | ABS | SUPPORT | FIELD | SITE-A |
Casey Brooks | STDBY | SUPPORT | SITE-A | — | SUPPORT |
Use this guide when you need to
- Track requests, approvals, balances, calendar visibility, and history.
- Make approved time away visible to schedulers before the week is built.
- Use absence roles and settings so unavailable members are represented clearly.
Jump to section
Purpose
Capture unavailability early enough to change the plan
- Capture time-away requests and status.
- Keep planners informed about real availability before building a week.
- Support both admin tracking and schedule clarity.
Workflow
Move absence information into the schedule before coverage is built
- Record or review requests as early as possible.
- Approve or deny them with enough lead time for planning.
- Confirm balances and settings for the relevant absence types.
- Check the weekly schedule after approvals so the coverage picture is still realistic.
Guidance
Absence data is valuable when it changes planning decisions
Requests, approvals, balances, and history matter most when they make availability visible before someone is assigned to a required role.
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.
Planning timeline
The earlier an approved absence enters the workspace, the cheaper it is to solve
An absence known before Auto-fill can be handled as an input. The same absence discovered after publication becomes a rework problem that may affect multiple people. The value of the absence workflow is not just recordkeeping—it is moving that information earlier in the planning cycle.
Practical notes
Absence practices that reduce last-minute coverage gaps
- 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.
Questions
Questions about availability before the schedule is built
How approved absences affect Auto-fill, when to enter them, and what viewers should actually see.
Does Auto-fill take approved leave and absences into account?
Yes. Approved absence information changes who should be considered available for the schedule. Capturing it before Auto-fill runs prevents the scheduler from building a first draft around someone who is already known to be unavailable.
What kinds of absences can I track?
RoleSchedule can support the absence types your organization uses, such as leave, pass, sick, training, appointments, or other non-availability categories. The important part is using categories that make planning clearer rather than creating unnecessary administrative noise.
Should I add an absence before or after the schedule is built?
As early as possible. An absence entered before the schedule is generated becomes a planning input; the same information discovered after publishing becomes rework that may affect several other assignments.
Do public schedules have to show why someone is absent?
No. Public pages should expose only the schedule context viewers actually need. Administrative absence detail can remain inside the protected workspace while the published schedule communicates the resulting availability or assignment state appropriately.