Summary

  • Canada’s numbering administrator projects that Alberta’s existing 368/403/587/780/825 area-code complex will need another code by February 2029; the CRTC has approved 568 for 10 June 2028.
  • That eight-month interval is a risk buffer around a forecast that has changed over time. It gives carriers and customers a scheduled migration window; it does not establish an exhaustion date or an imminent interruption.

A date built around uncertainty

An area code can look like a calendar problem until the calendar becomes part of the network. Alberta already has five area codes—368, 403, 587, 780 and 825—serving the same provincial geography. The Canadian Numbering Administrator (CNA) now forecasts that this complex will need another code by February 2029. The Canadian Radio-television and Telecommunications Commission (CRTC) has approved 568 as a distributed overlay, effective 10 June 2028.

The interval between those dates is the decision’s most useful number. The CRTC says the overlay will begin eight months before the projected exhaustion point. The Canadian NPA Relief Planning Guideline ordinarily provides a six-month lead time. The extra two months are intended to absorb a forecast moving forward by a few months without forcing the industry to reopen its plan, while leaving time to update carriers’ systems, databases and telecommunications equipment. That is a schedule for readiness. It is not a claim that the last usable number will be assigned in February 2029.

This distinction matters because a numbering forecast is an input to a public planning process, not a countdown clock attached to every customer line. It estimates when an area code complex may need new assignable resources under the reporting and utilization assumptions used in a particular forecast. The CRTC’s decision identifies the forecast as the CNA’s January 2026 result. It does not publish a certainty interval, a carrier-by-carrier shortage date or a prediction of when a particular customer will be unable to obtain a number.

The decision therefore converts a forecast into an implementation deadline without pretending the forecast is certain. It authorizes a new code and fixes a date on which the code can enter use. The buffer protects the implementation plan from ordinary forecast movement. It does not erase the uncertainty that made the buffer necessary.

The projection has moved before

Earlier official records show why the date should be read as a planning estimate. In November 2022, when the CRTC set aside 568 for this Alberta complex, its table showed projected exhaustion in February 2028. A Canadian Numbering Administrator report published in April 2024 recorded a series of later projections: June 2028 in the January 2023 general forecast, April 2028 in the July 2023 relief forecast, and May 2029 in the January 2024 relief forecast. The January 2026 forecast cited in the latest decision moved the projected need to February 2029.

Those dates do not make the current decision incoherent. They show that the purpose of forecasting is to update a plan as reported resource use and assumptions change. They also do not show why any individual forecast moved. The public documents report the dates and methods, but the material reviewed here does not support attributing the shifts to one factor, such as conservation, mobile growth, Internet of Things devices or a change in carrier behaviour. Treating a revised projection as proof of a particular cause would go beyond the record.

Alberta’s earlier relief cycle makes the same point. The CRTC’s 2019 decision approved area code 368 after a 2018 forecast projected exhaustion first in September 2022 and then in March 2022. A 2020 forecast later moved the projected date to November 2023. In 2021 the CRTC approved a revised 23 April 2022 implementation date for 368, roughly 19 months before that updated projection. The plan was adjusted as the forecast changed; the projection was not a promise that consumers would lose service on a specified day.

The histories are not perfectly comparable: the earlier cycle had a different code complex and implementation plan, and its record discussed then-existing network changes. They are useful for one limited reason. Canadian area-code relief planning has long used projected exhaustion to determine when coordinated implementation work should begin, and has revised dates when the forecast changed. That practice is evidence of planning responsiveness, not evidence that every forecast is accurate or that a future plan cannot need amendment.

Three functions, three kinds of authority

The process also separates functions that can easily be collapsed in public shorthand. The CNA administers numbering resources and produces the utilization forecast under CRTC-approved guidelines. It is not the policy-making body. The CRTC’s May 2026 notice established an ad hoc relief planning committee under its Interconnection Steering Committee and directed the CNA to chair it. The committee evaluated options and recommended a distributed overlay, area code 568 and the June 2028 date. The CRTC then approved the report and made the implementation decision.

