Aged care

Workforce compliance for aged care providers, with full HR and training.

Compliance about your workers, not your residents or clients. CORA holds the credentials, the policies, the supervision, the conduct record and the training on one file per worker. Your aged care evidence is held against the Strengthened Aged Care Quality Standards.

Eleven registers and reports export when somebody asks to see them. If you are registered for aged care and disability both, one workforce and one catalogue cover both regulators.

Is CORA built for aged care as well as NDIS?

Both, and the sector is set on your organisation rather than assumed. The worker record, the credential logic, the policy register, supervision, conduct and the audit exports are the same whichever sector you are in. What changes is the instrument your evidence is held against, and the courses your catalogue shows you.

A provider registered in one sector sees that sector. A provider registered in both sees one catalogue covering both, because the catalogue is the overlap of what your organisation is registered for and what each course applies to.

What does CORA hold about an aged care worker?

One file per worker. Role, employment type, start and end dates, and pre-employment checks. The same file carries declared secondary employment, right to work, credentials and their expiry dates, supervision sessions and practice observations. It also carries conduct and the steps taken on it, induction, and policies acknowledged against the version the worker read.

Eleven registers and reports export as CSV. Upload a certificate and CORA reads the printed dates. It never calculates an expiry that appears on no document, and it flags a file that looks like a different credential.

Does the evidence map to the Aged Care Quality Standards?

Yes. Aged care evidence is held against the Strengthened Aged Care Quality Standards, and it is labelled as aged care rather than folded into the NDIS wording. The standards a row satisfies are shown on the row itself rather than in a separate document.

Where a course applies to both sectors, the same completion is evidenced against each regulator's own instrument. The governing instrument, the regulator and the vocabulary change. The worker does the training once.

We are registered for both. Does that mean running everything twice?

No, and this is the case the sector model was built for. One workforce, two regulators, one catalogue containing both. A worker completes a course once and the completion is evidenced against both regulators, rather than being repeated under a second banner.

Your registers do not split either. One export covers the workforce, with each row carrying the standard it satisfies in the sector it belongs to.

Does CORA check the ACQSC banning orders register?

No. CORA holds the checks you run. You record a check against the ACQSC, NDIS Commission and Victorian Disability Worker Commission registers with the date you ran it, so the answer to “how do you know none of your staff is banned” is a dated record on the worker’s file rather than a memory.

The duty to check the register sits with the provider. The ACQSC register page states that registered providers must regularly check it, and CORA is where that check is evidenced rather than remembered.

Does it know aged care roles, or just disability ones?

Aged care roles are named in their own right. A Support at Home worker and a responsible person holding aged care key personnel duties are different roles with different requirements. CORA treats them that way rather than mapping everyone to a single support worker shape.

What a role must hold drives what the record asks for. A new starter's outstanding list is derived from the records you actually hold rather than from a status someone maintains by hand.

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 using your own API key, 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 it cost?

CORA is priced on how many workers you have. For fifteen workers it is $1,425 a year plus GST, which is $95 a seat, stepping down to $21 a seat at a thousand workers.

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. Running both sectors costs no more than running one.

See it on your own structure

Book a demo and we will show you the worker record and the registers with your own roles in them. If you run NDIS as well, see NDIS compliance software.

Request a demo See pricing