Every Workday Time Off Plan enforces a single Unit of Time—either Hours or Days—across all of its accruals, time offs, limits, and validation rules, and Workday performs zero automatic conversion between hours and days. When an external form, integration, or employee submits dailyQuantity: 1 (intending “one full workday”) to an hours-based hourly plan, Workday either books a 1-hour absence—shorting the worker’s paycheck by 7 hours—or rejects the transaction against a Minimum or Increments validation rule.
Because a single employee often holds both Hours-based plans (such as Paid Sick Leave or Hourly Vacation) and Days-based plans (such as Floating Holiday or Jury Duty) simultaneously, any self-service workflow or API integration must inspect plan metadata per absence type and per requested date before constructing a submission payload.
How Workday Configures Unit of Time Across Hourly and Salaried Plans
In Workday Absence Management (Create Time Off Plan / Edit Time Off Plan), Unit of Time sits at the plan header level alongside Track Balance and Position Based:
- Hourly Non-Exempt Populations (
Unit of Time = Hours): Almost universally configured in Hours so approved time-off entries flow cleanly into Workday Time Tracking (Time Calculation Tag) and Workday Payroll /PECIin exact hour increments (1,2,4,8,10, or12hours) matching variable shift lengths and statutory paid-sick-leave accrual formulas (such as 1 hour accrued per 30 hours worked). - Salaried Exempt Populations (
Unit of Time = DaysorHours): Frequently configured in Hours in North America (with4-hour or8-hour increments to comply with FLSA exempt partial-day docking rules) and in Days across EMEA/APAC (0.5-day or1.0-day increments) or on company-wide Floating Holiday plans. - Shared
Time Off TypeRule: If an administrator attaches multipleTime Offdefinitions to the same user-facingTime Off Type(for example, Vacation mapped to both an Exempt Vacation plan and a Non-Exempt Vacation plan), Workday requires that allTime Offobjects sharing aTime Off Typebelong to plans with the sameUnit of Time, and that worker eligibility rules remain mutually exclusive so a worker never deducts from two plans at once (Setup Considerations: Time Off).
Compare the structural settings across the three most common plan archetypes:
| Configuration Attribute | Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick) | Salaried Exempt Hours Plan (e.g., US Exempt Vacation) | Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave) |
|---|---|---|---|
Configuration AttributePlan Unit of Time |
Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick )Hours |
Salaried Exempt Hours Plan (e.g., US Exempt Vacation )Hours |
Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave )Days |
Configuration AttributeDaily Quantity Default |
Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick )Scheduled shift hours (Scheduling Worker - Scheduled Shifts: Shift Hours or Work Schedule Calendar), fallback 8. |
Salaried Exempt Hours Plan (e.g., US Exempt Vacation )Scheduled daily hours from Work Schedule Calendar (8). |
Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave )1 Day. |
Configuration AttributeMinimum & Increments (Edit Time Off -> Validations) |
Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick )Minimum: 1 (or 0.25 / 0.5 hrs), Increments: 0.25 or 1 hr. |
Salaried Exempt Hours Plan (e.g., US Exempt Vacation )Often Minimum: 4 hrs, Increments: 4 hrs (half-day or full-day only). |
Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave )Minimum: 0.5 or 1 Day, Increments: 0.5 or 1 Day. |
Configuration AttributeStart & End Time Settings (Edit Time Off -> Details) |
Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick )Often Display Start and End Time + Calculate Quantity Based on Start and End Time (and Enable Crossing Midnight for night shifts). |
Salaried Exempt Hours Plan (e.g., US Exempt Vacation )Usually unchecked; only dailyQuantity (4 or 8) is entered. |
Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave )Unchecked (Calculate Quantity Based on Start and End Time applies only to Hours plans). |
Configuration AttributeEntry Option |
Hourly Non-Exempt Plan (e.g., Hourly PTO / State Sick )Enter through Time Tracking or Time Off (or Time Off Only). |
Salaried Exempt Hours Plan (e.g., US Exempt Vacation )Enter through Time Off Only. |
Salaried or Company-Wide Days Plan (e.g., Floating Holiday / EMEA Annual Leave )Enter through Time Off Only. |
Five Tenant Rules That Trip Up Partial-Day and Variable-Shift Requests
Even when you know whether a plan tracks Hours or Days, five rules on Edit Time Off Plan and Edit Time Off govern whether Workday accepts or rejects a daily quantity:
1. Daily Quantity Default and Compressed / Variable Schedules
On Edit Time Off Plan -> Calculation tab (or overridden per Time Off on Edit Time Off), Daily Quantity Default pre-populates the units per day:
- A nurse working three 12-hour shifts (
Mon,Tue,Wed) who requests time off on Monday needs12hours, whereas a part-time retail worker scheduled 4 hours on Monday and 8 hours on Friday needs4and8. - Watch out for conditional calculations in
Daily Quantity Default: in standard Workday requests, a conditional calculation can evaluate based on the first day requested unless configured with date-aware schedule or Workday Scheduling shift calculations (Use Scheduling Shiftson worker-based plans). - If the generated default exceeds the worker’s
Maximumvalidation rule for one of the selected dates (for instance,0scheduled hours on a non-working Thursday whenRestrict Requests to Days to Include on Calendaris cleared), Workday raises an immediate validation error.
2. Calculate Quantity Based on Start and End Time
On Edit Time Off -> Details tab (available only when the plan’s Unit of Time is Hours):
- When selected, Workday automatically enforces
Display Start and End TimeandStart and End Time Required, ignoresDaily Quantity Default, and locksDaily Quantityto the exact elapsed duration betweenStart TimeandEnd Time. Workers and API callers cannot overridedailyQuantityindependently of the timestamps. - When not selected (even if
Display Start and End Timeis checked), a worker entering8:00 AMto5:00 PMwith an unpaid 1-hour meal break can manually overrideDaily Quantityfrom9hours down to8hours.
3. Overnight Shifts (Enable Crossing Midnight)
For 3rd-shift warehouse, manufacturing, and hospital staff (e.g., 10:00 PM Thursday to 6:00 AM Friday), enabling Enable Crossing Midnight on Edit Time Off lets the worker submit a single request rather than splitting hours across two calendar dates. Enabling this checkbox automatically selects Display Start and End Time, Start and End Time Required, and Calculate Quantity Based on Start and End Time.
4. Increments, Minimum, and Same-Day Maximum Validations
On Edit Time Off -> Validations tab, administrators add rows to the Data Entry Validation table. Every numeric threshold must match the plan’s Unit of Time:
| Validation Rule | Example Configuration | Exact Default Workday Error Returned on Violation |
|---|---|---|
| Validation RuleIncrements | Example Configuration4 (on an Hours plan) or 0.5 (on a Days plan) |
Exact Default Workday Error Returned on ViolationThe Daily Quantity must be in increments of 4 Hours. |
| Validation RuleMinimum | Example Configuration2 Hours (Individual Time Off Entry) |
Exact Default Workday Error Returned on ViolationThe Daily Quantity cannot be less than 2 Hours. |
| Validation RuleMaximum (Same-Date Total) | Example Configuration8 Hours across All Time Off Entries for Worker for Same Date |
Exact Default Workday Error Returned on ViolationThe total Daily Quantity for [Worker] cannot be more than 8 Hours. A previous Time Off exists for this date. |
| Validation RuleMaximum Unpaid Time Off Units Allowed | Example Configuration0 (paired with Time Off Plan Balance Lower Limit = 0) |
Exact Default Workday Error Returned on ViolationUnpaid time off is not allowed for [Time Off]. The Time Off request for [Date] exceeds the maximum amount of 0 unpaid Hours. |
5. Multi-Position Workers (Position Based vs. Require Position on Time Off Request)
When an hourly worker holds two concurrent jobs (for example, Banquet Server and Front Desk Associate), either a Position Based time-off plan or a worker-based plan with Require Position on Time Off Request checked requires an explicit position reference on every request entry so Workday routes approvals to the right manager and pays the right position rate.
The Mandatory 3-Step REST API Pattern (absenceManagement/v5)
Never hardcode dailyQuantity: 8 or dailyQuantity: 1 in external clients. Workday’s absenceManagement/v5 REST API provides a deterministic three-call sequence under the signed-in employee’s OAuth 2.0 token (Scope: Time Off and Leave):
Step 1: Discover Unit of Time and Timestamp Rules (eligibleAbsenceTypes)
GET /ccx/api/absenceManagement/v5/{tenant}/workers/me/eligibleAbsenceTypes HTTP/1.1
Accept: application/jsonInspect each returned item before rendering the form:
unitOfTime.descriptor:"Hours"or"Days"dailyDefaultQuantity: Plan or time-off fallback quantitydisplayStartAndEndTime,startAndEndTimeRequired,calculateQuantityBasedOnStartAndEndTime,crossingOverMidnightEnabled: Booleans governing whether your UI or tool must prompt forstartandendISO-8601 timestampspositionBasedandposition[]: Whether a position Workday ID is requiredreasonRequiredandabsenceReasons[]: Valid reason IDs if mandatory
Step 2: Resolve Schedule-Aware Quantities Per Date (validTimeOffDates)
Pass the selected timeOffType ID and every requested calendar date:
GET /ccx/api/absenceManagement/v5/{tenant}/workers/me/validTimeOffDates?timeOffType=a1b2c3d4e5f61000123456789abcdef0&date=2026-12-07&date=2026-12-08 HTTP/1.1
Accept: application/jsonWorkday filters out non-working days and public holidays (per the plan’s Days to Include and Holiday Calendar) and returns each valid date with its exact unit and schedule-derived dailyDefaultQuantity:
{
"total": 2,
"data": [
{
"date": "2026-12-07",
"dailyDefaultQuantity": 8,
"unit": { "id": "c45550b7fe3410001111222233334444", "descriptor": "Hours" }
},
{
"date": "2026-12-08",
"dailyDefaultQuantity": 4,
"unit": { "id": "c45550b7fe3410001111222233334444", "descriptor": "Hours" }
}
]
}Step 3: Submit requestTimeOff Matching the Exact Unit and Time Flags
For a partial-day 4-hour afternoon absence on an Hours plan where startAndEndTimeRequired is false (and projected time-off balances cover the 4 hours):
{
"businessProcessParameters": {
"action": {
"id": "d9e4223e446c11de98360015c5e6daf6"
}
},
"days": [
{
"date": "2026-12-07",
"dailyQuantity": 4,
"timeOffType": {
"id": "a1b2c3d4e5f61000123456789abcdef0"
},
"comment": "Afternoon dental appointment"
}
]
}If startAndEndTimeRequired or calculateQuantityBasedOnStartAndEndTime is true, include "start" and "end" timestamps on each day entry so Workday’s duration math matches dailyQuantity.
Admin Verification Checklist Before Launching Self-Service or External Flows
- Run the All Time Offs standard report to audit every active
Time Offalongside its parent plan’sUnit of Time,Entry Option,Increments,Minimum,Maximum, andCrossing Over Midnightsettings. - Run Evaluate Absence Calculation for one hourly worker on a variable shift schedule and one salaried worker to confirm
Daily Quantity Defaultresolves per date as intended. - Verify that any
Time Offobjects sharing a singleTime Off Typebelong to plans with identicalUnit of Timevalues and non-overlapping worker eligibility rules.
Whether employees submit leave from simplified frontline screens built with Kiweely Leaf (coming next) or from conversational AI assistants connected through Kiweely Bridge (coming next, pausing for an out-of-band browser approval card before any write), dynamically reading eligibleAbsenceTypes and validTimeOffDates under the signed-in worker’s own session ensures hours-based and days-based plans never collide.
Frequently asked questions
Does Workday automatically convert Days to Hours if a time-off request submits 1 against an Hours-based plan?
No. Workday never converts daily values to hourly values or hourly values to daily values on a Time Off Plan. Submitting dailyQuantity: 1 to an Hours-based plan literally requests 1 hour of time off—or fails if the Time Off definition enforces a 4-hour Minimum or Increments rule.
Can the same worker be eligible for both an Hours-based plan and a Days-based plan at the same time?
Yes. A single worker frequently holds an Hours-based plan (such as Hourly Paid Sick Leave or PTO) alongside a Days-based plan (such as Floating Holidays, Volunteer Day, or Bereavement). Each individual Time Off Plan, however, must use one single Unit of Time across all its accruals, time offs, and limits.
How does Workday determine Daily Quantity Default when a worker works 4 hours on Monday and 8 hours on Tuesday?
On the Calculation tab of Create/Edit Time Off Plan, if Daily Quantity Default uses a conditional calculation in the Workday UI calendar, the default quantity can anchor to the first day requested unless schedule-based shift calculations or GET /workers/{ID}/validTimeOffDates evaluate each individual date's scheduled hours.
When are start and end timestamps mandatory on a partial-day Workday time-off request?
Start and end timestamps are mandatory when the Time Off definition has Start and End Time Required, Calculate Quantity Based on Start and End Time, or Enable Crossing Midnight selected on Edit Time Off.