Scheduling reference

Contact centre shift design guide

Q: Can a contact centre run a 4-day working week?

Yes. A 4-day week typically means 4 × 10-hour shifts or 4 × 9-hour shifts (compressed) rather than fewer total hours. From a WFM perspective, the key consideration is that 10-hour shifts produce more fatigue-driven AHT creep in the last 2 hours, which reduces effective capacity. Some operations find that 4-day staff have higher shrinkage (more absence) in the compressed model. On the positive side, 4-day weeks consistently improve retention and reduce attrition, which reduces the long-term recruitment and training cost.

Shift design is how you convert Erlang C agent requirements into actual working schedules. The shift pattern you choose affects your total headcount, your shrinkage rate, your agent wellbeing, and your attrition, often more than any other operational decision.

Note on employment law

This guide describes employment law and HR practice as it applies in Great Britain. Employment law varies by jurisdiction and individual circumstances. Always verify the requirements applicable to your situation with your HR team, employment counsel, or ACAS before changing people management practices. This guide is for operational context, not legal advice.

How shift design connects to staffing numbers

Erlang C tells you the minimum seated agents needed per 30-minute interval to hit your service level target. Shift design is the translation layer between those per-interval requirements and the shifts agents actually work.

The headcount chain

Erlang C output

Seated agents per interval

→

÷ (1 − shrinkage)

Scheduled agents per interval

→

Shift design

Shifts that cover each interval

→

Total headcount

FTEs to recruit and employ

If your shifts are wider than your peak, you pay for idle time. If they are narrower, you miss the peak. Shift granularity, meaning how many start times you offer, determines how closely you can match actual volume shape.

Coarse shift design (3 fixed start times)

If you only offer 08:00, 12:00, and 16:00 starts, you get systematic over-staffing at 10:00–11:00 and under-staffing at 14:00–15:00. Your effective coverage is structurally wrong, and you need more total headcount to prevent the gaps.

Fine-grained shift design (30-min start slots)

Offering shift starts every 30 minutes lets you match your curve almost exactly. Fewer agents are wasted on idle time. Total headcount requirement falls by 8–15% vs. a three-option design on the same volume profile.

Six shift patterns: trade-offs at a glance

Fixed daytime (08:00–16:00 / 09:00–17:00)

Advantages

✓Simple to manage
✓Low scheduling overhead
✓Agent preference for predictability

Disadvantages

✗No evening or weekend cover
✗Overstaffs quiet midday periods
✗Wasteful if volume peaks early/late

Best for: B2B operations, back-office, lower-volume centres with limited hours

Rotating early / late (two-shift)

Advantages

✓Extends coverage to 20:00–22:00
✓Spreads unsocial hours fairly
✓Good for 10–16 hour operations

Disadvantages

✗Sleep disruption on rotation weeks
✗Scheduling complexity doubles
✗Bank holiday coverage gaps

Best for: Consumer-facing operations with significant evening volume

Three-shift rotating (including nights)

Advantages

✓Full 24/7 coverage achievable
✓Equitable distribution of nights
✓No permanent night workers needed

Disadvantages

✗Night rotation affects health and retention
✗Requires careful WTR compliance
✗Higher training overlap costs

Best for: 24/7 operations (utilities, emergency services, global support)

Compressed (4 × 10-hour days)

Advantages

✓3-day weekend improves retention
✓Fewer part-shifts at handover
✓Agents feel greater schedule control

Disadvantages

✗AHT creep in hours 8–10
✗10-hour minimum staffing commitment per agent
✗Less flexible for intraday variation

Best for: Operations where retention is a key cost driver and volume is relatively flat

Split shift

Advantages

✓Covers bimodal peaks without midday overstaffing
✓Lower headcount than two separate part-timers
✓Flexible for individual agent preference

Disadvantages

✗Agents dislike long unpaid gaps
✗High attrition risk
✗WTR rest period compliance complexity

Best for: High-volume morning + evening peaks with predictable midday trough

Annualised hours

Advantages

✓Maximum flexibility to staff to volume patterns
✓Avoids structural overstaffing
✓Can reduce overtime cost

Disadvantages

✗Complex contracts and payroll
✗Agents resent last-minute schedule changes
✗Requires strong forecasting to work well

Best for: Operations with strong seasonal volume variation and high scheduling flexibility need

Working Time Regulations: the non-negotiables

UK Working Time Regulations 1998 (implementing the EU Working Time Directive) set minimum standards that override any contractual or operational preference. Shift design that violates WTR creates legal liability regardless of agent consent.

RuleRequirement

Maximum weekly working time48 hours per week averaged over 17 weeks (can be opted out of individually)

Daily restMinimum 11 consecutive hours between working days

