A Code of Access to Telecommunications Transmission Towers, Sites of Towers and Underground Facilities

The Code defines a compact set of operational concepts that structure rights, duties and commercial allocation. Eligible Facility is the central asset class (cl. 6.1: “telecommunications transmission towers, sites of telecommunications transmission towers and eligible underground facilities” per clauses 33-35 of Part 5 of Schedule 1 to the Act). First Carrier is the owner/operator/controller of Eligible Facilities; Second Carrier is a Carrier seeking access (cl. 6.1). These two roles determine most entitlements and costs across the Code.

Make Ready Work (MRW) is a technical and cost concept defined in cl. 6.1 and is pivotal: MRW comprises the reasonable work necessary to prepare an Eligible Facility to accommodate a Second Carrier’s Equipment, including structural strengthening, head frames, rerouting, ducting, removal and replacement of towers, and other works (cl. 6.1, definition of Make Ready Work). The Code allocates responsibility and cost of MRW through cl. 4.4 and the Annexure Schedules. A Second Carrier may undertake MRW itself subject to qualification (cl. 4.4(1)); the First Carrier must perform MRW only where the Second Carrier is not qualified or where no competent contractors are available (cl. 4.4(5)). If the First Carrier performs MRW, Schedules (A1/B1) provide a detailed step process (Detailed Field Study, Orders, Responses, Delivery).

Master Access Agreement is a template negotiating concept (cl. 4.2). Where parties will repeatedly interact, the Code obliges them to make reasonable endeavours to negotiate a Master Access Agreement covering ordering, provisioning, maintenance, charges, dispute resolution, and technical rules (cl. 4.2(1), (4)). The Master Access Agreement binds subsequent site‑specific applications in its covered class (cl. 4.2(2)) but cannot displace the mandatory provisions set in Chapter 2 (cl. 1.2.2(3)).

Facilities Access Application and Information Package structure administrative flow. First Carriers must publish and provide an Information Package (cl. 3.1) describing contact details, physical arrangements, timeframes, financial security requirements, confidentiality forms and ordering practices. Second Carriers apply via a Facilities Access Application using Annexure procedures; the Annexures set concrete assessment periods (e.g. cl. 2.2 of Annexure A: 20 business days for PMTS Towers, 30 for Radcom Towers).

Financial Security Requirements and indemnities allocate risk (cl. 4.3; cl. 5.5). The First Carrier may require Financial Security Requirements proportionate to the access requested (cl. 4.3(3)). Examples include charges, bank guarantees or personal guarantees (glossary cl. 6.1). Indemnities for property damage and third-party risk are required by the Code and typically captured in access agreements (cl. 5.5; cl. 5.6).

Operational time constructs appear repeatedly: Business Days, Access Window (scheduled maintenance window), Advised Delivery Date (date on which access will be delivered), and Outage (temporary decommissioning) (cl. 6.1). The Code sets stepwise timeframes: Detailed Field Studies, Orders, Responses and Advised Delivery Dates in Schedules (e.g. Schedules A1/A2 and B1/B2 set 15-30 business day windows depending on facility type and distance).

Dispute resolution is multi‑tiered: bilateral negotiation and mediation first (cl. 2.4(1)); referral to an independent expert for arbitration (cl. 2.4(3)), with determinations binding (cl. 2.4(4)); and ACCC arbitration as the ultimate fallback (cl. 2.4(6)). The Code also requires dispute resolution be conducted by persons with sufficient decision-making authority (cl. 2.4(7)).

Native title and heritage claims are acknowledged and envisaged as a possible cause for variation or cost sharing: where a Claim arises the Carriers must cooperate and contribute proportionately to resolution costs (cl. 5.9).

These main concepts convert the Code’s policy aim of co‑location into operational levers: who pays for what (MRW, permits, security), who decides (First Carrier for site control; independent expert/ACCC for unresolved disputes), and what operational steps are required to deliver access (Information Package → Facilities Access Application → Detailed Field Study → Order → Response → Delivery).

The Code operates directly on “Carriers” as defined in s. 7 of the Telecommunications Act 1997; those are the primary regulated parties (cl. 6.1 definition references the Act). Within that population the Code creates distinct functional roles. A First Carrier is a Carrier which owns, operates or controls Eligible Facilities and therefore controls access decisions, lease relationships, site security and many operational obligations (cl. 6.1). A Second Carrier is a Carrier seeking access and therefore responsible for providing technical information, potentially funding MRW or performing MRW, securing permits, and meeting financial security requirements (cl. 6.1; Annexure A/B procedures).

