Summary

  • CRTC Notice 2026-259 invites views on simplifying or removing seven telecom reporting requirements; it has not removed any of them.
  • A safe sunset must name the oversight signal, its replacement, the blind spot created by the change and a date to test whether the replacement works.

A form is a sensor

A recurring report is easy to describe as paperwork. It is more useful to treat it as a sensor installed for a reason. The CRTC’s 6 October notice asks whether seven reporting requirements can be simplified or removed without materially harming oversight. The intervention deadline is 20 November 2026, with replies due 22 January 2027. This is a consultation, not a repeal notice.

The list spans different regulatory jobs. Four items concern service quality: semiannual indicators for local services in forborne markets; annual retail quality reports from small incumbent local exchange carriers; and annual technical reporting on non-mandated wholesale services. The original purposes were not identical: competitor access, rural service comparability, and conditions faced by providers that depend on wholesale infrastructure. A form that looks similar on an administrator’s desk may function as a different warning system in each market.

Three other items track affordability, market development or a historical test. They cover uptake of legacy lower-cost data-only plans; availability, promotion and take-up of lower-cost or occasional-use wireless plans; annual reports on regional carriers’ mobile virtual network operator progress; and manual route lists used in the “rule of three” for high-capacity interexchange private lines. The notice says MVNO progress information is now collected annually through the CRTC’s Data Collection System. That is a concrete duplication claim for this one series. The notice does not say that DCS already replaces the other six.

This distinction matters because removal changes what the regulator can see. A complaint can reveal a failure experienced by a customer or competitor. It may arrive late, and silence does not establish that service is healthy: people may not know where to complain, may decide the cost is not worth it, or may have left the service. An event-triggered return can focus attention on a material change, but only if the trigger is measurable and someone can detect when it has fired. Aggregation may reduce filing effort, yet conceal an outlier region or a particular wholesale customer.

These are risks to test, not proof that the current reports must stay.

The CRTC’s 2018 wholesale quality policy articulated the core trade-off: reporting should be frequent enough to reveal significant change in time for the Commission and competitors to respond, without imposing excessive burden. The 2026 review asks whether alternative reporting can retain that capability. A persuasive answer should identify which decision the old series informs, how the replacement produces an equivalent signal, what resolution and delay it permits, and who can act on it. “The market has changed” is a reason to re-test the sensor, not itself evidence that the signal no longer matters.

The history also counsels against treating forms as permanent. The CRTC introduced DCS in 2004 partly to lower burden and integrated some collection with Statistics Canada to avoid duplicate surveys. Yet the system still differentiates large and small providers, and its public guide says smaller telecom companies may file simplified paper registration forms. A shared portal can reduce duplicate entry; it cannot make every dataset comparable or every reporting burden equal.

The Commission’s April progress report describes a workload under pressure: it closed nearly 70% more Part 1 applications in 2025 than in 2024, while receiving 30% more. That helps explain why streamlined, timely signals matter to the regulator as well as industry. It does not establish that any specific report is redundant. The test must be conducted requirement by requirement, with the users of the data at the table, including rural customers and wholesale competitors who may not control the reporting system.

A practical rule for this proceeding is simple: before retiring a report, publish a short evidence map. State the decision it supports; the alternative source, complaint or event trigger; the level of detail and response time that will be lost; and a review date. If the substitute is an existing DCS return, show the field-level overlap and the responsible data owner. If it is a complaint channel, explain how the regulator will account for under-reporting and detect deterioration before complaints accumulate. If it is a sunset, define what observation would cause the requirement to return.

That is close to the design lesson in Lu Heng’s Note 64: keep the common specification to what participants need to coordinate, and leave later choices close to those who operate the system. Here, the analogy is limited. The CRTC is a statutory regulator, not a voluntary protocol; the note supplies an editorial lens, not Canadian law. The useful question is whether one uniform periodic return is truly necessary everywhere, or whether a minimum common signal can coexist with local or event-based reporting.

The notice separates seven immediate candidates from more complex DCS reporting for a future consultation. That sequencing gives the Commission a chance to test simpler substitutions first. The quality of the outcome will depend less on the number of forms deleted than on whether officials can still detect the condition each form was meant to expose. A report should end when its signal has become unnecessary or has a credible successor—not when its purpose has been forgotten.

Sources