Skip to content
Corella

Rostering & attendance

Build the week once — Corella carries it from there.

Rostering is where a care business wins or loses its week. Corella's board is built for the real thing — group shifts, sleepovers, recurrence, cancellations with the right NDIS codes — and everything that happens on shift flows straight through timesheets into payroll exports, without being typed twice.

How it flows

Rostering flow: a shift is created with conflict checks, assigned or offered first-wins on the job board, clocked on with GPS, clocked off with kilometres and travel time, then approved in bulk from the timesheet queue — and copy-week rolls the roster forward.notify togglestasks + note gate itone screen, one clickcopy week rolls it forwardShift createdconflicts checkedAssignedjob board — first winsGPS clock-onwindow + graceClock-offkm + travel togetherTimesheet queuerostered vs clockedApprovedbulk · scheduled or actual

Conflicts are caught at the board, the record completes itself on shift, and next week is one copy away.

A board that shows you the whole week

Roster by staff or by client, create a shift from any cell, and let recurrence do the heavy lifting — weekly or fortnightly patterns materialise months ahead, and 'copy week' carries a good week forward. Group shifts split billing equally across clients; sleepovers and multi-staff ratios are first-class, not workarounds.

Staff & client viewsGroup & recurring shiftsSleepoversCopy week
your-organisation's Corella
Corella's week rostering board with colour-coded shifts
The week board — quick-create from any cell

Conflicts that explain themselves

Double-bookings, approved leave, weekly-hour caps, compliance gaps and client-blocked staff are all caught as you roster — each warning says what's wrong and why. Overriding is allowed, deliberate, and leaves a trail. Cancellations are a proper flow too: provider or client, with short-notice billable handled under the correct NDIS codes.

Conflict checksExplicit override trailNDIS cancellation codes

Clock-on that protects the shift record

Carers clock on and off from their phone with GPS capture, inside a configurable clock-on window. If a shift has must-do tasks or requires a progress note, clock-off waits until they're done — so the record is complete when the shift ends, not chased on Friday. Open shifts go to a job board where available staff take or apply for them.

GPS clock-on/offTask & note gatesOpen-shift job board

Telling people — email notifications, and text broadcasts

A shift that changes is only useful if the person working it finds out. Corella notifies staff in the app and by email, and each person chooses which categories reach them. Text messaging is a different tool and worth being precise about: it is a **broadcast** you write and send to a group, not something that fires by itself — nothing texts a carer automatically when their shift moves, and if that is what you need, say so on the call rather than assume it. Both channels are included in your plan and activated when you go live. Every text names your organisation in its first words so nobody gets an anonymous message, carries “Reply STOP to opt out”, and honours a STOP from then on. A broadcast is capped at 500 recipients, and it records what the provider accepted per recipient — not what was delivered, because there are no delivery receipts and we will not pretend there are.

In-app & email notificationsText broadcasts, not triggersPer-person categoriesSTOP honoured

Change a run of shifts — and see what it refuses to touch

Somebody goes on leave, a service gets renamed, a house changes address. Pick a staff member or a participant and a date range, and change one thing across the run: who is on it, which participant, the service, the times, where it happens, or an allowance. Both ends of the range are required, because an open-ended sweep would quietly move next winter's roster. Before anything is written you get a count and a review table listing every shift it will NOT touch and why — and that list is the point. It refuses anything where money has already moved: invoiced, in a payroll batch, already worked, clocked on. On the staff axis it also refuses a shift carrying a pay-group override or a hand-attached allowance, because handing those to someone else pays them on an agreement nobody chose for them. Those rows are named, and the office moves them by hand. And on the times axis the confirmation reads twenty-five hours will change to forty-two — because changing times changes hours, and hours are pay, so you confirm the number you are actually agreeing to.

Six things you can changeNames what it skips, and whyRefuses invoiced & paidHours shown before you agree

Timesheets approved from one screen

The timesheet queue shows rostered versus clocked side by side, flags the variances, and lets you approve scheduled or actual times in bulk — tick, approve, done. Times are precise to the minute, and editing a time simply reopens the approval so nothing slips through half-checked.

Variance at a glanceBulk approval1-minute precision
your-organisation's Corella
Timesheet approval queue showing rostered versus clocked times
Rostered vs clocked, approved in bulk

Travel time, claimed when it actually happens

At clock-off — never before clock-on — carers log their kilometres and travel minutes together. The timesheet queue shows both for review, and approved travel pays automatically as its own payroll line at the shift's rate, flowing into the same payroll export. One system means the kilometres you pay are the kilometres you bill.

Km + minutes at clock-offTravel payroll linePaid = billed

Go deeper

Rostering intelligence, built in.

Three capabilities that live on the same week board — award rules and arithmetic a coordinator can check by hand, not a black box. No module to buy, no switch to flip.

Fair questions

Asked about this, often.

Can carers log travel before the shift?
They don't have to — and that's deliberate. Kilometres and travel minutes are claimed at clock-off, when the numbers are real. Nothing blocks a carer from starting their shift.
What can block clock-off?
Only what you configure: must-do tasks and mandatory progress notes. If a shift requires them, Corella holds clock-off until they're done, so the shift record is complete the moment the shift ends.
How do recurring shifts work?
Weekly or fortnightly patterns materialise about six months ahead as real, editable shifts. Change one, or change 'this and future' — both are one action.
Does Corella interpret the SCHADS award?
Corella's payroll engine uses simplified, clearly-labelled pay bands — weekend and public-holiday multipliers, sleepover rates, kilometres — and exports a CSV your payroll software imports. Pay execution and full award interpretation stay with Xero/MYOB and your payroll process, and we're upfront about that.

See your organisation in Corella.

A 30-minute walkthrough with the people who built it — your workflows, your terminology, not a canned demo.