Telecommunications (Statutory Infrastructure Providers—Circumstances for Exceptions to Connection and Supply Obligations) Determination 2024

The Determination rests on three core statutory building blocks, each reflected in the instrument text. First, the underlying statutory obligations are in s 360P and s 360Q of the Telecommunications Act 1997, which impose on SIPs an obligation to connect an end‑user at premises to a qualifying telecommunications network and to supply eligible services to carriage service providers on reasonable request (see notes in Part 2). Second, Parliament authorised the Minister to determine circumstances in which those obligations do not arise (subsections 360P(3) and 360Q(4) as cited in clause 3). Third, the Determination aligns certain exceptions with existing competition and access law under the Competition and Consumer Act 2010, specifically Part XIC declared service rules and exceptions (clauses 7(m) and 7(n) citing ss 152AR and 152AXB of the CCA).

Key definitional and scope points from the instrument:

• Relevant SIP: the SIP responsible for the service area that contains the premises subject to the request (clause 4(1)). The Determination explicitly contemplates more than one relevant SIP for a service area and allows the same circumstances to apply to each relevant SIP (clause 4(4)).
• End‑user and premises: the Determination treats an end‑user, for the purpose of requests, as the person who has entered into a legally binding arrangement with the carriage service provider for connection or supply to specified premises, unless the request says otherwise (clause 4(2)). For building lots with multiple premises, a request is taken to relate to the individual premises specified (clause 4(3)).
• Reasonableness and procedural standards: the Determination repeatedly uses standards such as "reasonably determined", "reasonable endeavours", and "reasonable timeframe" to qualify when a SIP can rely on an exception (see numerous clauses in 6 and 7). Those standards are embedded in the instrument rather than spelled out in detailed tests, so they are central conceptual levers for SIP discretion.
• Procedural steps when invoking certain exemptions: where an on‑site inspection identifies a topographical or other "impediment" that prevents connection or supply, the SIP must notify the requesting carriage service provider in writing, provide details of reasonable adjustments that could remedy the impediment, request the carriage service provider to notify the end‑user, and allow a reasonable timeframe for remedial action before relying on the exemption (clause 6(m)(ii)-(iv); clause 7(l)(ii)-(iv)).
• Publication obligations and terms and conditions: the Determination recognises the SIPs’ statutory obligations under the Act to publish their price and non‑price terms and conditions for connection and supply on their websites (citing ss 360W and 360X in notes to clauses 6(i) and 7(h)). It makes non‑acceptance of those terms by the carriage service provider a specified circumstance for exemption.

Conceptually, the Determination translates a set of practical, operational impediments into formal legal carve‑outs. The instrument organises those impediments into discrete categories: site readiness and compliance (construction status, structural safety, removal of impediments), access and consents (entry, attachment permissions, third‑party civil works), power and equipment availability, safety risks, pre‑existing service arrangements, fraudulent or defective requests, identity and occupancy/legal title issues, procedural non‑compliance with published SIP terms, and the special treatment of declared services under the CCA access regime. Each category is mapped to either connection exceptions (Division 1) or supply exceptions (Division 2) with largely parallel language.

The Determination also formally aligns the SIP exceptions with industry operational steps,inspection, written notification, requests to the carriage service provider to inform the end‑user, exhaustion of lawful avenues for access, and reliance on documentation for third‑party networks. Those procedural overlays are explicit mechanisms through which SIPs may lawfully decline to perform statutory obligations under the Act.

The Determination affects three classes of actors directly and several others indirectly.

Directly affected parties:

• Statutory infrastructure providers (SIPs): the Determination governs when SIPs can lawfully decline to connect premises to a qualifying telecommunications network under s 360P, or decline to supply eligible services under s 360Q. It gives SIPs specific circumstances they may rely on to avoid those statutory duties (see clauses 6 and 7). The instrument also imposes procedural expectations on SIPs when invoking certain exemptions, such as written notification and the obligation to have undertaken reasonable endeavours to obtain access (clauses 6(h) and 7(g) and the related notes).
• Carriage service providers (CSPs): CSPs are the parties that make requests on behalf of end‑users for connection and supply. The Determination changes the set of outcomes a CSP may face when requesting connection or supply: requests may lawfully be refused in specified situations. The Determination also imposes obligations on CSPs in the operational chain, for example to notify end‑users of impediments when requested by the SIP (clauses 6(m)(iii) and 7(l)(iii)), and to accept SIPs’ published terms and conditions where those are a prerequisite for supply or connection (clauses 6(i) and 7(h)). The Determination further contemplates that CSPs may need to provide documentation to SIPs to demonstrate that a third‑party network is in place (clauses 6(f) and 7(e)).
• End‑users at premises: the person who has entered into a legally binding arrangement with a CSP for connection or supply is treated as the end‑user for the Determination’s purposes (clause 4(2)). End‑users are affected because the Determination permits SIPs to refuse connection or supply in specified circumstances such as lack of power at premises, lack of legal right to occupy, presence of impediments, or where the premises is served by a third‑party network that is not being withdrawn (clauses 6(b), 6(l), 6(m), and 6(f)). End‑users also may need to undertake work to remove impediments or provide access/consent within a reasonable timeframe if they wish the SIP’s obligation to arise (clauses 6(m)(ii)-(iv) and 7(l)(ii)-(iv)).

