Good for the Goose, Good for the Gander: Show Me the Portal Reply
At 7.20 pm on 17 October 2026, Centrelink’s upload history shows Customer Feedback.pdf arriving through Online Services. Three minutes later it shows Enquiry Letter.pdf arriving through the mobile app. I can show you the screen. What I want Services Australia to show me is what happened on its side of the counter.
What’s good for the goose is good for the gander. If my account of sending something needs a timestamp and a document, an agency’s account of answering it should have a reply, a date and a destination. The same standard cuts both ways. I have to count the occasions where the agency did act.
Exhibit 1 · Two rows on the original screen
| Register ID | Portal display, 17 October 2026 | What I can verify |
|---|---|---|
| SA-002 | 19:20 · Customer Feedback.pdf | Online Services. Document type UNSFBK. |
| SA-001 | 19:23 · Enquiry Letter.pdf | Mobile App. Document type Other document. |
The retained screenshot IMG_0602 shows both entries. It also tells the customer that previously uploaded documents are available to view or download online for only 24 hours after upload. Months later, I can read the labels. I can’t open those two originals from this screen to show what each one said. A recovered Rent Assistance review letter dated 16 October is a candidate. Neither a similar date nor a plausible subject ties that letter to either upload.
Exhibit 2 · The agency did record action
Services Australia’s own release, LEX 93986, PDF and stamped page 30, gives us the other half of the test. At 12.47 pm on 27 March 2025, an officer recorded finalising three online complaints because successful contact had not been made. At 1.01 pm, a second entry records two Ask Hank complaints entered and finalised. On 28 March at 11.54 am, the file says an “Unable to Contact letter” was sent.
That is five identifiable complaint references across two entries and a recorded outward letter. It is evidence of handling. The page does not reproduce five answers, confirm delivery of the letter or match those complaints to the individual uploads in my spreadsheet. Anyone auditing this file should be able to say all three things in the same breath.
Exhibit 3 · Where 128 became 135
The original register has 128 upload-history rows. Its source column marks 119 as checked against screenshots and nine as carried forward. The 18 November dossier records 69 screenshot files and 52 distinct file hashes. Overlapping screens can show the same upload several times.
The corrected register keeps the 128 IDs, records eight transcription corrections and adds seven displayed entries. That makes 135 rows, 70 from the mobile app and 65 from Online Services. The earliest corrected entry is a medical certificate on 19 November 2024. The latest is the October 2026 enquiry above. Medical evidence, accommodation documents, rent certificates and FOI requests belong in that history. A complaints total can’t be read off it.
What I asked Services Australia to produce
On 16 November 2026 I sent the FOI team the 128-row spreadsheet and Markdown schedule. A delivery failure identified the separately copied complaints address. On 18 November I sent supplementary particulars in the same thread asking for FYI and feedback records beyond the upload screen. A sent message, a failed copy and a formal agency registration are three separate facts.
For each item, I want the portal receipt or backend ID, any linked complaint, the handling decision and the actual outward response. If items were combined, which ones and under what reference? If a call counted as the answer, where is the note of what was explained? If a file was closed after an unsuccessful call, what opportunity did I have to read the decision and respond?
The answer I am looking for is a row I can trace from my screen to theirs and back to me.
Sources checked on 19 November 2026 · Original 128-row register and retained screenshot IMG_0602 · corrected 135-row content index · LEX 93986, page 30 · sent FOI thread of 16 and 18 November. Read the complete public upload chronology · Truth Sequences evidence index.
Comments
Post a Comment