Key Observations

1. PP&C's CI dominance maps directly onto two active projects

People Performance & Culture generates 41% of CI submissions (79 of 191) — more than Operations, Customer & Practice, and Corporate Services combined. Two of the nine helicopter projects are squarely in PP&C's territory: Project 6 (HRIS/Payroll Discovery) exists because PP&C's current systems are fragmented; Project 2 (Connect) directly changed rostering and employee data management. The CI volume is likely a symptom of the same fragmentation those projects were commissioned to fix — not a sign that PP&C has stronger CI culture than other functions.

2. CI submission peaks align with project milestones

CI volume surges when project activity surges — particularly around Funding Optimisation. The register is at least partly absorbing improvement work that is project-adjacent or project-generated, not operating as an independent quality channel.

3. Executive CI accountability mirrors project sponsorship

The same five people carrying the project load are carrying the CI accountability load.

This is the CI register's "single point of dependency" finding made concrete — it reflects how leadership capacity is distributed across the whole organisation, not just a register design issue.

4. Operations: most project load, least CI voice

Operations touches 7 of the 9 helicopter projects — the highest cross-project load of any function. Yet Operations generates only 31 CI submissions (16%), fewer than half PP&C's volume, despite managing frontline delivery and participant risk across sites. The most plausible explanation: Operations is absorbing project-driven change from all directions and has no bandwidth to use the CI mechanism in parallel. Their improvements are either captured at the project level or not captured at all — both are risks.

What the KPI set measures well

The current KPIs are a reasonable corporate governance scorecard: financial sustainability, workforce stability, operational capacity (occupancy, vacancies), staff safety, and internal communications reach. These are legitimate things to track. Four of the eight areas are currently Behind — the financial result (net income $1.2M below budget) and workplace injury rate (19.3% vs 12% target) are the most material.

What the KPI set does not measure

• Participant outcomes. No goal achievement rates, no quality-of-life measures, no support plan data.
• Support quality. No incident trends by category/severity as a KPI. No restrictive practice rates. No documentation completion rates.
• Lead indicators for financial performance. Shift fill rates, roster stability, time-to-claim — the operational conditions that produce the financial results — are not in the KPI set.
• Why people leave. Involuntary exits are counted (4 in May, up from 1 in March) but not categorised or analysed as a KPI. The metric is framed as "voluntary exits reduced" — which is on track while involuntary exits are rising.
• Early-tenure staff loss root cause. 35.5% of staff leave within 12 months of joining (worsening). No KPI asks which sites, roles, or managers are driving it.

What the operational response actually looks like

The ops team built a spreadsheet to track mealtime management plan currency. This spreadsheet is a disconnected tool — it is not integrated with Visicase or Connect, is not suitable for Power BI integration, and will need to be rebuilt by the quality team before it can be used for reporting or escalation. Follow-up mechanisms and accountability for what happens when a plan falls due or goes overdue have not been defined. The spreadsheet is a tracking list, not a managed workflow.

This is the recurring pattern: a gap is identified, a bespoke tool is built, and the tool inherits none of the problems the gap was meant to solve — no integration, no accountability, no escalation pathway.

What a proactive quality review would have also asked

The intensive operational response confirmed 16 plans were not current. It did not ask: are the current plans accurate? Have support workers been trained on the plan content? Is the plan referenced in the participant's support plan? Are review dates set, and is there a trigger to act when they lapse?

Currency (a plan exists and has a date) and quality (the plan works and people know about it) are different tests. The response addressed currency. Quality was not part of the scope.

Case 1 — late-stage cancer diagnosis

One participant was diagnosed with cancer one week before her death and immediately placed on an end-of-life plan, returning home under palliative care support. The CEO report contains no information about prior health concerns or what prompted the hospital admission that led to the diagnosis.

The quality review question: the type of cancer involved typically presents with symptoms — urinary changes, discomfort, blood — that can be present for weeks or months before diagnosis. In a participant with complex communication needs, these may not be self-reported. Were they recognised, escalated, and acted on? Was there a regular proactive health check schedule? The individual health file, shift notes, and GP contact records would answer this — the CEO report cannot.

Case 2 — gastrointestinal presentation, rapid deterioration

A long-term participant was admitted to hospital for vomiting and constipation on 7 May and deteriorated rapidly after admission. Family made the decision for comfort measures, and she passed away on 21 May — 14 days after admission.

Constipation is the most common and most preventable serious health complication in people with intellectual disability, and can progress to bowel obstruction, perforation, or sepsis when unmanaged. The speed of deterioration after admission suggests the presentation on 7 May may not have been the beginning of the problem. The quality review question: was there a bowel management plan? Were there behavioural or physical changes in the weeks prior that appear in shift notes? Was constipation a known, monitored health risk for this person?

i. Enabling function efficiencies

