Multi-Shift Scheduling: Day, Swing, and Overnight Crews
A single-shift operation can run on a printed schedule for years. Add a second shift and the paper starts lying — usually before anyone notices, and usually in payroll.
Multi-shift scheduling in FabWise is a matter of naming the shift types you run and pointing each department at the right one.
Where Paper and Spreadsheets Break First
The failure is not that a second shift is complicated. It is that "Monday" stops meaning one thing.
On a printed weekly grid, Monday is a column. Once two crews work Monday at different times, that column has to hold two different sets of hours, two different sets of people, and two different definitions of late. Spreadsheets handle it by growing more columns, and within a few months the schedule is a document only its author can read.
Then the harder one: hours that cross midnight. A swing shift starting at 3 PM Tuesday and ending at 11:30 PM is easy. An overnight starting 10 PM Tuesday and ending 6 AM Wednesday is where hand-kept records reliably go wrong — the hours land on the wrong day, the week's totals stop tying out, and somebody reconciles it by hand every Friday.
Naming the Shift Types You Actually Run
FabWise treats the shift type as a thing you define rather than a fixed set.
A one-shift shop names one. A shop running around the clock names Day, Swing, and Overnight. A shop with a four-hour Saturday crew names that too.
Each schedule entry carries a start time, an end time, and its shift type. Each department is assigned one schedule. Shifts then generate automatically for every worker in that department.
The shift type travels with the record from there — through clock-in, through review, and into payroll export. That is what keeps a swing shift labeled a swing shift the whole way down, rather than becoming an anonymous block of hours somebody has to identify later.
Two Crews, One Monday
Because departments carry their own schedules, two crews working the same day are simply two departments pointed at two schedules.
Production runs Day. Finishing runs Swing. Both generate their own shifts for Monday, each with the right hours, each measured against its own start time — so a finisher arriving at 3:02 PM is on time rather than seven hours late against a schedule that was never theirs.
The comparison is the point. The schedule is what makes attendance mean anything, and on a multi-shift floor it has to mean something different for each crew on the same calendar day.
Rotating and Changing Shifts
Schedules change — a department moves to swing for a season, a shift type gets added, a start time shifts by half an hour.
FabWise handles the three cases differently on purpose:
- Future shifts regenerate to match the updated schedule
- Past shifts are untouched, so last month's payroll and job costs stay exactly as they were
- In-progress shifts continue, so nobody currently on the clock is disrupted
That last one matters more on a multi-shift floor than a single-shift one, because there is almost always somebody mid-shift when an edit happens. On a floor running three crews, there is no quiet hour to make changes in.
What This Does Not Do
FabWise captures time and attributes it. It does not classify shift differentials, calculate overtime, or apply premium pay rules. Your payroll provider does that.
Worth being direct about, because multi-shift operations are exactly where those rules get complicated — night premiums, weekend rates, differentials that vary by department. FabWise's job is to hand your provider accurate hours with the right shift type attached, so their rules apply to correct source data. It is not trying to be the thing that applies them.
Where It Fits
Multi-shift is where the pieces stop being optional. The kiosk captures the tap, the schedule says which shift it belonged to, review flags what does not match, and the export carries the whole thing out with its labels intact.
A single-shift shop can survive gaps in that chain. Three crews and a midnight boundary cannot.