Scheduled roster automation | BondiByte NDIS Software
Smart Rostering

The roster that advances itself.

BondiByte can run each roster period through the cycle on its own timing, instead of waiting for someone to start.

Scheduled roster automation loop

What you get with Scheduled roster automation.

  • Scheduled, per-period automation

    Each roster period moves through the cycle on its own timing, instead of waiting for someone to kick it off.

  • Publish reminders to managers

    Managers are nudged at the right moment to review and publish, so nothing stalls.

  • Owners govern automation use

    You decide how much runs automatically, with full control to dial it up or down.

Why it exists

The problem it solves.

Somebody has to remember to build next fortnight's roster, and everything downstream waits on them. When that person is on leave, the cycle slips: shifts are created late, staff find out their hours at the last minute, and managers publish under pressure. A roster cycle this regular should not depend on anyone's memory.

How it works

1

Set the timing once

Decide how many days before each period the cycle steps should run: creating the shifts, opening staff interest, generating the draft roster, and publishing. The defaults give three weeks of lead time.

2

Each period advances itself

On schedule, BondiByte prepares the next roster period, creates its shifts from your pattern, opens interest where you use it, and generates draft assignments, site by site.

3

Managers are told at the moments that matter

Emails go out when a period's shifts have been created and when draft assignments are ready, each linking straight to the right site and period on the roster.

4

The review gate holds

By default nothing publishes without a manager reviewing it. Auto-publish exists, but only for sites where you deliberately turn it on, and you can be notified whenever it runs.

5

Reminders that refuse to be ignored

If a roster sits unpublished, the site manager is reminded on your schedule, and after your set number of reminders the nudge escalates to organisation admins so the period never quietly stalls.

What you can do.

A cycle that runs on your calendar

Every roster period moves through the same steps on the timing you set, aligned to your fortnight or month.

Per-step lead times

Separate days-before settings for creating shifts, opening interest, drafting assignments and publishing.

Milestone emails with links

Shifts created and draft ready notices land in the manager's inbox with a one-click path to the exact roster.

Publish reminders with escalation

Unpublished rosters trigger reminders to the site manager, escalating to admins after the count you choose.

Run now, on demand

Trigger the next automation step manually when you do not want to wait for the schedule.

A visible run history

See what automation did, when, and for which site and period, so the cycle is never a black box.

The BondiByte Smart Rostering control centre
Automation timing, review gates and site enablement in one place.

You stay in control.

Review before publish, by default

Manager review is the standing gate. Auto-publish is opt-in per site, and you can require a notification every time it acts.

Reminder settings are yours

Choose the lead time and how many reminders go to the site manager before admins are brought in.

Site-by-site adoption

Run full automation at stable SIL sites while other sites stay manual. Each site opts in separately.

Governed by your automation allowance

Automation work draws on your plan's automation capacity, so usage is visible and governed rather than open-ended.

Learn how to use this feature.

Frequently asked questions.

Will a roster ever publish without us seeing it?

Not unless you switch auto-publish on for that site. The default requires a manager to review and publish, and auto-publish can notify you every time it runs.

Can we change the timing?

Yes. Each step has its own days-before setting, so you control how early shifts are created, when interest opens, and when drafts are generated.

What happens if a manager misses the publish reminders?

After the number of reminders you configure, the reminder escalates to your organisation admins, so a period cannot stall silently.

Can we trigger a step manually?

Yes. You can run the next step on demand rather than waiting for its scheduled day.

How is automation usage controlled?

Automation runs within your plan's automation capacity, and you can see the run history for every site and period, so the amount of automation is always a choice you have made.

See Scheduled roster automation in BondiByte

Start your free trial, or book a demo to see it with your own operation in mind.

Start free trial