A first-principles map of what frontline supports need to work well — built from the ground up, then mapped against Achieve's existing systems. The starting question is not "what does compliance require?" but "what does a support worker need on any given shift to support someone well?" Compliance attachment points are shown separately below the core flow.
These are genuine additions that don't fall out of quality naturally — they are required by the NDIS Practice Standards or legislation regardless of what the quality model looks like. The goal is to attach them to specific nodes in the quality loop, not run them as a parallel system. Current state at Achieve is shown for each.
| Requirement | Attaches to | What it adds beyond quality | Current state at Achieve |
|---|---|---|---|
| NDIS Practice Standards — intake documentation (PS 2.1) | 01 Person | Formal documented consent, service agreement, rights and responsibilities at commencement | Exists — Connect intake process handles this for SIL |
| Mealtime management plan (SLP/dietitian sign-off) | 01 Person | External clinician sign-off, formal plan, review schedule triggered by clinical events — not just calendar | Gap identified — 13% not current (April 2026 blitz); currency gap closed; quality review (accuracy, staff training, support plan reference) not done; tracking spreadsheet disconnected from Connect and Power BI |
| Behaviour support plan and restrictive practice authorisation | 01 Person 03 Deliver | NDIS-registered BSP sign-off; state-level authorisation for each restrictive practice; implementation fidelity record | Partial — plans exist; Connect migration scope for implementation recording not confirmed in this engagement |
| Medication management | 03 Deliver 04 Observe | Medication authority on file; administered as charted; PRN recording; pharmacist review triggers | Partial — medication charting exists; scope and format in Connect not assessed in this engagement |
| Reportable incident notification (NDIS Commission) | 04 Observe | External notification within Commission timeframes; investigation report; Commission correspondence | Exists — routes through OCG; four matters open as at June 2026 CEO report. The notification step works; the internal learning loop back from Commission response is the gap |
| Annual plan review (PS 2.2) | 05 Review | Documented review with participant, goals updated, supports adjusted — within NDIS funding review cycle | Exists — annual review cycle in place. Proactive triggers for between-review changes are the gap |
| NDIS quality indicator evidence | 05 Review 06 Learn | Documented evidence that each Practice Standard indicator is met — available for audit on request | Partial — evidence generated event-by-event; no standing evidence base; audit preparation is a sprint, not an ongoing process |
| Continuous Improvement Register | 06 Learn | Formal record of improvements identified and actioned — required by NDIS Practice Standards | Exists — CI register maintained with 191 entries. Pattern aggregation across entries is the gap (see CI Register deep dive) |
Achieve's current operating model runs a quality system (support plans, shift notes, incident reports) and a compliance system (CI register, Commission notifications, audit evidence) in parallel. They share some data but were built separately, are owned by different functions, and reported through different channels.
The frontline experience: documentation fills compliance, not learning. Reviews happen when something goes wrong or when an audit is due. The organisation improves when it is prompted externally, not when it notices something itself.
This is not a criticism of the people who built it. It is what happens when systems are added reactively, one compliance requirement at a time, without a quality architecture underneath.
Compliance steps attach to the quality flow at specific nodes rather than running as a separate system. The shift note is also the health observation record. The plan review is also the annual review evidence. The CI register captures what the review and learning cycle surfaces, not what someone inputs separately for audit purposes.
The frontline experience: one set of tasks, not two. Documentation serves the person first and compliance second. Quality data is available in real time rather than reconstructed when an audit is called.
The Commission's current enforcement direction — checking that systems work, not just that they exist — is easier to demonstrate from a quality-first model than from a compliance-first one.