All guidesRunning your team

Rolling out a policy your team actually reads, and knowing who has signed it

A folder of policies isn't the same as a team that has read them. How to publish a new or updated policy and know, at any moment, who has acknowledged it.

The Tasklith Team16 November 20262 min read

Most practices have the policies. Privacy, incidents, complaints, safeguarding, work health and safety. The harder part is showing that each person has read the current version, especially after an update.

Where a small practice usually starts

  • Privacy and confidentiality, including how client records are kept.
  • Incident management: what gets recorded and who is told.
  • Complaints and feedback.
  • Work health and safety, including working alone and home visits.
  • Code of conduct.
  • Child safety, if you see children.

Your professional body, your insurer and, if you're a registered NDIS provider, the NDIS Practice Standards will shape what else you need. Get advice on the content. This guide is about getting them read.

Publishing a policy so it gets read

  1. Write a two line summary at the top: what the policy is for and what changed since the last version.
  2. Send it to the people it applies to, not everyone. A clinical policy doesn't need to go to your bookkeeper.
  3. Ask each person to acknowledge it, so you have a record with a date.
  4. Follow up the people who haven't, a week later, by name.
  5. Talk about it at the next team meeting, briefly, with a real example.

Making a policy readable

Short paragraphs, plain words, and the steps someone actually takes written as a numbered list. A policy that reads like a contract gets signed without being read. One that reads like a procedure gets used.

When a policy changes

Update the version, say what changed in plain words, and ask for acknowledgement again. An old signature on an old version doesn't tell you the team knows the new rule.

What to keep

  • The current version, and the date it was published.
  • Who has acknowledged it, and when.
  • Who hasn't yet.
  • The date it's next due for review.
The question is never "do we have a policy?" It's "who has read this version?"

Where Tasklith fits

In Tasklith's People module, you publish a policy and your team reads and acknowledges it from their own HR page. You see an acknowledgement list for each policy, with who has and who hasn't, and you can export it when someone asks.

See how Tasklith helps your team

One platform for content, participants, compliance and more.

Explore features