Indirectly affected parties:

• Property developers and owners: the Determination identifies developer‑responsibility civil works as a reason SIPs may lawfully decline to connect if civil works required to support the connection have not been supplied or arranged by the date requested (clause 6(d)). The instrument explicitly notes that Part 20A of the Act generally requires developers to arrange civil works to ensure fibre‑ready facilities are installed; the Determination therefore interacts with developer obligations.
• Operators of third‑party networks and alternative network providers: where premises are already connected to another qualifying telecommunications network, SIPs may decline to connect or supply if certain documentary tests are met (clauses 6(f) and 7(e)). This affects competitive interactions and transfer processes between networks.
• Local and state authorities: because a SIP may decline to connect or supply where doing so would contravene applicable Commonwealth, State, Territory or local laws and no lawful steps to avoid contravention are reasonably available, local planning and building compliance decisions can have immediate operational effects on telecommunications connection and supply (clauses 6(c) and 7(c)).

Who pays and who bears costs:

• The Determination reallocates immediate compliance costs by allowing SIPs to require end‑users, developers or CSPs to resolve site impediments, provide power sources, arrange civil works, grant access and consents, or accept SIPs’ published terms before SIPs’ obligations arise (see clauses 6(b), 6(d), 6(h), 6(i), 6(m) and their parallels in clause 7). Those parties therefore bear the transaction and remediation costs if they want connection or supply to proceed.
• CSPs are expected to provide documentary evidence in some cases, for example that a third‑party network currently supplies the premises and that the service is not about to be withdrawn (clauses 6(f) and 7(e)). Gathering and presenting that documentation is a cost to CSPs.

Decision‑making power and discretion:

• The Determination assigns the SIP the power to make a number of determinations on "reasonable grounds" or after "reasonable endeavours", such as whether building works are sufficiently progressed, whether an end‑user lacks legal right to occupy, whether a request is fraudulent, or whether particular topographical features render premises incapable of supply (clauses 6(a)(i), 6(l), 6(k), 6(m) and parallel clauses in Division 2). That discretion is subject to the Act’s standard legal review mechanisms but is otherwise embedded in the instrument.

Overall, the Determination affects the incentive structure of SIPs, CSPs, end‑users and property developers by mapping a set of operational realities to formal legal escape routes from connection and supply obligations, and by prescribing procedural steps which the SIP must or should take before relying on certain exceptions.

The Determination itself does not create standalone duties in the sense of new obligations beyond those in the Act, but it allocates rights to SIPs to decline to perform statutory duties in clearly specified circumstances and it formalises certain procedural duties on both SIPs and carriage service providers. The main statutory duties that are relevant remain those in the Telecommunications Act 1997, specifically s 360P (connection obligations) and s 360Q (supply obligations). The Determination defines when those obligations do not arise by listing circumstances in clauses 6 and 7.

SIPs’ rights under the Determination

• Right to decline connection or supply in enumerated circumstances: A SIP may lawfully decline to connect premises or supply an eligible service when the specific circumstances in clause 6 (connection) or clause 7 (supply) apply. Examples include where premises are under construction and not sufficiently progressed (clause 6(a)(i), clause 7(a)(ii)), where a power source is unavailable (clause 6(b), clause 7(b)), where civil works required and not the SIP’s responsibility remain undone (clause 6(d)), and where installation would expose workers or the public to unreasonable health or safety risks (clause 6(g), clause 7(f)). The instrument grants the SIP legal cover for refusal in each listed circumstance.
• Procedural entitlement to rely on documentation and inspections: SIPs can base a refusal on evidence provided by the requesting carriage service provider or other information, for example to show an existing third‑party network connection (clause 6(f), 7(e)). SIPs can conduct on‑site inspections to determine topographical impediments and then notify the carriage service provider (clause 6(m), clause 7(l)).
• Right to require acceptance of published terms and conditions prior to obligation: The Determination makes non‑acceptance of a SIP’s terms and conditions for connection or supply a specified circumstance allowing a SIP to refuse (clause 6(i) and note referencing s 360W; clause 7(h) and note referencing s 360X). This gives SIPs a contractual gating mechanism: if CSPs do not accept the fully published terms, SIPs may lawfully decline.

SIPs’ procedural duties imposed by the Determination

• Written notification and reasonable endeavours: Where an impediment is identified that would render premises incapable of supply, the SIP must notify the requesting CSP in writing and provide details of reasonable adjustments that could remedy the impediment (clause 6(m)(ii); clause 7(l)(ii)). The SIP must have undertaken reasonable endeavours to obtain access or consent before relying on access refusals (clause 6(h)(ii); clause 7(g)(ii)-(iii)). The SIP is required to have exhausted all lawful avenues to obtain access before relying on that exception (clause 6(h)(iii); clause 7(g)(iii)).
• Requesting CSP to inform end‑user: The SIP must ask the requesting CSP to notify the end‑user in writing of the impediment and related details (clause 6(m)(iii); clause 7(l)(iii)). This places a communicative duty on the SIP in the operational chain.

