Dissecting an FOI — “Paste PS Review Macro here”
There it is, halfway down the page. “Paste PS Review Macro here.”
All that official weight, and somebody has left the assembly instruction in the file. Further up are “Yes/No” choices and an “XX/XX/XXXX” date. Further down is my life, squeezed into the template.
That is where I want to start. Pull out the page. Keep the awkward bits. Put it beside the other agency’s page and see where the story changes.
The LEX page — the instruction left in the record

The review entry is stamped 11 August 2026, 13:45. It carries a block of template prompts, followed by a populated Personalised Services review. “Complete section 1 & 2 then paste PS Review Macro here” appears in the text. Some “Yes/No” options and the placeholder date survive in the released record. That shows template material was retained in this export. It leaves open whether the source screen, the saved note or the export process produced that combination.
Read the channel instructions near the top. Face-to-face access is fully restricted. Phone contact is directed to the designated team. Written and digital contact is described as available without limitations. On the same page, email volume and email redirection are part of the case for continuing the arrangement. I can write. What happens to the writing is the question.
The neighbouring page, LEX 3, records a rationale and approval at 13:53, eight minutes after the 13:45 entry. The wording repeats across the review and rationale. Those timestamps describe recorded events; they do not tell us how long somebody spent considering the case. The record also contains an identifiable approval process. A pasted macro can sit inside a human workflow, an automated workflow, or a combination. We need the version history to trace this one.
Read the extracted text — LEX page 004
period Other: Discuss behaviours Proactive Contact Email redirection Internal: - External: - 12. Managed Service Plan Recommendations LAP date: 11/8/2026 MSP Recommendation MSP Action: Extend MSP Type: Reactive Duration: 8 months (19/4/2027) Restriction Recommendation F2F Restriction: Full F2F - Customer cannot attend, in person, any location where services provided by Services Australia are delivered. Phone Restriction: Partial Phone - Customer is directed to only call their One Main Contact or Personalised Services Officer. Write Restriction: Available Writing - Customer has no limitations on how to contact the agency through any written or digital channel. Employee Responsible: (SANA) OMC: PS BOMC: PS 13. Zone Delegate / Restriction Approver RM - region 2 / SZ SQLD Date: 11/8/2026 Endorsement method: SQLD LAP (weekly panel) Review recommendation PART 2: Personalised Services Review Contribution -Continues Recommendations PS recommendation: Continue PS PS recommendation on servicing restrictions: Extend Recommended servicing restrictions: - Full F2F - Partial phone Length of proposed MSP: • 8 Months 19.04.2027 PSO/OMC for upcoming MSP: • OMC – – BOMC Personalised Services recommends the Managed Service Plan and current servicing restrictions be extended. Mr Brecevic was referred to PS on a proactive MSP due to his excessive vexatious emails to the agency. Mr Brecevic’s restrictions were increased due to the threatening nature of some of his correspondence. Mr Brecevic utilises AI and has often sent a multitude of non-sensical emails. Mr Brecevic often provides false and misleading information about his circumstances, including signing rent certificates using his alias’s. Mr Brecevic’s behaviour improved during the review period, he ceased sending emails from November 2025 onward. However, his excessive emails in June 2026 and his contact regarding the MSP review indicate a high risk of this behaviour restarting in the future. OMC recommends an extension to the MSP to continue to monitor and minimize the impact on the agency and agency staff. Recommendations on servicing strategies for upcoming MSP period: - Discuss behavioural expectations with customer - Email re-direction - Proactive contact prior to payment date MSP recommendation endorsed by SSM: Not required 4. Customer profile for current MSP review period (refer to section 3) Customer Circumstances Nominee: Yes/No Weekly Payments: Yes/No Urgent Payments: Accommodation type (e.g.: Private, Government, Boarding, Other): Rent Assistance: Yes/No Participation Requirements: Yes/No/N/A Compliance issues: Yes/No/N/A Exemption: Yes/No/N/A Last ESAt/JCA report: XX/XX/XXXX Original incident date: Incident details: (include severity, trigger, actions. e.g. Serious – Damage to Property – Urgent Payment – Police attended) Vulnerabilities/Barriers/Risks Medical conditions/impacts: Yes/No/N/A Complaints/feedback: Yes/No/N/A Appeals: Yes/No/N/A Compliance investigation: Yes/No/N/A OPDL (debts): Yes/No/N/A Repayment arrangement in place: Yes/No/N/A Details: Self Service access management Self Service Registration: Online - Yes/No Phone Self Service - Yes/No Is self service locked: Yes/No Details: Number of successful contacts during MSP review period (N/A for provisional MSPs) : Number of Health Checks conducted and documented during review period (N/A for provisional MSPs) : 5. Summary of Servicing Strategies during review period 6. Behaviour during review period Number of incidents recorded during review period: Warning letters/SMS sent during review period: 7. Customer contribution Did you speak to the customer or nominee about the review of the MSP? Yes/No Date: Customer contribution details: If NO, MSP review invitation letter MUST be issued and uploaded to MSP Date letter sent and recorded in MSP: Was MSP review invitation SMS sent: Yes/No Date SMS sent: 8. Review Considerations Referred to Personalised Services: Current PS Do you agree with Personalised Services review recommendation?: Yes Notification Alert Is there a current Notification Alert? No Safety Alert Decision Is there a current Safety Alert? No Is the customer currently incarcerated?: No Does OMC/BOMC meet Recommendation 37? Yes 11/08/2026 13:45 PM Review recommendation PART 1: 1. Personal Information Full name: Ivan BRECEVIC CRN: Managed Service Plan Number: 2000096823 MSP period: 20/8/2025 to 19/8/2026 MSP type: Reactive Current payment type & status: DSP/CUR Service Zone: Southern Queensland Customer home site (as per OC): 2. Current MSP Restrictions F2F Restriction: Full F2F - Customer cannot attend, in person, any location where services provided by Services Australia are delivered. Phone Restriction: Partial Phone - Customer is directed to only call their One Main Contact or Personalised Services Officer. Write Restriction: Available Writing - Customer has no limitations on how to contact the agency through any written or digital channel. 3. Personalised Services Review Contribution FOR PS USE ONLY – Complete section 1 & 2 then paste PS Review Macro here Customer management - review PERSONAL INFORMATION: Customer name: Ivan Brecevic CRN: PS start date: 19/02/2025 MSP ID: 2000096823 MSP period: 20/08/2025 to 19/08/2026 MSP type/referred by: Reactive/Zone Current restrictions: - Full F2F - Partial phone Frequency of contact during MSP period: Low • There have been 9 phone contacts with Mr Brecevic during the review period. • All outbound contacts have been unsuccessful. Mr Brecevic generally does not answer his phone and does not respond to messages left. • Over 270 emails have been received via email redirection during the review period. • It should be noted these were received between 20.08.2025 – 20.10.2025 and on 28.06.2026 outside of these times, Mr Brecevic ceased sending emails. SERVICE ZONE Service zone: South & Northern Australia Regional office code: MGA Customer profile for current MSP review period Payment type: DSP Weekly payments: No Urgent payments: No Current nominee: Voluntary • Mr Brecevic has appointed an organisation as PPU. The Organisation is yet to contact on Mr Brecevic’s behalf. Address/accommodation status: • Mr Brecevic is currently in receipt of rent assistance. Mr Brecevic has a history of providing false and misleading information in regards to his address and accommodation. Accommodation type: Private Rent Assistance: Yes Participation requirements: No Compliance issues: No Exemptions: No Last ESAT/JCA conducted: None Medical issues: No Vulnerabilities: 'Psychiatric problem or Mental Illness' Complaints/feedback: • Mr Brecevic lodged 3 online complaints during the review period. • These complaints contained abuse directed at staff and were in relation to accommodation and Mobility allowance claims. Appeals: • Mr Brecevic has lodged an appeal in relation to his Mobility allowance application being denied. Compliance investigation: No Debts/Repayment arrangements: No Self service access management Self service registered: Online & phone Self service locked: Not applicable Summary of PS strategies during review period Discuss behavioural expectations with customer: In Progress • OMC providing consistent messaging, educating customer and setting strong boundaries around inappropriate behaviours. Email re-direction: In Progress • Email redirection remains in place. over 270 emails between 20.08.2025 - 20.10.2025 and on 28.06.2026 Proactive 11/08/2026 13:45 PM FOI/LEX 93986 - Page 4 of 153 s47E(d) s47E(d) s47E(d) s47E(d) s47E(d) s47E(d) s47F(1) s47F(1) s47F(1) s47F(1) s47F(1) s47E(d) s47E(d)
The NDIA page — “Save for later” loses its place

