Summary

  • For the investigation period from 1 May 2023 to 31 May 2024, Opticomm had 10 business days to notify ACMA after entering a covered infrastructure contract and 10 business days to declare a covered area after completing the network installation.
  • ACMA found 108 late anticipatory notices and 76 late completion declarations, for 184 carrier-licence contraventions. That is a count of notification findings, not 184 projects, customers, outages or unconnected homes.
  • The register is a public ledger of responsibility. It cannot build fibre or activate a service, but late records make it harder for residents, retailers and planners to know who is responsible and whether the handover has reached its stated stage.

What a statutory infrastructure provider does

New housing estates need more than roads, water and electricity. They also need a telecommunications network that can connect each premises and carry a usable broadband service. Australia calls the operator responsible for meeting that baseline in an area a Statutory Infrastructure Provider, usually shortened to SIP.

The SIP may be NBN Co or another carrier. Opticomm operates wholesale broadband networks in a number of new developments and held carrier licence 239. Retail service providers use the wholesale network to supply internet services to households and businesses.

For an ordinary buyer, the important question is simple: who is responsible for the fixed network at this address? A developer and a carrier may know the answer from their contract, but future occupants and retail providers also need a dependable public record.

That is why the legal framework creates two notification moments. The first comes after the carrier enters a contract to install network infrastructure. The carrier gives ACMA an anticipatory notice describing the project area, the infrastructure and the expected completion date. The second comes after installation is complete. The carrier declares the whole covered project area to be a provisional nominated service area.

The two entries resemble a building handover trail. One says, “this operator plans to build here.” The other says, “the covered installation is complete and this is now the service area.” ACMA maintains a register containing this information.

The deadlines that applied during the investigation

The dates matter because the law later changed. ACMA examined obligations arising between 1 May 2023 and 31 May 2024. During that period, both the anticipatory notice and the completion declaration had a 10-business-day deadline.

Later amendments expanded the anticipatory-notice period to 20 business days. The completion declaration remained due within 10 business days. The newer 20-day rule cannot be applied backwards to decide whether a 2023 or early-2024 notice was on time.

This distinction prevents a common reporting error. A current rule is useful for explaining what carriers must do today, but a historical investigation must be assessed against the rule in force when the conduct occurred.

What ACMA counted

Opticomm provided details of 121 anticipatory notices for the relevant period. Thirteen reached ACMA within 10 business days. The other 108 were supplied between 11 and 344 business days after Opticomm entered the related contract. ACMA found 108 contraventions of section 360HA.

For completed installations, Opticomm provided details of 80 declarations. Four were made within 10 business days. The other 76 were made between 11 and 334 business days after installation was completed. ACMA found 76 contraventions of section 360H.

Adding the two categories gives 184 carrier-licence contraventions: 108 late notices before construction plus 76 late declarations after construction.

That arithmetic does not reveal how many unique projects were involved. A project can have a contract notice and a completion declaration, while a large development may be divided into stages. The public findings also do not say that 184 customers lost service, that 184 networks failed, or that 184 estates lacked fibre.

The numbers measure lateness in two record-making duties. That is serious on its own and does not need exaggeration.

How one missing notice led to the wider investigation

In April 2024, ACMA was making enquiries about delays connecting end-user premises at an estate whose identity is redacted in the public documents. It identified that Opticomm had not given an anticipatory notice for that area.

Opticomm then filed a notice and later told ACMA that the related contract had been signed on 10 August 2018. Based on that information, the regulator established that the notice was more than five years overdue.

ACMA began a formal investigation in June 2024 and requested information about contracts entered into and network installations completed during the defined period. That broader evidence produced the 108 and 76 findings.

The source boundary is important. The missing notice was discovered during enquiries into connection delays. The published reports do not prove that the missing notice caused those delays. A late registry entry can obstruct visibility and coordination, but cause and effect for that estate cannot be inferred from the public evidence.

Its identity is also redacted. There is no public-interest reason to guess the development, its residents or the individual staff member mentioned in Opticomm's explanation.

The register is a ledger, not the network

A service-area register tells the public which operator has taken responsibility for an area and what stage the deployment has reached. Retail providers can use it when deciding how to serve an address. Occupants and developers can use it to understand where responsibility sits. Policymakers can use it to reduce unnecessary duplication and see where NBN Co is not the default SIP.

But the register cannot pull fibre through conduit, configure an optical line terminal or make an appointment at a home. A perfect record does not substitute for a working network.

The reverse is also true. Fibre in the ground does not make a stale public record harmless. If the physical build, the contract system, the completion evidence and the public register disagree, people outside the carrier have to resolve uncertainty using calls, emails and manual escalation.

Good infrastructure governance therefore joins two kinds of truth. The running network establishes what can actually serve a premises. The ledger establishes who accepted responsibility, which area is covered and when the public handover was recorded. Neither should be treated as a replacement for the other.

This is especially important in a new estate. Streets and lot boundaries change during construction. A multi-stage project can open sections at different times. A mapping error or late declaration can leave a retail provider unsure whether an address is inside the relevant footprint, even if equipment is nearby.

What Opticomm said about the process

The investigation report says Opticomm attributed the non-compliance to human error and manual processes that did not reveal problems promptly. It specifically cited reliance on one Head of Design for all notification processes; that person departed in May 2024 without a proper handover.

The report also records the complexity of large, multi-stage developments. Contracts can be signed well before planning approval and detailed maps are available, making early project-area information harder to prepare. Completion reporting can depend on connection reports and data held in other systems.

These facts do not justify blaming an unnamed employee. They describe an operating design in which a regulatory control depended heavily on one role, manual review and data arriving from several places.

