Policy Attestation Software for Aged Care: Provider Guide

A policy is useful only when the people who need it can find it, understand it and apply it. Policy attestation software helps an aged care provider record which worker acknowledged which version, and identify assignments that still need attention.

An acknowledgement is evidence of a recorded response. It does not, by itself, prove understanding, competence or compliant practice. A sound process brings policy records, training, supervision and follow-up together.

Policy attestation is a recorded acknowledgement of a specified policy. A useful record identifies the worker, policy title, version, acknowledgement statement and date. It should remain possible to distinguish an acknowledgement of an old version from the current assignment.

Keep three questions separate: Was the policy acknowledged? Was the relevant training completed? Can the worker apply it in practice? Each needs its own evidence. A signature cannot answer all three.

The Aged Care Code of Conduct applies to registered providers, their aged care workers and responsible persons. Its requirements cover individual rights, dignity, privacy, safe and skilled care, integrity, action on concerns, and preventing and responding to abuse and sexual misconduct. See Part 5 of the Aged Care Rules 2025.

The Commission’s provider guidance describes training, support, supervision and monitoring that help workers understand and apply the Code. A provider’s policy acknowledgement process can support that work.

Set and document acknowledgement deadlines in your induction and policy procedures, reflecting the applicable duties and risks. Do not describe an internal 30-day target as a universal Code signature deadline. An acknowledgement schedule also does not postpone a worker’s conduct obligations.

Build an assignment matrix around responsibilities, service setting and the work people actually perform. Candidate topics include the Code of Conduct, privacy, incident reporting, complaints, whistleblowing, infection prevention and workplace safety, with clinical procedures assigned to relevant roles. This is a planning list, not a universal statutory signature checklist.

For agency workers, contractors and volunteers, agree who provides the induction, what provider-specific information is needed and where evidence will be held. Assign an owner to resolve gaps rather than assuming another organisation has covered them.

1. Identify the required version. Record the approved policy, its effective date and the intended audience.
2. Make it accessible. Give workers time, access and an opportunity to ask questions. Provide language or accessibility support where needed.
3. Teach the relevant practice. Use discussion, examples and appropriate competency checks alongside reading.
4. Record the acknowledgement. Retain the worker, version, statement and completion date.
5. Review outstanding work. Give a manager responsibility for follow-up and record the action taken.

For example, a changed incident procedure may need a short team briefing and a practical discussion about escalation, as well as acknowledgement of the updated document. Completion of one step should not silently mark the others complete.

When a policy changes, decide which roles are affected, what needs to be explained and whether a new acknowledgement is required under your process. Retain the prior version and its evidence while making the current assignment clear.

Apply the same review when a worker changes roles or service settings. When employment ends, remove the worker from active follow-up through the appropriate process while retaining records under your retention requirements. Historical evidence should not disappear to improve a completion percentage.

An outstanding item is a prompt to investigate. Check whether the person can access the document, understands the request, is on leave or has raised a question about the policy. Record the barrier, responsible manager and next action.

Address any immediate care or safety risk promptly. An overdue acknowledgement alone does not establish misconduct or an automatic disciplinary outcome. Escalate unresolved matters through the provider’s applicable HR process, with individual circumstances considered.

A useful management view separates current assignments, completed acknowledgements, overdue work and historical versions. Define the population and reporting date so that a headline completion rate can be explained.

Ask the supplier to walk through a policy being revised after workers have acknowledged it. Can you see the old evidence, the new assignment and who still needs to respond? Then test a worker changing role and an assignment that cannot be resolved.

Check role access, version history, the meaning of completion statuses and the evidence available for review. Ask how reminders, escalation and reporting work in the proposed configuration. Do not assume every product automates the same steps.

Use the software evaluation workbook to record the demonstration, unanswered questions and agreed follow-up.

Statura’s worker policy view separates outstanding current-version assignments from historical acknowledgements. Prior-version evidence remains visible and does not count as a current acknowledgement. The policy library supports worker-facing version records; publication and assignment are handled through the Policies & Conduct workbench. Publishing a governance policy is a separate operation and does not itself create a worker acknowledgement assignment.

That distinction helps your People team manage what workers are being asked to acknowledge while preserving the evidence behind earlier responses. Explore workforce and HR software, then book a demonstration using a policy update from your own operating process.

Editorial review: 25 September 2026. Use the linked official sources for the applicable regulatory requirements; provider procedures and software configuration need their own review.