Carriage service providers’ duties and rights

• Right to make requests on behalf of end‑users: CSPs retain the statutory right to make reasonable requests for connection and supply under the Act. The Determination does not extinguish their ability to request, but alters the situations in which SIP obligations will follow.
• Duty to accept reasonable SIP terms where required: If the SIP’s terms and conditions are compliant with the instrument, non‑acceptance by the CSP is a stated ground for exemption (clause 6(i); clause 7(h)). The CSP therefore has a practical duty to accept network terms if it wants to avoid the exception.
• Duty to provide information and to notify end‑users when asked: CSPs may be required to provide documentation to demonstrate that a premises is served by a third‑party network for the SIP to rely on the exemption (clauses 6(f) and 7(e)). CSPs may also need to notify end‑users of impediments when requested by SIPs, as part of the SIP’s procedural steps (clauses 6(m)(iii); 7(l)(iii)).
• Duty to comply with industry transfer processes: The Determination allows SIPs to decline to process transfers where the requesting CSP has not undertaken actions required under any industry standard, code or guideline applicable to such a transfer (clause 7(p)). This places on CSPs the responsibility to follow industry transfer protocols.

End‑user duties and rights

• Right to request connection via a CSP: The Determination acknowledges the end‑user’s position as the contracting party with the CSP and treats that contracted person as the end‑user for the purpose of requests (clause 4(2)). The DSP (duty‑statutory position) remains the existing Act obligations, modified by the Determination’s exceptions.
• Duty to provide site readiness, power and access where necessary: The Determination makes lack of a power source, lack of access, refusal to grant consent, inability to occupy premises lawfully, and failure to remove impediments within a reasonable timeframe reasons for SIPs to refuse connection or supply (clauses 6(b), 6(h), 6(j)-(l), 6(m)(iv) and parallels). End‑users thus bear the practical obligations to prepare premises and cooperate with access arrangements if they want SIPs’ duties to attach.

Other statutory and regulatory duties referenced

• Publication of terms and conditions: The Determination recognises the Act’s publishing duties on SIPs for connection and supply terms, referencing ss 360W and 360X of the Act. Compliance with those publishing duties is a precondition to the SIP relying on the non‑acceptance exception (note to clause 6(i); note to clause 7(h)).
• Interaction with the CCA declared services framework: The Determination permits SIPs not to supply an eligible service where they are not required to do so under the CCA’s category A or B standard access obligations, with explicit textual references to ss 152AR and 152AXB of the CCA (clause 7(m) and 7(n)). That links SIP rights under this Determination to the access obligations and exceptions in the CCA.

Enforcement and remedies are not specified in the Determination itself. The instrument allocates rights and defines circumstances where SIPs’ statutory duties are suspended, and therefore enforcement against a SIP for failure to connect or supply will depend on whether the SIP’s refusal fits within the enumerated circumstances and on the enforcement and dispute resolution mechanisms provided in the Act and other statutes or contracts. The Determination sets out the rights and procedural duties that parties must observe to have or to avoid obligations arising, but it leaves the legal consequences of improper reliance on exceptions to the Act’s broader enforcement framework.

The Determination does not itself create new criminal offences, civil penalties, or a bespoke enforcement regime. It is a ministerial determination that specifies factual and procedural circumstances in which the statutory duties in the Telecommunications Act 1997 to connect premises to a qualifying telecommunications network (s 360P) or to supply eligible services to carriage service providers (s 360Q) do not arise (clause 3; Part 2). The instrument therefore functions as a rule about the scope of statutory obligations rather than a standalone sanctioning instrument.

What the Determination provides about enforcement indirectly

• Preconditions for liability under the Act: Because the Determination identifies when SIP obligations do not arise, whether a SIP may be subject to enforcement under the Act for failing to connect or supply depends on whether the factual circumstances relied on by the SIP fall within the Determination’s enumerated exceptions. If a SIP refuses to connect or supply outside of these circumstances, enforcement mechanisms under the Act and applicable regulatory instruments could be invoked. The Determination does not identify the specific enforcement mechanisms; those remain located in the Act and any regulatory instruments made under it.
• Procedural steps that affect evidentiary burden: The Determination imposes procedural steps on SIPs when invoking certain exceptions. For example, when an impediment is identified, the SIP must notify the requesting CSP in writing, provide details of reasonable adjustments, ask the CSP to notify the end‑user, and allow a reasonable timeframe for remedial action before relying on the exception (clauses 6(m)(ii)-(iv) and 7(l)(ii)-(iv)). These procedural steps create a documented trail and evidentiary requirements the SIP must satisfy to rely on the exemption. Failure by the SIP to follow these steps could be material in any dispute or enforcement action over whether the SIP lawfully declined to connect or supply.
• Reliance on "reasonable" standards creates reviewable discretion: The Determination repeatedly uses standards such as "reasonably determined", "reasonable endeavours", and "reasonable timeframe", for instance in relation to assessing building progress, obtaining access, or deciding that a request is fraudulent (see many subclauses in clauses 6 and 7). Those standards are legal standards susceptible to review in judicial or administrative proceedings. A party alleging incorrect application of an exception would need to challenge the reasonableness of the SIP’s assessment through the normal dispute resolution routes under the Act or judicial review avenues, where justiciable.

