Rosters, Grace, Rounding & Exceptions

The roster says what was expected. Grace and rounding tidy the punches around it. Exception codes flag whatever still doesn’t match.

This page is a glossary rather than a how-to. It’s here so the terms on your timesheet make sense, and so you can tell us how your business wants these handled.

Every example uses a nine-to-five day. Your own thresholds are set with the biotime team to match how you actually run, so treat the numbers as illustration.

A weekly timesheet approval screen showing Wed to Fri, annotated: 1 the paid time biotime displays after grace and rounding, 2 the raw clock punch in brackets that produced it. Thursday shows In 09:00 (08:44); Friday shows In 08:15 (08:22). Beneath each day, the paid segment 09:00-17:00 and the ORD total for the day.

1 the paid time after grace and rounding  ·  2 the raw clock punch that produced it

The order things happen in

Each step hands its result to the next, so the sequence matters more than any single setting.

1

The roster sets the expectation

A shift with a start, a finish and a break. Everything after this is measured against it.

2

Grace and rounding tidy the punches

Grace forgives small differences against the roster. Rounding tidies what’s left to a sensible interval.

3

Exceptions flag what’s left

Anything still outside the expected window gets a code for a manager to review.

Grace and rounding never both act on the same punch. A punch inside grace becomes the rostered time and rounding doesn’t run on it — which is why a slightly early clock on usually produces no exception and no odd minutes.

Ways a roster gets built

Most sites use more than one method. What they share is the output: a shift on a date for an employee, which grace, rounding and exceptions all measure against.

MethodWhat it’s forProduces a shift?
Master RosterConsistent, repeating patterns — a nine-to-five week, or a longer rotating cycleYes
Ad hoc segmentA one-off shift with a start and finish, entered directlyYes
Auto rosterbiotime matches the employee to a shift — early, afternoon, night — based on when they actually clocked onYes, once matched
PlannerDrag and drop open shifts onto people or groups. Useful for casual workforces and shifts you can’t assign in advanceYes
Work PatternContracted hours per day rather than shift times. Common for salaried staffNo

Any of these can be adjusted for one employee afterwards, however the shift was created.

That last column matters more than it looks. Grace and the early and late codes are measured from a shift’s start and finish, so they need a shift to exist at all. Rounding doesn’t, which is why hours on a day with no shift still land as tidy figures.

GraceRoundingEarly / late codes
Day with a rostered shiftAppliesAppliesApply
Day covered only by a Work PatternNoAppliesNo — the day reads as unrostered
Unrostered dayNoAppliesNo Roster instead

Grace

Grace is a window either side of a rostered time where a punch is treated as if it happened at the rostered time. It exists so a few minutes’ difference doesn’t generate work for anyone.

A rule sets how far before the rostered time it reaches and how far after. Clock-on and clock-off usually get different rules.

Clock on at 08:52, inside the window, and you’re paid from 09:00.

Clock on at 08:25, outside it, and you’re paid from 08:25.

Grace on a nine-to-five day. The grace window runs for 22 minutes before the 09:00 start. A punch clocked at 08:52 falls inside it and becomes 09:00, paid from the rostered start. A punch clocked at 08:25 falls outside it and stands at 08:25.

Grace decides what gets paid. It doesn’t decide whether an exception code appears — those are separate thresholds, which is why the two are set up together.

Rounding

Rounding moves a time to the nearest interval once grace has had its turn. It’s what makes a timesheet readable instead of a column of odd minutes.

A rule has an interval and a pivot — what it rounds to, and the point where it starts rounding up rather than down.

A dial showing a fifteen-minute rounding interval with the pivot at seven minutes. A light blue arrow labelled back sweeps from the pivot to the 00 mark, and a dark blue arrow labelled forward sweeps from the pivot to the 15 mark, showing which way times move either side of it. Worked examples: 17:05 falls before the pivot and becomes 17:00, while 17:10 falls from the pivot and becomes 17:15.

Smaller intervals stay closer to the punch — six minutes lands on tenths of an hour, fifteen moves times further but reads more simply. Rounding can be set separately for clock-on, clock-off, breaks and transfers, and can behave differently on rostered and unrostered days.

