Compliance & Governance
Code of Conduct
Know what was acknowledged. Follow through on concerns.
Review the current Code version, worker acknowledgements, linked learning and conduct case records.
Residential care · Home care
In practice
The work behind code of conduct.
Keep the published Code version and its acknowledgement records visible to your team. Statura separates acknowledgement, linked training and follow-up so one completed step does not stand in for the others. For a conduct concern, maintain the allegation, investigator, notes, findings and corrective actions in the case record.
A signed acknowledgement does not show that training is complete or that a concern has been resolved. Governance and workforce teams need to see these records separately, then follow up the people and cases that need attention.
Current published version
Review the current Code policy version and its publication record. The workspace identifies when no current version has been published.
Acknowledgement and assignment status
Review recorded acknowledgements and assignments for the current Code. Earlier acknowledgement history is kept separate and does not, by itself, establish current-version completion.
Linked learning
Where learning is linked to the Code, review training due and completed separately from acknowledgement. See the count of workers who have acknowledged the Code but still have training due.
Conduct case records
Review the allegation, worker, investigator, investigation notes, findings, corrective actions and outcome. Investigator selection excludes the accused worker; your team remains responsible for a fair investigation.
Case status and incident context
Follow the case through its recorded status to closure. Closed cases are read-only in this workflow. Where a SIRS incident is already linked, open it from the case to review that separate reporting workflow.
The wider workflow
Where code of conduct connects.
Bring evidence, review and improvement actions into the quality conversation. Inspect a source record instead of relying only on a dashboard status.
A workflow illustration showing the broader operating context.
Explore the product tour
Evaluation
What to inspect with your team.
Bring a representative code of conduct scenario and use these questions to guide your demonstration.
Book a demo with this scenario- Walk through current published version using a representative example.
- Check the permissions and review steps for acknowledgement and assignment status.
- Inspect the records and outputs available for linked learning.
Requirements and responsibilities
The requirements behind the workflow.
Review how these requirements apply to your services and the responsibilities your team retains.
Reference area: Code versions, acknowledgements & concerns
Code coverage
The Code applies to registered providers, their responsible persons and aged care workers, including volunteers and relevant contracted workers. Check the Commission’s guidance for the scope of coverage.
Provider responsibilities
Providers must support and prepare workers and responsible persons to comply with the Code, and take reasonable steps to secure compliance. Records of acknowledgement and learning support that work; they do not guarantee compliance.
Respond to concerns
Review concerns promptly, protect people receiving care and determine any reporting obligations. A conduct case may also involve a SIRS-reportable incident; assess that requirement separately.
Related workflows.
Explore the records and responsibilities that connect code of conduct with the wider platform.
Questions about code of conduct.
Does an acknowledgement also mean training is complete?
No. The current Code workspace separates acknowledgement, linked learning and follow-up. A worker can have acknowledged the Code while still having training due.
Do earlier acknowledgements count for the current version?
Earlier records are available as history. They do not, by themselves, establish completion for the currently published Code version. Review the current assignment and acknowledgement records.
What can we record for an alleged breach?
The case record includes the allegation, investigator, investigation notes, findings, corrective actions and outcome. The investigator must differ from the accused worker. Your team determines the investigation steps, ensures fairness and assesses any external reporting obligations.
Does recording a conduct case notify the Commission?
No. Recording the case is separate from external reporting. Where a SIRS incident is already linked, the case provides a route to that incident record; your team assesses reportability and completes the required notification.
See Code of Conduct in action.
Bring a code of conduct scenario. We’ll walk through the relevant records, review steps and scope for your organisation.