The instrument organises obligations around five core concepts: qualifying carriage service provider, benchmark period, specific record types, compliance reporting, and ACMA‑directed audit. Each concept is defined or linked to upstream instruments.

• Qualifying carriage service provider (s 7). A provider is qualifying for a benchmark period if, on the last day of the preceding financial year, it supplied 100,000 or more CSG services for which it was obliged to comply with one or more performance standards. That threshold ties the Rules’ application to a volume/obligation nexus; providers below the threshold are outside the Rule’s record‑keeping and reporting duties (unless they become qualifying in later periods).
• Benchmark period (s 6(2)). The Rules use the Benchmarks Instrument’s definition of benchmark period. The instrument therefore operates as part of a system: the definitions and benchmark boundaries are determined in the Benchmarks Instrument and the CSG Standard, not in these Rules (see s 6(2)-(3)).
• Record types (Part 2, ss 9-14). The Rules require discrete records in certain classes:
  • Counts of CSG services by area on the last day of each benchmark period (s 9; Sch 1 item 2).
  • Detailed transactional records for in‑place connection requests (s 10) and new connection requests (s 11), including timestamps for receipt, expiry of guaranteed maximum connection period and compliance, the connection period in business days, area classification, and identification of failures attributable to other carriage service providers where relevant.
  • A specific set for requests required to be complied with in the guaranteed maximum connection period under subsection 11(2) of the CSG Standard (s 12).
  • Fault/service difficulty reports (s 13) with timestamps for receipt, expiry of guaranteed maximum rectification period, rectification timestamps, rectification period in business days, area classification, and attribution of failures to other providers.
  • Connection/rectification appointment records (s 14), including latest date/time by which presence at site is required for the appointment to be regarded as kept under section 20 of the CSG Standard, and the actual site arrival date/time. These fields are granular and repeated across different record classes. The Rules also exclude specific fault types from the record/reports regime: reports about inoperative enhanced call handling features are excluded (s 13(2); Sch 1(5)(2)).
• Retention (s 15). Providers must retain required records until at least two years after the end of the benchmark period in which the record was required. The example in s 15 makes the retention rule operational. Transitional s 22 reinforces retention periods already required under the 2011 Rules where applicable.
• Compliance reporting and audit (Part 4 and Part 5). Qualifying providers must prepare compliance reports in the form specified and include the content listed in Schedule 1 (s 16; Sch 1-2). Reports are due to ACMA within 40 business days after the benchmark period (s 17). ACMA may require an external audit at the provider’s cost where it forms a view on reasonable grounds that an audit is necessary (s 18). The process for audit terms of reference, nomination and approval of auditors, timetable and required audit deliverables is detailed in ss 19-21.

Two ancillary concepts affect interpretation and implementation. First, many defined terms are imported from the Benchmarks Instrument and the CSG Standard (s 6(2)-(3)), so compliance requires consulting those instruments for area classifications, guaranteed maximum connection/rectification periods, performance standard content, and appointment definitions. Second, the Rules contain specific procedural timelines and notice mechanisms for ACMA decisions (for example, 21 and 14 day deadlines for draft/revised terms of reference and auditor nomination in ss 19-20), which embed administrative cadence into compliance operations.

Finally, the Rules include several cross‑references to other instruments and to ACMA’s published information (for example the email address for giving compliance reports: s 17(2)), and transitional provisions that treat the 2011 Rules as still operative for retention/audit where applicable (ss 22-23). The result is an instrument that sets operational obligations while relying on upstream instruments for critical substantive definitions and performance benchmarks.

The Rules apply to a subset of carriage service providers: those who are qualifying carriage service providers for a benchmark period (s 7). That is providers who, on the last day of the financial year preceding a benchmark period, supplied 100,000 or more CSG services where they were obliged to comply with one or more performance standards in respect of those services (s 7). The “100,000” threshold is the numeric trigger; the additional phrase "where the carriage service provider was obliged to comply with any one or more of the performance standards" narrows the count to services to which a compliance obligation attached.

Practical consequences of that definition:

