Schedules

Plan and publish employee shifts — open shifts and claiming, recurrence, bulk tools, copy/clear week, the team matrix, the department-head review workflow, and an optional org default schedule.

What is scheduling?

The Schedules module plans who works when. Managers create shifts, assign them (or leave them open for anyone eligible to claim), and publish a schedule so employees can see it. Shift times are interpreted in the organization's timezone.


Anatomy of a shift

FieldDescription
TitleA label for the shift
Start / End timeDefines the shift window (org timezone)
Break durationUnpaid break minutes, deducted from net hours
Assignee (optional)The employee working it — no assignee = an OPEN shift anyone eligible can claim
Department (optional)Ties the shift to a department
TypeA category for the shift
RecurrenceA recurrence rule for repeating shifts

Shift statuses

StatusMeaning
ScheduledPlanned, not yet started
In progressCurrently underway
CompletedFinished
CancelledCalled off
No-showAssignee didn't show up

Creating shifts

RoleCan create
Administrator / ExecutiveShifts for any employee
Department HeadShifts only for users in their department
EmployeeCannot create (but can claim open shifts)

Beyond creating one shift at a time, managers have:

ToolWhat it does
Bulk createCreate many shifts at once
Bulk updateEdit many shifts at once
Copy weekDuplicate one week's shifts into another
Clear weekRemove a week's shifts

When Copy week is limited to chosen people, only those people's shifts are copied. Choosing no one copies nothing ("No employees selected to copy"); it never falls back to copying everyone. A department head can choose only people in their departments. When the copy sends notifications, only the people who actually received new shifts are emailed.

Timezone. Start and end times are interpreted in the organization's timezone, so everyone reads the same schedule regardless of where they open it.

Open shifts and claiming

A shift with no assignee is an open shift. Any eligible user can claim it.

  • If the shift is tied to a department, the claimant must be in that department.
  • Only shifts in a published week can be claimed. An unpublished week is still a draft, and its open shifts are refused with 409 "This shift is not open for claiming yet".
  • A shift can be claimed only before it starts. Once it has started, claiming is refused with 409 "This shift has already started and can no longer be claimed".
  • Claiming uses an optimistic lock: if two people try to claim the same shift, the second one gets a 409 "already claimed".
Why a lock? Open shifts are first-come, first-served. The optimistic lock guarantees exactly one person ends up with the shift even if two tap "Claim" at the same moment.

Publishing a schedule

Employees see a schedule only once it's published. Until then, the week is hidden from regular employees.

ActionWhoNotes
PublishAdministrator / Executive onlyPublish 1–4 weeks at a time; optionally email employees
UnpublishAdministrator / ExecutiveHides a previously published week again

Department-head review workflow

Department heads cannot publish. Instead, a department head can "Submit for review", which notifies Administrators/Executives to review and publish on their behalf.

Why a review step? It lets department heads own day-to-day planning while keeping the act of making a schedule official — and emailing it to staff — in the hands of admins.

Emailing a schedule

Administrators and executives can send the current week to employees with Email Schedule in the schedule's menu. It goes to everyone with a shift that week.

When a department head emails a schedule (through BookYourPTO Intelligence or the AI connector), it reaches only people in the departments they belong to or manage. Choosing a department outside their own is refused, and choosing a department with no scheduled people sends nothing rather than emailing the whole organization.


Recurring shifts

Repeating shifts are defined by a recurrence rule on the shift, so a regular pattern (for example, the same weekday shift each week) is generated automatically rather than entered by hand.


Optional org default schedule

An organization can enable a default schedule with default start/end times and a break duration.

  • When enabled, it auto-generates this week's business-day shifts for all active employees.
  • When disabled, it removes those auto-generated shifts from this week onward.

This is a quick way to give a standard-hours workforce a baseline schedule without building each week manually.


The schedule interface

  • Team matrix view — an employee × day grid for the selected week
  • Open-shift cells that eligible employees can claim
  • Publish / Unpublish controls (Admin/Exec)
  • Copy week to roll a week forward
  • An export page for the schedule

Visibility

Who can see a schedule is governed by the time-tracking visibility settings (see Overtime & Pay-Period Lockdown):

  • Administrators and Executives always see everything.
  • Department Heads always see their own department.
  • Employees see schedules based on the "allow viewing department schedules" (default on) and "allow viewing all schedules" (default off) settings — and only weeks that have been published.

Troubleshooting

SymptomCauseFix
"Already claimed" (409)Someone else claimed the open shift firstPick another open shift
Can't claim a department shiftYou're not in that departmentOnly members of the shift's department can claim it
"This shift is not open for claiming yet" (409)The shift's week has not been publishedWait until the week is published
"This shift has already started" (409)Open shifts can be claimed only before they startPick a future open shift
Copy week created nothingNo people were chosen to copyChoose the people to copy, or copy the whole week
Can't publish a scheduleYou're a Department HeadUse Submit for review — Admin/Exec publishes
Can't see a scheduleThe week isn't published yet, or visibility settings are off for your roleWait for publishing or ask an admin to enable schedule visibility
Default-schedule shifts disappeared this weekThe org default schedule was disabledAuto-generated shifts are removed from this week onward when it's turned off