That sequence is more than administrative detail. A forecast supplies evidence about future resource pressure. A committee turns that evidence into a proposed plan, with carrier and customer readiness in view. The regulator decides which plan is authorized. Each step has a different job; none should be used as a substitute for the next. The forecast does not itself assign a new area code. The committee’s recommendation was not yet the binding decision. The CRTC’s approval does not transform the underlying forecast into a guaranteed date of exhaustion.

The public process is consultative and open to participants, but attendance or participation does not itself become a public mandate. Heng Lu’s Note 73 distinguishes stakeholder participation from authority to bind principals. Applied narrowly here, that distinction asks readers to identify who produced the forecast, who recommended the implementation sequence, and who approved it—rather than treating “the industry” as one undifferentiated decision-maker.

The CRTC’s notice says the committee was open to the public; it does not claim that participation was a referendum of Alberta residents or a statistical representation of all telephone users.

This is not a defect in the process. Numbering requires technical coordination across providers, while the CRTC retains the formal decision. The accountability test is whether each function is visible and the evidence is proportionate to the decision. The decision’s record makes the implementation date, the underlying forecast month, the ordinary lead time and the committee’s rationale explicit. It does not provide enough information to say precisely how much unused capacity remains with each provider or how far the forecast could move.

What a distributed overlay changes

Area code 568 will be a distributed overlay: it will serve the same geographic area as the existing complex. The method adds numbering resources without requiring current customers to change their telephone numbers. The CRTC’s 2019 Alberta relief decision selected a distributed overlay across the then-existing exchanges rather than concentrated overlays that would divide the province into separate future relief-planning areas. The current decision continues the same province-wide form as the complex has grown.

An overlay does not mean that a subscriber’s number changes, that local calling rates change, or that a new service becomes available. The CRTC’s May 2026 notice expressly excludes local and long-distance calling patterns and rates from the relief committee’s scope. Nor does the overlay demonstrate how many numbers are actually in use, how many spare central-office codes remain for any carrier, or whether a customer can obtain a particular number. Those questions involve assignment and utilization information beyond the approved area-code schedule.

The practical work is distributed across systems. Carriers need to recognize the new NPA in provisioning, routing, billing, customer records and equipment; other service providers and organizations that store or validate telephone numbers may also need to update their systems. The CRTC’s decision says the date is intended to provide sufficient time for changes in systems, databases and telecommunications equipment. The detailed approved implementation plan contains the working schedule, but the decision itself is not a completion report.

As of approval, it establishes what participants are expected to implement, not proof that every database, device or customer-facing interface has been updated.

The distinction between an approved plan and completed implementation is the same evidence discipline needed for service continuity. A regulator’s approval is an authorization. A forecast is an estimate. A plan is a sequence of work. Evidence of completion requires the work to be performed and verified. None of those records, by itself, proves that users have experienced a failure—or that every downstream system is ready.

The useful reading of the eight months

The eight months should be read as a hedge against forecast volatility and a coordination allowance. It is two months longer than the guideline’s ordinary six-month lead time. The CRTC says that margin means a projection advancing by a few months would not necessarily require reopening the recommended plan. It also allows participants to prepare before the forecasted need date.

That margin carries a trade-off. Beginning earlier gives carriers and businesses more preparation time, but it also asks them to complete work before the projected date when new resources may be needed. The 2021 decision on area code 368 discussed the then-current estimate that extra early expenditure would be minimal because Alberta already had overlay-capable network and business systems. That historical conclusion cannot simply be carried over to the 568 plan: the equipment, vendors and scope may differ, and the current record does not quantify present costs.

The current CRTC decision supports the readiness rationale, not a claim that implementation is costless.

For customers, the central assurance is narrower than “nothing will change.” Existing telephone numbers do not have to change under a distributed overlay, but organizations that validate, store or route numbers may need to recognize a new area code. The CRTC’s decision does not report a consumer-impact assessment for every such system. It creates an implementation window in which those changes can be made and tested.

For oversight, the central question is whether the evidence chain stays legible. The CNA’s next forecast may revise the exhaustion estimate. The CRTC’s 2026 decision nevertheless fixes the approved launch date unless a later authorized process changes it. Public reporting should keep those facts side by side: the operative date is 10 June 2028; the current forecast is February 2029; and the buffer is eight months. A changed forecast would be a new input, not proof that the existing decision was wrong when made.

Sources