There are several special-status entities and consequential effects. Telstra and certain designated Telstra successor companies have partial carve-outs: the Code does not apply to the extent it would prevent a designated Telstra successor company or Telstra from complying with undertakings under ss. 577A, 577C or 577E of the Act (cl. 1.2.1). NBN corporations are specifically excluded from being treated as operators or controllers of an Eligible Facility in defined circumstances where there is a pre‑existing agreement with Telstra or a designated successor (cl. 1.2.1). These textually explicit exemptions mean some of the largest historical site owners may not be subject to every obligation in the Code in certain contractual contexts.

The Code also affects a chain of third parties that are not Carriers but interact operationally. Lessors and landlords appear repeatedly: the First Carrier is commonly the lessee of a Tower Site and must remain so while granting sub‑leases to Second Carriers (Annexure A cl. 2.4(1)-(6); Schedule A2 Part 2 on replacement towers addresses property rights). The Code requires the Second Carrier to secure an Adjoining Site for its Equipment Shelter where relevant (Annexure A cl. 2.4(5)(i)-(ii)), which means landowners and councils can be affected through lease negotiations and planning approvals.

Contractors and equipment suppliers are affected operationally. MRW can be performed by the Second Carrier or First Carrier; where the Second Carrier undertakes MRW, the Code requires them to be suitably qualified (cl. 4.4(1)) and to bear costs (Schedules A2/B2, cl. 1.3/3.3). The Code also contemplates Third Party Users (non‑Carriers) placing equipment on a site; such users must accept terms consistent with interference rules and indemnities (cl. 5.6).

Regulatory bodies are implicated: the ACCC is the Code maker and arbiter (cl. 1.1.1; cl. 2.4(6)), and the ACMA may be consulted by an independent expert (cl. 2.4(5)). Disclosure obligations under stock exchange listing rules and lawful directions from Ministers, ACMA or ACCC can require Carriers to disclose Confidential Information despite the Code’s confidentiality regime (cl. 2.1(4)(e),(g)).

Finally, financiers and insurers are indirectly affected. Financial Security Requirements may include charges, guarantees or mortgages (glossary examples in cl. 6.1), and the Code contemplates insurance requirements in a Master Access Agreement (cl. 4.2(5)). Insolvency or changes in corporate status of either party trigger termination rights (cl. 5.8(4)(a)-(l)), so secured creditors face practical consequences.

In short, the Code’s immediate legal target is carriers; practically, it reallocates negotiation power, costs and operational duties across a network of carriers, landlords, contractors, insurers and regulators whose behaviour and commercial choices determine deployment, co‑location and timing of infrastructure.

The Code divides duties and rights into mandatory principles (Chapter 2), administrative tasks (Chapter 3), negotiation structures (Chapter 4) and implementation mechanics (Chapter 5). Key duties flow from those chapters and from the Annexures.

Confidentiality: Each Carrier must keep confidential the other party’s Confidential Information disclosed in connection with applications or agreements (cl. 2.1(1)). Use is limited to Code‑related purposes (cl. 2.1(1)(c)). There are enumerated exceptions permitting disclosure to directors, legal advisers, stock exchange requirements, or as required by law or a lawful ACCC/ACMA/Ministerial direction (cl. 2.1(4)(a),(c),(e),(g)). Carriers must establish procedures to protect Confidential Information and may require third-party disclosees to accept confidentiality obligations (cl. 2.1(5)-(6)).

Non‑discrimination and queuing: First Carriers must, so far as practicable, treat other Carriers on a non‑discriminatory basis and give access equivalent to what they provide themselves, taking into account legitimate business interests and third parties (cl. 2.2(1)). A First Carrier must publish a queuing policy (cl. 2.3(1)) which must be non‑discriminatory and seek to maximise efficiency (cl. 2.3(3)(i)-(ii)). The Code contains a specific queue removal rule that a Facilities Access Application must be removed from a tower queue after 24 months if the applicant has not commenced ordering/installing (cl. 2.3(3)(ii)), subject to transitional rules (cl. 2.3(7)-(8)).