External enforcement regimes remain applicable

• Competition and access regime: For eligible services that are declared services under the Competition and Consumer Act 2010, the Determination expressly permits SIPs not to supply where they are not required to do so under ss 152AR and 152AXB of the CCA (clauses 7(m) and 7(n)). Enforcement within the declared services framework, including determinations by the ACCC or other mechanisms provided in the CCA, remains relevant where the CCA’s rules are implicated. The Determination does not abolish those frameworks; it maps the Act’s SIP exceptions to the CCA exceptions.
• Contractual and industry remedies: The Determination anticipates industry standards, codes or guidelines for processes such as transfers of eligible services. It makes non‑compliance with those industry transfer processes a basis for a SIP to refuse supply or transfer (clause 7(p)). Disputes over adherence to such codes may be addressed under industry dispute resolution mechanisms, contract law or regulatory oversight depending on the instrument and the parties involved.

Operational enforcement risks and evidence issues

• Documentation and written notices will matter: The Determination’s requirements that SIPs notify carriage service providers in writing for certain exemptions, and that CSPs provide documentation in specified circumstances (for example, proof of third‑party network supply), creates a record‑keeping and documentary burden. Failure to produce or retain such documents will make it harder for a SIP to justify a refusal in a regulatory or legal challenge.
• Ambiguity in "reasonable" standards creates scope for disputes: The frequent use of open‑ended standards such as "reasonable endeavours" and "reasonable timeframe" will generate disputes about the sufficiency of steps taken. Aggrieved parties may seek remedies by arguing that a SIP’s decision was not reasonable in the circumstances.
• No explicit administrative appeal process in the Determination: The instrument does not set out a special internal appeal or fast‑track dispute process specific to these exemptions, so affected parties will need to rely on the Act’s general dispute resolution and enforcement mechanisms, industry complaint processes, or judicial review where applicable.

In short, the Determination changes the circumstances under which SIPs will be in breach of their connection and supply obligations, but it leaves the Act’s enforcement architecture to operate against those altered obligations. The Determination embeds procedural and evidentiary expectations that will shape how enforcement arguments are advanced, while leaving ultimate sanctions, remedies and dispute resolution to the Act, the CCA where relevant, industry codes and the courts.

This Determination explicitly cross‑references and interacts with several other statutory regimes and legal concepts described in its text. The instrument frames its exceptions by reference to provisions in the Telecommunications Act 1997 and to the Competition and Consumer Act 2010. It also makes practical reference to planning, building, and local laws by identifying contraventions of those laws as grounds for exemption. The key points of intersection are the following.

Interaction with the Telecommunications Act 1997

• Enabling authority: The Determination is made under subsections 360P(3) and 360Q(4) of the Telecommunications Act 1997 (clause 3). The instrument therefore operates as a ministerial determination that specifies the circumstances in which the statutory obligations in ss 360P and 360Q do not arise (notes preceding clause 6 and clause 7).
• Reference to other Act provisions: The Determination notes Part 20A of the Act regarding developers’ obligations to arrange civil works for fibre‑ready facilities and refers to Schedule 3 to the Act which gives carriers powers to install and maintain facilities and certain immunities from state and territory legislation (see notes to clause 6(d) and clause 6(h), and note in clause 7(g)). The Determination therefore sits alongside, and depends on, the Act’s broader schema for infrastructure installation and developer responsibilities.

Interaction with the Competition and Consumer Act 2010 and Part XIC

• Declared services exceptions: For eligible services that are declared services under the CCA, the Determination permits SIPs to decline supply where they are not required to supply under the CCA’s category A or category B standard access obligations (clauses 7(m) and 7(n)). The Determination explicitly incorporates by reference the tests and grounds in ss 152AR and 152AXB of the CCA, including the enumerated effects and events at paragraphs 152AR(4)(a)-(f), 152AR(9)(a)-(b), 152AXB(3)(a)-(c) and 152AXB(6)(a)-(b) and related grounds at 152AR(10) and 152AXB(7).
• Regulatory overlap: Where CCA declared service rules apply, both the Act and the CCA’s access regime may bear on whether a SIP must supply. The Determination does not displace the CCA; rather it provides that a SIP may rely on the CCA exceptions documented in the Determination as a reason not to supply.

Interaction with planning, building and local laws

