Loading this page
Opening the page. The page structure is ready while the last details arrive.
Neo operations OS
Run NDIS provider operations from one connected system
Keep the roster, worker updates, attendance and service records together. Neo is designed to be usable by a small team without specialist software training.
01
Start simply and keep the same workflow as you grow
Neo uses one product and one connected operating model. Start with the defaults, then add sites, teams and organisation structure when the work requires them.
Nothing to configure first
Everything has a working default. Settings are for changing them later, not for reaching a usable state.
Set up without waiting for us
Create your workspace, add people and build the roster without a sales or implementation call.
Grows with you
Add sites, teams and organisation units when you need them while keeping the same connected workflow.
02
The day stays visible without chasing it
Roster changes, open shifts, attendance and service records stay connected across the provider and worker experiences.
One live roster
Coordinators see the latest assignment and workers see the shifts sent to them.
Open work stays open
Unassigned shifts remain visible until a coordinator chooses the right person.
Records stay attached
Attendance, notes and follow-up keep the context of the service that created them.
03
Who sees what
A participant's funding is sensitive. Neo limits it in the database, not just on screen.
Owners and admins
See funded amounts, days of cover and when funding runs out.
Coordinators
Do not see funding status or amounts. An owner may grant one named coordinator access to days of cover, and the grant is recorded.
Support staff
See nothing about funding at all, and that one is not configurable.