Information provision and administration: First Carriers must provide an Information Package on request within five Business Days (cl. 3.1(2)), and update Second Carriers of amendments within three Business Days (cl. 3.1(3)). The package must include the Proper Officer contact (cl. 3.1(4)(a)), physical arrangements and a pro‑forma Physical Inspection Notification (cl. 3.1(4)(b)), financial security information (cl. 3.1(4)(e)), and confidentiality templates (cl. 3.1(4)(f)).

Proper Officer duties: Both parties must appoint a Proper Officer responsible for administering access (cl. 3.3(1)). The Proper Officer must have adequate authority, may delegate, and must coordinate Make Ready Work, receive fault notifications and handle application processes (cl. 3.3(2)-(5)).

Facilities Access Applications and technical warranties: Second Carriers must submit detailed technical and credit information in a Facilities Access Application (Annexure A/B cl. 2.1). Second Carriers warrant the accuracy of technical and credit information and the qualifications of the persons providing it; disputes over those warranties are routed to dispute resolution (Annexure A cl. 2.1(3),(9)-(11); Annexure B cl. 2.1(3),(7)-(9)).

Master Access Agreement rights and duties: Parties must make reasonable endeavours to negotiate a Master Access Agreement covering charges, dispute resolution, technical specifications, and scheduling (cl. 4.2(1),(4)). The Master Access Agreement applies to subsequent facility-specific applications for the defined class (cl. 4.2(2)). The Code allows certain contractual flexibility but preserves Chapter 2 mandatory conditions (cl. 1.2.2(3)).

Financial security and credit assessments: If the First Carrier has reasonable concerns about a Second Carrier’s creditworthiness or prior non‑compliance, it must provide specific evidence and engage to resolve concerns (cl. 4.3(1)). Financial Security Requirements must be proportionate to the access and may be varied by agreement (cl. 4.3(3)-(5)).

Make Ready Work allocation: The Second Carrier may perform MRW (cl. 4.4(1)), but First Carrier may choose to perform any MRW involving its Equipment (cl. 4.4(6)). If both perform work, the parties must agree a combined procedure (cl. 4.4(7)). Detailed administrative procedures for either party performing MRW are in Schedules A1/A2 and B1/B2.

Operational duties: First Carriers maintain Eligible Facilities in safe and operable condition but are not required to reconstruct a facility (cl. 5.1(1)-(2)). Carriers must maintain their own Equipment and avoid endangering others (cl. 5.1(3)). The First Carrier must not, except with consent and subject to compensation, later require a Second Carrier to relocate equipment once installed (cl. 5.1(4)).

Interference and remedial duties: Carriers must not cause interference or materially obstruct other Equipment (cl. 5.4(1)). If interference is alleged soon after installation, the responding Carrier must remedy that breach as soon as possible and within 24 hours if alleged within one week of installation or commissioning (cl. 5.4(3)). If unresolved after 48 hours, an independent expert should be appointed (cl. 5.4(4)-(5)).

Suspension and termination rights: First Carriers may suspend access after a Suspension Event and specified notice (cl. 5.7(1)-(2)). Termination rights for both parties are set out at length (cl. 5.8), including short notice termination for insolvency, force majeure, or material breach (cl. 5.8(4)). On termination the Second Carrier must remove equipment and reinstate sites, and cost allocation rules for disconnection are specified (cl. 5.8(5)-(7)).

Native title and heritage: If a Claim arises, Carriers must cooperate and contribute in proportion to the space occupied (cl. 5.9(2)).

These duties and rights allocate commercial risk, technical responsibility and operational control across the parties, and they are generally enforceable via contractual remedies, dispute resolution procedures and ACCC arbitration rather than internal criminal sanctions in the text.

The Code is an administrative instrument that embeds enforcement through contractual remedies, suspension/termination powers, independent expert determinations and ACCC arbitration rather than by creating stand‑alone criminal sanctions or pecuniary penalties within the text. The primary enforcement mechanisms are:

1. Contractual and commercial remedies: The Code anticipates that access will be governed by site‑specific access agreements and Master Access Agreements (cl. 4.2). Many duties (indemnities, payment obligations, removal obligations on termination) are intended to be enforced under those agreements (see cl. 5.5 on indemnity; cl. 5.8(5)-(7) on removal and cost allocation). Where agreements exist, contractual remedies (damages, indemnities, enforcement of security interests) will apply.

