Every care provider faces the same quiet payroll question at the end of a pay run: do you pay people for the shift you rostered, or the times they tapped clock-in and clock-out? It sounds trivial. In practice it is one of the biggest drivers of unbudgeted wage cost in the disability and aged care sectors, and one of the easiest things to get wrong in either direction.
Pay purely to the clock and you inherit every stray minute of early arrivals and late departures. Pay purely to the roster and you risk stripping time a worker was genuinely directed to work. The answer that most compliant, well-run providers land on is a middle path: default to the rostered hours, and treat any material difference from the clock as an exception a manager reviews. This guide explains why, and how to run it in practice.
What is the difference between rostered hours and clocked hours?
Rostered hours are the agreed, published shift. If a support worker is scheduled from 7:00am to 3:00pm, that is eight hours of planned, budgeted, client-funded time. Both the worker and the provider know it in advance, and it usually maps directly to a client's plan or funding.
Clocked hours are what the timekeeping system actually records: the moment a worker taps clock-in on arrival and clock-out on leaving, ideally with a GPS location to prove they were on site. Clock times are essential evidence. The Fair Work Ombudsman requires employers to keep accurate records of hours worked, and a GPS-verified clock event is far stronger evidence than a paper timesheet filled in from memory (see the Fair Work Ombudsman guidance on pay and record keeping).
The trouble is that the two numbers almost never match to the minute. Someone arrives a few minutes early to receive handover. Someone stays a little late because the next worker was delayed. Someone's phone clock is slightly off. These differences are the raw material of the whole problem.
Why does clock drift cost care providers money?
Clock drift is the small, everyday gap between the scheduled shift and the actual clock taps. It is rarely deliberate. But it is relentless, and because it almost always drifts in the worker's favour, it only ever adds cost.
Consider a worker who habitually clocks in six minutes early and clocks out eight minutes late. That is fourteen minutes of unapproved time per shift. It looks like nothing. Run the numbers across a roster:
| Scenario | Drift per shift | Shifts per fortnight | Extra paid hours per year |
|---|---|---|---|
| One worker | 14 min | 10 | ~61 hours |
| Team of 20 | 14 min | 10 each | ~1,213 hours |
| Team of 50 | 14 min | 10 each | ~3,033 hours |
At a typical SCHADS support worker rate, a team of fifty drifting by a quarter of an hour a shift is well over one hundred thousand dollars a year of wages that no manager ever approved and that no client funding covers. None of it reflects work anyone asked for. It is simply the difference between "the shift" and "the taps".
Should you pay rostered hours or clocked hours?
For the vast majority of shifts, the rostered hours are the right baseline to pay. They are agreed in advance, they match the funding, and they are predictable for both the worker and the business. A worker who clocks in two minutes early and out three minutes late has not done extra work in any meaningful sense; they have arrived and left around the edges of a shift that ran exactly as planned.
This is where a grace window matters. A grace window is a tolerance either side of the scheduled start and finish, inside which small differences are ignored and the worker is treated as having worked the roster. A worker who clocks in inside the grace window is on time and paid the full shift. A worker who clocks in outside it has a variance worth looking at.
Paying to the roster is entirely compliant, provided one condition holds: workers must still be paid for all the hours they are actually required to work. The moment genuine additional work happens, it has to be captured and paid. That is the job of the exception process.
How does exception approval keep payroll fair and compliant?
The safeguard that makes "pay the roster" fair is that every material difference between roster and clock is surfaced and reviewed before the pay run closes. Instead of silently paying the clock, or silently paying the roster, the system pays the roster and asks a manager to decide on the differences. Two exceptions matter most.
Overtime and stay-backs
Sometimes a worker legitimately stays past the rostered finish. The next worker is stuck in traffic, a participant is in distress and cannot be safely left, an incident is unfolding that has to be documented. This is real, directed work, and it must be paid. Under the SCHADS Award it may attract overtime rates once ordinary hours are exceeded. Our guide to SCHADS Award overtime rules covers exactly when the higher rates kick in. The point here is that the stay-back should be a deliberate, approved decision, not something the clock decides on its own.
Cut-short shifts
The reverse also happens. A participant is admitted to hospital, a shift is cancelled part-way through, a worker has to leave early. Here the clock finishes before the roster. Depending on the award, notice period and cancellation rules, the worker may still be entitled to a minimum payment. A manager reviewing the variance can apply the right outcome rather than the payroll system either overpaying to the roster or underpaying to the clock.
In both cases the principle is the same: the variance is visible, a human with context decides, and the decision is recorded. That record is what protects you in an audit. The Fair Work Commission publishes the modern awards that set these entitlements, including the SCHADS Award, on its modern awards register, and the Fair Work Ombudsman explains the general rules on hours of work, breaks and rosters.
What about late clock-ins and no-shows?
The third exception runs the other way: a worker who arrives late. Late arrivals are the mirror image of stay-backs. If a worker is rostered from 7:00am but does not clock in until 7:35am, and your grace window is thirty minutes, that is five minutes outside the window that a manager should see.
The right handling is not to dock people automatically and it is not to ignore it. It is to flag it. A good system records the scheduled start, the actual clock-in, whether it fell outside the grace window, and how many minutes outside. The manager then decides: was this a genuine handover overrun that carried into the next shift, or a pattern of late starts that needs a conversation? Either way the data is captured, the decision is deliberate, and the audit trail exists.
GPS-verified attendance makes this far more reliable than a memory-based timesheet, because you know not just when the worker clocked in but where. Our piece on verifying support worker attendance without paper timesheets goes deeper on why location-stamped clock events matter for both payroll accuracy and funding evidence.
How does CareIQ default to rostered hours with manager approval?
CareIQ is built around exactly this model. By default the platform pays timesheets to the rostered hours, so clock drift never quietly inflates a pay run. Every clock-in records the scheduled time, whether the worker was outside the company's configured grace window, and the number of minutes outside it, so nothing is hidden.
From there the exceptions surface to managers:
- Overtime and stay-backs are flagged where the clock runs past the roster, so a manager can approve the extra time and let the SCHADS engine apply the correct overtime rate.
- Cut-short shifts are flagged where the clock finishes early, so the right minimum-payment or cancellation outcome can be applied.
- Late clock-ins are auto-flagged against the grace window and feed a "Late Clock Ins" dashboard tile, so managers can spot patterns and review before pay is finalised.
The grace window itself is configurable per company, so a provider can set the tolerance that suits its service model. Contractors sit outside the SCHADS calculation entirely, and managers get a review step before the pay run rather than a surprise after it. The result is payroll that starts from the fair, funded baseline of the roster and only moves off it when a human decides it should. That review flows straight into the timesheet, which you can read more about in our guide to timesheet management from shift completion to pay run.
How can providers put this into practice?
You do not need a specific platform to adopt the principle, though automation makes it dramatically easier. The building blocks are the same everywhere:
- Decide your default. Make the rostered hours the paid baseline and put it in writing, so workers understand that small clock differences will not change their pay and that genuine extra work will always be approved and paid.
- Set a grace window. Choose a sensible tolerance either side of scheduled start and finish. Inside it, the roster stands. Outside it, the variance is reviewed.
- Capture clock evidence. Use GPS-stamped clock-in and clock-out so attendance is provable, both for payroll fairness and for funding and audit purposes.
- Route exceptions to a manager. Overtime, cut-short shifts and late arrivals should all reach a person with context before the pay run closes.
- Keep the record. Log the scheduled time, the actual time, the variance and the approval decision. This is your defence in any audit and your data for spotting patterns.
Handled this way, "rostered versus clocked" stops being a source of quiet cost or quiet unfairness. You pay from a baseline everyone agreed to, you catch and pay every genuine extra hour, and you leave clock drift where it belongs, which is out of the pay run.
Stop paying for clock drift
CareIQ defaults pay to rostered hours, auto-flags late clock-ins, and routes overtime and cut-short shifts to managers for approval, so every pay run is fair, funded and audit-ready.
Start Your Free TrialFrequently Asked Questions
Should care providers pay rostered hours or clocked hours?
Most well-run care providers default pay to the rostered hours and treat any material difference from the clock as an exception that a manager reviews. Rostered hours are the agreed, published shift times, so they are the fairest and most predictable baseline. Clock times still matter because they are the evidence of attendance, but small clock drift of a minute or two either side of the shift should not change pay on its own.
What is clock drift and why does it cost money?
Clock drift is the small, everyday gap between when a shift is scheduled and when a worker actually taps clock-in or clock-out. A worker who clocks in six minutes early and clocks out eight minutes late has added roughly a quarter of an hour of unapproved time. Across a large roster that drift compounds into thousands of dollars of unbudgeted wages each pay run, none of it deliberate and none of it reflecting extra work that a manager asked for.
Is it legal to pay rostered hours instead of clocked hours in Australia?
Yes, provided workers are paid for all hours they are actually required to work. Paying to the roster is compliant when genuine additional work is captured and paid through an exception or overtime approval process. What is not acceptable is using the roster to quietly strip time a worker was directed to work. The safeguard is a documented review of every material variance, so approved extra time is always paid and casual clock drift is not.
How should providers handle late clock-ins?
Late clock-ins should be flagged automatically against the scheduled start and the company grace window, then reviewed. A worker who arrives inside the grace period is treated as on time. A worker who arrives outside it should have the shortfall visible to the manager, who decides whether to dock the time or accept a reason such as a handover overrun. Automating the flag removes the guesswork and creates an audit trail.
What counts as an exception that a manager should approve?
The two most common exceptions are overtime, where a worker legitimately stays beyond the rostered finish because care could not be safely handed over, and cut-short shifts, where a shift ends early. Both change pay away from the rostered baseline, so both should require a manager to review the variance and approve or adjust it before the pay run. Late arrivals outside the grace window are a third exception worth reviewing.