Guides4 min read

How often should you review your policies, and what counts as a review?

Review each policy on a cycle you set and write down, sooner for higher-risk procedures, and straight away when something changes. A review counts when it is dated, attributable and ends in a decision. Here is how to set it up.

The Accorda Team · 20 November 2026

Photo of a printed policy document with a pen and reading glasses on an office desk beside a laptop

Review each policy on a cycle that you set and write down, sooner for the procedures that carry the most risk, and bring a review forward whenever something changes, such as the rules, an incident, an audit finding or the way you deliver the service. A review is only useful as evidence if it leaves a record: who reviewed the policy, on what date, what they checked it against, and what they decided, even when the decision is "no change".

The standards your service is audited against, such as the aged care Quality Standards or the NDIS Practice Standards, expect policies and procedures that are current and followed, and an auditor will ask how you know yours are. How often you review each document is generally a decision for you to make and be able to justify, unless your regulator sets a period for a particular document. What applies to your service changes over time, so confirm it with the Aged Care Quality and Safety Commission or the NDIS Commission.

Give each policy its own review date

Reviewing every policy on the same day once a year sounds tidy, but it creates one large job that slips, and it treats a medication procedure the same as a dress code. A pattern that holds up better:

  • Give each policy its own review date, written on the document and in your policy library.
  • Weight the interval by risk. Procedures that protect people from harm, such as medication assistance, incident reporting or anything involving a restrictive practice, should be reviewed more often than administrative ones.
  • Write the rule down. The policy that governs your other policies should say how review intervals are set, so every review date follows a rule rather than a guess.
  • Spread the dates out, so a few reviews fall due each month instead of all at once.

When to review early

A review date is the latest a policy should go unchecked, not the only trigger. Bring a review forward when:

  • the law, a standard or your regulator's guidance changes;
  • an incident or complaint shows the procedure was unclear, unworkable or not followed;
  • an internal or external audit raises a finding against it;
  • you add a service, a site or a new kind of work;
  • something the procedure names changes, such as a role title, a contact number or a form.

A change in the rules is easy to miss if nobody is watching for it. Whatever the source, record which policies you checked against the change and what you decided, so the review is on the record even when nothing needed to change.

What counts as a review

Opening a document and saving it with a new date is not a review. A real review means someone with the right knowledge read the policy against what it is meant to achieve, and made a decision. A review worth keeping records:

  • Who reviewed it, and their role.
  • The date.
  • What it was checked against: the current standards, recent incidents, complaints and audit findings, and how the work is actually done.
  • The outcome: no change, minor edits or a substantial rewrite, with the reason.
  • Who approved it, if that is a different person.
  • The next review date.

Keep the earlier version. When an auditor asks what the procedure said on the day of an incident last year, the answer should come from the record, not from memory.

After the review, make sure staff know

A policy that has changed but that nobody has read again is still the old policy in practice. When a review leads to a real change, ask the people it applies to to read and acknowledge the new version, and check that the acknowledgements come in. Where understanding matters, as it does for a medication procedure, a few questions on what changed show more than a signature does.

Decide in advance whether a small correction, such as a typo or a new contact number, needs everyone to acknowledge the document again, or only a real change does. The policy that governs your policies should say where that line sits, so the decision is consistent rather than made fresh each time.

Common ways a review cycle goes wrong

  • Every policy falls due on the same date, and the job never gets done.
  • The review date changes but nothing was checked.
  • A change in the rules is noticed months later, at audit.
  • The policy is updated but staff are never asked to read it again.
  • The old version is overwritten, so nobody can show what applied before.

How we help

In policy management, every version of every policy is kept, dated and attributable, and every review and change is timestamped and SHA-256 signed. Accorda reviews each policy against the standards for your sector, flags gaps and can draft updates for you to consider; a person approves every change. Regulatory Radar shows which of your policies a regulatory change affects, and records your review decision and who made it.

When a new version is published, the people in the right staff groups are asked to sign it again, with an optional policy quiz before they sign, and the AI assistant can tell an admin which policies are due for review.

For how this fits with the rest of your compliance system, see the aged care page, or the NDIS page if you are an NDIS provider. What your regulator expects of your policies in detail can change, so confirm it with the Aged Care Quality and Safety Commission or the NDIS Commission.

Start today

See your compliance audit-ready in one place

Try Accorda free for 14 days. Every feature, no credit card, no auto-charge.