Rostering Community Support Workers in New Zealand — Best Practices

Scheduling support workers in NZ disability services is more complex than any generic rostering tool accounts for. You're matching workers to specific people based on established relationships, skill requirements, geographic location, and availability constraints — all while staying within funded hours, meeting minimum engagement obligations under the NZ Holiday Act, maintaining continuity of support, and keeping a relief pool deep enough to handle the inevitable sick calls.

Get it right and your team is stable, your clients are well-supported, and your roster runs itself most weeks. Get it wrong and you're spending half your coordination time fire-fighting — calling through lists at 6am, making do with whoever is available, and creating exactly the kind of inconsistency that harms the people you support.

This article covers practical rostering approaches for community, SIL, and day programme settings, and the NZ-specific employment law considerations that make disability rostering different from most other industries.

Different Service Types, Different Rostering Logic

The three main disability service delivery contexts each have distinct rostering challenges. Treating them the same way is the first mistake many coordinators make.

Community Support (1:1)

Community support — accompanying someone to appointments, supporting daily living activities, facilitating community participation — is typically scheduled in 2–4 hour blocks, often non-contiguous across the day. The key challenges:

• Relationship continuity: The quality of community support depends enormously on the relationship between the worker and the person being supported. Consistent assignment of the same worker is not a preference — it's a quality standard. Build your roster to protect that consistency before optimising for cost or convenience.
• Travel between clients: Community workers often move between multiple clients across a geographic area. Back-to-back shifts with 45 minutes of travel between them aren't viable — the worker arrives late, stressed, or not at all. Build travel time explicitly into the schedule.
• NASC-funded hours: Each person has approved support hours. The roster must deliver what's funded — over-delivery risks funder recovery; under-delivery may indicate unmet need. Track allocated vs delivered per person, not just total hours.

Supported Independent Living (SIL)

SIL settings — shared group homes where 2–4 people with disabilities live together with support staff on site — require a fundamentally different approach. The roster must ensure continuous appropriate coverage, not just fill individual shifts:

• Coverage gaps have immediate consequences: Unlike community shifts where a late cancellation affects one client, a gap in a SIL house leaves residents without support. Identify backup workers for every SIL shift before the week starts, not on the morning of.
• House-specific compatibility: Workers need to be suitable for the specific house they're covering — the residents' needs, behaviours, the house dynamics. A worker who covers House A effectively may not be appropriate for House B. Document house-specific requirements and enforce them in scheduling.
• Sleepover shifts: Sleepover shifts are a distinct employment category under NZ law — not simply a night shift. A sleepover worker is paid a flat sleepover rate to be available overnight, plus any active care hours if they're required to provide support during the night. Rostering a sleepover as if it were a standard shift creates payroll and employment compliance errors.
• Weekly continuity: SIL residents experience a roster, not individual shifts. A roster that looks fine shift-by-shift may expose a resident to 8 different workers in a week — which is deeply disruptive. Review the roster from the resident's perspective, not just the worker's.

Day Programmes

Day programmes have fixed operating hours and a more structured weekly pattern. Rostering is more predictable but has its own challenges:

• Participant-to-worker ratios: Your contract will specify minimum ratios for different activity types. Understaffing a day programme is both a safety risk and a contract breach — ensure the roster always meets the ratio requirement even if attendance varies.
• Activity-specific qualifications: Activities like hydrotherapy, horse riding, or intensive behavioural support may require workers with specific training. Don't roster unqualified workers for specialist activities even if they're otherwise competent.
• Variable attendance: Day programme attendance fluctuates — illness, family events, holidays. Build a dynamic roster rather than assuming 100% attendance, and have a protocol for adjusting staffing when confirmed attendance drops significantly below plan.

Managing Worker Availability

Your roster is only as reliable as your availability data. Most rostering problems trace back to outdated or inaccurate availability information.

• Collect availability as structured data, not conversation: "Let me know when you're available" via text creates ambiguity. Collect availability through a structured process — available days and times per week, any standing constraints, and preferred hours. Update it quarterly at minimum.
• Distinguish absolute constraints from preferences: Some workers genuinely cannot work certain days (childcare, second job, study). Others prefer certain patterns but can flex with notice. Know which is which before you build the roster.
• Track actual hours scheduled vs agreed hours: Part-time workers employed with a minimum hours guarantee are entitled to those hours. If the roster consistently delivers fewer hours than guaranteed, you have an employment liability building. Monitor it weekly, not at year-end when backpay is the only remedy.
• Maintain a pre-qualified relief pool: For every regular shift, identify at least two workers who could cover it on short notice. This list should already be checked for qualifications and compatibility — not assembled reactively when someone calls in sick at 6am.

