Scheduling method: split shifts
One shift, two pieces
A split shift divides one working day into two separate working periods with a longer unpaid break in the middle. A typical pattern might be 08:00–12:00, then four hours off, then 16:00–20:00 — eight hours of work spread across twelve hours of the day. Split shifts are familiar in hospitality, transport, and broadcasting; in contact centres they appear specifically when demand has a strong double peak (morning and evening) with a quiet midday. Used well, they cover the demand profile more economically than two separate cohorts would. Used badly, they impose an unworkable rhythm on the workforce and produce attrition that erases the scheduling saving. This article walks through how split shifts work in a contact centre context, when they make sense, and the practical design choices.
When the demand pattern justifies them
Split shifts make scheduling sense when the volume curve has a pronounced double peak: a busy morning, a quiet middle, a busy evening, with limited demand in the middle. The classic contact centre examples are consumer-facing retail support (people call before work and after work), parking and transport queries (commute peaks), and cross-time-zone services where the operation covers two regional working days from a single location. If the demand profile is roughly flat through the day, split shifts produce no scheduling benefit and the workforce cost they impose is wasted.
A reasonable rule of thumb: if midday demand is less than 40% of peak demand for at least three hours, split shifts can pay back. If midday demand stays above 60% of peak, the simpler answer is overlapping standard shifts.
What they cost the agent
Split shifts are expensive for the workforce in ways that are easy to miss. The unpaid middle four hours are not really free time — they are not enough to do anything substantial with, often spent commuting or hanging around the workplace area, and they extend the agent’s working day from eight hours to twelve. The total time committed to work is fifty percent more than for a standard shift, for the same pay. Childcare arrangements become impossible. Second jobs become impossible. Social and family life on a working day disappears. The pattern is sustainable for some agents in some life circumstances; it is unsustainable for most.
This is why operations that introduce split shifts without a meaningful pay premium typically see acute attrition on the affected cohort. Where split shifts are part of the workforce’s expected pattern, a 10–25% pay premium is standard, and operations that try to introduce them without one rarely succeed.
Design choices that matter
Four design choices separate sustainable split shifts from punishing ones. The break length. Two hours is too short to do anything but stay near work; six hours is enough to genuinely go home. Most operations land at four hours as a compromise, which is the worst of both worlds for the agent and the cheapest for the operation. Where the workforce will not absorb it, the choice becomes either pay them properly or move to overlapping shifts. Voluntary or mandatory. Split shifts as one option on a menu, chosen by agents who genuinely prefer the pattern, work; split shifts as an imposed pattern produce resistance. Pay premium. A premium of 10–25% on top of the standard rate reflects the genuine extra burden and is the price of getting and keeping workers on the pattern. Travel and facilities. Agents working a split shift need somewhere to be in the middle — a quiet room at the office, free transport home, or a short enough commute that going home is realistic. Operations that ignore this push the agent into hanging around the workplace area, which is corrosive.
Alternatives worth considering first
Before adopting split shifts, three alternatives are usually worth modelling. Overlapping cohorts. A morning cohort works 08:00–16:00 and an evening cohort works 12:00–20:00, with the overlap in the middle handling the quieter period. This produces a similar staffing curve without imposing split shifts on anyone. Part-time shifts at the peaks. Specifically recruiting four-hour morning shifts and four-hour evening shifts gives the operation peak cover without the middle gap. Part-time workforces typically have lower attrition than split-shift workforces. Self-rostering. Let agents bid on which slots they want; if some genuinely want a split shift, they will choose it; most will not.
Split shifts often emerge from a desire to use the existing full-time workforce more flexibly. Where the alternatives can deliver the same coverage at lower workforce cost, they are usually the better choice.
Where split shifts genuinely work
Three situations consistently justify split shifts despite their cost. Agents who actively want the pattern. Students with university lectures in the middle of the day, parents whose childcare schedule fits the split, agents with second jobs that occupy the middle hours. Where the workforce has genuine appetite, split shifts can be a draw rather than a deterrent. Operations with a small workforce. A 20-agent operation cannot easily run separate morning and evening cohorts; split shifts let the same small team cover both peaks. 24/7 operations with constrained recruitment. In specialist roles where recruiting is hard, split shifts spread the contracted hours of the available workforce across the demand profile more efficiently than alternatives.
Common mistakes
Three patterns recur. No pay premium. Introducing split shifts at standard pay almost always fails — the workforce treats it as a pay cut and resigns. Imposing rather than offering. Mandatory split shifts produce resentment; voluntary ones with appropriate compensation produce a cohort that has chosen the pattern. Modelling the staffing benefit without modelling the attrition cost. A split-shift schedule that delivers a 12% reduction in agent-hours but increases attrition by ten percentage points loses money over twelve months. The full economics need both sides.
Conclusion
Split shifts are a legitimate scheduling tool for the specific demand profile they fit, but they are also one of the easiest patterns to use carelessly. The cost to the agent is large, often hidden in the planner’s headline numbers, and pays back in attrition that erases the scheduling saving. Where they make sense, design them honestly: voluntary, paid at a premium, with thought given to the practical realities of the middle break. Where the demand profile does not really justify them, the alternatives are almost always better.
Pair this with building a work-life-balance friendly schedule menu and rotating shift patterns for the wider toolkit.
Comments
Comments are powered by Giscus — sign in with GitHub to join the discussion.