Part-time and custom work schedules
Ask AI
Working days and hours per person, per-date leave counting and how part-time leave amounts are scaled
A work schedule is which weekdays someone works and how many hours, effective from a date. Leave counting and timesheet quotas resolve it per date; part-time leave amounts read its weekly hours.
What a schedule is
A schedule is a slice effective from a date: working weekdays plus hours. The editor's Work model picks the hours shape - Fixed takes hours per selected weekday and sums them into the weekly total, Flexible takes a weekly target split evenly. A per-day map must cover every working day.
Schedules are a history, not a single row - a change adds a slice that takes over from its effective date, and a second save on the same date replaces that slice. The Schedule tab carries the slice in force and the full version history: My profile → Schedule in the account menu for your own, People → Teams → [team] → [person] → Schedule for a report, People → People → [person] → Schedule for an admin. Only an admin sees the Change schedule form.
How it changes leave counting
Each date in a request resolves the slice in force on that date, so a request that crosses a schedule change counts the days on either side under the right one. A leave type's Days counted decides whether the schedule applies: Working days skips the person's days off and their public holidays, Calendar days counts every day of the request.
How part-time amounts are scaled
An allowance's Part-timers setting decides what a shorter week does to the amount: Same amount for everyone, Scaled by contract hours, Scaled by contract hours, counted in hours, or Counted in hours below a weekly threshold. Scaling uses the contracted weekly hours averaged over the part of the leave year the person is employed, against the allowance's full-time week, and rounds up to a whole day. The schedule form's FTE field is not an input to it.
Nothing is posted when a schedule changes: the amount is worked out from the schedule history whenever it is read. Saving a schedule first freezes what earlier leave years carry over, so a change never reaches back into a year that is over.
Expected timesheet hours
A day's scheduled hours come from the slice in force that day: the per-day map if one is set, otherwise the weekly total split evenly across the working days. Expected hours are those minutes minus approved leave; a non-working day, a public holiday or a date before the employment start expects 0.
Worked example
Marta's Leave seniority is over 10 years of total service, so Northlake's Polish preset gives her 26 days of annual leave, scaled by contract hours against a 40-hour week. From 1 September 2026 she moves to Monday-Thursday at 8 hours a day: a 32-hour week.
Her leave type counts working days, so a Monday-to-Friday request after that date charges 4 days, not 5: Friday is no longer a working day, and drops out like a weekend.
Her amount for 2026 also moves. Over the year she averages
(243 days × 40 h + 122 days × 32 h) / 365 = 37.33 h a week, 93.3% of full time, so
26 × 0.933 = 24.26, rounded up to 25 days. Her Time off tab shows it as soon as the
schedule is saved; 2027 starts from a full year at 32 hours.