Intermittent leave, counted to the entitlement
Protected leave can be taken in pieces, an hour for an appointment, a day for a flare, each drawn against a fixed entitlement. Workday deducts each piece from the leave balance. The register of every worker’s remaining hours on any date, with its pieces, is still yours to build.
◆ Continuous leave, and the case that is notone interval versus many small usages.
A continuous leave is one interval: out on a date, back on a date, and the workers-on-leave page models it cleanly. Intermittent leave is the opposite shape. An hour for a recurring appointment, a day for a flare, taken in pieces across months, each piece drawn against a fixed entitlement, usually 480 hours in a rolling 12-month window.
Delivered absence does part of this. Intermittent time off linked to a leave type is deducted from both the time off plan balance and the leave entitlement balance, and Workday’s FMLA example measures the year forward from the first day of leave (status October 2026). What it does not hand you is one register: every worker’s remaining hours on a chosen date, with the pieces behind each figure, practitioner-observed.
◆ The register, workedentitlement, used, remaining, exhaustion flagged.
| Worker | Entitlement | Used, rolling 12mo | Remaining |
|---|---|---|---|
| W-1102 | 480 | 468 | 12 |
| W-0847 | 480 | 320 | 160 |
| W-1339 | 480 | 88 | 392 |
| W-0521 | 480 | 0 | 480 |
Each row is one subtraction: entitlement minus used equals remaining, checked by the same battery that ties the money pages. W-1102, at 12 hours remaining, is the row that matters: a worker nearly out of protected leave, and the conversation a manager must have before the next request, not after. The used column is the sum of many intermittent pieces over the trailing year, not a calendar total. Sample values are illustrative, never client data.
◆ The owned answerusage events, a rolling window, a defensible flag.
Model each piece as a usage event, then compute the used total with a window function over the trailing twelve months, per worker, on any date. Remaining is the entitlement minus that rolling sum. The near-exhaustion flag becomes a filter, and the audit answer, why did this worker have this much protected leave on that date, is a query with the pieces listed beneath it.
-- protected leave used, rolling 12 months, per worker, as of a date
SELECT worker_key,
480 AS entitlement_hours,
SUM(hours) AS used_rolling_12mo,
480 - SUM(hours) AS remaining
FROM fct_absence_event
WHERE leave_type = 'protected_intermittent'
AND event_date > DATE '2026-05-31' - INTERVAL '12' MONTH
AND event_date <= DATE '2026-05-31'
GROUP BY 1 ORDER BY 4
The usage events are rows on the absence star; the rolling window is a date filter over them.
The same rolling-window discipline the turnover denominator and the hours lookback use, applied to a statutory entitlement. A policy that looks back twelve months from each request needs the backward window this query uses, not the forward year in Workday’s example. Across every worker and any past date, that answer belongs in a model you own.
- FMLA
- The United States Family and Medical Leave Act and similar protections that grant leave entitlement.
- intermittent leave
- Protected leave taken in pieces rather than one continuous interval.
- entitlement
- The capped protected leave a worker is granted, often 480 hours.
- rolling 12-month
- A window ending on the query date, not the calendar year.
- usage event
- One dated piece of leave taken, drawn against the entitlement.
- exhaustion
- Reaching the entitlement cap, after which protection may not apply.
- continuous leave
- A single leave interval with one start and one return.
- window function
- Database math over a sliding set of rows, here the trailing year.
- practitioner-observed
- Seen by absence teams in the field, not stated in Workday’s documentation.