Build and publish schedules
Create drafts, resolve conflicts, and publish immutable weekly versions.
Build the draft
Open Schedule, choose one Location and workweek, and use Add to create Shifts.
The ⋯ menu reuses work you already did: Import shifts from CSV, Copy last week, Save as template, Apply pattern, Auto-assign open shifts, and Apply a saved Schedule Template such as Typical service week. Manage teams is where you manage the Location's Schedule Teams.
Add shifts creates several Shifts at once: pick one or more days, a time range, a Position, and any number of Workers, and jooling creates one Shift per worker and day. Leave the workers empty to create Open Shifts that workers can request. The dialog offers Apply time block and Apply shift template shortcuts. Overnight Shifts are supported but belong to one schedule day.
Open an existing Shift to edit its day, time range, Position, Worker, and note. More options holds tags, tasks, and repeat options, which copy a Shift into later weeks.
Filters narrow the grid by Position, schedule state, Worker Group, Shift Tag, or Time Block. The same popover switches the grid between Compact and Comfortable density and shows the position color key.
Resolve conflicts
jooling flags overlaps, approved time off, Unavailability, missing Location or Position access, too few hours of rest between shifts, and long runs of consecutive workdays. Conflicts show a warning chip and stay on the grid — you can still save or publish with them, so review the grid before publishing.
Unavailability is a hard constraint: scheduling through one asks for an override reason in the shift dialog. Work Preferences are advisory only. Open Shifts are staffing gaps, not conflicts — workers can request them after publication.
Publish
Select Publish to open Publish this draft?. It shows how many conflicts remain and, when you are republishing a week, lists each change since the last version. Select Publish now and the whole selection is published at once. Publication creates the immutable Schedule Version, makes it the current source of truth, records delivery, and queues notifications.
Change a published week
Editing a published week begins a private Successor Draft copied from the current version — workers see nothing until you publish. Publication calculates the differences and creates a new version while history stays intact. A new or materially changed Shift inside the Notice Window requires explicit Shift Acceptance from the affected Worker; acknowledging that they saw the schedule is separate.