A no-show is when someone rostered to work a shift simply doesn't turn up, without giving the business any notice beforehand. It's distinguished from a cancellation with notice, where the person tells the business in advance that they can't make it.

How it's treated operationally

The two events look similar on paper — a shift ends up short a person — but they carry very different operational costs:

• A cancellation with notice gives the business time to react: call down a standby pool, adjust the roster, or accept a smaller crew for that shift.
• A no-show is discovered at or after the shift's start, when there's little or no time left to recover the seat — the business is short-staffed in the moment, often mid-service or mid-shift.

Because of that difference, most reliability systems weight no-shows more heavily than notified cancellations when scoring a worker's track record.

Why it matters

No-shows are the costliest failure mode in a shift-based roster: they're unpredictable, they can't be planned around, and they directly reduce the people available on the floor at the moment they're needed most. Reducing no-shows — through reminders, clear confirmation steps, and fast standby recovery when they do happen — is one of the main operational goals of any rostering system.

Note: whether a no-show affects pay, disciplinary process, or ongoing engagement depends on the employment relationship and applicable law — check current NZ or AU guidance rather than treating this as advice.

In Chronomancer

Chronomancer's reliability formula penalises no-shows specifically, separate from and heavier than cancellations given with notice, and a no-show on the night is a trigger event for dropout recovery — automatically opening the vacated seat to the standby pool via a one-time claim link.