Bulk Documentation
Product referencePeople and trainingPeople

Manage shifts

Define reusable work patterns — working days, start and end times, breaks, and multi-week rotations — that you assign to employees and that drive absence day-counting.

A shift in Bulk is a reusable work pattern for a site: it records which days of the week are working days, the start and end times for each day, any unpaid break, and how the pattern repeats over a rotation cycle of one to six weeks. You build shifts once, then assign them to employees so Bulk knows each person's normal working days.

Shifts are the foundation for two other People features. When you assign a shift to an employee, it appears on their record as their Shift, and when someone logs an absence Bulk counts only the working days in that employee's shift pattern — a five-day holiday that overlaps two rest days is recorded as the correct number of working days off, not a flat calendar count.

Shifts belong to a single site (in Bulk, an "entity" — one plant or facility). The shifts you create on one site are not shared with another, so each location manages its own working patterns.

Where to find shifts

Open Settings, choose People, then select Shifts. The page opens at /settings/people/shifts and shows a two-panel layout: a list of every shift on the left and the details of the selected shift on the right.

The Shifts settings page showing a list of shifts on the left and the selected shift's pattern details on the right.
Shifts open in a two-panel layout — the list of shifts on the left, the selected shift's pattern on the right.

people.shifts-01

Before you start

Managing shifts is permission-controlled:

  • View shifts requires the shifts.view permission.
  • Create, edit, delete, and reorder shifts require shifts.create, shifts.update, and shifts.delete respectively.

By default these permissions are granted to the Super user, Entity admin, Manager, and People roles. If the Shifts item does not appear under Settings, People, ask an administrator to grant your role the shift permissions.

What a shift contains

Each shift is made up of the following:

  • Name — a plain label such as "Day Shift" or "Night Shift".
  • Code — a short uppercase reference. Bulk generates the code automatically from the name (for example, "Day Shift" becomes DAY_SHIFT) and keeps it unique within the site, so you never type it yourself.
  • Color — a color used for the dot beside the shift and in downstream views.
  • Rotation length — how many weeks the pattern runs before it repeats, from one to six.
  • A weekly schedule for each week in the rotation — for every day, whether it is a working day or a day off, its start and end time, and an optional unpaid break in minutes.

Codes are generated for you

The shift code is derived from the name and shown as a read-only field. Rename a shift and the code updates to match. You cannot type a code by hand.

Create a shift

  1. Select New Shift in the top-right corner. The Create Shift dialog opens.
  2. Enter a Name. Bulk fills in the code for you as you type.
  3. Choose a Color.
  4. Configure the Work Pattern:
    • Set the Rotation Length — for a standard fixed week, leave it at "1 week rotation".
    • Set the Pattern Start Date. This is the reference date that aligns Week 1 of the rotation; for a single-week pattern it has no visible effect, but for multi-week rotations it decides which calendar week counts as Week 1.
    • In the day grid, toggle each day On or Off, and set the start time, end time, and break (in minutes) for the working days. New shifts start with Monday to Friday on and the weekend off, at 06:00 to 14:00 with a 30-minute break.
    • To apply the same hours to every day in a week quickly, use the Same time for this week row: enter a start time, end time, and break, then select Apply.
  5. Select Create Shift. The new shift is added to the list and selected so you can review it.

A shift must have at least one working day, and every time must be in 24-hour HH:MM form (for example, 06:00 or 14:30). If the end time is earlier than the start time, Bulk treats the shift as running overnight into the next day.

The Create Shift dialog showing name, color, rotation length, and the seven-day work-pattern grid.
Build a shift's working days, times, and breaks in the Work Pattern grid.

people.shifts-02

Set up a rotating shift

For shifts that change from week to week — such as a crew that works days one week and nights the next — increase the Rotation Length to between two and six weeks. Each week gets its own tab (for example, "Week 1" and "Week 2"), with a working-day count beside each tab so you can see the balance at a glance. Configure the days for each week independently.

