Let's examine the architecture properly: NDIA PACE, Services Australia, Victorian DFFH, National Redress, identity systems, contact restrictions and the infrastructure that might connect them.
The critical distinction isn't simply whether government agencies exchange information. They do, through various authorised arrangements.
The interesting questions are what information travels, through which systems, who can see it, and whether a restriction recorded by one agency can influence how another agency treats you.
Your August 2026 FOI disclosure gives us a particularly useful starting point. An NDIA record reportedly referred to a Services Australia communication restriction associated with the volume of FOI requests.
That raises a concrete question: how did information about a Services Australia restriction enter an NDIA record?
There are several possible routes, and they leave different evidence trails. Let's map them.
### 1\. The documented architecture is more interconnected than it first appears
The strongest evidence comes from the NDIA's own published systems overview and parliamentary scrutiny of PACE.
Services Australia
Historical SAP CRM hosting · shared financial services · identity checking
Documented service and data interfaces
NDIA operational systems
PACE (Salesforce CRM) · SAP Finance · enterprise data warehouse
Separate statutory information-sharing arrangements
National Redress
Commonwealth administration and Services Australia delivery functions
Victorian DFFH
State counselling, redress-related services and housing functions
Conceptual map of documented organisational connections, not a claim that all four systems share one database or unrestricted access.
The findings are substantial.
First: NDIA previously used a SAP customer relationship management system hosted and maintained by Services Australia. PACE, built on Salesforce, was introduced to replace it. The Australian National Audit Office reported that migration from the previous system was still progressing in June 2025. ndis.gov.au +1
Second: NDIA's own overview documents SAP Finance, payment intermediaries and an enterprise data warehouse integrating participant, planning, budget and payment information. This isn't just a contact-centre address book. It's an interconnected operational environment. ndis.gov.au
Third: NDIA's published privacy assessments include a December 2025 data-sharing agreement with Services Australia specifically for identity checking and related purposes. They also list an API gateway, managed file-transfer capability, risk-scoring project and other data infrastructure. NDIS
Those are real documented components. Their existence doesn't tell us which were used in your particular case.
### 2\. The National Redress connection is especially interesting
The National Redress Scheme is administered federally, with Services Australia performing delivery functions. Victorian DFFH separately provides counselling and psychological care services for eligible people in Victoria. DFFH Service Providers +1
Here's the particularly revealing discovery.
Services Australia's National Redress privacy notice says that, when handling a redress application, it may accept a person's confirmed digital identity from the Centrelink system.
That's an explicit example of information or identity verification crossing service boundaries. Services Australia
The National Redress privacy policy also describes authorised disclosures to participating institutions, contracted service providers, Services Australia and certain other authorities. nationalredress.gov.au
So the proposition that redress administration operates entirely separately from Commonwealth identity and service infrastructure would be wrong.
There are documented connections.
And Victoria's counselling service itself collects identifiers including your Redress ID, date of acceptance, previous counselling and other information needed to match you with services. vic.gov.au
This helps explain why David can have a legitimate role in your redress history without necessarily being able to see your entire Centrelink or NDIS record.
### 3\. The most important technical distinction: sharing information versus sharing a restriction
Here's where your own FOI record becomes central.
You have described an NDIA record from 19 August 2026 referring to a Services Australia communication restriction associated with your FOI activity.
If the wording is as previously discussed, it establishes that information about a restriction at one Commonwealth agency was recorded in another agency's case material.
But how did it arrive?
| Possible mechanism | Evidence that would identify it |
| -------------------------------- | --------------------------------------------------------------- |
| Staff-to-staff communication | Email, telephone note, referral or internal message |
| Participant-provided information | Original call recording, uploaded letter or intake note |
| System integration | Interface specification, API transaction or data-transfer log |
| Shared service arrangement | Service agreement, permitted data fields and access controls |
| Copied administrative decision | Original restriction notice, recipient list and decision record |
The distinction is critical.
A restriction being mentioned in another agency's records is not necessarily the same as the restriction being enforced there.
To determine whether the restriction travelled as an operational instruction, we'd need the original decision, its distribution history and evidence of any subsequent action.
That's a precise audit question, not a speculative one.
### 4\. What about AI, risk scoring and automated workflows?
This is another substantial discovery.
The NDIA's privacy register identifies projects relating to an API gateway, identity and access management, eDiscovery, an integrity management system, a log landing zone and a Risk Scoring and Response Capability Project. NDIS
A parliamentary inquiry also recorded that PACE has a rules-based engine designed to implement government policy changes. aph.gov.au
These are different technologies.
A rules engine can automatically apply defined business conditions without using generative AI.
Risk scoring may involve statistical models, deterministic rules or other analytical methods. The project title alone doesn't tell us which.
And a CRM can automatically create tasks, route enquiries, flag cases or prompt staff without using a large language model.
That means the technically useful questions are:
* Does a participant record contain risk classifications, communication-management flags or contact restrictions?
* Are those fields entered manually, generated automatically or imported from another system?
* Can those classifications influence routing, escalation or staff instructions?
* Which officers can view, change or override them?
* Are previous values and access events retained in audit logs?
Those questions would tell us considerably more than asking whether the government uses AI in general.
### 5\. The next documentary targets
I'd concentrate on four specific records rather than sending another broad complaint.
The Services Australia–NDIA identity-sharing agreement, listed as privacy assessment 7453 in December 2025, would help define the formal scope of that connection.
The NDIA API Gateway assessment, reference 51362, could explain categories of external system interfaces and associated controls.
The Risk Scoring and Response Capability assessment, reference 63068, could clarify what kinds of risk information are processed and how decisions are governed.
Your original August 2026 case record and its audit history could identify where the reference to the Services Australia restriction came from.
The public register lists the assessments; it does not publish their complete technical contents. Access to detailed documentation may be limited for security and privacy reasons.
You can inspect the official [NDIA privacy and assessment register](https://www.ndis.gov.au/policies-rules-and-legal/using-our-websites-and-social-media/privacy?utm_source=chatgpt.com).
### 6\. Where David fits into this architecture
David's role is particularly interesting because the National Redress system itself has documented federal–state information pathways.
He may be familiar with the practical way a Victorian counselling service receives referrals, verifies eligibility, manages correspondence and retrieves historical records.
His offer to retrieve your earlier $10,000 paperwork is a concrete example of a records process you may now get to examine firsthand.
But I wouldn't put him in the position of explaining PACE, Services Australia's internal contact restrictions or infrastructure he doesn't administer.
The strongest opportunity is to understand the systems he directly works with, while pursuing the other agencies' records through their own access and FOI processes.
### My conclusion
We've established something substantial from official sources:
There is documented shared infrastructure, identity verification, interagency disclosure, CRM integration, financial-system integration and data processing across parts of the Australian Government.
That isn't conjecture. The parliamentary reports, NDIA technical overview and privacy notices document it.
What remains to be established in your particular case is whether information about your communication restrictions moved through an automated interface, a human referral, a shared service or a combination of those mechanisms — and whether that information actually affected subsequent decisions.
The strongest next question is therefore:
Who originated the restriction information, who transmitted it, who received it, where was it recorded, and what action followed?
That's the point at which a general discussion of government technology becomes a testable examination of your own administrative record.
And the most useful discovery from today's research is that we now have specific systems, agreements and privacy assessment
reference numbers to pursue, rather than an unidentified data pipeline.
