To replace your support team scheduling spreadsheet, first write down every working rule the sheet only enforces through someone's memory, then export your contact volume by channel, day and hour, load both into workforce management (WFM) software that checks each draft roster against those rules, and run it alongside the spreadsheet for at least one roster week before you switch. The rules worth checking are contracted hours, rest between shifts, channel skills, approved leave and coverage against forecast demand.

This guide is for support teams of 20 or more agents covering live chat and phones. It sets out eight steps, the legal minimums worth writing down if you roster in the UK, Australia or the US, what still needs a person, and a short table of tools that do the checking.

Key takeaways

• Write the rules down before you buy anything. If a rule only lives in a team lead's head, no software can check it.

• Rest rules differ by country. UK workers have the right to 11 hours rest between working days; in Australia, awards and registered agreements may set a minimum break between shifts; the US FLSA sets overtime after 40 hours in a workweek but no limit on weekly hours for workers 16 and older.

• Export volume by channel, day and hour, not daily totals. Coverage gaps hide inside the day.

• Run one parallel week. Compare the software's draft with your spreadsheet roster shift by shift before you retire the sheet.

• Keep people on the judgement calls: award interpretation, roster-change consultation, fairness and individual circumstances.

Which tools check working rules for support rosters?

Lorikeet Workforce Manager starts each roster week as a draft and checks it against contracted hours, rest between shifts, channel skills, approved leave and demand before you publish, and you can import your current roster model from a spreadsheet or a helpdesk export. Other tools that check rules:

• Assembled lets agents trade shifts within rules you set for skills, queues and team eligibility, with automatic validation to maintain coverage, according to its pricing page.

• Calabrio WFM, now part of Verint, says its multi-skill scheduling engine accounts for work-hour legislation, demand and employee requests.

• Deputy covers break compliance, qualifications and fatigue limits, and its scheduling is built for shift-based businesses, comparing wages with sales.

How do you know the scheduling spreadsheet has broken?

You know the spreadsheet has broken when coverage problems are found by customers in the queue rather than by you before the roster goes out. Common signs:

• Gaps show up after publishing. Nobody checks the roster against forecast demand by hour, so the first warning is a long chat queue.

• Rules live in people's heads: who is not trained on phones, who cannot start early after a late shift, who is on a reduced contract.

• Leave is approved in one place and the roster is built in another, so approved leave and rostered shifts collide.

• Only one person can safely edit the file, and one bad formula can break it.

• Building the roster takes longer every quarter. Assembled's guide to scheduling software describes one company whose monthly scheduling in Google Sheets stretched from a three-day process to a full week as the team grew from 30 to more than 200 agents.

• Nobody can answer "how many people do we need in March?" without a separate model.

How do you replace a support team scheduling spreadsheet?

You replace a support team scheduling spreadsheet by turning its hidden rules and volume history into inputs that software can check, then proving the software's roster is at least as good as yours for one real week. The eight steps below take most teams from a shared sheet to a published, rule-checked roster.

1. List the team rules the spreadsheet enforces from memory

Start with a plain document, not a tool. Go through your current roster with each team lead and write every rule they apply as one testable sentence. "Sam works 30 contracted hours over four days" can be checked. "Sam prefers mornings" is a preference, so mark it as one.

For a chat and phone team, the list usually covers:

• Contracted hours per person, including part-time patterns and maximum hours per week.

• Rest between shifts, such as the gap required after a late shift before an early one.

• Channel skills: who can take phones, who can take chat, who handles escalations, languages spoken.

• Leave: approved annual leave, recurring days off, training days.

• Coverage minimums: for example, at least two phone-skilled agents on from opening to close.

• Fairness rules: how weekend and late shifts are rotated.

Expect to find rules nobody agreed on. Settle them now, because software will apply whatever you give it, every week.

2. Add the legal minimums for each country you roster in

Labour law sets the floor your team rules sit on. Examples from official guidance, current when we checked on 23 Oct 2026:

• UK. Under GOV.UK's rest breaks guidance, workers over 18 who work more than 6 hours a day have the right to one uninterrupted 20 minute rest break, 11 hours rest between working days (finish at 8pm, do not start again until 7am), and either an uninterrupted 24 hours without work each week or 48 hours each fortnight. GOV.UK also says you cannot work more than 48 hours a week on average, normally averaged over 17 weeks, unless you opt out.

• Australia. The Fair Work Ombudsman says that under the National Employment Standards an employee can work a maximum of 38 hours in a week unless an employer asks them to work reasonable extra hours. Awards and registered agreements may provide for a minimum amount of time off between the end of one shift and the start of another, so check the award your team is covered by.

• US. The Department of Labor says the FLSA requires overtime pay at not less than time and one-half for hours over 40 in a workweek, that a workweek is a fixed, recurring 168 hour period, and that averaging hours over two or more weeks is not permitted. The FLSA sets no limit on the number of hours employees 16 and older may work in a workweek.

Write these as rules too ("no agent rostered under 11 hours apart"), and note that awards, agreements and state laws can add more. This is a checklist for operations, not legal advice.