Automation of HR processes and compliance checking (i.a, i.b): The Connect implementation was intended to deliver automated compliance visibility — specifically, documentation currency alerts, workflow prompts, and escalation pathways. The CEO report acknowledges it could not. The budget is planning automated compliance checking in a context where the current implementation attempt for exactly this functionality has not been resolved. The question is not whether automation is a good idea — it is — but whether the system architecture that would underpin it has been designed, or whether this is a second attempt at the same goal with a different label.

HRIS system review (i.c): PP&C already generates 41% of all CI submissions — the highest volume of any department. A system review in HR is likely to generate another significant burst of documentation change activity. This is not a reason not to do it, but it is relevant context for CI register management capacity planning.

ii. Strategic workforce design

Reducing Senior Support Worker headcount (ii.a): SSWs are typically the staff members with deepest participant knowledge — the people most likely to notice health changes, behavioural shifts, and early warning signs. The health monitoring flag in this document (four deaths in care, two with unanswered questions about lead-up indicators) is directly relevant. Reducing SSW headcount before proactive health monitoring systems are embedded in the clinical and documentation layers increases reliance on exactly the individual knowledge and manager oversight that the CEO report has already identified as Achieve's current compliance weakness.

Reducing RN headcount via clinical skills uplift (ii.b): Substituting frontline clinical capability for RN headcount is a legitimate model. It requires embedded training, competency assessment, and supported practice. The KPI set does not currently measure training uptake or clinical competency as outputs. You cannot safely reduce RN headcount without first knowing whether the training investment is producing measurable capability in the people who will fill the gap.

iii. Readying for SIL commissioning

Paperless group homes (iii.d): Moving group home documentation to digital is the right direction, and is directly connected to the "lack of visibility of expired documentation" the CEO report identifies as unresolved. But paperless is a risk amplifier if the embedded workflows, prompts, and escalation pathways don't come with it. Making documentation digital without making it managed means information moves faster to a place where it is equally invisible. The mealtime management plan gap was in paper-era documentation habits; paperless homes could reproduce the same gap in a digital form.

Headcount reduction via increased hours (iii.c): Fewer workers with longer hours reduces handover frequency. Handovers are where participant health observations get communicated between shifts. Fewer handovers can improve continuity of care, but they also mean that when an observation is missed, it is missed for longer. This is a detail for the workforce design modelling, not a reason to reject the approach.

The sequencing question

The common thread across all three strategy areas is sequencing. Each planned efficiency is sensible in isolation. Each one becomes higher-risk if it is implemented before the underlying systems gaps are addressed.

Achieve's current quality assurance model relies heavily on individual manager oversight and periodic audit — not embedded controls. The budget strategies reduce headcount, reduce clinical capacity, and move documentation to digital. All three reduce the human compensating mechanisms that currently hold the system together. If the embedded controls don't exist yet, the compensating mechanisms are not redundant — they are load-bearing.

The systems scoping work is relevant to the budget planning for this reason: it can tell the organisation which efficiency strategies are safe to move on now and which ones need a system precondition to be in place first.

The risk register: where board attention is formally directed

The Risk Report (CFO, June 2026) identifies four enterprise risks currently rated High or Extreme:

• Risk of Miscalculations of Correct Award Entitlements
• Risk of Award entitlement corrections not being done within agreed time limits
• Risk of inadequate Emergency Management and Business Continuity documentation
• Risk of not paying staff accurately or on time

All four are workforce and payroll risks. Not one participant-facing risk reaches the High or Extreme threshold visible to the board. The report does note that 11 risks are currently "above appetite," with "client health safety and wellbeing" and "legislative and regulatory compliance" explicitly named among the categories represented — but the detail is in an Excel appendix not provided to this engagement. The formal board risk reporting structure routes through the CFO and FRAC Committee, not through the DSP. The charter acknowledges this coordination gap without resolving it.

What the DSP needs to function — and what doesn't exist yet

The DSP charter creates the governance obligation. The data infrastructure to fulfill it doesn't exist. For the committee to do its job, it would need:

• A standing incident trend report (not a CEO narrative paragraph)
• Participant outcome data (not occupancy and exit rates)
• Clinical risk reporting from frontline through to committee level
• Consumer feedback data (not staff-reported impressions of participant satisfaction)
• A complaints analysis with trend visibility

None of these information flows are visible in the June 2026 board papers. The committee's advisory-only status means that even when it identifies gaps, it cannot compel action. But it cannot even identify gaps it isn't seeing data about.

What "client satisfaction" currently means in Achieve's KPI set

The Organisational KPI Report (Attachment 1, Strategy Implementation Report) lists "Client satisfaction — Clients are satisfied with the quality-of-service provision" as a goal. The actual measures used are:

• Voluntary client exits (reduced)
• Involuntary client exits (May 2026: 4, up from 1 in March)
• Occupancy rate (target 93%; May 2026: 91.6%)
• Vacancy count (target 21; May 2026: 26)