2. Suspension and termination rights: The First Carrier may issue a Suspension Notice for a Suspension Event and require remedial action; failure to remedy within the Remedy Period can lead to suspension or removal of Equipment (cl. 5.7(1)-(3)). Detailed termination grounds (insolvency, force majeure, material breach, non-payment, illegality, site unfitness, safety) are set out in cl. 5.8(4). Those provisions directly change access availability and create commercial consequences (cl. 5.8(6)-(8) on disconnection costs and dispute resolution over costs).

3. Independent expert determinations and binding compliance: The Code requires carriers to refer unresolved disputes over terms and conditions first to an independent expert (other than the ACCC) and to comply with the expert’s determination (cl. 2.4(3)-(4)). An independent expert may consult the ACMA (cl. 2.4(5)). The Code makes the expert’s determination binding on the parties, which is an explicit enforcement step.

4. ACCC arbitration and certificates: If the independent expert stage fails, the parties must refer the dispute to the ACCC for arbitration (cl. 2.4(6)). Annexures provide for the First Carrier to request an ACCC certificate supporting a proposed rejection on technical grounds (Annexure A cl. 2.3(2); Annexure B cl. 2.3(2)), and a failure by the ACCC to issue a certificate results in the First Carrier being deemed to have accepted the application (Annexure A cl. 2.3(3); Annexure B cl. 2.3(3)). Hence the ACCC’s administrative determinations have concrete operational effect.

5. Disclosure and statutory compliance drivers: Confidential Information exceptions include lawful or binding directions from the ACMA or ACCC or any Minister (cl. 2.1(4)(g)). Carriers must comply with such directions, which can operate as a form of statutory enforcement.

6. Dispute resolution procedural obligations: The Code compels parties to engage in dispute resolution procedures and to ensure those procedures are carried out by persons with decision‑making authority (cl. 2.4(7); cl. 2.5(3)). Failure to follow prescribed dispute-resolution steps may limit procedural remedies and can be taken into account by an arbitrator or independent expert.

Notably absent from the Code text are express monetary penalties or criminal sanctions imposed by the Code itself. Enforcement instead depends on contractual remedies, commercial rights such as suspension and termination, binding determinations by independent experts and the ACCC, and statutory directions. This means that practical enforcement largely operates through the chain of contractual obligations, the ACCC’s arbitration power under Part 5 (cl. 2.4(6), note references to cl. 36 of Part 5), and property and insolvency law consequences linked to termination grounds (cl. 5.8(4)).

For practitioners, the enforcement architecture implies attention to draft contract wording, security instruments, insurer and guarantor arrangements, and careful compliance with dispute resolution steps because binding determinations can be invoked and operational rights (suspension/removal) can be exercised while remedies are being pursued.

The Code is enacted under the Telecommunications Act 1997, Schedule 1, Part 5 (cl. 1.1 background and cl. 1.1.1). It must be read and applied against that statutory backdrop; the Code repeatedly references the Act for definitions, limits and specific mechanisms (for example, Eligible Facility is defined with reference to clauses 33-35 of Part 5 (cl. 1.2.1 and cl. 6.1 glossary)).

Statutory undertakings and carve-outs: The Code explicitly disapplies to the extent it would prevent a designated Telstra successor company or Telstra from complying with statutory undertakings under ss. 577A, 577C or 577E of the Act (cl. 1.2.1). These are statutory contractual undertakings given under the Act and therefore can override or limit the Code’s application to those entities in practice.

Regulatory interface with ACCC and ACMA: The ACCC is both the Code maker and an arbitration backstop (cl. 1.1.1; cl. 2.4(6)). Annexe procedures envisage the ACCC issuing technical infeasibility certificates that can determine whether an application is rejected (Annexure A cl. 2.3(2)-(3); Annexure B cl. 2.3(2)-(3)). The ACMA can be consulted by independent experts and is a named party for disclosure exceptions (cl. 2.4(5); cl. 2.1(4)(g)). Carriers must therefore manage administrative engagement with both regulators.