• Large retail providers of fixed telephone services and certain bundled services that include a specified service subject to the CSG are likely to meet the 100,000 threshold and therefore be captured (the instrument uses the term CSG service, imported from the CSG Standard, s 6(3)(c)). Smaller providers or new entrants below that threshold are not required by these Rules to keep the specified records or lodge the compliance reports, unless they later cross the threshold in the relevant timing measurement.
• The timing measurement is precise: qualification is assessed by reference to the last day of the financial year immediately preceding the benchmark period (s 7). That creates an annual status determination tied to financial‑year end volumes. Providers whose volumes fluctuate around the threshold need an internal process to determine status as of that specific date.
• The Rules use the language “is or was a qualifying carriage service provider for a benchmark period” when imposing reporting and audit duties (ss 16, 18). That captures both currently qualifying providers and those that were qualified for the benchmark period being reported on, so a provider that falls below the threshold after the relevant measurement date must still comply with reporting and audit obligations covering that period.
• The Rules also require providers to record details of interactions with customers at the granular level (customer names, site addresses, timestamps, area classification), and to record when failures are attributable to other carriage service providers (ss 10-14). This imposes obligations on providers to collect and retain personally identifying customer data and internal operational data.
• Other parties are affected indirectly. The Rules require providers to identify and describe acts or omissions by other carriage service providers when those acts/omissions contributed to a failure to meet guaranteed maximum connection or rectification periods, and to record when failures to keep appointments are attributable to other providers (ss 10(1)(h), 11(1)(h), 12(1)(k), 13(1)(j), 14(1)(j); Sch 1 items 3-6). That generates information that ACMA may use to allocate responsibility or to analyse systemic issues across networks and providers.
• The ACMA is an explicit actor: it receives compliance reports (s 17), approves or modifies proposed audit terms of reference (s 19), approves or rejects auditor nominations (s 20), and may require audits where it has reasonable grounds (s 18). ACMA’s procedural powers shape who decides the scope, format and timing of audits.

Excluded or carved‑out items: the Rules exclude reporting of faults or service difficulties relating to inoperative enhanced call handling features on services that include that feature (s 13(2); Sch 1(5)(2)). Also, the required counts of CSG services (s 9; Sch 1 item 2) are only those services where the provider was obliged to comply with performance standards , the supply of services outside that obligation does not increment the 100,000 test for qualification.

Finally, the Rules preserve certain obligations under the 2011 Rules for periods where those retention obligations remain in force (s 22). Providers that were bound by the 2011 Rules may therefore have overlapping retention or audit obligations for legacy records relevant to benchmark periods falling under the 2011 regime.

The Rules allocate a structured set of duties to qualifying carriage service providers and grant procedural rights to ACMA; they do not create separate civil penalties within the instrument.

Key duties on qualifying providers:

• Record‑keeping. A qualifying carriage service provider for a benchmark period must keep the specific records listed in Part 2 (ss 9-14). The Rules enumerate the exact data elements to be captured for each class of record: counts by defined area (s 9); name, site address, timestamps, expiry times of guaranteed maximum periods, dates and times of compliance/rectification, business‑day counts for connection/rectification periods, area classification, and identification/description of other carriage service provider acts or omissions where they contributed to failures (ss 10-14). The required data fields are repeated in the compliance report Schedules (Sch 1) and the form (Sch 2).
• Retention. Providers must retain records required under Part 2 until no earlier than two years after the end of the benchmark period in which the records were required (s 15). The Rules give an explicit example in s 15’s note.
• Compliance reporting. Providers that are (or were) qualifying for a benchmark period must prepare a compliance report for that benchmark period, including the information specified in Schedule 1 and in the form specified in Schedule 2 (s 16; Sch 1-2). The compliance report must be given to ACMA no later than 40 business days after the end of the benchmark period, unless ACMA agrees in writing to a later time (s 17(1)).
• Delivery method. Compliance reports are to be delivered by electronic transmission to the email address published for that purpose on ACMA’s website; the report may be in an electronic format agreed in writing by ACMA (s 17(2)-(3)).
• Cooperation with audits. If ACMA requires an audit under s 18, the provider must engage an external auditor at its own cost (s 18(2)), provide draft audit terms of reference within 21 days (s 19(2)), respond to ACMA’s change requests to those terms (s 19(3)-(5)), nominate an auditor and notify ACMA within 21 days (s 20(2)), and take all necessary steps to ensure the auditor complies with terms and can form the required opinion (s 20(6)). After the provider receives the auditor’s report, the provider must give the audit report to ACMA within 14 days, and must ensure the report contains the audit plan, an audit memorandum and an expression of opinion as to whether the provider prepared required compliance reports and kept required records in accordance with the Rules (s 21(2)-(4)).

Procedural rights/constraints involving ACMA:

• ACMA’s threshold for requiring an audit is limited by the instrument: an audit may only be required if ACMA forms a view on reasonable grounds that an audit is necessary (s 18(5)). That attaches a “reasonable grounds” condition to ACMA’s exercise of its audit requisition power.
• ACMA may approve or require changes to draft audit terms of reference, and may specify terms of reference if it forms the view on reasonable grounds that the revised terms do not give effect to the changes it required (s 19(3)-(5)). The terms of reference must include stated items (objectives; format of opinion; auditing standards; timetable) (s 19(6)).
• ACMA may approve or reject a nominated auditor, and may require the provider to contract with a specified auditor or from a specified group (s 20(3)-(5)). This gives ACMA a degree of control over auditor selection.
• ACMA may agree in writing to extensions of time for compliance report delivery (s 17(1)) and for various draft/revised document delivery periods (ss 19(2), 19(4), 20(2), 20(4), 21(2)).

Rights expressly not created by the Rules:

• The Rules do not themselves create criminal or civil monetary penalties for non‑compliance within the instrument text. Enforcement mechanisms available under the Telecommunications Act or other laws are not set out in the Rules. The instrument focuses on record‑keeping, reporting and audit procedures rather than specifying sanctioning mechanisms in the instrument text.

Obligations that impose measurable resource costs:

• Audit costs are borne by the provider (s 18(2)).
• Providers must collect granular customer and operational data and retain it for at least two years after the benchmark period (s 15), and prepare and deliver compliance reports within a 40 business‑day window (s 17(1)). These are administrative burdens with associated resourcing and data‑management costs.

Other specific duties to note:

• Providers must identify and document when failures are wholly or partly attributable to another carriage service provider and provide names and descriptions of those acts or omissions across a number of record classes (ss 10(1)(h), 11(1)(h), 12(1)(k), 13(1)(j), 14(1)(j); Sch 1 items 3-6).
• The Rules rely on definitions in the Benchmarks Instrument and the CSG Standard for key concepts such as guaranteed maximum connection/rectification periods, business day, and area classifications (s 6(2)-(3)). Practically speaking, providers must coordinate record‑keeping systems with those upstream definitions.

In short, the Rules impose prescriptive and repeatable duties on qualifying providers to collect and retain specified data, to furnish formal compliance reports to ACMA on a set timetable, and to submit to external audits at their own expense when triggered by ACMA. ACMA is given procedural levers to set audit scope and approve auditors; the provider bears the costs and operational burden of compliance.

The Rules themselves do not specify civil or criminal penalties within their text. The instrument structures enforcement primarily through reporting, audit, and ACMA oversight powers, rather than by creating new sanctioning provisions in the Rules.

Key enforcement mechanisms contained in the Rules:

• ACMA’s audit power (s 18). ACMA may, on reasonable grounds that an audit is necessary, require a qualifying carriage service provider to engage an external auditor at the provider’s cost to audit compliance with these Rules (s 18(2), (5)). ACMA may require one initial audit in respect of each compliance report (s 18(3)) and, where ACMA on reasonable grounds considers the initial audit inadequate, may require one follow‑up audit (s 18(4)). The audit mechanism is the primary supervisory tool the Rules provide.
• Procedural control over audits and auditors (ss 19-21). ACMA can approve or require changes to audit terms of reference, specify terms of reference if a provider’s proposal is deficient, approve or reject the provider’s choice of auditor, and require the provider to contract with a specified auditor or any auditor from a specified group (ss 19(3)-(5), 20(3)-(5)). These provisions enable ACMA to enforce substantive and procedural rigor by restricting the auditor’s scope and imposing reporting content (s 21(4) requires an audit plan, audit memorandum and expression of opinion regarding whether compliance reports were prepared and required records kept in accordance with the Rules).
• Reporting obligations and timelines (ss 16-17). The requirement that qualifying providers prepare and lodge compliance reports in a prescribed form and within a defined timeframe (40 business days after the benchmark period) creates a regulatory obligation. Failure to prepare or give the compliance report would place the provider in breach of the Rules; however, the instrument itself does not specify fines or penalties for such a breach.
• Implied enforcement under the Act. The Rules are made under section 529 of the Telecommunications Act 1997 (s 3). Enforcement beyond the record‑keeping/reporting/audit architecture therefore depends on ACMA’s broader statutory powers under the Telecommunications Act and other law. The Rules themselves do not set out monetary penalties or formal sanctioning procedures. Users must therefore look to the Act and ACMA’s statutory regime for the full range of enforcement remedies (the Rules do not attempt to restate those powers).

Implementation risk and practical enforcement effects:

• The Rules give ACMA substantial control over the audit process and the ability to require an audit at the provider’s expense. That is an enforcement tool that imposes direct cost on providers and creates reputational and compliance risk if audit findings are adverse.
• The instrument’s silence on specific monetary penalties means that any formal sanction (fines, enforceable undertakings, injunctions) would need to be founded on the Act or other instruments. The Rules’ practical enforceability therefore relies on ACMA using its audit, disclosure, and other statutory tools under the Telecommunications Act where deficiencies are identified.
• The procedural requirement that ACMA form a view on reasonable grounds before requiring an audit (s 18(5)) imposes a standard on ACMA’s exercise of power; in practice this will involve an internal assessment and creates an administrative threshold that ACMA must satisfy.

Note on drafting: s 21(4)(c)(i) requires the auditor’s expression of opinion as to whether the carriage service provider has “prepared any compliance reports required under section 13” and kept records required under Part 2. Section 13 is a Part 2 provision relating to fault or service difficulty records, while s 16 is the provision that requires compliance reports. The cross‑reference in s 21(4)(c)(i) to section 13 rather than section 16 could create an ambiguity about the targeted compliance reports for the auditor’s opinion. This is a drafting point internal to the Rules that may affect enforcement if relied on literally.

In sum, enforcement within the Rules is procedural and supervisory: ACMA collects compliance reports, can compel external audits at the provider’s cost, and controls audit scope and auditors. The instrument does not itself prescribe pecuniary or criminal penalties; recourse to such penalties would depend on the Act and ACMA’s broader enforcement powers.

The Rules are an instrument in a networked regulatory regime that includes the Telecommunications Act 1997 (the Act), the Telecommunications (Customer Service Guarantee) Standard 2023 (the CSG Standard), and the Telecommunications (Customer Service Guarantee - Retail Performance Benchmarks) Instrument 2023 (Benchmarks Instrument). The Rules repeatedly import definitions and rely on those upstream instruments for substantive content and thresholds.

Direct cross‑references and interactions:

• Authority and enabling law. The Rules are made under section 529 of the Act (s 3). The Rules therefore operate within the Act’s legislative framework and must be read together with the Act’s powers and enforcement mechanisms.
• Definitions imported from other instruments. Section 6 imports a range of defined terms from the Benchmarks Instrument (such as benchmark period, in‑place connection, new connection request, and area categories) and from the CSG Standard (such as business day, connection period, CSG service, guaranteed maximum connection/rectification period, performance standard, site, specified service). That means practical interpretation of many record‑keeping obligations requires consulting both the Benchmarks Instrument and the CSG Standard to ascertain thresholds, durations, and area classifications.
• Relationship to the CSG Standard. The Rules specifically tie record obligations to guaranteed maximum connection and rectification periods set out in the CSG Standard (for example, notes in ss 10(1)(d) and 11(1)(d) refer to subsection 11(1) and items in Schedule 1 to the CSG Standard; s 13(1)(f) refers to sections 14 and 15 of the CSG Standard for guaranteed maximum rectification periods). The Rules do not restate the performance standards; they operationalise data capture, retention and reporting against those standards.
• Relationship to the Benchmarks Instrument. Schedule 1 in these Rules includes an explicit note that the information in item 2 (CSG service counts) is for the purpose of applying sections 4 and 6 of the Benchmarks Instrument (Sch 1 item 2 note). The definition of qualifying carriage service provider in s 7 corresponds to section 4 of the Benchmarks Instrument (s 7 note). That shows the Rules are intended to feed the Benchmarks Instrument’s application and data analytics.
• Interaction with the 2011 Rules. These Rules repeal the 2011 Rules (s 4). Transitional provisions (ss 22-23) preserve retention obligations and treat certain references in s 18 as including the 2011 Rules for audit purposes. Specifically, section 22 requires that records required under Part 2 of the 2011 Rules that were obliged to be retained under the 2011 Rules must continue to be retained for the same minimum period. Section 23(1) treats the reference in s 18(2) to "these rules" as including the 2011 Rules; s 23(2) maps the audit reference in s 18(3) to an earlier subsection of the 2011 Rules. Those transitional rules manage the switch from the 2011 Rules to the 2023 Rules.
• Use of external administrative sources. The Rules require providers to give compliance reports to the ACMA by electronic transmission to an email address published on ACMA’s website for the purpose (s 17(2)). This creates an operational link between the Rules and ACMA’s electronic notice infrastructure.
• Interpretive Acts. The instrument contains notes referencing the Acts Interpretation Act 1901 and Legislation Act 2003 for interpreting Commonwealth Acts and legislative instruments (s 8 notes), which is a standard pointer that these Rules should be interpreted within normal Commonwealth legislative interpretation frameworks.

Potential points of implementation friction because of inter‑instrument dependence:

• Because the Rules import key definitions and guaranteed maximum periods from the CSG Standard and area classifications from the Benchmarks Instrument, practitioners must read the three instruments together. Failure to reconcile definitions across these documents risks misclassification of requests or miscalculation of deadlines for reporting and retention.
• The Rules’ reliance on the CSG Standard for the meaning of “appointment” and when an appointment is taken to have been kept (s 14; note referencing s 20 of the CSG Standard) means record‑keeping systems must be aligned to the Standard’s substantive tests.
• The Rules’ automatic repeal when the CSG Standard is repealed (s 5) directly ties the Rules’ lifespan to the Standard. Because the Standard provides it is repealed at the end of 36 months (s 5 note), the Rules are time‑limited unless the Standard is extended or remade. Practically, that creates a sunset for record‑keeping obligations tied to these Rules.

Drafting inconsistency to note: s 21(4)(c)(i) requires auditors to express an opinion as to whether the carriage service provider prepared any compliance reports required under section 13. Section 13 in these Rules is a record‑keeping provision about fault reports, while the compliance report obligation is under s 16. This cross‑reference might create uncertainty about the precise audit target and its relation to the CSG Standard; the issue is internal to the instrument and will require resolution in practice when ACMA sets audit terms of reference.

In aggregate, these Rules operate as part of a regulatory suite. They do not stand alone; compliance requires checking the CSG Standard and Benchmarks Instrument for definitions, thresholds and the substantive obligations that the record‑keeping is intended to evidence. The Rules also rely on the Telecommunications Act for ACMA’s broader enforcement powers.

The instrument itself contains its immediate amendment and repeal history and transitional mapping to previous rules; it does not display any amendment schedule beyond its own creation and repeal provisions.

Relevant items from the instrument:

• Repeal of the 2011 Rules. Section 4 expressly repeals the Telecommunications (Customer Service Guarantee) Record‑Keeping Rules 2011 (Registration No. F2011L01997). That is the immediate amendment action: the 2011 instrument is superseded by this 2023 instrument on commencement.
• Commencement. Section 2 sets the commencement as the start of the day after registration on the Federal Register of Legislation. The instrument is dated 28 September 2023 (front matter) and was signed by ACMA Members (front matter).
• Sunset tied to the CSG Standard. Section 5 provides that these Rules are repealed on the same day that the CSG Standard 2023 is repealed. The explanatory note in s 5 states that the Standard itself is repealed at the end of 36 months after its commencement (s 5 note). Therefore, unless the Standard is extended or remade, these Rules are designed to have the same 36‑month lifespan. The instrument therefore embeds a time‑limited regime tied to the Standard.
• Transitional provisions. Sections 22 and 23 provide transitional arrangements to bridge obligations under the 2011 Rules and these Rules:
  • Section 22 preserves retention obligations imposed by Part 3 of the 2011 Rules for records that were required under Part 2 of the 2011 Rules and which were required to be retained under the 2011 Rules.
  • Section 23(1) states that references in s 18(2) to “these rules” include the 2011 Rules, and s 23(2) maps the audit reference in s 18(3) to subsection 14(1) of the 2011 Rules. Those transitional clauses manage continuity of audit and retention obligations for matters transitioning from the 2011 framework to the 2023 framework.

No amending instruments or subsequent variations are contained within the text supplied. The instrument also includes notes directing readers to the Federal Register of Legislation for other instruments (s 6 notes; s 8 notes), indicating that any future amendment history would be recorded there.

Operational consequences of the amendment structure:

• Providers subject to the 2011 Rules retain certain retention obligations per s 22; those obligations survive the 2011 Rules’ repeal to the extent they would have required retention beyond the date of repeal. This avoids premature destruction of records created under the 2011 Rules.
• The sunset mechanism (link to the CSG Standard’s repeal) means the Rules are not open‑ended. Providers, counsel and compliance teams should monitor whether the Standard (and thus these Rules) will be extended, remade, or allowed to lapse.
• Because the Rules repeal the 2011 Rules on commencement, providers must migrate record‑keeping and reporting practices to the new forms (Sch 1 and Sch 2) and data elements required by the 2023 Rules, but must also respect retained obligations from the 2011 Rules under s 22.

No further internal amendment history, legislative instrument variations or earlier drafts are contained in the provided instrument text. Practitioners should monitor the Federal Register of Legislation for any subsequent amendment instruments or legislative action that extend, replace or modify the CSG Standard or Benchmarks Instrument, since changes there will directly affect the operation and life of these Rules.

