Crew Scheduling by Department: From a Four-Person Shop to a Full Plant
The work of scheduling in FabWise scales with the number of different schedules you run, not the number of people running them. A four-person shop on one shift sets up one department. A two-hundred-person plant across three shifts and an office sets up four. The mechanism is identical.
Headcount is the wrong axis
Most scheduling tools price and design around how many people you have. But adding the fiftieth person to a shift that already exists is not work — you put them in the department and their shifts generate like everyone else's.
What actually costs effort is schedule variety: how many genuinely different patterns your operation runs. That number is often small even in large shops, and it is what FabWise asks you to describe.
| Your operation | Departments you set up |
|---|---|
| Four people, one shift, same hours daily | 1 |
| Twenty on the floor, plus an office starting at 8:30 | 2 |
| Two hundred across day, swing, and overnight, plus office | 4 |
| Multiple buildings, each with its own start time | One per distinct schedule |
The two-hundred-person plant is not forty times the setup of the four-person shop. It is four departments instead of one.
The mechanism, at any size
A department is a group of people who work the same hours. In a four-person shop that is usually everybody — one department, often just called Shop. In a plant it is Production Day, Production Swing, Maintenance, Office.
Each department gets one schedule. Choose a standard template — 7:00 to 3:30, 7:30 to 4:00, 8:00 to 5:00, second shift, third shift, four tens — or define your own. Every account starts with the standard set already in place.
Shifts generate from it. FabWise creates each person's individual shift records going forward, for every worker in every department, from that department's schedule. Nobody assigns Tuesday to anybody.
Adding a person is one action at four people and one action at four hundred: put them in the right department. That is the property that makes the model scale.
Shift types keep multiple crews straight
A single-shift operation names one shift type and never thinks about it again. An operation running around the clock names Day, Swing, and Overnight, and points a department at each.
Naming the shift type is what keeps hours attributed correctly when they cross midnight, when a department rotates, or when "Monday" means two different crews — the cases where paper and spreadsheets break first, and the reason multi-shift operations outgrow them earliest. See multi-shift scheduling for that in depth.
When one person doesn't match their department
Every operation has exceptions — somebody comes in an hour early to run the saw, or leaves at 2:00 on Fridays.
A person can carry their own schedule, and when they do it takes precedence over their department's. The department keeps covering everyone else while the exception stays attached to the one person it belongs to.
The precedence order is what matters: the department is the default, the individual is the override. That keeps exceptions from eroding the structure — a shop with thirty people and four exceptions still has departments doing the work for the other twenty-six, and the exception set up in March is still right in November without anyone maintaining it.
Starting small without painting yourself in
A shop that begins with one department and later adds a night crew does not undo anything. Create the second department, give it its own schedule, move the right people in. Everything already set up stays true.
That is the argument for using departments from day one even when you have four people and could plausibly schedule them by hand: the four-person setup is the two-hundred-person setup, with fewer rows.
What the schedule buys you
A schedule is not paperwork — it is the thing that gives every other number meaning.
Without one, a clock-in is a timestamp. With one, FabWise knows a 7:42 clock-in was twelve minutes late, that Thursday's shift never happened, and that the week is short before payroll finds out. Exception review is built on the gap between scheduled and actual, and there is no gap without the scheduled half.
It is also what makes punctuality and schedule adherence computable at all — which is why the schedule is the first thing to set up and the last thing you should have to think about.