Quality and team

Shift Planning Basics for Phone Teams: From Forecast to Rota

How to turn expected call volume into a fair, workable rota: the inputs you need, how to shape shifts, where breaks go and how to check the plan.

Call editorial team · Published · 6 min read

Shift planning is the quiet job that decides how every call day feels. When the rota matches demand, queues stay short, agents get proper breaks and nobody is sent home early without notice. When it does not, you get a cycle of overtime, burnout and callers who hang up. This guide covers the basics for a small or mid-sized phone team: what to gather, how to shape shifts, how to place people fairly and how to check that the plan worked.

A team lead reviewing a weekly rota on a screen in a contact-centre office
Illustrative image

If you have never forecast volume before, read Forecasting Call Volume first, and keep Erlang C Explained nearby for the staffing arithmetic. This article picks up where those end: with a number of people needed per interval and the job of turning it into real shifts.

What you need before you build a rota

Planning goes wrong most often because an input is missing, not because the maths is hard. Collect these four things first.

The four planning inputs

  • Expected demandCalls per half hour for each day type, from your own history. Include how long calls last, including wrap-up work.
  • Service goalThe wait you want most callers to experience. It decides how many people you need for the same volume.
  • Who can work whenContract hours, stated preferences, hours people cannot work, and any rules about rest between shifts.
  • Skills and queuesWhich people can handle which queues or languages, so cover is counted by qualification and not headcount alone.

Be honest about call length. Many first rotas fail because they use talk time only. The time an agent spends typing notes after the call is still time they cannot take another call, so it belongs in the number.

Design a few repeatable shift shapes

A shift shape is a saved pattern such as an early shift, a mid shift or a late shift, with a start time, an end time and the weekdays it applies to. Teams that plan by shape rather than by person get a rota that is easier to read, easier to explain and easier to change when demand moves.

Start with the demand curve. If calls peak mid-morning and again after lunch, an early shift and a mid shift that overlap at those hours cover the peaks without paying for idle time at dawn. If your day is flat, simpler shapes work. Avoid the temptation to create ten variants; four or five are plenty for most teams.

Where breaks go

Breaks are part of the shape. Placing them all at the same time empties the queue at once, so stagger them. A common approach is to schedule meal breaks away from the busiest intervals and shorter breaks in the quieter gaps. Check the local rules on rest and working time that apply to you, because they differ by country and by contract.

From forecast to published rota

  1. Read the forecastNote the people needed in each half hour for each day.
  2. Draw the curveMark the peaks and the quiet stretches before choosing any times.
  3. Choose shapesPick a few shifts whose overlaps match the peaks.
  4. Place peopleAssign by skill, contract and preference, rotating the less popular hours.
  5. Publish earlyGive people enough notice to plan their own lives.
  6. ReviewCompare planned cover with the day that actually happened.

Placing people fairly and sensibly

Once the shapes exist, placing people is a puzzle with three kinds of constraint: hard limits, skills and preferences. Hard limits come first: hours people cannot work, minimum rest between shifts and maximum run of days. Then check skills so that every queue has at least one qualified person on shift in every interval. Finally, weigh preferences where the cover allows.

Fairness in the rota connects directly to fairness in leave. The next guide, Handling Time-Off Requests Fairly, covers how to decide between competing requests without resentment.

Check the plan against reality

A rota is a forecast with names on it. It will be wrong in places, so build a routine of comparing it with the actual day. Look at two things: whether cover matched demand in each interval, and whether people kept to the shifts they were given. A plan that looks perfect on paper but is routinely missed by a few minutes at the start of the day has a different problem from one that is simply too thin at lunchtime.

Plan versus actual: reading the gaps

Likely causeFirst thing to try
Too few people at the peakShapes do not overlap where demand is highest, or breaks fall in the peakMove an overlap or stagger breaks
Too many people in quiet hoursShapes start too early or end too late for the real curveShorten or shift the shape
Cover looks fine but the queue is longCalls run longer than assumed, or the right skills were not on shiftRecheck call length and cover by skill
Frequent late startsStart times do not suit commutes or handover tasksTalk to the team; adjust the start time
Everyone is busy all dayThe plan is built on too little coverLook at occupancy before blaming people

Mistakes to avoid

Weekly planning checklist

  • Forecast updated with last week's actual volume
  • Peaks and quiet stretches marked
  • Shift shapes still match the demand curve
  • Every queue has a qualified person in every interval
  • Breaks staggered away from peaks
  • Preferences and unavailable hours applied
  • Rota published with enough notice
  • Last week reviewed: plan versus actual

Planning shifts in Call

Call has a Workforce page under Calls where you can compare the staff you need with the staff you have scheduled for a day. Pick a date and you see, for each half hour, the headcount the forecast needs against the people on shift, along with a list of gaps and what to do about them. Admins and managers can rebuild the day's forecast from the history of an inbound queue.

The same page lets you save shift shapes with a name, start and end time and weekdays, then put a shape on the rota for chosen people and dates. Each shift is given a fixed break, and new shifts start as drafts. On Staffing ops, people record the hours they prefer, would rather avoid or cannot work, and the cover-by-skill view shows whether each queue has someone qualified on shift. After the day, the roster and adherence panels show how closely people kept to the plan. For the broader picture see Workforce Management.

Frequently asked questions

How far ahead should a rota be published?

As early as you can manage while still being accurate. Many teams publish a few weeks ahead and treat changes after that as exceptions. Check any legal notice rules that apply to your location.

How many shift shapes do I need?

Most small teams do well with four or five. More shapes make the rota harder to read without covering demand much better.

Should I plan around peaks or averages?

Plan around the curve, interval by interval. An average hides exactly the half hours in which callers wait longest.

What if people want different hours from the plan?

Collect preferences in advance and honour them where cover allows. Rotate the awkward hours so the burden is shared and visible.

How do I handle unexpected absence?

Keep a short list of people who can cover at short notice, and know which queues can be paused or reduced if needed. Review after each incident to see whether the rota was too thin.

How often should I review the plan?

Weekly at minimum. Compare planned cover with actual volume and adherence, then adjust shapes and forecast before the next rota is built.

Plan shift shapes and compare cover with demand in Call

In the demo console you can try incoming calls in a simulation.

Related guides