This document maps where AI can add genuine value to the 36 managed documentation controls, what each AI touchpoint does, and what the build looks like. The mapping is honest about sequencing: AI quality is bounded by data quality. Most of these applications require the basic automated workflows (Categories 1–5 in the managed documentation register) to be in place first — because without structured data, AI is reading noise.
The three tiers below are roughly sequential. Tier 1 can start now with existing data. Tiers 2 and 3 require the structured documentation workflows to be in place first — because they depend on shift notes and participant records containing meaningful, structured data rather than compliance tick-boxes.
AI reads what it is given. If shift notes are "John had a good shift and enjoyed dinner," AI will identify patterns in good shifts and enjoyed dinners. The Category 2 adaptation in the managed documentation register — restructuring shift note format to include domain-based observation fields — is not just an operational improvement. It is a prerequisite for meaningful AI analysis. A shift note that captures: food texture, volume consumed, behaviour observations, health indicators, follow-up items produces data an AI can reason about. A shift note that captures: "settled and happy" does not.
This means the AI build for Tiers 2 and 3 is gated on the documentation quality improvements that precede it. Getting the structured workflows right first is not a delay to the AI strategy — it is what makes the AI strategy work.
Currently: worker reads plans themselves (if they read them at all) or gets a verbal handover. AI generates the summary; worker still acknowledges the source plans. Clinician reviews the briefing summary before it is published to confirm accuracy.
Plans exported from Connect as structured text → AI model with a fixed prompt template (participant briefing format) → output posted back to Connect as a worker-facing document attached to the participant record. Reviewed and approved by SM or clinical nurse before activation. Rebuild triggered whenever a source plan is updated.
A signature on a form. Legally equivalent but clinically meaningless. A worker who answers specific questions about this person's plan has demonstrably read it.
Plan text → AI generates question set → questions delivered in Connect or a linked form → answers recorded against the worker-participant pairing. AI generates questions at plan update, not on a fixed schedule. Wrong answers prompt re-read of the relevant plan section, not an automatic fail.
Manual classification (error-prone, especially for complex incidents) and blank-page notification drafting (time-consuming, inconsistent quality across writers). Four matters currently open with the Commission — consistent, accurate notifications reduce the risk of Commission escalation.
Incident report submitted in Connect → AI reads incident description and structured fields → classifies as reportable/non-reportable with confidence level and reasoning → if reportable, generates draft notification in Commission format → SM and OCG review, edit, and submit. AI flags where it is uncertain about classification for human determination.
Manual review by SM or practice leader. AI is faster and applies the same checklist consistently — human reviewer confirms flagged gaps and makes clinical decisions about whether they represent genuine omissions or justified exclusions.
Support plan document → AI reads against a fixed domain checklist → outputs structured gap report: domain addressed / partially addressed / not addressed / not mentioned. Clinician or SM reviews and approves before plan is marked as active. Checklist is maintained by quality team — AI applies it, humans define it.
Calendar-only review scheduling. When 15 plans come due in the same month, AI helps the quality team know which three to prioritise — not just which three are oldest.
Monthly run: AI reads plan review dates + incident count since last review + hospitalisation records + health flag count from shift notes → generates a priority-ranked list for the SM or quality team. Output is a recommendation, not a decision — the human determines whether to bring forward a review. Requires incident data and some shift note data from Connect; does not require full structured shift note reform.
The current compliance model says "note filed = done." The quality model asks "note filed AND contains what matters = done." SM can see which workers consistently produce thin notes and intervene with coaching rather than waiting for an audit to surface the pattern.
Shift notes exported from Connect → AI evaluates against a rubric (health observations present, follow-up items documented, plan-specific observations included) → quality score per note → weekly summary report per site for SM. Rubric is maintained by the quality team. AI applies it consistently; quality team reviews outliers.
This is the gap behind the health monitoring quality review flag in the exec summary. Four deaths in care, two with unanswered questions about whether lead-up health indicators existed in the weeks before acute presentation. Shift notes may have contained those indicators. AI can read them in a way no individual SM can at scale across 700+ participants.
Weekly batch: AI reads last 60 days of shift notes per participant → identifies semantic patterns in health, nutrition, mobility, behaviour, and social domains → flags participants with concerning patterns to SM and clinical nurse. Output is a flag with evidence ("here are the 5 notes that show this pattern"), not a diagnosis. Clinical nurse reviews and determines response.
Annual plan review as the only mechanism for catching plan-practice drift. By the time a plan is reviewed, the practice may have been misaligned with the plan for 11 months. AI runs this check continuously and flags interim review when drift is detected.
Plans from Connect → AI extracts expected practices per plan domain → shift notes from same period → AI compares described practice against plan expectations → drift flags generated for clinician review. False positive rate expected to be meaningful — requires clinical review before any action is taken. The value is in surfacing cases for clinical attention, not in automated plan updates.
A flat list of alerts that a SM must sort themselves. In high-volume sites, SMs receiving multiple simultaneous alerts without prioritisation will address the easiest ones first, not the most important ones.
Alert generated by rules engine → AI reads participant risk profile (health complexity, recent incidents, plan currency history) → assigns priority score to alert → SM receives prioritised alert list with brief rationale ("prioritised because participant has active dysphagia risk and recent incident cluster"). SM can override priority — AI is informing, not deciding.
The clinical nurse or SM reading through 60+ shift notes, three plan documents, and an incident log before the discharge review meeting. This typically doesn't happen — the review proceeds without full context. AI makes full context available in 30 seconds.
Hospitalisation event recorded in Connect → AI immediately reads participant record (plans, recent notes, incidents, medication, health flags) → generates structured briefing in fixed format → delivered to SM and clinical nurse within minutes. Briefing is a summary tool, not a clinical assessment. The clinical nurse makes the assessment.
The current shift note prompt is a blank text field, or at best a generic observation structure. This replaces it with a participant-aware guide that pulls from the active plans to tell the worker what to document. It makes the plan visible at the point of care — not just filed somewhere in Connect.
Connect shift note interface → AI reads active plans for this participant → generates contextual prompt list at note-opening → prompts displayed alongside free-text field → responses structured by domain → AI quality scores the completed note in real time and flags before submission if key domains are missing. Requires Connect front-end integration or a Connect-adjacent interface that feeds back into the record.
Workers describe what they observe. They don't always know when a pattern of observations constitutes a clinical concern. AI bridges that gap — reading the observation language and applying clinical pattern recognition that a frontline worker is not expected to have. This is where AI adds something that neither better documentation nor better training can fully replace.
Continuous note monitoring → AI applies NLP across rolling 30-day note window per participant → pattern detection across health, behaviour, nutrition, mobility domains → threshold flag to SM and clinical nurse with evidence ("3 of the last 5 notes contain language associated with appetite or eating difficulty") → clinical nurse reviews. False positive management is critical: alert rate must be calibrated so SMs respond to alerts rather than ignoring them.
Blank-template plan drafting, which requires the clinician to re-synthesise information they partially have from memory and partially need to look up. AI does the synthesis; the clinician does the clinical judgement and participant engagement.
Plan review task triggered in Connect → AI reads previous plan, last 90 days of shift notes, incident history, and any clinical reports filed → generates draft plan in the required format with inline notes ("no shift note references to swallowing difficulty in the last 90 days — confirm texture recommendation is still appropriate") → clinician reviews, edits, and approves. AI draft is never published without clinician sign-off. Participant review meeting still required.
Alerts without context are often deprioritised because the recipient doesn't know how urgent the situation is. Context-rich alerts are acted on faster. This applies to the same escalation pathways in the managed documentation register — AI adds the context layer to automation-generated alerts.
Alert triggered by rules engine → AI reads participant record for relevant context → generates contextualised alert message with priority reasoning → delivered to SM via Connect notification or email. Connect front-end displays context summary alongside the action required. SM can see the full participant context from the alert without navigating to the participant record manually.
All of these applications require programmatic access to data held in Connect — shift notes, incident reports, participant records, plan documents. Whether Connect provides an API or data export mechanism suitable for AI integration is a technical question that needs to be answered before any build is scoped. If Connect does not support API access, the build approach shifts to batch export and processing rather than real-time integration — which affects Tier 3 specifically, and changes the latency on Tier 2 alerts.
Connect went live in June 2026. The implementation team (Karen Moore-Evans) would know whether API access is available or on the roadmap. This is the single most important technical prerequisite to confirm.
All of these applications process participant health information, shift note content, and incident data. Before any AI model is applied to this data, Achieve needs to confirm: which AI providers are acceptable under their privacy and data governance policies, whether participant consent (or the existing service agreement) covers AI processing of health-adjacent data, and how audit logs of AI outputs are maintained for regulatory purposes.
The NDIS Commission does not currently have AI-specific guidance for providers, but the NDIS Practice Standards on information management apply. Any AI system processing participant data must meet the same security and privacy requirements as any other system holding that data. Most providers in this space use closed, self-hosted, or privacy-preserving AI deployments rather than sending participant data to general-purpose AI APIs.
Tier 1 applications can be structured to process de-identified or minimally-identified data in many cases (plan documents with identifying fields removed). Tiers 2 and 3 require fuller data access and need the governance framework in place first.