Skip to content
Corella

Staffing & funding forecast

See the underspend while there's still time to fix it.

Under the NDIS, the expensive failure usually isn't a plan running out — it's a plan finishing with money unspent. That underspend is support the participant never received, and a reason the next plan may be cut. Corella projects every active plan forward and raises the flag while there's still time to do something about it.

How it flows

Forecast flow: the roster, active service agreements and the price book are projected forward — priced exactly the way the invoice will price them — into per-plan funding with burn rate, exhaustion date and projected underspend, and staffing demand against leave-adjusted capacity week by week, with funding alerts pushed by the daily sweep.arithmetic, checkableprojected underspendshortfall, weeks outalerts arrive dailygaps named by weekYour live dataroster · agreements · ratesProjected forwardpriced like the invoicePlan fundingburn rate · underspendStaffingdemand vs capacityAct in timenot at plan review

A plan that ends with money unspent is support never delivered — and a reason the next plan may be cut. This flags it early.

The underspend, while it's still fixable

For every active service agreement: invoiced to date, the value of shifts already rostered ahead, the daily burn rate, the projected total, the projected exhaustion date — and the projected underspend, the figure that matters most. A burn-down strip sits on each client's funding tab, and the daily sweep pushes funding alerts to the office, so the forecast arrives instead of waiting to be looked at.

Projected underspendExhaustion dateDaily burn rateAlerts arrive daily

Priced the way the invoice will price it

Committed work is valued exactly as invoicing will value it — split across time bands, honouring per-client price overrides and group-shift splits — so the forecast and the eventual invoice agree. And where a forecast can't be honest, it says so: per-kilometre and per-item services need actuals, so they're excluded and labelled excluded rather than guessed.

Time-band splittingClient price overridesGroup splitsPer-km excluded — and said

Staffing demand against real capacity

Week by week for the next four to twelve weeks: rostered hours, unfilled hours, and what's still likely to be scheduled based on your own eight-week pattern — pro-rated by how much of each week remains. Capacity comes from each staff member's weekly cap less approved leave, so the shortfall you see is the shortfall you'll actually feel, named weeks before it lands.

4–12 week horizonYour own 8-week patternLeave-adjusted capacityShortfall by week

Revenue in three honest layers

Month by month, split into invoiced, delivered-but-not-yet-invoiced, and rostered-ahead — so the gap between work done and money banked is visible, and next month's number is grounded in shifts that actually exist rather than optimism.

InvoicedDelivered, not invoicedRostered ahead

Fair questions

Asked about this, often.

Is the forecast AI?
No. It's arithmetic over data you already own — the roster, active service agreements, the price book and your own eight-week scheduling pattern. Any figure on the screen can be checked by hand, and finance people do.
Why lead with underspend instead of running out?
Because under the NDIS, underspend is the common and expensive failure. A plan that ends with money unspent is support the participant never received — and at review time it reads as evidence the funding wasn't needed. Overspend announces itself; underspend hides until it's too late to deliver. So the forecast leads with it.
Why are travel and per-item services excluded?
They depend on actuals — kilometres actually driven, items actually supplied — and a forecast that guessed them would be wrong with confidence. Corella excludes them and says so on the screen, so every number you do see is one that can be defended.
What does it need from us to work?
Nothing new. It reads the roster, the service agreements and the price book you already keep — and the scheduling pattern comes from your own history. If those are current, the forecast is current.

See your organisation in Corella.

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