Workforce compliance

Workforce compliance software, with full HR and training.

Compliance about your workers, not your participants. CORA holds the credentials, the policies, the supervision, the conduct record and the training on one file per worker, for Australian NDIS disability and aged care providers.

Eleven registers and reports export when somebody asks to see them. There is one plan and one record, so the HR fields sit on the same file as the course history and nobody reconciles two systems the week before an audit.

What does NDIS compliance software need to do?

Three things, and most products do one. It has to hold the records an auditor asks for. It has to keep them current without someone remembering to check. And it has to show the evidence on demand, in the form the question was asked.

CORA holds the worker half of that. Credentials, policies, supervision, conduct, induction and training sit on one record per person, with eleven registers and reports that export as CSV.

Of the 21 worker records an auditor asks for, CORA gives you a surface for all 21. The workforce audit checklist lists them in the Commission's own wording.

What is workforce compliance, and what sits outside it?

Workforce compliance is what a regulator asks you to prove about the people you employ, rather than about the people you support. Worker screening and credentials, the policies they have acknowledged, the supervision they have had, the training they have done, and whether anyone watched them apply it.

Participant records, plans and incident reporting sit on the other side of that line, usually in your CRM. CORA runs the workforce side and does not try to run the participant side.

The boundary is deliberate. The day CORA's version of a participant record disagreed with your CRM, CORA would be the one that was wrong.

Does it include the full HR record?

Yes, on the same file as the training. One record per worker holds role, employment type, start and end dates, and pre-employment checks. The same file carries declared secondary employment, right to work, qualifications and experience, and the date the record was last reviewed.

Credentials carry their expiry dates, and you choose whether the warning arrives at 7, 14, 30, 60 or 90 days. All ten Human Resource Management indicators are held. See the HR layer in full.

Upload a certificate and CORA reads the printed dates. It never calculates an expiry that appears on no document, because a CPR certificate prints a completion date and no expiry at all.

How does the training evidence compliance?

Every course maps to the NDIS Practice Standards, and the mapping shows on the training register row itself rather than in a separate document. The record also holds why a course was assigned. Training that followed a complaint, an incident or an identified risk still says so after the person who decided it leaves.

Practical sign-off sits on the same record, with its own due date. That second clock is why the register can show you a certificate that is current beside a competency that has lapsed.

The competency finding stays yours. CORA holds the observation and the evidence behind it, and your assessor makes the call.

How do I see where we stand right now?

You look, and the answer is worked out at the moment you look. Outstanding policy acknowledgements and onboarding steps are derived from the records you actually hold, rather than stored as a status somebody has to maintain. When a policy changes, every worker in scope is asked again.

A stored status is what goes quietly wrong. It is right on the day somebody sets it and silently wrong a month later, which is usually the month an auditor asks.

Can it handle several sites and teams?

Yes. Policies are scoped to teams or to everyone, supervision cadence is set per employment type, and the registers filter to the group you are reporting on.

A provider registered for both NDIS and aged care records one completion and evidences it against both regulators, rather than running the same training twice. See aged care workforce compliance.

Do I still need a compliance consultant?

Possibly, and CORA does not replace one. A consultant sells you the policy and the procedure, which CORA never supplies, because your policies stay entirely your own. What CORA holds is what happens after the document exists.

Who acknowledged which version, whether the training built from it was completed, and whether anyone observed the practice.

A template answers whether you have a policy. A register answers whether your workforce is following it.

Does it do payroll or rostering?

No, and that line is held on purpose. CORA keeps records about a worker and never inputs to pay. It reads your roster rather than replacing it.

There is a ready to go integration for ShiftCare, CSV in and out for everything else, and custom built connections against whatever you run. See integrations.

Leave shows where the line sits. A balance belongs in payroll, because the day our number disagreed with payroll, ours would be the wrong one.

What does NDIS compliance software cost?

CORA is priced on how many workers you have. For fifteen workers it is $1,425 a year plus GST, or $140 a month plus GST on a twelve month term.

There is one plan, so the compliance records, the HR record and the course library are included rather than tiered. Full bands are on the pricing page.

See where you stand

Book a demo and we will show you the registers with your own structure in them. Or start with the free checklist and see how many of the 21 worker records you already hold.

Request a demo Free audit checklist