Communication Restrictions and LEX 93986
Editorial and source note: This research summary contains analysis and unresolved questions. The internal citation markers in the draft have been removed and replaced with public source links below; no claim should be read as a proven finding unless the underlying record is identified.
Public sources: Services Australia responsibilities and contact arrangements · LEX 88368 disclosure (PDF) · LEX 93986 reading guide
Deep Research Report: Services Australia Communication Restrictions, Managed Service Plans, Privacy, Procedural Fairness and LEX 93986
Executive findings
The legislative framework in the material you supplied is broadly on the right track, but the deeper research materially changes the picture in two ways. First, a Services Australia communication restriction is not best analysed merely as a privacy or social-security secrecy issue. Services Australia publicly confirms that it uses Managed Service Plans (MSPs) to restrict how some customers may contact the agency, including restricting telephone numbers, requiring contact online or in writing, restricting attendance at service centres, or requiring appointments. Services Australia says MSPs may be imposed after customer aggression, where behaviour could pose a risk to staff safety, or where a customer requires particular support.
Second, there is now unusually detailed public evidence of Services Australia's internal MSP procedures. A 120-page disclosure released under FOI/LEX 88368 contains internal instructions governing the proposal, approval, review, extension, variation, recording and notification of MSPs. Those instructions expressly require procedural fairness, evidence-based decision-making, freedom from bias, customer participation, proportionality, written reasons, review rights and documented rationales.
That makes FOI/LEX 88368 potentially more important to a future analysis of LEX 93986 than the general legislation alone. It provides a concrete internal benchmark against which the handling of an individual restriction could be tested.
I searched specifically for LEX 93986, including on Services Australia's public website and disclosure-log domain, but did not locate a publicly indexed copy matching that reference. The searches instead returned unrelated uses of the number 93986. Accordingly, I cannot responsibly make findings about what LEX 93986 itself proves until the actual documents are available.
The legal foundation for restricting contact
Services Australia has a legitimate legal interest in protecting its workers and other persons from health and safety risks. Under s 19 of the Work Health and Safety Act 2011 (Cth), a person conducting a business or undertaking must, so far as reasonably practicable, ensure the health and safety of workers and ensure that other persons are not put at risk by the conduct of the undertaking. That provides an important statutory context for measures aimed at customer aggression and staff safety.
Services Australia's public customer guidance expressly connects that safety concern with MSPs. It states that an MSP may be put in place where behaviour has made staff or other customers feel unsafe, after an incident of aggression, or where behaviour could pose a risk to staff safety. The same guidance states that an MSP may limit communication channels but that the customer can still access payments and services.
This means the central legal question is unlikely to be simply, "Does Services Australia have any power to restrict communications?" The stronger question is whether the particular restriction was lawfully, rationally, proportionately and procedurally imposed, consistently with the agency's statutory functions, WHS obligations, privacy law, administrative-law principles and its own published procedures.
The Commonwealth Ombudsman has long recognised that government agencies may sometimes restrict a person's access because of unreasonable or unsafe conduct. Its guidance says restrictions can concern when, whom or how a person may contact an agency. But it also states that such decisions should be made at an appropriately senior level under an established written procedure, that the person should be advised in writing, and that options for review should be provided.
The Ombudsman's later complaint-assurance work similarly says service restrictions should be grounded in clearly documented procedures, with clearly defined circumstances for restriction and regular review by appropriate staff.
Those principles align strikingly with Services Australia's own internal MSP documentation.
What Services Australia's own MSP rules require
FOI/LEX 88368 is particularly significant because it goes far beyond the agency's high-level public webpage. The internal instructions state that MSP reviews must assess ongoing risk and whether a customer can transition back to standard service channels. They provide that an MSP may be ended, extended, varied or replaced, and that an MSP automatically ceases on its recorded end date if no extension or variation decision is made.
The same document states that MSP decisions must be based on the customer's individual circumstances and requirements and made on the merits using all available information. Staff are specifically instructed to apply procedural fairness, give a reasonable opportunity for customer input, avoid bias, gather evidence rather than rely on personal opinion or assumptions, give appropriate weight to relevant facts, and genuinely consider matters in dispute.
This is an exceptionally useful evidentiary benchmark. If LEX 93986 reveals that a restriction was imposed or maintained on the basis of assertion, assumption, untested characterisation, stale incidents or undisclosed allegations, that would not automatically establish illegality, but it could be evidence of non-compliance with the agency's own decision-making procedure and potentially support an administrative-law or Ombudsman complaint.
The policy also requires customer involvement. Customers may request a review at any time, and listed reasons for review include financial hardship, difficulty meeting obligations, alleged bias, changed circumstances, alleged unreasonableness and denial of an opportunity to contribute to the original decision.
When conducting a review, Services Australia says its decision-makers should consider the severity of the original incident, customer vulnerabilities, outstanding business, MSP documents and notes, information supplied by the customer, behaviour since implementation, compliance with restrictions, the success of servicing strategies, legal considerations and whether the customer continues to need access through a particular service channel.
The policy expressly requires proportionality. When considering the duration of a new MSP, the timeframe must be proportional to the customer's circumstances and the level of risk posed. It also instructs staff to consider partial rather than full channel restrictions where a full restriction could interfere with a person's obligations, adversely affect a vulnerable customer or prevent necessary services from being delivered.
That is one of the most consequential findings of this research. A restriction is not simply a binary safety measure. Services Australia's own rules contemplate tailoring and require decision-makers to consider less restrictive alternatives.
The policy also demands a documentary rationale. Every MSP must contain a "Rationale for decision" note describing, among other matters, the behaviour or vulnerabilities leading to the MSP, the duration, relevant servicing strategies and the ongoing risk to staff.
Before approval of an MSP review, a draft outcome letter must be attached. The letter must describe relevant behaviour and considerations, explain the customer's continuing access to Services Australia and state the customer's right to request a review. After approval, the customer must be advised in writing of the outcome even if the MSP has not changed.
Those requirements create a highly concrete evidentiary checklist for LEX 93986: Was there a documented incident? Was the risk assessed? Who approved the restriction? Was a rationale recorded? Was customer input sought? Were alternatives considered? Was the restriction proportionate? Was an end date recorded? Was the customer notified? Were review rights explained? Was the restriction later reviewed?
Privacy, accuracy, disclosure and record correction
The Privacy Act 1988 adds an important second layer because MSPs depend heavily on personal information: incident reports, allegations about behaviour, risk assessments, staff observations, vulnerability information and internal alerts. The current Privacy Act compilation confirms that Commonwealth agencies are subject to the Australian Privacy Principles, including APP 6 on use and disclosure, APP 10 on data quality, APP 12 on access and APP 13 on correction.
APP 6 generally limits the use or disclosure of personal information to the purpose for which it was collected unless an exception applies, including consent, reasonable expectations in appropriate circumstances, or use or disclosure authorised or required by law.
Services Australia's current privacy policy expressly states that its staff are subject to secrecy provisions covering social security, family assistance, health, child support and related information, which restrict access, use and communication of protected information, including within the agency.
Under the Social Security (Administration) Act 1999, protected information may be obtained, recorded, used or disclosed for specified authorised purposes. Section 202 is therefore relevant if information derived from a social-security record was used to create or administer a restriction.
A particularly important principle is APP 10. OAIC guidance states that an agency must take reasonable steps to ensure personal information it collects is accurate, up to date and complete, and that information it uses or discloses is accurate, current, complete and relevant having regard to the purpose of use or disclosure.
This matters because a customer-aggression designation, risk note, "counterproductive behaviour" characterisation or internal safety alert may materially affect the way a person can deal with Services Australia. OAIC guidance says more rigorous accuracy steps may be required where inaccurate information could cause greater adverse consequences.
OAIC also draws an important distinction between facts and opinions. A third-party opinion is not automatically inaccurate merely because the individual disagrees with it, but its reliability may depend on whether it is properly identified as opinion, whether it reflects the view actually held, whether it is informed, and whether competing facts and views were considered.
That distinction should be central in any LEX 93986 examination. An internal note saying, for example, "customer made three calls on 5 May" is a factual assertion capable of objective verification. A notation that a customer "poses an ongoing risk" is evaluative. A statement that the customer "threatened staff" could be either factual reporting or an allegation, depending on source and evidence. Those categories should not be treated interchangeably when assessing record accuracy. OAIC's guidance supports scrutinising both factual accuracy and whether opinions are complete, current, relevant and not misleading.
APP 12 gives a person a right, subject to statutory exceptions, to access personal information held about them. If access is refused, the agency ordinarily must give written reasons and advise the individual of complaint mechanisms.
APP 13 requires reasonable steps to correct personal information that is inaccurate, out of date, incomplete, irrelevant or misleading. If correction is refused, the agency generally must provide reasons and complaint avenues, and the individual can request that a statement disputing the information be associated with the record.
The Freedom of Information Act 1982 adds a separate avenue. Section 11 provides a legally enforceable right of access to agency documents subject to exemptions. Part V, including s 48, allows a person to seek amendment or annotation of a personal record that is incomplete, incorrect, out of date or misleading and is used or available for use for an administrative purpose.
Services Australia's own MSP policy explicitly states that free-text MSP notes are subject to the FOI Act. It also says, in the context of safety alerts, that information in CIMS must be factual, use exact quotations where appropriate and must not include personal commentary or opinion.
That internal requirement could become particularly important if LEX 93986 contains subjective descriptions presented as facts.
Formal information notices are a separate issue
The original text correctly identified the statutory requirements surrounding formal information demands, but those provisions should not be conflated with an MSP. The current Social Security (Administration) Act 1999 gives the Secretary information-gathering powers in Part 5, including ss 191A–196. Section 191A requires a reasonable belief that the person can provide the information or document sought, while ss 192–195 specify the circumstances in which information may be required.
Section 196 provides that a requirement under that Division must be made by written notice. The notice must describe the information or document, explain how it must be provided, give a compliance period, identify the relevant officer where applicable, and state that the notice is given under s 196. Ordinarily the compliance period cannot expire earlier than 14 days after notice unless a shorter period is reasonably justified for effective administration of social-security law.
DSS's Social Security Guide confirms those formal requirements and distinguishes Part 5 notices from other forms of social-security notification.
Accordingly, the question "Was a valid written s 196 notice issued?" is relevant only if LEX 93986 actually involves a statutory demand for information under Part 5. It is not a general prerequisite for imposing an MSP or restricting communication channels. The earlier draft risked blending two legally distinct matters.
Procedural fairness and review mechanisms
Administrative law provides the broader accountability architecture. The Attorney-General's Department identifies merits review, Ombudsman investigation, OAIC investigation, internal agency processes and judicial review as distinct mechanisms through which Commonwealth administrative decisions may be scrutinised.
Services Australia's internal MSP procedure itself uses the language of procedural fairness and requires an opportunity for customer input, freedom from bias, evidence-based assessment and genuine consideration of disputed matters.
That does not automatically mean every departure from internal policy amounts to a jurisdictional error or invalidity. Whether common-law procedural fairness is legally enforceable in relation to a particular MSP decision would depend on the legal character of the decision, its source, its consequences, any applicable statutory scheme and the circumstances of the case. The Attorney-General's natural-justice guide remains useful as best-practice guidance, although the Department expressly notes that the 2007 guide has not been updated for subsequent legal developments.
The most immediately relevant review route appears to be Services Australia's own MSP review procedure. Its public webpage says a person may contact the named MSP contact to discuss the restriction and, if dissatisfied, ask the agency to review it.
A service complaint can also be made to Services Australia. The agency says it aims to resolve complaints within 10 working days and may review records, correct errors and advise of further options. If dissatisfied, the person may complain to the Commonwealth Ombudsman.
The Commonwealth Ombudsman confirms that it can investigate complaints about Services Australia, although it cannot itself direct the agency to change a decision. It generally suggests raising the matter with Services Australia first.
Privacy concerns may be taken through Services Australia's privacy complaint process and ultimately to the OAIC. Services Australia's current privacy policy expressly directs unresolved privacy complaints to the OAIC, while OAIC guidance confirms that complaints may concern collection, use or disclosure, accuracy, security, refusal of access or refusal of correction.
The Administrative Review Tribunal requires more caution. The ART has no general jurisdiction over every Services Australia administrative action; it can review only decisions for which legislation gives it jurisdiction. Its Centrelink jurisdiction principally covers statutory decisions concerning payments, benefits, debts, claims, rates and similar matters, usually after internal review by an Authorised Review Officer.
Therefore, it would be unsafe to state that an MSP or communication restriction itself is necessarily reviewable by an ARO or the ART. If an MSP separately caused or accompanied a reviewable social-security decision—for example, a payment suspension or cancellation—that underlying statutory decision may have merits-review rights.
Evidentiary test for LEX 93986
The strongest future analysis would not start by presuming unlawfulness. It would reconstruct the decision chronologically and test each stage against the agency's own MSP requirements, privacy obligations and applicable administrative-law standards.
| Issue to test | What the governing material requires | Evidence to seek in LEX 93986 | Significance if missing or contradicted | |---|---|---|---| | Trigger for restriction | MSP should be connected to identified risk, aggression, counterproductive conduct, vulnerability or another recognised basis | Incident report, referral, chronology, source material | May undermine factual foundation or rationality of the restriction. | | Evidence quality | Decisions should rely on evidence, not assumptions or personal opinion | Call recordings, correspondence, contemporaneous notes, witness reports | Unsupported characterisations may conflict with internal decision rules and APP 10 expectations. | | Procedural fairness | Customer should have a reasonable opportunity to contribute and disputed matters should receive genuine consideration | Invitation to respond, customer submissions, review notes | Absence may support an administrative-process complaint. | | Bias | Review process should be free of bias; affected staff may be inappropriate reviewers | Identity and role of decision-maker/reviewer | Material involvement of an interested person may require closer scrutiny. | | Proportionality | Restriction duration and channel limitations should reflect actual risk; partial restrictions should be considered | Risk assessment, options analysis, reasons | A blanket restriction without consideration of alternatives may conflict with policy. | | Approval authority | MSP restrictions require the appropriate approving role under agency procedures | Approver identity, delegation/role, approval timestamp | Could establish procedural non-compliance if the wrong officer approved it. | | Written rationale | Every MSP must include a rationale describing behaviour, vulnerabilities, duration and risk | CIMS rationale note | Missing or generic reasoning would be important evidence. | | Notification | Customer should receive written notification of outcome and review rights | MSP letter, delivery record, SMS, contact note | Failure may conflict directly with the documented MSP procedure. | | Review cycle | MSPs must be reviewed and do not automatically continue indefinitely | Start date, end date, review invitations, review outcome | An expired or mechanically extended restriction could be significant. | | Accuracy of personal information | Information used should be accurate, current, complete and relevant | Incident descriptions, alerts, risk labels and source records | Material inaccuracies may engage APP 10 and correction rights under APP 13 or FOI Part V. | | Disclosure or cross-agency sharing | Protected and personal information must have a lawful basis for use/disclosure | Recipients, emails, referrals, inter-agency disclosures | Could engage APP 6 and statutory secrecy provisions. |
The core conclusion is therefore more precise than the original draft: Services Australia plainly has mechanisms for imposing communication restrictions, but its own published procedures constrain how those restrictions should be created, justified, documented, reviewed and communicated. FOI/LEX 88368 provides unusually detailed evidence of those constraints.
What remains unproven is whether LEX 93986 shows compliance or departure from those requirements. Until that record is available, claims that a particular restriction was unlawful, fabricated, unsupported, improperly disclosed, procedurally unfair or based on inaccurate information remain allegations rather than findings. The strongest next-stage evidentiary exercise would be a document-by-document chronology matching every incident, restriction, approval, rationale, notification, review and disclosure in LEX 93986 against the standards identified above.
Related archive: Managed Customer Trap · cross-agency evidence pack · parliamentary brief