A data centre moratorium is a tool, not a policy
Ontario municipalities are making visibly different choices about data centre development.
Mississauga adopted a one-year interim control by-law on September 16 for facilities with a peak power demand of at least 10 megawatts while it reviews planning rules, infrastructure impacts, water consumption, noise and other effects.
Centre Wellington approved a one-year interim control by-law on September 28, temporarily prohibiting new data centres in specified industrial zones. Its study will examine electricity demand, long-term drinking water supply, noise, lighting and land-use policies, with recommendations expected in 2027.
Quinte West considered a similar pause and rejected it on October 7. Existing proposals will continue through the municipality's planning process, including an 18-megawatt project whose proponent has offered commitments concerning cooling water, noise, generators, heat recovery and ratepayer costs.
York Region has taken another approach. Following a request from Richmond Hill, Regional Council directed staff to examine current and future infrastructure considerations relating to data centres and report back in 2027. A central concern is protecting water and wastewater servicing for existing communities, planned housing and future economic development.
There are examples from south of the border too. Memphis has launched a 90-day policy review covering land use, infrastructure, aquifer protection and the possible use of treated wastewater. Its council is separately considering a moratorium. Santa Clara's municipal electricity utility has not accepted new data centre electricity load applications since 2023, while the city reviews its broader policies, with that work expected to continue until late 2027.
These are different procedural responses that do not necessarily represent different answers to the underlying policy questions. And one question that deserves more attention before municipalities decide whether to pause development: Why does the community want to attract data centres in the first place?
For some municipalities, data centres may fit an established economic development strategy. They may be trying to build a technology or digital services sector, attract new investment, or make productive use of existing industrial properties. There may already be development applications under review or credible prospects expected in the near future.
Other municipalities may attract interest because of their particular characteristics, even if data centres were never part of their economic development plans. Reliable or competitively priced electricity, access to low-emissions power, a cooler climate that can reduce cooling requirements, good fibre connectivity, available industrial land, a skilled workforce or sites sufficiently removed from residential areas can all influence where developers look to invest.
These advantages are not always straightforward. An area may have relatively clean electricity but insufficient grid capacity for a large new facility. A remote site may offer separation from neighbouring uses but lack adequate transmission or communications infrastructure. The advantages also vary depending on the type of data centre and its intended customers.
For others, data centres may not be a priority at all. Their economic development plans may place greater emphasis on manufacturing, agriculture, housing or other industries. These activities may compete for the same serviced land, electricity and water capacity.
Those circumstances should influence how much attention municipalities give to the issue, and how urgently they need to act.
A municipality actively pursuing data centre investment needs to understand what infrastructure it can support, what economic benefits it expects and what conditions should apply. A municipality attracting unexpected interest needs to assess whether that investment is consistent with its broader priorities. One with no applications or realistic prospects may reasonably decide that other planning work deserves more immediate attention.
There is an opportunity cost to consider as well. Even where sufficient capacity exists today, committing substantial electricity or water resources to one development may affect what remains available for future growth. The value of a project needs to be considered alongside what the community may be giving up.
What makes a location commercially attractive to a data centre operator does not automatically make the development a good investment for the community. Those are two different assessments, and municipalities need to consider both.
York Region illustrates another complication. Local municipalities are responsible for land-use approvals, while the Region plans and delivers major water and wastewater infrastructure. Electricity connections involve a different set of authorities. A project that appears manageable from a local planning and development perspective may have implications for infrastructure serving several communities.
These responsibilities need to be considered together, particularly when assessing cumulative demand and future growth.
This brings us back to the question of moratoriums. A moratorium can provide time to study an unfamiliar form of development before more applications arrive. It can protect a municipality from making successive project decisions without understanding their combined effect.
But a pause does not itself decide how much water or electricity a project may use, which infrastructure costs belong to the developer, how community benefits will be measured or what happens when a facility expands.
But allowing an application to continue does not necessarily mean accepting the proposal without safeguards. Existing planning, servicing and environmental processes may be capable of imposing appropriate conditions, depending on the powers of the authorities involved.
If a proponent promises closed-loop cooling, the approval record should define the system and its expected water requirements. Closed-loop does not necessarily mean zero water consumption. If the facility later changes its equipment or operating profile, the municipality needs to know whether additional review is required.
If a project promises no cost to ratepayers, the responsible authorities should identify which grid, road, water, wastewater and emergency-service costs are included. They should also address what happens if infrastructure requirements change after construction begins.
Promises about local employment, heat recovery or community benefits need the same treatment. Who delivers them, by when, and who verifies the result?
These commitments also need to be secured through the appropriate agreements or regulatory processes. Not every matter falls within municipal authority, and a public promise is not necessarily an enforceable obligation.
Outside of imposing a moratorium, a durable municipal or regional data centre policy would establish:
whether data centres fit local economic development priorities, including the expected benefits and competing demands on infrastructure;
what local characteristics may attract data centre investment, and whether those advantages translate into benefits for the community;
which projects require enhanced review and whether there is an existing or anticipated development pipeline;
what electricity, water and infrastructure information proponents must disclose;
how cumulative demand will be assessed alongside housing, employment and other planned growth;
how public and private costs will be divided;
where project commitments will be legally recorded and which authorities are responsible for enforcing them;
who will monitor compliance after approval; and
what changes require the decision to be revisited.
Ontario's proposed Data Centre Playbook may eventually help determine which projects obtain electricity grid connections by considering their economic value, digital sovereignty and community benefits. That is a useful provincial consideration, but it does not replace local decisions about land use, servicing, infrastructure capacity and community priorities.
Nor should every municipality need to develop an elaborate data centre policy simply because other communities are receiving applications. The appropriate response should reflect local circumstances, the scale and likelihood of development, and the adequacy of existing planning and infrastructure processes.
A pause can create room to develop new rules. Continuing with an application can test whether existing rules are adequate. A broader infrastructure assessment can help determine how proposed developments fit with other demands on limited capacity.
None of these approaches is right or wrong, and the useful metric is not whether a municipality froze development. Instead, we can ask whether the process that the municipality chose reflects the community's priorities and can produce decisions that remain understandable, enforceable and adaptable after all the immediate controversy passes.
Facing a similar decision?
BlueVector Strategy provides independent strategic advice to municipal and utility leaders navigating major water and wastewater decisions.
If your community is weighing development opportunities against infrastructure capacity, investment requirements or competing priorities, we can help you assess the options and understand the commitments before making a decision.
Let's talk.