3. Export contact volume by channel, day and hour

Pull contact history from your helpdesk and phone system, split by channel, day of week and hour of day. Daily totals hide the problem you are trying to solve: a team can be fully staffed for the day and still short between 9am and 11am on Mondays.

Include at least one full seasonal cycle you care about, such as last year's sale period, and note known events (launches, outages, billing runs) so you can explain the spikes later. Keep handle time by channel alongside volume, since phone and chat take different amounts of agent time. Our guide to forecasting for support teams covers how much history to use and how to treat one-off spikes.

4. Turn volume into a staffing requirement

Volume is not headcount. For each hour you need the number of agents required to meet your service target, then an allowance for time people are paid but not available, such as breaks, training and leave. Our Erlang C staffing guide works through the arithmetic for phone and chat, and our guide to shrinkage, adherence and occupancy shows how to set the allowance.

Most WFM tools do this conversion for you. Do it once by hand for a busy hour anyway, so you can sense-check the software's numbers in step 7.

5. Choose software that checks rules before you publish

The point of moving off the spreadsheet is that rule breaks are caught on a draft, not discovered on the day. When you test tools, check that each one can:

• Hold every rule from steps 1 and 2 and flag a draft that breaks one.

• Show coverage against forecast demand by channel and hour.

• Suggest who can cover a gap, using skills and availability.

• Import your current roster and history without a long services project.

• Plan months ahead, so hiring decisions come from the same numbers.

Lorikeet Workforce Manager is built for this case: it is aimed at support teams of 20+ agents running live chat or phones, and when an agent is on leave and phone coverage falls below forecast demand, it flags the shift and suggests agents who are qualified and available to cover it, according to the launch post.

6. Import the roster model and rebuild one real week

Load your team, contracts, skills and leave, plus the volume history from step 3. Most tools accept a spreadsheet import. Lorikeet's launch post says you can upload your current roster model from a spreadsheet or a helpdesk export, and that Lorikeet customers can skip the upload because Workforce Manager reads ticket history directly.

Then build the next real roster week in the new tool. Do not tune it to match your spreadsheet. The question is whether the software's draft, built from your rules and volume, is good enough to publish.

7. Run a parallel week and compare shift by shift

Keep publishing your spreadsheet roster for one week while the software builds its own for the same week. Compare them on four things:

1. Rule breaks: does either roster break a rule from steps 1 and 2? Spreadsheets often do, quietly.

2. Coverage: which roster matches forecast demand more closely, hour by hour, on each channel?

3. Hours: total rostered hours against contracted hours, by person.

4. Actuals: at the end of the week, which roster would have handled the real volume better?

Fix the inputs, not the output. If the software rosters someone onto phones who is not ready, the skill data is wrong. One week is the minimum; run two if your weeks differ a lot.

8. Switch over, retire the sheet and plan ahead

Publish from the new tool, tell agents where to find their shifts, and make the spreadsheet read-only so nobody edits two versions. Set a monthly review: compare forecast with actual volume, update rules when contracts change, and use the longer view for hiring. Lorikeet's capacity planning, for example, compares hours needed with hours available month by month, factoring in growth, and shows shortfalls up to 12 months ahead.

How we chose and checked these tools

We included tools that build rosters for support or shift-based teams and publish, on their own pages, which working rules they check. Every vendor fact below was checked on the vendor's public pages on 23 Oct 2026 and is linked. Lorikeet publishes this guide and is one of the tools listed. We have tried to describe every product, including our own, using only what each vendor publishes, and we link to the source for each claim.

Tools that help

A dedicated support WFM tool fits best when your rules depend on channels, skills and hourly demand. A general shift tool such as Deputy fits when pay rules and awards are the harder problem. For a wider comparison, see our guide to workforce management software for support teams.

Questions to ask before you pick a tool

• Can I enter every rule on my list from steps 1 and 2, and will the tool block or flag a draft that breaks one?

• Does it forecast by channel and hour from my own history, and can I adjust for a known event?

• How do I import my current roster, and how long does that take?

• Is pricing published, and is there a trial long enough to run a parallel week on real data?

• What happens during the day when someone calls in sick?

What still needs a human?

Software can check a roster against rules. It cannot decide what the rules should be or when to make an exception. Keep people responsible for:

• Interpreting awards and agreements. Deciding whether extra hours are reasonable under the Australian NES is a judgement, and roster changes need consultation: Fair Work says employers must discuss a change to a regular roster with employees first and invite their views.

• Individual circumstances, such as caring responsibilities, health, or a request that falls outside policy.

• Fairness. Who gets the late and weekend shifts is a team decision, even if a tool applies it.

• The day itself. Sick calls and spikes still need someone to decide. Lorikeet's launch post says in-day management, closing gaps from sick calls and spikes within rules you set, is the next step.

If your team is in Australia, our guide to rostering software for customer support in Australia goes deeper on awards. To try this on your own volume, you can start a 30-day free trial and build a first roster from your data.