• Compliance ground: The Determination allows a SIP to refuse to connect or supply where fulfilment would contravene applicable Commonwealth, State, Territory or local laws and no reasonably available lawful steps exist to avoid the contravention (clauses 6(c) and 7(c)). That means decisions by planning authorities, building regulators, or local government bodies can directly affect whether a SIP’s obligations fall due.
• Developers’ civil works: Clause 6(d) points out that where civil works not the SIP’s responsibility are required and have not been supplied or arranged by the date requested, the SIP may refuse to connect. The Determination notes Part 20A of the Act as establishing developers’ obligations to arrange civil works for fibre‑ready facilities. Thus, the developer’s compliance or non‑compliance with planning or developer obligations will influence SIP duties.

Interaction with industry standards, codes and guidelines

• Transfer processes and industry guidance: Clause 7(p) allows SIPs to decline to process requests that would result in the transfer of an eligible service the SIP is already supplying if the requesting CSP has not completed all actions required under any applicable industry standard, industry code or supplementary industry guideline for such a transfer. This explicitly integrates industry processes into the statutory calculus for supply obligations.

Interaction with property and contract law concepts

• Legal right to occupy: The Determination makes absence of a legal right to occupy the premises a ground for refusal (clauses 6(l) and 7(k)). Determinations about legal occupation will implicate property and tenancy law; SIPs rely on legal determinations or reasonable grounds to assess occupancy rights.
• Consent to attach facilities: Where SIPs need the consent of a person to attach or install facilities to premises, the Determination requires that reasonable endeavours be taken and all lawful avenues exhausted before a SIP can rely on a refusal of consent (clauses 6(h)(i)-(iii) and 7(g)(i)-(iii)). That interacts with property owner rights, strata or HOA governance documents, and rights under the Act (for example powers in Schedule 3), and may engage contract law between owners and tenants.

Interaction with occupational health and safety law

• Health and safety exemptions: Clauses 6(g) and 7(f) allow SIPs to refuse if installations would put employees, contractors, agents or members of the public at "unreasonable risk" of health or safety hazards. Determinations about health and safety risk will invoke workplace health and safety standards and possibly related statutory obligations, requiring SIPs to assess risks under the relevant WHS framework.

Records, notice and evidentiary interactions

• Written notices and documentation: The Determination’s procedural requirements for written notifications, requests that CSPs inform end‑users, and the use of documentation to show third‑party network supply create evidentiary interactions with contract law and regulatory record‑keeping standards. For example, clauses 6(f), 6(m)(ii)-(iv), 7(e), and 7(l)(ii)-(iv) require documentary steps that have legal force in subsequent disputes.

In summary, the Determination sits within an interlocking legal landscape: it is a ministerial instrument under the Telecommunications Act that takes account of developer obligations in the Act, folds in the CCA declared services framework for certain eligible services, and interacts practically with planning, building, property, occupational health and safety, industry codes and contract law. The Determination frames SIP non‑performance as lawful where the specified cross‑linked legal and operational conditions are met.

The Determination is a stand‑alone ministerial instrument dated 21 May 2024, and clause 1 records its formal name. Clause 2 sets out commencement, namely the day after registration. Clause 3 records the enabling authority under subsections 360P(3) and 360Q(4) of the Telecommunications Act 1997. Clause 4 contains definitions and interpretative rules specific to the Determination.

The instrument expressly repeals the entire Telecommunications (Statutory Infrastructure Providers,Circumstances for Exceptions to Connection and Supply Obligations) Determination 2021. Schedule 1, item 1, states "The whole of the instrument" and then the instruction "Repeal the instrument." That is a complete repeal of the 2021 Determination by this 2024 Determination (Schedule 1).

Beyond that explicit repeal, the Determination makes no other amendment to other instruments. Clause 5 states that "Each instrument that is specified in a Schedule to this instrument is amended or repealed as set out in the applicable items in the Schedule concerned, and any other item in a Schedule to this instrument has effect according to its terms." In the present instrument, the sole Schedule is Schedule 1 and its single item effects the full repeal of the 2021 Determination.

There is no further internal amendment history documented within the text. The Determination does not contain transitional or savings clauses concerning requests made before its commencement. It likewise includes no sunset clause or periodic review timetable. It replaces the 2021 Determination wholly from the date of commencement onward.

Administrative record details: The instrument records the responsible Minister (Michelle Rowland, Minister for Communications) and the date of making (21 May 2024). The commencement provision in clause 2 is immediate by being the day after registration, so there is no delayed or staged commencement schema.

No other amending instruments are referenced or attached within the Determination itself. The instrument therefore creates a clean substitution: the 2024 Determination supersedes and repeals the 2021 Determination, and sets out the current circumstances for exceptions to SIP connection and supply obligations as of its commencement.

For historical research or compliance review, note that the 2021 Determination is explicitly repealed, so parties should not continue to rely on its text after commencement. Any prior practice or contractual arrangements that were premised on the previous Determination will need to be evaluated against the 2024 text for continued validity.