Weekly restMinimum 24 hours off per week (or 48 hours per fortnight)

Rest breaks20-minute break after 6 hours worked; paid or unpaid depending on contract

Night worker limit8 hours average per 24-hour period for night workers; free health assessment required

Young workers (under 18)Max 8 hours per day, 40 hours per week; 12-hour daily rest

These are UK rules as of 2024. Northern Ireland, Scotland, and devolved nations apply the same WTR. Operations with TUPE-transferred staff should check whether inherited contracts apply more favourable terms.

How shift design drives shrinkage

Shrinkage is not just absence and training. Much of it is structural, built into the shift design itself. Understanding which shrinkage components are fixed vs. variable lets you reduce total headcount without cutting staff.

Planned break clustering

If all agents on an 8-hour shift take lunch at the same time, you lose 15–20% of available capacity for that 30-minute interval. Staggering break schedules can flatten this to 3–5% and avoid needing an extra agent.

Handover overlap

Agents leaving and arriving at the same time produce a 15–30 minute window where both are on the floor but productivity is split. Overlapping shifts by 30 minutes and counting only 70% of overlap hours as productive reduces headcount error.

Training scheduling

Training placed in peak intervals removes capacity exactly when you need it. The WFM rule is: no training in the first 90 minutes or last 90 minutes of peak periods. Place training in the identified troughs from your interval-level forecast.

Shift length and fatigue

AHT tends to increase in the final 2 hours of a shift, as agents handle calls more slowly when fatigue accumulates. Longer shifts increase effective AHT, which increases the Erlang C agent requirement slightly. A 10-hour shift is typically 3–5% less efficient per hour than an 8-hour shift.

Read the full shrinkage guide →

Weekend and bank holiday cover

Weekend volume varies enormously by sector. Retail and consumer operations often see Saturday as a peak day. B2B operations see near-zero Saturday volume and nothing on Sunday. Bank holidays are the structural staffing trap: many operations have full contractual staff entitlements but dramatically reduced volume.

The bank holiday over-staffing trap

If your contracts require a fixed number of agents to work every bank holiday, regardless of volume, you will structurally over-staff eight days per year. In a 100-agent centre, over-staffing by 30% on 8 days costs the equivalent of 1.2 FTEs annually. Solve this by: negotiating flexible bank holiday provisions in contracts; offering bank holiday leave trading; and adjusting scheduled hours on known-low-volume bank holidays.

Bank holiday forecasting

Treat each bank holiday individually. Christmas Day is different from August bank holiday. Build a bank holiday volume index from 3+ years of history per calendar event, not a generic 'bank holiday multiplier'.

Weekend shift design

If Saturday is a peak day, your weekend roster needs to be staffed to meet the Erlang C requirement, not just to meet a contractual obligation minimum. Model Saturday and Sunday separately.

Shift design questions

What is a rotating shift pattern in a contact centre?

A rotating shift pattern cycles agents through different shifts (e.g. early, late, night) on a pre-defined schedule, so no single agent is permanently assigned to the same hours. Rotating patterns distribute unsocial hours fairly across the workforce. They are more complex to manage and can disrupt sleep patterns, but are legally required in some collective agreements and are the norm in 24/7 operations.

How does shift design affect Erlang C staffing requirements?

Erlang C gives you the minimum seated agents needed per interval to meet a service level target. Shift design is how you cover those intervals. If your shift start times are every 30 minutes, you can fine-tune coverage closely. If your shift start times are fixed to three options (08:00, 12:00, 16:00), you will have systematic over- and under-staffing at the boundaries, and higher effective shrinkage because breaks cluster. Finer-grained shift start times always reduce total headcount required.

What is a split shift and when should a contact centre use one?

A split shift divides an agent's working day into two separate periods with an unpaid gap (e.g. 08:00–12:00, then 17:00–21:00). They cover bimodal volume patterns without paying for idle midday hours. In the UK, split shifts are legal but must comply with Working Time Regulations minimum rest requirements. Agents typically dislike split shifts; turnover risk increases and they should be offered voluntarily with a premium where possible.

Can a contact centre run a 4-day working week?

Yes. A 4-day week typically means 4 × 10-hour shifts (compressed) rather than fewer total hours. From a WFM perspective, 10-hour shifts produce more fatigue-driven AHT creep in the final hours, which slightly reduces effective capacity. On the positive side, 4-day weeks consistently improve retention and reduce attrition, which reduces long-term recruitment and training cost: a significant offset.

Build your shift plan in Turnella

Start with Erlang C to find your per-interval agent requirement. Apply shrinkage. Use the what-if tool to model different volume scenarios before committing to a shift structure.

Open Turnella free →Erlang C calculator