A dependable process should survive ordinary staff turnover. Ownership must transfer before access disappears. Every contract and stage should have a visible deadline. Missing maps or reports should create an exception with an owner, rather than leaving the job outside the queue.

The central failure mode is not simply that someone forgot a form. It is that the organisation lacked a sufficiently observable path from a real-world event to a completed public record.

What the penalty did and did not cover

Opticomm paid AUD 150,240 after ACMA issued an infringement notice. The notice specified eight alleged contraventions of subsection 68(1), dated 12, 18 and 30 April 2024. Each was calculated at 60 penalty units.

Those eight alleged contraventions are not the same set as all 184 findings in the investigation report. The payment should not be described as a fine calculated across every late notification.

The notice also says that payment does not amount to a finding that the alleged contraventions occurred and is not an admission of liability. It resolves the identified infringement-notice matter without a Federal Court proceeding if the conditions are met.

Separately, the enforceable undertaking says Opticomm acknowledged that it failed to lodge the relevant notices and declarations within the statutory timelines. Keeping those two instruments separate produces a more accurate account than turning the payment itself into an admission.

The remediation is a useful control map

The enforceable undertaking records steps Opticomm had already taken: more staff for compliance work, additional training, revised systems, clearer workflows for mapping and drafting, automation of parts of anticipatory-notice preparation and streamlined notification processes.

Opticomm also said an automated process was expected to address delays in receiving connection reports that had affected declarations. It was exploring ways to reduce reliance on third-party systems and data for declarations covering separate stages of large projects.

The undertaking adds independent assurance. An ACMA-approved consultant is to review policies, management oversight, escalation and training. Opticomm must respond to recommendations, create an action plan and report implementation.

It also requires a useful evidence trail. Quarterly reports for eight consecutive periods are to show contract dates, estimated completion dates, notice dates and forms. For completed sites, they include installation-completion, declaration, website-publication and ACMA-notification dates. Six-monthly reporting must include known non-compliance and responses.

Those fields turn a vague promise to “improve compliance” into something testable. A reviewer can compare the event, deadline, submission and publication instead of relying only on a policy document.

How to build a live handover record

First, create one identifier when a development contract is signed. Carry it through the commercial system, mapping work, construction stages, completion evidence, regulatory submission and public-register confirmation.

Second, make deadlines event-driven. The signed-contract timestamp should automatically create the anticipatory-notice task. Accepted completion evidence should create the declaration task. Staff should not have to remember to start either clock.

Third, preserve versions of the geographic boundary. If a development changes stages or lot layouts, the system should show what changed, who approved it and which public notice uses which version.

Fourth, make missing inputs visible. A delayed plan, absent connection report or failed submission should sit on an exception dashboard with an age, owner and escalation point. It should never disappear into an inbox.

Fifth, separate preparation from confirmation. Drafting a notice is not filing it. Sending it is not proof that ACMA accepted it. Closing the task should require a receipt or a confirmed register state.

Sixth, design handover for people as well as data. Each control needs a primary owner, a trained alternate, current instructions and access that can be transferred before a role changes.

Seventh, reconcile regularly. Compare new contracts, completed builds, the carrier's website and ACMA's register. Differences should generate tracked work until the physical and recorded states agree.

Eighth, sample the result from the outside. Give a reviewer a real address inside a completed stage and ask whether the responsible wholesale operator can be identified without private knowledge. That is the public usability test.

Questions non-specialists can ask

A homebuyer in a new estate can ask the developer which wholesale network serves the address, whether the lot is inside a declared service area and which retail providers can order service. The answer should include a checkable reference, not only a brochure statement.

A retail provider can ask which project-stage map is current, when the installation was completed and whether the register reflects that completion. If systems disagree, the provider needs a named escalation route.

A developer can ask whether signing or varying a contract automatically starts a notification task, and whether construction completion can be closed without a declaration receipt.

Boards and auditors can ask a more revealing question: how many contracts or completed stages are older than the applicable deadline but lack a confirmed public record? A zero backed by a reconciled list is stronger than a compliance policy with no event data.

What the public record does not prove

The sources do not prove that broadband was absent or unusable in every area associated with a late notice. They measure notification timing, not network performance at each premises.

They do not establish 184 unique developments, 184 customers or 184 outages. The number is the sum of 108 anticipatory-notice findings and 76 completion-declaration findings.

They do not prove that the missing notice caused the connection delays that prompted ACMA's initial enquiries.

They do not identify the redacted estate or support naming the employee whose role was described. The accountable subject is the carrier's process and control design.

They do not show that the AUD 150,240 payment was calculated over all 184 findings. The infringement notice lists eight alleged subsection 68(1) contraventions.

They do not make the current 20-business-day anticipatory-notice deadline the test for the earlier investigation period. The applicable historical deadline was 10 business days.

These limits do not weaken the story. They focus it on what the evidence can support: a significant gap between infrastructure events and the public record designed to describe them.

The durable lesson

Broadband accountability has a physical layer and a record layer. The physical layer is fibre, powered equipment, tested links and homes that can actually connect. The record layer says who is responsible, where that responsibility applies and whether the planned build has reached completion.

The register should not be treated as sovereign over the network; a database entry cannot create service. Yet operators should not use the existence of physical assets to excuse a stale ledger. Outside parties need both realities to match.

Opticomm's case shows the practical control: capture the contract, map the area, observe completion, file on time, confirm publication and reconcile the result. When that path runs automatically and survives staff changes, a public service-area record becomes a reliable handover rather than paperwork catching up months later.

Sources