← All guides

Configuration

Set the rhythm every roster runs on.

Rostering rules define the roster period calendar for the whole organisation, optional end-of-period draft timesheets and invoices, and the organisation-wide clock-in defaults that sites can override.

Overview

Rostering rules hold the tenant-wide roster calendar and the automation that hangs off each period's end.

The section also hosts the full Smart Rostering workspace, including scoring weights and capability requirements.

Before you begin

  • Know your current rostering fortnight or month so the first period start date lines up with it.
  • Check Automation Capacity: draft timesheet and invoice generation are capability-gated features.

Recommended setup order

  1. Open Configuration and select Rostering rules.
  2. Turn on automatic roster periods, pick a Sunday or Monday start date, and choose 2 weeks or 1 month.
  3. Enable automatic draft timesheets and set how many hours after period end they generate.
  4. Enable automatic draft invoices where shift billing line items are in use.
  5. Set clock-in and geofence defaults, then save the section.

Key fields and settings

First period start date

Only Sundays and Mondays can be chosen. The weekday you pick becomes the rostering week start for the whole organisation.

Period size

How long each standard roster period covers: 2 weeks or 1 month.

Period lock

Once smart rostering or automation is active, the start date and period size lock. Turning off all smart rostering and automations on every site unlocks them.

Automatic draft timesheets

Creates draft timesheets from rostered shifts after each period ends. Staff still review and submit; managers still approve or return.

Automatic draft invoices

Creates draft client invoices from approved shift billing line items after each period ends. Invoices stay editable and are never sent automatically.

Clock-in default

The organisation-wide default for mobile clock-in and clock-out. Individual sites can still turn it on for themselves, and geofence checks use each site's saved location.

Best practice

  • Line the first period start date up with your live rostering period before saving.
  • Give draft generation a small delay after period end so late shift edits land first.
  • Turn on the staff email for draft timesheets so people know a draft is waiting.

Common mistakes to avoid

  • Setting the anchor date casually: changing it after automation runs is a heavy change that resets every cycle.
  • Expecting draft invoices without shift billing line items: drafts build from shift billing.
  • Enforcing the geofence for community-access work where staff legitimately start away from the site.

Need help applying this setup path?

Book a BondiByte demo and we can walk through the right setup order for your provider.

Start free trial