Now turn to 19 August. This is a different agency and a different record. Complaint 37617802, related enquiry 37637709. The entry at 12:18 pm says, “Due to Save for later error, notes do not populate in Details of the request”.
The complaint has a level, a theme and a risk rating. The explanation says the expected details field did not populate. The complaint text continues on page 199, so it would be wrong to say the whole complaint vanished. The sharper question is which fields the next officer or queue actually saw, and whether the error changed how the matter was handled.
Page 197 contains a later internal note at 3:56 pm. Page 198 then moves into the earlier 12:18 pm complaint entry. The printed page sequence is not a simple oldest-to-newest chronology. Page 199 attributes parts of the account to me and points back to the related enquiry. A reader needs those joins. Otherwise an allegation, a summary and a referral can start to look like three independent confirmations.
Read the extracted text — NDIA page 198
Escalation of request declined with TL CSB684. Open Feedback and complaints case #37617802 - Case has been referred to Level 2 for review and response as PPT has noted to be currently homeless. ** Both open PCC and Complaints cases are in progress addressing PPT Enquiry #37637709. NFAR from PSO - Awaiting review and outcome from PCC and Complaints case. Subject Contact with Participant Activity Type Inbound Email Case 37617802 Case Type or Category Feedback and Complaints - 37617802 Outcome Not Applicable Completed Date/Time 19/8/2026, 12:18 pm Alias MDT184 Comments *** Due to Save for later error, notes do not populate in Details of the request *** Enquiry Type: Feedback/Complaint Enquiry Received: 19/08/2026 Enquirer Name: Ivan Brecevic Enquirer Email: brecelicthomas@gmail.com Enquirer Number: Enquirer Verified: N/A, referred Enquirer Relationship: Participant Complaint Case: 37617802 Related Case: 37637709 Complaint Level: Level 2 Complaint Theme: Other* - Services Australia Restriction and Impact on NDIS Supports Complaint Risk Level: Medium Complaint Description: FOI 26/27-0675 Page 198 of 318
Was it AI? Follow the work
I suspect AI-assisted triage. These two pages give us something specific to investigate. They show a template instruction, a recorded approval, structured complaint fields and a save error. They do not identify a model, a prompt or an AI-generated classification applied to my file.
The reference to AI on LEX 3 and NDIA 197 is about my use of AI for correspondence. It does not identify the agency’s authoring tool. The alias field identifies the account associated with an entry; it cannot, on its own, tell us how the prose was written. A dot, a bullet or a repeated sentence cannot do that either.
There is public evidence of agency AI activity. Services Australia’s October 2025 estimates brief, released in LEX 88598, describes automation and AI capabilities and an opt-in Microsoft Copilot trial. The same brief says AI was not used to determine customer outcomes or process claims. That is a dated agency statement about its practices. The missing link is the record of what happened in this particular case.
The records that would answer it
- The saved note’s creation and edit history, with the business role attached to each event.
- The review macro or template version used on 11 August, including instructions for mandatory fields.
- Any case-linked routing rule, model output, suggested summary, classification or risk score, and the staff action accepting, changing or rejecting it.
- The NDIA error or support ticket for “Save for later”, affected fields and any repair or re-entry history.
- The source of the restriction explanation on NDIA 197 and the recorded review or outcome of complaint 37617802.
The overnight NDIA clarification already asks for the source of the 19 August entry and any audit or disclosure trail. It asks the agency to identify whether the source was my account, a document, a call or an electronic exchange. That is where the next instalment begins. Show the source. Show the change. Show who relied on it.
The pile behind the pair
The accompanying reading pack contains 24 extracted pages. The next pairs are already visible: LEX 11 and NDIA 199 on the office visit; LEX 3 and NDIA 197 on how AI-assisted correspondence is described; LEX 13 and NDIA 222 on the source material carried into later decisions. Each needs its own close reading.
Page concordance for all 24 extracts
| Record | Printed page | Original PDF page | Pack page |
|---|---|---|---|
| LEX | 1 | 1 | 1 |
| LEX | 2 | 2 | 2 |
| LEX | 3 | 3 | 3 |
| LEX | 4 | 4 | 4 |
| LEX | 5 | 5 | 5 |
| LEX | 11 | 11 | 6 |
| LEX | 12 | 12 | 7 |
| LEX | 13 | 13 | 8 |
| LEX | 16 | 16 | 9 |
| LEX | 17 | 17 | 10 |
| LEX | 18 | 18 | 11 |
| LEX | 26 | 26 | 12 |
| NDIA | 197 | 79 | 13 |
| NDIA | 198 | 80 | 14 |
| NDIA | 199 | 81 | 15 |
| NDIA | 221 | 103 | 16 |
| NDIA | 222 | 104 | 17 |
| NDIA | 237 | 119 | 18 |
| Reasons | 1 | 1 | 19 |
| Reasons | 4 | 4 | 20 |
| Reasons | 5 | 5 | 21 |
| Reasons | 7 | 7 | 22 |
| Reasons | 9 | 9 | 23 |
| Reasons | 10 | 10 | 24 |
Read the sequence
The source pages, the requests and the overnight correspondence belong together. These are the linked instalments published on 18 November.
- How to write a better FOI request — put my request on the bench
- The file calls my writing AI. Which tools wrote the file?
- A risk profile ought to have a source
- The big dossier needs individual records
- Who supplied the flag?
- Old material, new decisions
- The request is in Sent. Five addresses say otherwise.
- Copied to Parliament. What enters the register?
- The debt, the missing call and the hospital file
- One request, one recipient, one bounce
- The complaint had a risk level. Where did its words go?
- They count the emails. I asked for the work ledger.
- Five complaints finalised. Where are the answers?