Corporations, insolvency and secured transactions: Termination events list insolvency events and appointment of administrators, receivers or liquidators (cl. 5.8(4)(a)-(c)) and non‑payment as grounds for termination (cl. 5.8(4)(h)). The Code interacts with corporate insolvency law (Corporations Act provisions are referenced indirectly; cl. 5.8(4)(f) refers to s. 459F of the Corporations Law in the text). Financial Security Requirements (cl. 4.3) may include fixed and floating charges, mortgages and rights of set-off (glossary cl. 6.1), which brings the Personal Property Security Register and security enforcement regimes into practical play.

Native title, heritage and planning consents: The Code recognises that Eligible Facilities may be subject to native title or heritage claims and imposes duties to cooperate and to share resolution costs proportionately (cl. 5.9). Annexures repeatedly require parties to obtain permits, approvals and landowner consents (Schedules A2/B2 cl. 1.2; Annexure A cl. 2.1(4)), so planning law, local government approvals and land rights regimes are implicated. The Code does not displace those legal regimes , instead it allocates the commercial responsibility for obtaining or funding approvals (Second Carrier usually bears costs, see Schedules).

Contract law and existing leases: The First Carrier is expected to remain the prime lessee and to grant sub‑leases to Second Carriers (Annexure A cl. 2.4(1)-(3)). The Code requires that site sub‑leases are generally co‑extensive with the First Carrier’s lease (Annexure A cl. 2.4(3)). It also obliges First Carriers to seek to incorporate clause 3.2 into negotiations with Lessors where decommissioning is proposed (Annexure A cl. 3.2(1)(d)). Thus existing contractual rights between carriers and property owners remain central and the Code shapes how parties are expected to manage those relationships.

Other legislation: The Code references other federal statutes and rules (Bankruptcy Act terms appear in cl. 5.8(4)(g) and listing rules are contemplated in cl. 2.1(4)(e)). Where disclosure is required by any law, the Code permits such disclosure (cl. 2.1(4)(d)). The interplay means carriers must ensure Code compliance alongside obligations under corporate, securities, insolvency, planning and native title law.

In sum, the Code is embedded within a network of legislative and contractual regimes: it prescribes procedural and allocation rules for access while leaving statutory undertakings, property law, planning and insolvency law operational. Parties must therefore coordinate Code compliance with obligations under other applicable law, and in several places the Code makes performance subject to obtaining consents and approvals under other laws (Schedules A2/B2 cl. 1.2; Annexures).

The compilation header and endnotes record the Code’s amendments and compilation status. This compilation is dated 1 January 2023 and includes amendments up to Act No. 140, 2021 (Compilation No. 3, compilation date 1 January 2023). The notes list prior instruments: the original Code gazetted 13 October 1999; a Variation 2013 (F2013L01732) effective 24 September 2013; and A Code of Access Amendment 2020 (No. 1) (F2020L00692) effective 12 June 2020 (Notes table and legislative history).

The endnotes’ amendment table records many clause‑level changes: for example, cl. 2.3 (queuing policy) was amended by F2020L00692; cl. 3.2 (other information requirements) was amended by F2020L00692; cl. 4.4 and 4.5 were amended by F2013L01732; cl. 5.6 and 5.8 were amended by F2013L01732; cl. 6.1 (glossary) was amended and later rs. (repealed and substituted) by No. 140, 2021 (the Telstra Corporation-related amendments) (see the Amendment history table in the notes). The table lists which specific clauses were amended, added or repealed by those instruments.

Noteworthy is the Telstra Corporation and Other Legislation Amendment Act 2021 (No. 140, 2021) which has commencement Sch 2: 1 January 2023 for items affecting the Code (Notes table). The Code’s cl. 1.2.1 was amended to reflect Telstra undertaking exceptions and the NBN corporation carve‑out (see cl. 1.2.1 text and amendment notes). The amendment history also records that several schedule clauses were repealed or substituted by the 2020 and 2013 instruments (Schedules A1 and B1 clauses, certain A2/B2 clauses).

Transitional provisions and uncommenced amendments: the compilation explicitly notes that uncommenced amendments are not shown in the text and that modifications made by other laws may not amend the compiled text shown (About this compilation). The Code’s own cl. 1.1.3-1.1.4 gives the ACCC power to vary or review the Code; such ACCC variations would themselves be recorded in future amendment histories.

Practitioners should consult the endnotes table for clause‑level amendment provenance when drafting or litigating under older agreements. The amendment history demonstrates iterative adjustments to operational details (queuing, make‑ready procedures, definitions), as well as later statute‑driven changes which affect Telstra and NBN corporation treatment. The compilation information cautions that the Code’s operational text in any governing agreement should reference the current instrument and check whether a particular clause has been amended or superseded by one of the instruments noted in the amendment table.