The instrument supplied contains no litigation history. It is a legislative instrument that establishes record‑keeping, reporting and audit procedures; the text does not refer to any court decisions, tribunal determinations, or litigation arising from these Rules. There are no cases named or cited in the instrument.

Practical points:

• Because the Rules are new (2023) and repeal the 2011 Rules, any litigation that pre‑dates 2023 would relate to the 2011 Rules or to the broader Telecommunications Act and CSG regime, but those materials are not included in the instrument text provided. This Rules instrument does not summarise or list prior litigation.
• Potential future litigation vectors, not asserted but identifiable from the instrument’s mechanics, could include disputes about:
  • ACMA’s exercise of its discretion to require an audit under s 18, including whether ACMA had "reasonable grounds" for requiring an audit (s 18(5));
  • ACMA’s approval or rejection of an auditor nomination or its direction to a provider to contract with a specified auditor (s 20(3)-(5));
  • interpretation of key data fields or area classifications where definitions are imported from the Benchmarks Instrument or the CSG Standard (s 6(2)-(3));
  • compliance report content sufficiency or audit findings on whether the provider prepared compliance reports and kept records in accordance with the Rules (s 21(4)). These are theoretical litigation scenarios derived from the instrument’s design; the instrument itself contains no case law.

Where litigation occurs concerning compliance with these Rules, it will be necessary to read the Rules alongside the Telecommunications Act, the CSG Standard and the Benchmarks Instrument for context and for understanding ACMA’s statutory powers that might underpin any enforcement action. Any judicial review of ACMA’s administrative decisions in relation to these Rules would likely require reference to the Act’s procedural and substantive standards.

At present, no litigation history is recorded in the Rules; practitioners should monitor ACMA publications and court/tribunal databases for any disputes arising from the implementation or enforcement of these Rules.

This instrument contains a number of concrete implementation traps and drafting features that practitioners and compliance teams should note. Each item is grounded in the text.

1. Qualification timing and counting nuance (s 7). The qualifying threshold is set by reference to the last day of the financial year preceding the benchmark period. Providers must count only those CSG services “where the carriage service provider was obliged to comply with any one or more of the performance standards in respect of the carriage service provider’s supply of those CSG services.” That double‑nexus (volume plus obligation) can produce edge cases where services supplied are not counted because no performance obligation attached, or where obligations changed mid‑period. Practitioners need a precise cut‑off calculation and documentation for status on that single date.

2. Definitions are not self‑contained (s 6(2)-(3)). Many critical terms are imported from the Benchmarks Instrument and the CSG Standard. You must consult those instruments to determine what counts as a new connection request, an in‑place connection, the area classifications (urban, remote, rural variants), and guaranteed maximum periods. Failure to reconcile cross‑instrument definitions can result in misreporting.

3. Short reporting timeframe (s 17(1)). Compliance reports are due no later than 40 business days after the end of the benchmark period, unless ACMA agrees to a later time. That is a relatively short window given the record volumes and the need to assemble counts and breakdowns by area and failure attribution. Providers must plan data extraction and quality assurance schedules to meet the timeline.

4. Data granularity and privacy considerations (ss 10-14; Sch 1). The Rules require customer names, site addresses and timestamps for individual requests and faults. That requires processing of personally identifiable information and operational metadata for at least two years after the benchmark period (s 15). Providers should ensure that their data retention, access controls and privacy compliance align with these requirements.

5. Attribution of failures to other providers required (ss 10(1)(h), 11(1)(h), 12(1)(k), 13(1)(j), 14(1)(j); Sch 1). The Rules require providers to identify when failures are “wholly or partly attributable” to another carriage service provider and to name and describe the acts or omissions. That requires internal processes to trace failure causes, obtain corroborating evidence, and, where necessary, liaise with other providers to compile accurate descriptions. Disputes about attribution could arise.

6. Audit cost is on the provider (s 18(2)). If ACMA requires an audit, the provider must engage an external auditor at its own cost. ACMA’s power is limited by the requirement it have reasonable grounds (s 18(5)), but once exercised the direct financial burden falls on the provider.

7. ACMA control over audit scope and auditor selection (ss 19-20). ACMA can require changes to draft terms of reference and can specify terms where it considers the draft deficient (s 19(3)-(5)). ACMA can reject an auditor and require the provider to contract with a specified auditor or from a group (s 20(3)-(5)). That reduces provider autonomy in selecting auditors and may affect audit independence perceptions and cost.