The Determination text contains no references to any judicial decisions, tribunal determinations or administrative appeals that interpret or apply the 2024 Determination. It does reference statutory provisions and procedural mechanisms in the Telecommunications Act 1997 and the Competition and Consumer Act 2010 that themselves are subject to litigation, but the instrument does not cite or summarise any litigation.

Because the Determination is new as at 21 May 2024 and repeals the 2021 Determination in full, the text does not include any recorded adjudications concerning the 2024 instrument. Accordingly, there is no litigation history contained in or accompanying the instrument that explains how courts or regulators have treated these specific exceptions.

From the Determination’s structure, one can infer likely grounds for future disputes, which would be litigated under the Act or other applicable laws rather than in the Determination itself:

• Reasonableness disputes: The Determination repeatedly uses legal standards such as "reasonable", "reasonable endeavours" and "reasonable timeframe" (see clauses 6 and 7). These are classic grounds for challenge where an aggrieved party may contend that the SIP’s assessment was unreasonable or that the SIP failed to undertake reasonable endeavours.
• Procedural non‑compliance with the Determination’s notification requirements: Where an SIP invokes the "impediment" exceptions (clauses 6(m) and 7(l)), the SIP must have given written notice and supplied details of reasonable adjustments. Litigation or regulatory complaints may arise where those procedural steps are alleged not to have been followed.
• Conflicts between the Determination and CCA declared service obligations: Clause 7 ties SIP non‑supply exceptions to the CCA’s ss 152AR and 152AXB. Disputes could arise about whether the SIP’s reliance on the CCA exceptions is appropriate in particular fact patterns.
• Transfers and industry process disputes: Clause 7(p) allows refusal where the requesting CSP has failed to comply with industry standards or codes for transfer. This could produce disputes over whether the CSP followed applicable industry procedures.

However, because the Determination itself does not record any case law or prior adjudication about these exceptions, parties and practitioners must look to the Act, the CCA and general administrative and contract law for existing judicial principles that will be applied to disputes about the exercise of the Determination’s carve‑outs. Any litigation to challenge a SIP’s reliance on an exception will proceed by reference to the statutory framework and legal standards that govern the SIP’s conduct, evidence and reasonableness, not by reference to precedent specific to the 2024 Determination.

For practitioners preparing to litigate or arbitrate such disputes, the Determination’s procedural requirements create evidentiary focal points: written notices to CSPs and to end‑users, records of on‑site inspections, documentation of reasonable endeavours to obtain access or consent, and the documentary basis for reliance on third‑party network evidence will be central. Absent an existing body of case law on the 2024 Determination, litigants will need to rely on established principles from administrative law and telecommunications regulatory jurisprudence to frame challenges.

This Determination contains a number of details and drafting features that create practical and legal traps for the unwary. Below are specific points within the text that commonly produce disputes or unexpected outcomes, along with the mechanistic reasons they matter.

1. Frequent use of open‑ended standards such as "reasonable", "reasonable endeavours" and "reasonable timeframe". The instrument repeatedly requires SIPs to make "reasonable determinations", to use "reasonable endeavours", or to invite responses within a "reasonable timeframe" (see many subclauses in clauses 6 and 7). These standards are fact‑sensitive and will generate disputes about sufficiency of steps taken. Parties may differ over what counts as reasonable in rural versus metropolitan contexts, for example.

2. "Under construction and ... not sufficiently progressed" hinge language (clauses 6(a)(i) and 7(a)(ii)). The determination that building works "will not have sufficiently progressed to a stage that is adequate for the connection to be undertaken" is a SIP assessment. Absent objective milestones, parties may litigate whether the SIP's assessment was justified and what technical criteria govern "adequately" progressed works.

3. Power source requirement (clauses 6(b) and 7(b)). The Determination allows refusal where a power source is required and not reasonably expected to be available by the requested date. This raises practical questions about what constitutes an adequate power source, who must install it, and how "reasonably expected" is demonstrated. Disputes may arise when temporary power could be deployed or where multiple parties dispute responsibility.

4. Civil works not provided or developer responsibility (clause 6(d)). The Determination flags developer responsibility for civil works (note to clause 6(d) referencing Part 20A of the Act). Practitioners should not assume that SIPs will self‑perform civil works. If developers fail to provide pit and pipe or other civil infrastructure, SIPs may lawfully refuse connection, leaving end‑users and CSPs needing to negotiate with developers.

5. Existence of third‑party network (clauses 6(f) and 7(e)). SIPs can refuse where premises are connected to another qualifying network and evidence shows service will not be withdrawn and the end‑user does not intend to cancel. This creates evidentiary battlegrounds over the sufficiency and currency of documentation provided by CSPs to demonstrate withdrawal or cancellation intentions.

6. Access and consent requirements (clauses 6(h) and 7(g)). SIPs can refuse where access to non‑public areas or consents are required and have been refused after reasonable endeavours and exhaustion of lawful avenues. The Determination references Schedule 3 powers in the Act which give carriers some powers to inspect land and install facilities, but those powers have limits. SIPs invoking this exception must have a documented trail showing they exhausted legal options, and disputes will arise about whether alternate lawful avenues remained.