The Code itself contains no judge‑made cases or litigation entries in the compilation. The endnotes and the body of the Code do not name judicial decisions or administrative rulings. The Code’s dispute resolution architecture is administrative and contractual , it directs parties to negotiate, mediate, appoint independent experts and, failing that, seek ACCC arbitration (cl. 2.4). The Code references statutory mechanisms (cl. 2.4 note refers to Telecommunications (Arbitration) Regulations and ACCC Pricing Principles in the notes), but it does not record outcomes of ACCC arbitrations or independent expert determinations within the text.

Consequently, there is no litigation history recorded in the instrument to cite. Where disputes arise under the Code in practice, remedies and enforcement will arise through:

• independent expert determinations that the Code makes binding if parties agree to that mechanism (cl. 2.4(3)-(4)); and
• ACCC arbitration where independent expert stages fail (cl. 2.4(6)).

Absent case law in the document, the Code anticipates administrative resolution processes rather than judicial precedent within the instrument. For research or litigation planning, practitioners should:

• search ACCC arbitration determinations or public registries for decisions under Part 5 of Schedule 1 to the Act, as the Code contemplates ACCC determinations and certificates (Annexures A/B cl. 2.3);
• review any contractual disputes resolved by independent experts , those determinations may have limited public dissemination but could be relevant if referenced in later proceedings; and
• where court proceedings are initiated (for breaches of contractual obligations or injunctive relief), expect those matters to involve standard contract and property law principles interacting with the Code’s procedural steps.

Because the Code requires compliance with independent expert determinations and ACCC arbitration, many operational disputes are likely to be resolved administratively. Any judicial litigation would likely concern enforcement of those determinations, questions about the proper exercise of the Code’s dispute resolution processes, or conflicts with other statutory duties (for example, Telstra undertakings referenced in cl. 1.2.1).

In short, the compilation contains no litigation entries; practitioners should treat the Code as a statutory administrative framework whose operational disputes are designed to be resolved via experts and the ACCC, with courts as fallback enforcers of contractual and statutory rights where necessary.

The Code contains numerous specific operational and drafting points that can catch parties or their advisers unaware. These are concrete mechanisms in the text that effect timing, cost exposure and decision rights.

Telstra and NBN carve-outs. The Code does not apply to the extent it would prevent Telstra or a designated Telstra successor from complying with undertakings under s. 577A, 577C or 577E (cl. 1.2.1). Also an NBN corporation may not be treated as operator/controller when specific pre-existing agreements with Telstra apply (cl. 1.2.1). Parties dealing with Telstra or NBN‑contracted facilities need to check whether these carve‑outs apply to their site.

Confidentiality exceptions. The confidentiality regime is robust but contains enumerated exceptions that can lead to disclosure: ACMA/ACCC/Minister directions, stock exchange listing rules, or legal process (cl. 2.1(4)(c),(e),(g)). A Second Carrier should anticipate that information disclosed under the Code may need protection clauses to control the form and timing of any compelled disclosure; the Code permits conditional disclosure but also obliges the Disclosing Carrier to notify the Other Carrier when disclosure is required by law (cl. 2.1(4)(d)).

Queuing and application removal. The queuing policy requires the First Carrier to remove an accepted Facilities Access Application from a Tower queue after 24 months if the applicant has not commenced ordering/installing (cl. 2.3(3)(ii)) but transitional rules modify timeframes for earlier applications (cl. 2.3(7)-(8)). Parties should track dates precisely because an application can be removed by operation of the queuing rule.

Who pays what for MRW and permits. The Code commonly imposes MRW costs on the Second Carrier where it elects to perform MRW (Schedules A2/B2 cl. 1.3/3.3 and Schedules for new towers cl. 2.3). The Second Carrier typically bears permit and approval costs (Schedules A2/B2 cl. 1.2/2.1). However, the First Carrier may perform MRW in specified circumstances and recover costs; the allocation can become contested and disputes are routed via the Code’s dispute resolution steps (cl. 4.4 and Schedules A1/B1). Practitioners must draft site agreements that itemise cost caps, variation procedures and responsibility for unforeseen add‑ons (see Schedule A1 cl. 6 on Work Variation Report).