The NZ Holiday Act — Why It Matters for Rosters

The NZ Holiday Act 2003 is notoriously complex, and disability providers are among the sectors most exposed to getting it wrong. The roster pattern directly affects how leave entitlements are calculated.

Relevant Daily Pay vs Average Daily Pay

When a worker takes a day of annual leave or sick leave, they must be paid the higher of their relevant daily pay (what they would have earned on that specific day) or their average daily pay (their average daily earnings over the past 52 weeks). For workers with regular, consistent rosters, these are usually similar. For workers with highly variable shift patterns and penalty rates, the difference can be significant — and calculating average daily pay across 52 weeks of varying hours requires accurate historical timesheet data.

If your timesheets are reconstructed from memory or contain systematic rounding errors, your Holiday Act calculations will be wrong. The resulting liability can be significant — WorkSafe and the Labour Inspectorate have both pursued disability providers for Holiday Act underpayments in recent years.

Public Holidays

Workers rostered on a public holiday are entitled to time-and-a-half plus an alternative holiday (a day off in lieu). Workers not rostered who would otherwise have worked are entitled to the public holiday on pay. The key question is whether the public holiday falls on what would otherwise have been a working day for that specific worker — which depends on their regular pattern, not just whether they happened to be rostered that week.

This requires per-worker analysis, not a blanket rule. Track which workers are rostered on each public holiday, which workers have public holidays as ordinary working days (and weren't rostered), and ensure both categories receive their correct entitlements.

Casual Workers and Leave

Casual workers accrue holiday pay at 8% of gross earnings, typically paid out with each pay. This is correct for genuinely casual workers with no regular pattern. However, if a casual worker works a regular, consistent pattern over several weeks or months, they may be reclassified as a regular part-time employee under NZ employment law — with consequent entitlements to annual leave as a separate accrual rather than 8%. Roster patterns that create de facto regularity for "casual" workers are a common source of legal exposure in disability organisations.

Shift Swaps and Last-Minute Changes

Shift changes happen in every organisation. How you manage them determines whether they're a minor operational task or a weekly crisis.

• Build a swap process, not an ad-hoc system: Workers contacting each other directly to arrange swaps and only informing the coordinator after the fact creates coordination failures. The coordinator must approve every swap before it's confirmed — the replacement needs to be checked for qualifications, compatibility, and maximum hours.
• Require advance notice where possible: Incentivise workers to flag unavailability at least 48 hours ahead. Last-minute cancellations are sometimes unavoidable — but many aren't. A worker who knows they have a conflict on Thursday should tell you Monday, not Thursday morning.
• Document every change: Who was originally rostered, who covered, the reason for the change, and the date it was confirmed. This documentation matters for payroll accuracy, incident investigation (if something goes wrong on a shift covered by an unplanned replacement), and pattern analysis.
• Track cancellation patterns: Frequent cancellations from the same worker may indicate wellbeing concerns, a workload problem, a difficult client relationship, or personal circumstances. Address the pattern with the individual rather than just managing each cancellation transactionally.

Moving Beyond Spreadsheets

Most small NZ disability providers start with Excel or Google Sheets. This is manageable with 5 workers and limited shift complexity — but it doesn't scale, and it doesn't protect you from the errors that grow invisibly over time.

Spreadsheets can't show you conflicts before they happen — a worker double-booked, a shift requiring a qualification the assigned worker doesn't have, a SIL house that falls below ratio on Tuesday. They can't send workers their schedule. They can't capture GPS-verified clock-in. They can't generate the timesheet data you need for Holiday Act calculations and funder reporting. They can't flag that a worker's police vet expires next month. Each of these gaps is managed by a separate manual process — and collectively, those manual processes consume far more coordination time than the roster itself.

Purpose-built scheduling software designed for care providers connects all these pieces: the roster drives the timesheet, the timesheet feeds the progress notes, the attendance record supports the service delivery report. The compliance record is built as a by-product of normal operations, not assembled separately before each audit. Take a tour of how KareShift handles rostering for NZ disability providers.