There is no survey, no NPS, no outcome measure, no participant feedback mechanism of any kind. Client satisfaction is being measured by whether beds are filled. This is a retention and occupancy metric. It says nothing about whether participants are thriving, whether their goals are being met, whether they feel safe, or whether the support they receive is quality support. The board cannot answer "how do you KNOW your services are good?" because the data to answer that question has not been defined, let alone collected.

Why this matters now — not just as a gap, as a risk

The NDIS Commission's current enforcement focus is explicitly shifting from checking that systems exist to checking that systems work. The question they are asking providers to answer is not "do you have a quality framework?" but "how do you know your services are delivering good outcomes for people?" Achieve cannot answer that question in June 2026.

The DSP Committee charter — drafted by Gilbert + Tobin, signed February 2026 — places Customer Voice as the committee's first named responsibility. The committee has a formal mandate to advance participant outcome measurement. But without data infrastructure, the committee has nothing to look at and nothing to report. The charter creates the obligation; the two-year deferral of Client Voice KPIs means the obligation has not been met.

Achieve is also about to absorb 226 clients from Focal Community Services (August 2026). Bringing in 226 additional participants without a functioning participant outcome measurement framework amplifies an existing governance gap. The board will have less visibility of quality at the moment Achieve's footprint is growing fastest.

What Daniel said — when he was consulted once

The ME Services Assessment records Daniel's framing: "focus less on refining already functional onboarding processes and more on improving the 10+ year lived experience of clients once in service."

This is a fundamentally different problem statement than any other input in the same exercise. Every other stakeholder's input was oriented toward systems, technology, and process efficiency. Daniel's was about what it feels and functions like to live in a service for a decade — and whether the systems built around that experience are designed for the person or for the organisation.

That framing has not appeared in any subsequent diagnostic output. It is the only input in the diagnostic record that originates from direct operational leadership of the division delivering services.

The board attendance pattern confirms the structural position

In the June 2026 board papers, the CFO presents or co-presents at least seven agenda items. The COO presents none. In the May 2026 board minutes, Daniel Kyriacou, Sarah Archer (CSO), and Angela Johnston (CPO) are all listed as attending by invitation — not as regular management attendees. The CEO and CFO are the consistent operational voices at board level.

Operations — the division responsible for delivering services to 700+ participants across SIL, Day Programs, and Respite — has no standing reporting presence at board level and has been peripheral in every diagnostic exercise conducted over the past 18 months.

This is not a criticism of Daniel Kyriacou. It is a finding about how the organisation is structured to generate and surface knowledge about its own service delivery.

The evidence across four layers

CI register and the KPI set. The CI register tracks document and process improvement inputs. The KPI set tracks operational and financial outcomes. No entry in the CI register references a KPI. No KPI cites CI activity as a leading indicator. The two most critically behind-target KPIs — net income and LTIFR — have the weakest visible CI coverage of their root causes. 191 items closed; no evidenced connection to any KPI movement.

Governance and data infrastructure. The DSP Committee charter names Customer Voice as its first responsibility domain and requires the committee to monitor consumer trends and outcomes. No participant outcome data exists for it to look at. No standing incident trend report exists for it to review. The governance obligation and the data infrastructure to fulfil it were designed independently and have never been joined.

Documentation and training. Plans exist — support plans, mealtime management plans, health action plans. Training exists. There is no mechanism connecting a specific plan to whether the workers implementing it have read, understood, and been verified on its content. A plan can be current and a worker can be untrained on it simultaneously, with no system aware of the gap.

Diagnostic exercises and operational knowledge. Four diagnostic exercises over 18 months. The people who deliver services day to day — service managers, frontline workers — have not been systematically consulted in any of them. Every map has been built from enabling-function inputs. The connection between what the documents describe and what happens on a Monday morning at a group home has never been formally tested.

Why this framing matters for what comes next

This is a structural problem, not a performance problem. Each piece of Achieve's quality infrastructure was built rationally — for the audit that was in front of the organisation at the time, by the function responsible for that domain, with the resources available under growth pressure. Nobody built a bad CI register. Nobody built a weak KPI set deliberately. The architecture that would connect them was simply never part of any brief.

This pattern is not unique to Achieve. It is the dominant pattern across the NDIS sector — which is precisely what the Commission's shift from checking that systems exist to checking that systems work is designed to surface. Achieve is not behind the sector; it is exactly where most providers of its scale are. The difference is that Achieve now has a name for the gap.

Naming it as an architectural problem rather than a performance problem also changes what the fix looks like. It is not a matter of doing more — adding another diagnostic exercise, another KPI, another committee. It is a matter of designing the connections that turn existing activity into visible learning. The pieces are there. What is missing is the layer that makes them talk to each other.

Practically: fixing the CI register-to-KPI connection, defining what data the DSP Committee needs to function, linking plan currency to staff training — these are connective changes, not replacement changes. They do not require starting over. They require someone to be accountable for the joins.