Qualification to perform MRW. The Second Carrier may undertake MRW but must be suitably qualified (cl. 4.4(1)). If the First Carrier disputes qualification, the Code requires good faith negotiation and, failing that, dispute resolution (cl. 4.4(2)-(3)). Delays can result if qualification disputes proceed to expert determination.

Inspection and safety accompaniment. The First Carrier may require Second Carrier representatives to be accompanied at their expense when there is a significant safety or network integrity risk (Annexure A cl. 1.2(4) and Annexure B cl. 1.2(4)). The Code leaves assessment of “significant risk” to the parties, subject to dispute resolution if contested (Annexure A/B cl. 1.2(6)). Costs for accompanied access can be non‑trivial.

Interference timelines. If alleged interference arises within one week of installation or commissioning, the responding Carrier must remedy “as soon as possible” and, in any event, within 24 hours (cl. 5.4(3)). If not promptly resolvable, the parties must appoint an independent expert within 48 hours (cl. 5.4(4)). These tight deadlines can be operationally challenging for engineers and call for pre‑agreed processes in Master Access Agreements.

Relocation and site stability. Once a Second Carrier’s Equipment is located, the First Carrier must not require relocation except with consent and payment of reasonable costs (cl. 5.1(4)). Nevertheless, the First Carrier can terminate or withdraw access if it decommissions a site or sells/leasebacks it (cl. 5.8(2)). The Code requires the First Carrier to give at least six months’ notice before withdrawal and consider substitute facilities (cl. 5.8(12)), but in practice the notice regime and the availability of substitute sites can be material commercial risks.

Financial security and creditworthiness. The First Carrier can require proportionate Financial Security Requirements (cl. 4.3(3)). The examples include charges, guarantees and mortgages (glossary cl. 6.1) and can affect balance sheets and financing arrangements for a Second Carrier. Additionally, if the First Carrier reasonably doubts creditworthiness it must disclose specific evidence and engage to resolve concerns (cl. 4.3(1)), but unresolved disputes may delay access or require higher security.

Termination costs and allocation. On termination, disconnection costs are allocated according to the termination cause (cl. 5.8(7)). For example, where the Second Carrier causes disconnection because of non‑payment or breach it bears costs (cl. 5.8(7)(a)), but if the First Carrier failed to maintain the facility, the First Carrier bears costs (cl. 5.8(7)(d)). Parties should examine termination triggers and cost allocation carefully when drafting site leases.

Native title and heritage claims. The Code requires cooperation and proportionate cost contribution in the event of a Claim (cl. 5.9). Native title processes can introduce significant delay and cost and the Code’s proportional allocation of resolution costs can crystallise unexpected liabilities.

Taken together, these “gotchas” are not legal surprises in the sense of hidden obligations, but they represent specific operational and commercial leverage points created by the Code that parties must manage with contractual detail, insurance, and processes for rapid technical response.

Compliance under the Code is an operational programme: parties must translate the Code’s clauses into policies, templates and procedures. Below is a practical, clause‑linked checklist oriented to carriers and advisers.

1. Governance and appointments

• Appoint a Proper Officer for administration of access (cl. 3.3(1)). Give the Proper Officer explicit delegation, contact details and authority to make reasonably prompt operational decisions (cl. 3.3(3)-(4)). Ensure counterpart details are exchanged.

2. Documentation and public‑facing material

• Prepare and maintain an Information Package that meets cl. 3.1(4) requirements (contact details, Physical Inspection Notification, ordering and provisioning outline, Financial Security Requirements, confidentiality template). Make the package available within five Business Days on written request (cl. 3.1(2)).

3. Confidentiality and information handling

• Implement confidentiality procedures consistent with cl. 2.1(1)-(6). Use standard Confidentiality Agreements that allow required exceptions (ACMA/ACCC directions, listing rules, legal process) and include procedures for notifying the other Carrier before compelled disclosure (cl. 2.1(4)(d)). Ensure employee/agent NDA coverage (cl. 2.1(5)-(6)).

4. Queuing and intake

• Create a non‑discriminatory queuing policy per cl. 2.3(1)-(6). Track acceptance dates and the 24‑month removal rule for Tower applications (cl. 2.3(3)(ii)). Implement queue‑management workflows and notifications within five Business Days of receipt as required (cl. 2.3(5)).

