Negotiating with municipalities: servicing, taxes and community benefits

Approvals are not only technical. A data centre campus is a major development that asks a lot of its host: roads, water, sewers and power infrastructure; changes to the landscape and soundscape; years of construction traffic. In return, it can offer large property tax revenues, construction jobs, a smaller number of skilled permanent jobs, investment in local infrastructure and sometimes waste heat for community use. Municipalities, and increasingly provinces, negotiate the terms on which they will accept a project. This lesson covers the main subjects of negotiation, servicing and development charges, property and other taxes, incentives, community benefits and Indigenous partnerships, and the principles and practices that lead to durable agreements.

Servicing and infrastructure

A campus needs roads that can carry heavy construction traffic and transformer deliveries, water and wastewater connections sized for its cooling design, stormwater outlets, and, most expensively, transmission lines and substations. Who builds and pays for this infrastructure is a central negotiation:

• Development charges: Ontario municipalities levy development charges under the Development Charges Act to fund growth-related capital costs (roads, water, wastewater, stormwater), calculated per square metre of non-residential floor area. Alberta municipalities levy off-site levies under the Municipal Government Act, and British Columbia municipalities levy development cost charges. For a large data centre, these can reach many millions of dollars, and some municipalities have created specific rates or exemptions for data centres.
• Servicing agreements: where new or upgraded mains, pumping stations or roads are needed, the developer often builds them to municipal standards under a servicing or development agreement, sometimes with credits against development charges or cost recovery from later developers who benefit.
• Electrical infrastructure: connection costs follow the utility's and regulator's rules, such as the Ontario Energy Board's Transmission System Code and Distribution System Code, under which large customers typically fund their own connection assets and may contribute to network upgrades. Provincial frameworks for large data centre loads are adding new obligations and cost allocation rules.

Taxes

Property tax is the main way a data centre contributes to municipal finances. In Canada, property is assessed by provincial assessment agencies (for example MPAC in Ontario and BC Assessment) and taxed by municipalities at rates for each property class. Whether and how the IT equipment, electrical and mechanical systems are included in the assessed value varies by province: in some provinces much of the machinery and equipment is not assessable as real property, while in others municipalities may tax machinery and equipment. The classification of the property (industrial, commercial or a special class) and the treatment of equipment can change the tax bill by a large factor, so assessment is often discussed early with the municipality and assessor. Federal GST and provincial HST paid by businesses are generally recoverable through input tax credits, but provincial sales taxes in some provinces apply to equipment purchases and can be a significant cost on servers that are replaced every few years.

Incentives in Canada

Canadian incentives for data centres have historically been more limited and more provincial than in the US. They have included competitive industrial electricity rates (now under review for data centres in several provinces), provincial economic development funds, municipal tax increment equivalent grants or community improvement plan incentives in Ontario, and federal and provincial support for related investments in clean power or AI infrastructure. Provinces are also increasingly selective, using connection approvals, rate classes and allocation processes to favour projects with local economic, strategic or sovereignty benefits, such as domestic data hosting.

Development agreements and community benefits

Commitments negotiated with a municipality are typically secured in a development agreement or site plan agreement registered on title, with financial security. Beyond the legally required elements, many projects now include community benefits:

• Infrastructure that serves the community as well as the project, such as road improvements, upgraded water mains or a new substation that also strengthens local supply.
• Operational commitments: noise limits with continuous monitoring and a complaint line, daytime-only generator testing, light shielding, landscaping maintenance, and water use limits or reclaimed water.
• Waste heat recovery to district heating systems, greenhouses, aquaculture or public buildings, more common in Europe and growing in Canada and the northern US, where heat demand is high (DCE-460).
• Local hiring, apprenticeships, procurement from local businesses, and partnerships with colleges for technician training.
• Community funds, parks, trails or donations, sometimes tied to the project's size or revenue.
• Decommissioning commitments for the end of the facility's life.

Partnerships with First Nations and Métis communities are increasingly central in Canada, including equity participation in power supply or the data centre itself, employment and training agreements, and joint ventures. Such partnerships can be the basis of a project's long-term social licence, and in some provinces they are encouraged or expected for projects on traditional territories.

Negotiation principles

Negotiations with governments and communities are repeated, public and multi-issue. A few principles apply:

• Interests, not positions: the municipality's position may be "no generators within 300 m of homes", but its interest is protecting residents from noise and emissions. A layout with a 200 m setback, a sound wall, quieter enclosures and daytime-only testing may meet the interest better than a bigger setback.
• Know the alternatives: each side's best alternative to a negotiated agreement (BATNA) sets the limits. The developer's BATNA is its next-best site; the municipality's is another use for the land, or no development. The zone of possible agreement lies between what the developer can afford to give and what the municipality must receive.
• Package issues: trading across issues (for example, a longer phasing period for development charges in exchange for a road improvement that the municipality values highly) creates more value than haggling over each one separately.
• Make commitments measurable and enforceable: "reasonable efforts to reduce noise" invites disputes; "no more than 45 dBA at the property line at night, verified by continuous monitoring with public reporting" builds trust.
• Balance confidentiality and transparency: developers often keep site searches confidential under non-disclosure agreements, sometimes with municipal staff, but communities that learn of a large project late often react with distrust. Early, honest engagement once the site is secured usually costs less than repairing a damaged relationship.

Note also that municipal records are subject to provincial freedom of information legislation, such as Ontario's Municipal Freedom of Information and Protection of Privacy Act, so confidentiality agreements with public bodies have limits.

Community engagement and moratoria

Communities in many established markets have become more sceptical of data centres, citing noise, transmission lines, water use, electricity rates, loss of farmland and the small number of permanent jobs relative to the land and infrastructure used. Several jurisdictions have paused or restricted approvals while they revise their rules, and elected officials have campaigned on the issue. A credible engagement strategy is therefore part of the project, not an afterthought:

• Open houses and information sessions early, with realistic renderings, noise and traffic studies, and clear answers on water and power.
• A community liaison committee meeting throughout construction and operation.
• Construction management plans for traffic, hours, dust and noise, with a responsive contact.
• Public reporting on commitments such as noise monitoring and water use.
• Honest discussion of benefits, avoiding inflated job claims that undermine credibility.

A project that has earned local support also strengthens the developer's position with higher levels of government that increasingly influence power allocation and approvals.

Lesson 11 shows how to quantify the economic and fiscal effects that underpin these negotiations, and Lesson 12 combines all the approvals into a single strategy and schedule.