What is an obligations register?

A single spreadsheet listing every dated obligation your organisation has - insurance renewals, worker screening expiries, behaviour support plan reviews, registration and audit dates, policy review cycles and regulator correspondence deadlines - each with an owner, a due date, a renewal cycle and a link to the evidence. Paired with automated reminders, it becomes the safety net that stops things lapsing quietly.

What deadlines should NDIS providers track?

At minimum: all insurance renewals, every worker's screening check and first aid expiry, behaviour support plan review dates, NDIS registration and audit milestones, policy review dates, vehicle and equipment renewals, and any deadline attached to correspondence from the NDIS Commission, your auditor, the public guardian or a tribunal.

Do I need special software for this?

No. A spreadsheet in your existing Microsoft 365 or Google Workspace does the register job, and a lightweight automation tool like n8n or Power Automate handles the reminders. It should all run in your own accounts, so it keeps working through staff changes and you can switch it off whenever you like.

How should the reminders work?

Escalating, not one-off: a heads-up at 60 days before the due date, action-needed at 30 days, urgent at 7 days, and if something goes overdue it escalates and repeats in a weekly digest until it's closed. Reminders should go to at least two people so no single person's inbox is the point of failure.

How NDIS Providers Stop Missing Compliance Deadlines (The Obligations Register Method)

Nobody decides to let their insurance lapse. Nobody chooses to leave a Commission information request unanswered for four months. These things happen quietly, in busy weeks, to good providers - and when we map NDIS organisations' workflows, the same pattern shows up almost every time.

The uncomfortable truth: most NDIS compliance failures aren't knowledge failures. Providers know their obligations. They're deadline failures - a date that lived in one person's head, an email that landed in the wrong week, a renewal that only comes around once a year so nobody has muscle memory for it.

How deadlines actually get missed

Here are the patterns we see repeatedly when we audit NDIS providers' admin (details changed, patterns real):

A request for information from the NDIS Commission arrives by email, gets opened on a chaotic Tuesday, and sinks below 200 newer emails. Months pass.
An insurance policy renews annually. The one person who remembered it last year is on leave, or has left. The policy lapses and nobody notices until something needs claiming.
A worker's screening check expires mid-roster. They keep working shifts, because no system connects the expiry date to the roster.
A behaviour support plan review date passes unnoticed, because it was recorded in the plan document itself - which nobody opens until something goes wrong.
Three versions of the incident register exist in three places, and they disagree.

Every one of those is a serious problem in an audit, and every one is preventable with the same boring, powerful fix.

The obligations register

One spreadsheet. Every dated obligation your organisation has, in one place, with these columns:

Obligation - what it is ("public liability insurance renewal", "J.S. worker screening check")
Category - insurance, workforce, participant, regulator, governance
Owner - the named person responsible
Due date and renewal cycle - when, and how often it repeats
Evidence location - where the proof lives (certificate, filed response, signed policy)
Status - current, due soon, overdue, closed

What goes in: all insurances. Every worker's screening and first aid expiries. Behaviour support plan review dates. Your registration and audit milestones. Policy review cycles. Vehicle and equipment renewals. And a row for every piece of regulator correspondence that carries a deadline.

We've made a free starter version you can use today: download the NDIS obligations register template (CSV). It opens in Excel or Google Sheets and comes pre-loaded with the obligation types above - replace the placeholders with your real dates and owners.

The part that makes it work: escalating reminders

A register nobody looks at is just a nicely formatted filing cabinet. The system only works when the register chases you. The pattern we build:

60 days out - a heads-up. Plenty of time to get quotes, book training, schedule a review.
30 days out - action needed now.
7 days out - urgent, flagged as such.
Overdue - escalates, and repeats in a weekly digest until someone closes it. Overdue items don't go quiet; going quiet is how they became overdue in the first place.

Two rules make the reminders trustworthy. First, they go to at least two people - the owner and a backup - so one person's inbox is never the single point of failure. Second, you test the system before you rely on it: seed a fake obligation due in eight days and watch the reminder arrive. Let one go overdue on purpose and watch the escalation fire. If you haven't seen it work, you don't have a system, you have a hope.

The companion move: regulator mail triage

The obligations register catches known dates. Regulator mail triage catches the deadlines that arrive by surprise. Set up rules in your mailbox so that anything from the NDIS Commission, your auditor, the public guardian or a tribunal is automatically flagged, moved to a dedicated folder, and logged in the register with a response deadline the moment it lands.

The goal is structural: it should be impossible for a regulator's email to sit unanswered for months, no matter how chaotic the week it arrived in. This takes about fifteen minutes to set up and is the single highest-value fifteen minutes of admin work available to most providers.

How to build it (and who should own it)

You don't need special software. The register is a spreadsheet in the Microsoft 365 or Google Workspace you already pay for. The reminders run on a lightweight automation tool - we use n8n, and Power Automate works too. Two principles matter more than the tool choice:

It runs in your accounts, not your consultant's. If the person who built it disappears tomorrow, the reminders keep firing. You hold the off-switch.
Every automation gets a runbook. One page: what it does, how to add an obligation, what to do if a reminder doesn't arrive, how to turn it off. No runbook, not done.

One caution if you're mid-audit: this is exactly the kind of safe, additive improvement you can make during a live audit. Record-system migrations are a different story - in our experience the assessor is testing the system you've been running, so our strong advice is to hold migrations until your audit decision lands. Presenting a working obligations register to an auditor is strong continuous improvement evidence; it shows the gap was found and closed.

Where this fits in the bigger picture

The obligations register is the first thing we build for NDIS clients because it prevents the failures that cost the most. Once it's running, the rest of the automation stack - notes, intake, claiming, document filing - builds on the same foundations. The full map is in our complete guide to AI and automation for NDIS providers, and if your team is already using AI tools day to day, read Is ChatGPT safe for NDIS participant data? before they get too creative.

If you'd rather have it stood up for you: we build the register, the reminders and the mail triage as a fixed-price package, in your accounts, with runbooks - and you own all of it. Book a free 30-minute call and we'll map your obligations together.

How NDIS Providers Stop Missing Compliance Deadlines