8. Potential drafting inconsistency in s 21(4)(c)(i). Section 21(4)(c)(i) requires an auditor’s opinion as to whether the provider has “prepared any compliance reports required under section 13” but the compliance report obligation is in s 16. Section 13 is a record‑keeping provision about fault reports. This cross‑reference could cause uncertainty about the auditor’s remit and should be clarified with ACMA in practice or handled by ensuring the audit covers the full scope of compliance reports and Part 2 records.

9. Exclusion of enhanced call handling feature faults (s 13(2); Sch 1(5)(2)). Faults regarding inoperative enhanced call handling features are excluded from the fault reporting and record‑keeping obligations. Providers that conflate general faults with these excluded faults may over‑report or misclassify. The exclusion is explicit and must be operationalised in triage rules.

10. Sunset linked to CSG Standard (s 5). The Rules are repealed when the CSG Standard is repealed; the Standard is itself limited to 36 months after commencement (s 5 note). This time limit may affect investments in long‑term data infrastructure intended solely to meet these Rules.

11. Delivery mechanics require ACMA‑published email and possible agreed electronic format (s 17(2)-(3)). Providers should not send reports to ad hoc addresses; use the email published on ACMA’s website and seek written agreement for any non‑standard format. ACMA’s acceptance of file formats is discretionary in writing.

12. Multiple deadlines create administrative risk (ss 19-21). The Rules impose short deadlines for draft terms of reference (21 days), revised terms (14 days), auditor nomination (21 days), nomination revision (14 days), and delivery of audit report to ACMA (14 days after receipt). A cascade of administrative tasks arises if an audit is required; providers should build project plans that accommodate ACMA’s potential requests and approvals within those windows.

13. Records retention dovetails with previous Rules (s 22). Retention obligations under the repealed 2011 Rules may persist for certain records. Providers must map legacy retention obligations to avoid premature deletion.

Each of these “gotchas” arises directly from text in the Rules. Practitioners should ensure alignment between operational systems, legal interpretation of definitions in the Benchmarks Instrument and CSG Standard, and ACMA’s procedural expectations to avoid reporting errors and audit escalation.

This section sets out a practical, source‑grounded compliance roadmap based on the Rules’ requirements. It follows the life cycle: status assessment, systems and processes to capture required records, retention, reporting, and audit readiness. All citations are to the Rules.

1. Determine qualifying status for the benchmark period (s 7; s 6(2)). On the last day of the financial year preceding each benchmark period, establish whether your organisation supplied 100,000 or more CSG services where you were obliged to comply with one or more performance standards. Use the definitions of “CSG service” and “benchmark period” from the CSG Standard and the Benchmarks Instrument (s 6(2)-(3)). Document the calculation and retain records supporting the count.

2. Map definitions and business rules (s 6). Extract definitional content from the Benchmarks Instrument (for area classifications, in‑place/new connection definitions) and the CSG Standard (for guaranteed maximum connection/rectification periods, appointment definitions, business day definitions). Build a compliance dictionary so that IT, operations and compliance use the same rule set.

3. Implement data capture for Part 2 fields (ss 9-14). Configure CRM, ticketing and workforce management systems to record the precise fields required:

   • For counts (s 9; Sch 1 item 2): snapshot number of CSG services on last day of benchmark period by area (nominated area, urban, major rural, minor rural, rural, remote).
   • For in‑place connection requests (s 10): capture customer name, site address, date/time request received, expiry of guaranteed maximum connection period (derived from CSG Standard), any agreed altered period (section 12 arrangements), date/time of compliance, connection period in business days, and if failure is attributable to another CSP, the other CSP’s name and description of acts/omissions.
   • For new connection requests (s 11) and guaranteed maximum connection requests under subsection 11(2) of the CSG Standard (s 12): likewise capture customer/site/timestamps/area classification plus whether site is urban/rural/remote (s 11(1)(i); s 12(1)(l)).
   • For faults/service difficulties (s 13): capture customer/site/date/time report received, expiry of guaranteed maximum rectification period (from CSG Standard ss 14-15), any alternate agreed period (s 17 of CSG Standard), date/time rectified, rectification period in business days, attribution to other CSPs where relevant, and area classification (s 13(1)(k)).
   • For appointments (s 14): capture customer/site/date/time or time window, any changes to date/time/location, latest date/time to be present to be taken to have kept the appointment (derived from s 20 of CSG Standard), actual presence date/time, and attribution to other CSPs if applicable. Ensure timestamp formats include both date and time; ensure data capture of whether a period was one arranged under s 12 or s 17 of CSG Standard.