The Pattern Start Date anchors the cycle: Bulk uses it to work out which week of your rotation applies to any given calendar date, so the same rotation stays correctly phased into the future.

A shift's rotation pattern editor showing Week 1 and Week 2 tabs for a two-week rotating pattern.
Rotations of two to six weeks get a tab per week; the Pattern Start Date aligns Week 1.

people.shifts-03

Review and edit a shift

Select any shift in the left list to open it on the right. The detail panel shows:

  • The shift's working hours as a time label (or "Varies by day" when the times differ across the pattern).
  • Three quick figures: Duration (the length of a working day, start to end), Working (working hours after the break is deducted), and In Schedules.
  • An Active or Inactive status and a plain-language pattern summary such as "Weekly: 5 on, 2 off".
  • The Rotation Pattern editor with the pattern's start date.

To change the name or color, select Edit, adjust the fields, and select Save Changes. Changes you make in the rotation pattern — toggling a day, adjusting a time, or changing the rotation length — save automatically as you make them, so there is no separate save step for the pattern.

Reorder and delete shifts

Hover over a shift in the list to reveal its controls. Use the up and down carets to change the order shifts appear in, and the trash icon to delete a shift. Deleting asks you to confirm, because it cannot be undone.

Reassign employees before deleting a shift

Deleting a shift does not check whether employees are assigned to it. If you delete a shift that employees still use as their default, Bulk can no longer count their absence days and absence logging for those people fails until you assign them a valid shift. Move employees to another shift first, then delete.

Example: shift patterns at Leeds Fabrication Plant

Granite Peak Manufacturing runs its Leeds Fabrication Plant across a day team and a night team, plus a rotating crew on the press line.

  1. Dana, the site owner, opens Settings, People, Shifts and selects New Shift.
  2. She creates DOCS Day Shift: a one-week rotation with Monday to Friday on, 06:00 to 14:00, and a 30-minute break. The detail panel then shows a Duration of 8h, Working hours of 7h 30m, and the summary "Weekly: 5 on, 2 off".
  3. She adds DOCS Night Shift: Monday to Friday, 22:00 to 06:00. Because the end time is earlier than the start time, Bulk records it as an overnight shift.
  4. For the press line she creates DOCS Continental, a two-week rotation: Week 1 works four long days, Week 2 works three, so the two teams alternate coverage without gaps.
  5. Dana then assigns each employee their shift from the employee record, so absence requests and working-day counts follow the right pattern.

Every record she creates is prefixed DOCS and belongs only to the Granite Peak documentation tenant.

What you can expect

Once saved, a shift appears in the list for the site and becomes available to assign to employees. From that point on, the shift's working-day pattern is what Bulk uses when it counts absence days for anyone assigned to it, and the shift shows on each assigned employee's record.

Limitations and feature state

Shift management is generally available. Keep these points in mind:

  • In Schedules always shows 0. The detail panel includes an "In Schedules" figure, but it is not yet connected to live scheduling data and currently reads zero for every shift. Do not rely on it to tell whether a shift is in use.
  • Delete is not blocked by assignments. There is no dependency check before deletion, so it is your responsibility to reassign employees first (see the warning above).
  • Shifts are site-specific. A shift created on one site is not visible on another. Set up the patterns each facility needs on that facility.
  • Codes are automatic. You cannot set a shift code manually; it is always generated from the name.

Troubleshooting

  • "Employee has no default shift assigned" when logging an absence. Absence day-counting needs the employee to have a shift. Open the employee's record and assign a shift, then retry the absence. See Record an absence.
  • Absence logging fails with a "shift not found" message. The employee's assigned shift has been deleted or belongs to another site. Reassign a valid shift for the current site on the employee's record.
  • The Shifts item is missing under Settings, People. Your role lacks the shifts.view permission. Ask an administrator to grant the shift permissions.