Summary

  • CRTC Decision 2026-272 reduces the underlying carrier’s deadline to tell a reseller that a number has left—from as long as one week to two business days or less.
  • The CRTC kept residential validation optional under the bilateral model, even as it tightened post-port notice and clarified expedited requests, fees and partial migrations.

A faster receipt arrives after the decision

A phone number leaves a reseller’s customer for a new provider. The carrier that executed the port must tell the reseller within two business days. That notice is now faster. But the reseller still has no guaranteed opportunity to confirm a residential customer’s request before the number moves.

That is the consequential split in Telecom Decision CRTC 2026-272, issued 16 October. The decision approves updates to Canada’s local ordering guidelines and transfer maps: same-day expedited ports involving resellers are generally barred; rejected expedited requests may attract both rejection and expedite fees; reseller types and partial migrations are defined more clearly. In a dispute, an expedited request remains possible, with a future standard cut-off based on the local time the ordering provider receives it.

The two-day notice responds to a real operational problem. If the reseller learns late that service has moved, its billing record may remain open and call routing can diverge from the customer’s actual provider. The previous ceiling was one week. Faster notice narrows the period in which the reseller and underlying local exchange carrier (LEC) may hold inconsistent records.

But notice follows completion. Validation happens before completion. The decision’s majority retained the 2013 rule: primary resellers get an opportunity to validate business transfers, not residential ones. Bilateral agreements remain the route for the parties that want more coordination. The Commission said the record did not provide compelling evidence for a regulatory change and that some LECs already hold enough customer information to validate a request themselves.

The older decision explains why this is not merely a theoretical distinction. In 2013, CRTC described transfer requests rejected by automated checks because a customer’s name did not match the LEC’s record; the upstream database might contain the primary reseller’s name instead. The resulting workarounds and escalations could delay a legitimate switch. That decision still concluded that residential risk did not justify a mandatory validation opportunity, while requiring one for business customers, where an erroneous transfer could cost revenue.

Commissioner Bram Abramson’s dissent identifies the unresolved counter-case. The concern, he argues, is not only that the wrong transfer might be completed. The mismatch can also obstruct the right transfer. His proposed rule would require an opportunity, not a compulsory reseller response: if the reseller did not answer within an agreed window, the LEC could proceed. That preserves a path to completion while letting the party with the customer record contribute when the LEC lacks the needed information.

The majority and dissent therefore weigh different failure modes. One emphasizes added handoffs, uneven reseller systems and a lack of compelling evidence of residential harm. The other treats record mismatch and bargaining position as structural risks, even without a prescribed technical interface. The decision does not publish a current residential false-rejection rate, retry duration or complaint count. Neither position can be read as a measured estimate of how often the problem occurs.

The day before, CRTC Decision 2026-271 addressed a different boundary: registered full mobile virtual network operators may directly access wireless number-porting systems if they meet existing obligations, with implementation changes due by 1 February 2027. That is an access-right decision for operators with their own mobile core. Decision 2026-272 is about the workflow between an upstream carrier and a reseller, especially residential validation. The two rulings show that “reseller” is not a single operational category, but they do not resolve the same problem.

The practical test for 2026-272 is whether the shorter notice interval reduces stale billing and routing records without leaving legitimate residential requests trapped at the validation step. The decision sets process rules; it does not order publication of outcome data. A credible evaluation would count rejected requests by reason, resubmissions, time to completion, unauthorized completed ports, billing overlaps, routing errors and customer complaints—and separate residential from business transfers and reseller types.

Until those measurements exist, the two-day deadline is evidence of a tighter post-port handoff, not proof that switching has become frictionless. The unresolved question is whether the party that knows the customer can be heard early enough to prevent a mismatch from turning into a failed exit.