4. Build processes for attribution to other carriage service providers (ss 10(1)(h), 11(1)(h), 12(1)(k), 13(1)(j), 14(1)(j); Sch 1). Create internal workflows for investigation and validation when a failure involves another CSP. Maintain documentary evidence of third‑party actions/omissions and ensure the description recorded meets Sch 1 items requesting “name” and “description of those acts or omissions”.

5. Retain records for the prescribed period (s 15). For records required in a benchmark period, retain them until at least two years after the end of that benchmark period. Map retention schedules in your records management system to ensure that records are not prematurely deleted. If records were required under the 2011 Rules and subject to retention under Part 3 of those Rules, continue to retain them to the same minimum period (s 22).

6. Prepare compliance reports to Schedule 1 and use Form in Schedule 2 (s 16; Sch 1-2). Your compliance report must include:

   • Provider name and ABN, date of preparation, start/end dates for the benchmark period (Sch 1 item 1; Sch 2 Table 1).
   • Counts of CSG services by area per Sch 1 item 2 and Table 2.
   • Performance summaries for in‑place connection requests, new connection requests by area, faults/service difficulties by area, and appointment keeping as set out in Sch 1 items 3-6 and Tables 3-6 in Sch 2. Ensure all table fields are completed; nil returns must be specified where appropriate (Sch 2 instructions).

7. File compliance reports within 40 business days after the benchmark period (s 17(1)). Submit by electronic transmission to the ACMA email address published on ACMA’s website for this purpose (s 17(2)). If you need more time, seek written agreement from ACMA before the deadline (s 17(1)) and retain evidence of any extension.

8. Prepare for possible audits (ss 18-21). Because ACMA may require an external audit on reasonable grounds (s 18(5)), put in place:

   • A shortlist of qualified independent auditors experienced in telecommunications regulatory audits.
   • A project plan that can meet the deadlines in ss 19-21: draft terms of reference to ACMA within 21 days of a notice (s 19(2)); revised terms within 14 days after ACMA requests changes (s 19(4)); auditor nomination within 21 days of relevant notice (s 20(2)); replacement nomination within 14 days if rejected (s 20(4)); and delivery of the auditor’s report to ACMA within 14 days after receipt by the provider (s 21(2)). Note that ACMA can require different timeframes by agreement.
   • Contract templates that permit ACMA‑mandated auditor changes, and budgetary approvals for the provider to cover audit costs (s 18(2)).
   • A playbook for responding to ACMA requests to approve or change terms of reference and auditors (s 19(3)-(5); s 20(3)-(5)), including how to demonstrate auditor independence and capability to form the required opinion (s 20(6)).

9. Ensure audit deliverables meet s 21(4). The audit report must include an audit plan, an audit memorandum explaining how scope/objectives were applied, and an auditor’s expression of opinion as to whether compliance reports have been prepared and records kept in accordance with the Rules. Because s 21(4)(c)(i) cross‑references section 13 (a records provision), ensure the audit covers both the production of compliance reports and Part 2 record‑keeping to remove ambiguity.

10. Record governance, evidence trails and data quality. Given the level of granularity required and ACMA’s ability to audit, implement data‑quality checks, timestamp verification, and change logs for appointment modifications. Keep audit trails for all data extractions and transformations used to produce compliance reports.

11. Privacy and security. Because the Rules require holding customer names, addresses and service history, ensure data handling complies with applicable privacy obligations and internal information security controls. Retention for at least two years after the benchmark period means relevant personal data will be stored for that period; document legal bases and minimise access.

12. Monitor the life cycle of the Rules and related instruments. Because the Rules are linked to the CSG Standard (s 5) and import definitions from the Benchmarks Instrument and the CSG Standard (s 6), monitor those instruments for amendments or re‑enactment that would change definitions, thresholds, guaranteed maximum periods, or the Rules’ expiry.

13. Escalation and legal review. Where the provider’s internal investigations identify failures attributable to other carriage service providers, consider engagement with legal or commercial teams to manage inter‑provider disputes and ensure the descriptions provided to ACMA are accurate and defensible (ss 10-14; Sch 1 items 3-6).

14. Documentation for audit readiness. Maintain a compliance pack for each benchmark period that includes: the compliance report (Sch 2), data extracts and raw logs supporting the figures, examples of recorded requests/faults/appointments (with any personal data redacted where appropriate for internal review), and a retention index showing how records are stored and retained per s 15.

By following the steps above and mapping each internal process to the specific Rule citation, a qualifying provider can operationalise compliance. Administrative design should focus on timestamp capture, area classification consistency with the Benchmarks Instrument, attribution workflows for multi‑provider incidents, and a contractual/audit capability to respond to ACMA’s audit demands in the deadlines prescribed.