7. "Fraudulent" or "not legal right to occupy" grounds (clauses 6(k)-(l) and 7(j)-(k)). These grounds give SIPs discretion to refuse based on beliefs formed on "reasonable grounds". The Determination does not define evidentiary thresholds, so careful documentation of investigations and sources is necessary.

8. Procedural steps for impediments (clauses 6(m) and 7(l)). These exemptions require the SIP to notify the requesting CSP in writing, give details of reasonable adjustments, ask the CSP to notify the end‑user, and allow a reasonable timeframe for remediation. If the SIP fails to follow these steps, the SIP may find it harder to justify refusal later. Conversely, CSPs and end‑users who fail to act within the reasonable timeframe may lose entitlement to connection or supply.

9. Acceptance of SIPs’ published terms and conditions (clauses 6(i) and 7(h)). The Determination makes non‑acceptance a ground to refuse. Practitioners should check whether SIPs have complied with the Act’s publication requirements (s 360W and s 360X) because if those processes are deficient, the SIP’s reliance on non‑acceptance could be challenged.

10. CCA declared service exceptions (clauses 7(m) and 7(n)). The Determination ties non‑supply of declared services to the CCA’s sophisticated tests in ss 152AR and 152AXB. Parties should not assume that the Determination’s list is independent of the CCA; SIPs will need to demonstrate that supplying would have particular effects or that specified events would occur under those CCA provisions. That can require economic and factual analysis.

11. Industry transfer standards (clause 7(p)). Transfers of eligible services are tied to industry codes and guidelines. If CSPs do not comply with those standards, SIPs can refuse transfer. Disputes over which standards apply and whether they have been met may result in delays.

12. Multi‑SIP service areas (clause 4(4)). The Determination contemplates that more than one SIP may be relevant for a service area. Determining which SIP has responsibility for a premises may itself be contested, producing procedural delay.

13. No centralised appeal or dispute mechanism built into the Determination text. Remedies for wrongful refusal are not set out in the instrument and must be pursued under the Act’s general mechanisms, industry processes or courts. That may increase costs and time to resolve disputes.

In practice, these "gotchas" mean that parties should not assume a straightforward binary entitlement to connection or supply. The Determination shifts many operational details into discrete legal triggers and procedural steps that create evidentiary and timing risks. For SIPs, failure to document inspections, notifications and reasonable endeavours will weaken reliance on an exception. For CSPs and end‑users, failure to accept published terms, to arrange power and civil works, to provide necessary identification or documentation, or to follow industry transfer processes can quickly lead to lawful refusals under the Determination.

This section provides practical, instrument‑grounded steps for each affected party to reduce risk of lawful refusal under the Determination. The aim is to translate the Determination’s circumstances and procedural requirements into operational checklists that parties can adopt. Each recommended action is traceable to specific clauses in the Determination.

For carriage service providers (CSPs)

1. Verify end‑user contractual status and occupancy rights: Ensure the person identified as the end‑user is the party who has entered into a legally binding arrangement for connection or supply (clause 4(2)). Obtain and retain written evidence of the end‑user’s legal right to occupy the premises to counter any SIP assertion under clauses 6(l) and 7(k).

2. Provide complete, accurate requests: Ensure requests for connection or supply comply with any reasonable process or form requirements in the SIP’s access agreement or the terms published under s 360W or 360X. The Determination allows refusal for non‑compliant requests or invalid, inaccurate or incomplete information (clause 7(o)).

3. Accept published SIP terms and conditions where appropriate: If the SIP has published compliant price and non‑price terms under s 360W or s 360X, consider accepting those terms to avoid the non‑acceptance exception (clauses 6(i) and 7(h)). Document acceptance and maintain records of the published terms.

4. Arrange or confirm site readiness and power: Before requesting connection or supply, confirm that premises are structurally compliant with planning and development laws and that a required power source will be available by the requested date (clauses 6(a)(ii) and 6(b); clauses 7(a)(iii) and 7(b)). Obtain written confirmation from end‑users or developers as appropriate.

5. Provide documentary evidence of third‑party network status when applicable: If the premises is connected to another qualifying network, provide the SIP with documentation showing whether the third‑party service is active and whether it is to be withdrawn or cancelled within a specified timeframe (clauses 6(f) and 7(e)).

6. Follow industry transfer standards: If a request will result in transfer of an eligible service the SIP is already supplying, ensure all steps required by applicable industry standards, codes or guidelines have been completed (clause 7(p)). Keep logs and confirmations to avoid an SIP refusing on procedural grounds.

7. Cooperate with SIP notifications about impediments: If a SIP notifies you in writing of impediments and reasonable adjustments, act promptly to communicate the required remedial steps to the end‑user and to coordinate remediation. The SIP will have a right to refuse where the end‑user fails to remove impediments within the reasonable timeframe (clause 6(m)(ii)-(iv); clause 7(l)(ii)-(iv)).