5. Facilities Access Application workflow

• Implement template Facilities Access Application forms reflective of Annexure A/B cl. 2.1 requirements (technical specs, Work Plan, creditworthiness materials). Build structured review procedures to meet prescribed response times (e.g., Annexure A cl. 2.2: 20/30 business day assessment windows).

6. Technical qualification and MRW

• Define criteria for acceptable qualifications for MRW performers and build an approval/qualification register (cl. 4.4(1)-(3)). If the First Carrier will reserve right to perform MRW on certain works (cl. 4.4(6)), document triggers and cost allocation. Prepare Draft Construction and Work Plan templates (Schedules A2/B2 cl. 1.1/1.1) and Work Variation Report templates (Schedule A1/B1 cl. 6).

7. Financial security, credit and billing

• Put in place a commercially justified Financial Security Requirements policy aligned to cl. 4.3(3) proportionality factors (creditworthiness, Forecast Information, prior payment record). Establish templates for bank guarantees, directors’ guarantees and set‑offs. Ensure credit assessment procedures are documented to comply with the disclosure obligations in cl. 4.3(1)(a)-(c).

8. Operational coordination and maintenance

• Schedule Access Windows and coordinated maintenance rules per cl. 4.2(6) to reduce outages. Prepare procedures for emergency responses consistent with cl. 5.2 (notification and emergency attendance duties). Maintain logs of site visits as required by Annexure A/B cl. 1.2(8).

9. Interference management

• Build immediate response protocols for interference complaints: within 24 hours for new installations where notified within one week (cl. 5.4(3)), with escalation to an independent expert if causation cannot be reasonably demonstrated within 48 hours (cl. 5.4(4)). Pre‑agree testing and isolation procedures to avoid operational gridlock.

10. Permits, approvals and native title

• Assign responsibility to obtain planning consents, Lessor consents, heritage and native title permissions per Schedules (A2/B2 cl. 1.2). Where law requires First Carrier to obtain such approvals, document cost‑recovery terms as the Code contemplates (Schedules A2/B2 cl. 1.2(1)). Include native title contingency budget lines so cost sharing per cl. 5.9(2) can be executed.

11. Insurance and indemnity

• Include insurance requirements in Master Access Agreements as permitted in cl. 4.2(5). Ensure indemnity clauses for property damage and third‑party liability are consistent with cl. 5.5 and cl. 5.6.

12. Dispute resolution and escalation

• Build a dispute resolution ladder consistent with cl. 2.4: bilateral negotiation, agreed independent expert (with terms for consultation with ACMA), and ACCC arbitration fallback. Ensure persons conducting dispute resolution have sufficient authority as required by cl. 2.4(7) and cl. 2.5(3). Maintain a roster of potential independent experts and agreed procedural rules.

13. Drafting Master Access Agreements

• Negotiate Master Access Agreements with explicit terms on ordering, maintenance, access windows, charges, Financial Security, dispute resolution and procedures for MRW allocation (cl. 4.2(4)(a)-(s)). Insert clear definitions for Advised Delivery Date, acceptance timelines and Work Variation triggers (Schedule A1/B1 cl. 3-6).

14. Decommissioning and termination planning

• Include clauses to handle decommissioning and lease novation per Annexure A/B cl. 3.2, and ensure notice periods and substitute facility processes are in the site agreements to reflect cl. 5.8(12). Preplan removal, reinstatement and cost allocation obligations (cl. 5.8(5)-(7)).

15. Recordkeeping and compliance monitoring

• Keep records of Information Package distributions (cl. 3.1(2)), Physical Inspection Notifications and logs (Annexure A/B cl. 1.2(1),(8)), Orders and Responses (Schedules), Detailed Field Study documents (Schedules A1/B1 cl. 1), and Financial Security instruments. Use these records defensibly in any dispute resolution process.

Finally, check for Telstra and NBN exceptions (cl. 1.2.1) before assuming a given facility is fully governed by the Code. Practically, compliance is a mixture of document templates, technical qualification registers, financial security instruments, dispute‑resolution readiness and rapid operational processes for interference, safety and emergency response. Drafting site‑specific access agreements that reflect the Code’s mandatory minimums and that provide pragmatic operational detail will be essential to avoid protracted disputes and to ensure that access windows, MRW responsibilities and cost allocations are clear and enforceable.