Exception codes

An exception is biotime telling you a punch didn’t match the roster, and by how much. Codes exist so nobody has to read every timesheet — you look at what’s flagged.

They sit on a ladder either side of the rostered start and finish, and the colours follow severity. They also mirror: clocking on early and clocking off late both add time, while clocking on late and clocking off early both take it away.

Exception windows drawn to true scale in two panels, one around the 09:00 roster start and one around the 17:00 finish, both at the same scale with the middle of the shift omitted. Around the start: In Very Early runs up to 08:30, In Early from 08:30 to 08:38, no code from 08:38 to 09:00, In Late to 09:15, then In Very Late. Around the finish: Out Very Early up to 16:45, Out Early to 17:00, no code for seven minutes, Out Late to 17:30, then Out Very Late. In Very Late and Out Very Early are joined across a jagged break marking the middle of the shift, left out to fit. A light blue bar beneath runs continuously from the start to the finish. The legend lists the codes in two groups, clock on and clock off, split into before and after each boundary and ordered outward from it — the mildest code first, the most serious last.

The windows that catch almost every punch are the narrow ones close to the boundary. Clock on after the rostered finish and biotime stops treating it as lateness and records the day as No Roster instead.

Exceptions cover more than clock-on and clock-off. Others catch breaks that are missing, unscheduled, short or exceeded, plus missing punches, absence, working outside a geofence, and conditions such as insufficient rest between shifts.

The Exceptions panel on the biotime dashboard, listing each code with a count beside it: Absent 24, In Very Late 1, Missing In 1, Missing Out 2. In Very Late is expanded to show the employee behind it, then the date behind that. Missing Out is expanded to show its two employees.

What we’ll ask you

You don’t need to arrive with numbers. These are the decisions the setup turns on, and they’re much easier to answer in your own words than in ours.

  • How early can someone clock on before it stops counting as their rostered start? How late?
  • Should the end of the day get the same tolerances as the start? Usually not — people arrive early far more often than they leave late.
  • What interval should times round to, and does that differ for breaks?
  • Which exceptions do you actually want to see, and what do you call them?
  • What should happen when someone works a day they weren’t rostered for?

Glossary

TermMeans
PunchA single clocking event — on, off, break start or break end
SegmentA block of time on a timesheet, produced from punches and the roster
RosterThe shift an employee was expected to work on a date
Ad hoc segmentA one-off shift entered directly rather than generated from a pattern
GraceA window where a punch is treated as if it happened at the rostered time
RoundingMoving a time to the nearest interval, using a pivot to decide up or down
PivotThe point inside a rounding interval where rounding switches from down to up
ExceptionA flag showing a punch didn’t match the roster, with a code naming how
Unrostered dayA day worked with no roster to measure against
ApprovalA manager accepting or declining flagged time so it can be paid

FAQ

An employee clocked on early and nothing was flagged. Why?

They were inside the grace window, so the punch was treated as if it happened at the rostered start. That’s grace working as intended.

The timesheet shows a different time from the clock. Is that wrong?

Usually not. The clocked time is what happened; the paid time is what your rules produce after grace and rounding. Both are kept, so the original punch is always there to look at.

Why did two employees clocking at the same minute get different codes?

Their rosters differ. Every threshold is measured from the rostered start and finish, so the same clock time can be early against one shift and late against another.

What does No Roster mean?

The punch was too far from any rostered shift for biotime to treat it as a very early or very late arrival. It usually means someone worked a day they weren’t rostered for, or a roster is missing.

Do exceptions stop someone being paid?

Not by themselves. An exception flags time for review. Whether that time needs approval before it pays depends on how your site is set up.

Need a hand?

Our support team knows biotime inside out. Send us a message and we’ll get back to you, usually within one business day.

Prefer to call? AU 1300 139 460  ·  NZ 0800 111 438
From overseas: +61 7 5613 2700  ·  +64 9 820 3444
Monday to Friday, 8:30am – 5:00pm (AEST/NZST)

Scroll to Top