For end‑users and property developers

1. Ensure structural and planning compliance: Confirm that premises are compliant with applicable planning, development and building laws pertaining to structural safety and integrity before requesting connection or supply. The Determination allows refusal where a permanent structure does not comply (clauses 6(a)(ii) and 7(a)(iii)).

2. Provide or arrange for power supply: If the eligible service requires an external power source, arrange that the power source will be available by the requested commencement date, or obtain evidence that it will be so (clauses 6(b) and 7(b)).

3. Arrange required civil works and pit and pipe installations when developer responsibilities apply: Developers should ensure that any civil works required to support connection are completed or arranged by the time of request; otherwise a SIP may refuse on the basis the civil works were not supplied or arranged (clause 6(d), note referencing Part 20A).

4. Grant and document access and consents: For attachments or internal installations, grant necessary consents and access to the SIP’s employees, contractors or agents. If consent cannot be given, be prepared that the SIP may have lawfully exhausted available lawful avenues and may refuse connection or supply (clauses 6(h)(i)-(iii) and 7(g)(i)-(iii)).

5. Remove identified impediments promptly: Where the SIP identifies particular topographical or other impediments and provides written details of reasonable adjustments that would enable connection, take action within the reasonable timeframe specified or coordinate with the CSP to do so (clauses 6(m)(ii)-(iv) and 7(l)(ii)-(iv)).

For statutory infrastructure providers (SIPs)

1. Document on‑site inspections and technical assessments: Where you assert that premises are under construction, structurally non‑compliant or otherwise impeded, maintain dated inspection reports, technical assessments and reasons supporting a "reasonable determination" as to progress or capability (clauses 6(a)(i)-(iii) and 7(a)(i)-(iv)).

2. Use and record "reasonable endeavours": Where access or consent is required, keep a record of efforts to obtain access, including correspondence, requests, invitations and, if applicable, notices of legal avenues pursued. The Determination requires that SIPs have undertaken reasonable endeavours and exhausted all lawful available avenues before relying on the access/consent exception (clauses 6(h)(ii)-(iii) and 7(g)(ii)-(iii)).

3. Provide timely written notices and details of reasonable adjustments: If an impediment is identified, notify the requesting CSP in writing, provide details of reasonable adjustments that could be undertaken to remove the impediment, and ask the CSP to notify the end‑user (clauses 6(m)(ii)-(iii) and 7(l)(ii)-(iii)). Retain copies of these notices as evidence.

4. Require and verify documentation from CSPs about third‑party networks: Where the premises is connected to another qualifying network, request and retain documentary evidence from the CSP to demonstrate whether the third‑party service will be withdrawn or cancelled within a specified timeframe (clauses 6(f) and 7(e)). Ensure that your reliance on such documentation is supported by objective evidence.

5. Publish and maintain compliant terms and conditions: Publish price and non‑price terms and conditions for connection and supply on your website as required by ss 360W and 360X of the Act, and keep records of when terms were published. If you intend to rely on non‑acceptance by CSPs as a ground for refusal, ensure your published terms are accessible and compliant (clause 6(i) note; clause 7(h) note).

6. Assess declared services against CCA tests: For declared services, document the economic and factual analysis showing that supply would have the effects enumerated in ss 152AR(4) or 152AXB(3), or that the events set out in ss 152AR(9) or 152AXB(6) are reasonably likely, when relying on the CCA‑based exceptions (clauses 7(m)-(n)). Retain that analysis to support decisions.

7. Train staff on "reasonable grounds" standards and recordkeeping: Because the Determination permits refusal on grounds such as belief of fraud or lack of right to occupy where founded on reasonable grounds, ensure staff understand the evidential standards required and keep contemporaneous notes that can be produced if the SIP’s decision is challenged (clauses 6(k)-(l) and 7(j)-(k)).

Cross‑party steps

1. Use clear contractual allocations of responsibility: CSPs, SIPs, developers and property owners should use contracts to allocate responsibilities for civil works, power connections, access consents, and timing. Well drafted contracts can reduce the incidence of disputes about who should act to remove impediments identified under the Determination.

2. Keep comprehensive records: Across the board, preserve written requests for connection or supply, all responses, inspection reports, evidence of power or civil works, copies of published terms, and any documents provided to support third‑party network status. The Determination’s reliance on written notice and documentary checks makes recordkeeping central to compliance and to defending or challenging refusals.

3. Establish dispute escalation processes: Given the Determination does not create a bespoke appeal mechanism, parties should build industry or contractual escalation pathways, including timelines for remediation and dispute resolution, to reduce litigation risk and to provide predictable processes when refusals are asserted.

Compliance with the Determination therefore requires a combination of procedural diligence, clear contractual arrangements, contemporaneous evidence, and proactive site readiness. Parties should treat the Determination as changing the trigger conditions for statutory obligations rather than as creating new substantive entitlements, and should organise operational processes to ensure that neither SIPs nor CSPs inadvertently fall into the pitfalls the Determination identifies.