Five expectations arrived from Ottawa carrying not one switch to enforce them. The launch came on September 3, 2026, with a minister, a municipal federation and 23 company signatures behind it. The document cannot approve a single building, and it was never built to. That missing power is the real story here.
The announcement came from Toronto, where Evan Solomon, the Minister of Artificial Intelligence and Digital Innovation, launched the principles beside Tim Tierney, president of the Federation of Canadian Municipalities. The pairing was deliberate, and it told any careful reader where this file actually lives. The federal case rests on infrastructure: the release ties these buildings to health care and financial services first, and to research computing and secure government work behind them. Much of the cloud and storage behind Canadian AI still runs on machines outside this country. More capacity at home is sold as insurance, and as a choice Canada currently does not have.
The short answer. Ottawa set five expectations for data centre projects: lasting local benefits, no shift of electricity costs onto Canadians, minimized water use and environmental impact, transparency about local impacts, and strategic value to Canada. The standard binds nobody, and any town can pick it up and use it in a hearing. They approve nothing, connect nothing and zone nothing under any reading of the document. Development decisions remain provincial, territorial, municipal and Indigenous decisions, on the release’s own terms.
Every company that signed handed the next town it approaches a measuring stick with its own name already on it.
- What exactly did Ottawa announce on September 3?
- What do the five expectations ask a builder to prove?
- Who holds the switches Ottawa left off the table?
- What should an operator take into the next hearing?
What exactly did Ottawa announce on September 3?
The document is a framework of expectations for building the data centre capacity Canada needs. Signatories come from the data centre, cloud, AI and technology sectors, and the list carries weight on both sides of the border. Amazon Web Services, Anthropic, Google, Meta, Microsoft and OpenAI signed, alongside Canadian names including Bell Canada, Cohere, eStruxture, QScale and TELUS. Twenty-three organizations committed in total, behind one consistent, community-centred approach to development. No enforcement office, no penalty and no reporting deadline appears anywhere in the announcement itself. The framework’s authority rests entirely on the fact that the signatories agreed to it in public.
What do the five expectations ask a builder to prove?
Each expectation answers a complaint that host communities already raise in hearing rooms across the country. Lasting local benefits speaks to towns that watch construction crews arrive and leave without permanent gain remaining behind them. The electricity expectation holds that a project’s power costs stay with the project rather than migrating onto household bills. Water use and environmental impact carry one condition, transparency about local impacts another. Strategic value to Canada closes the list, and it is the only expectation written at a national scale. Read together, the five lines form a checklist that any council can put to a proponent in writing. An expectation that nobody tests stays a slogan, and these five become evidence only when a local process demands answers on the record.
Who holds the switches Ottawa left off the table?
One passage in the release outweighs the launch around it: the paragraph where Ottawa describes its own limits. Tested against that paragraph, the two claims made for this framework both fail. The first claim says a national framework means Ottawa has taken charge of data centre development at last. The second says voluntary principles are theatre on letterhead, binding on nobody and forgotten by winter. Where a project lands, the call belongs to the place itself: its priorities, its approvals, its residents’ needs. The principles were written to sit alongside provincial, territorial, municipal and Indigenous processes, adding a standard without touching a single one of their powers. Electricity answers to provinces and land use answers to municipalities, and neither fact moved on September 3. What survives is narrower than either claim and stronger than both. The principles govern what a builder publicly owes a community, while the jurisdictions govern whether the builder builds at all. A signatory now enters every hearing carrying a standard it endorsed, facing a process that owes it nothing. That is the ground the Mississauga council stood on when it paused approvals inside its own borders. (Mississauga Had One Data Centre Application. It Froze Every Lot in the City.)
What should an operator take into the next hearing?
The practical force of the framework will appear first in hearing rooms rather than in Ottawa press releases. When a signatory proposes a project, expect councils and residents to read the five expectations back to the company. A builder that signed in September and argues against the same tests later has created its own public record. Public opinion is moving on the same track, and the consent question now sits beside the power question. For executives siting anything power-hungry in Canada, the working lesson sits close to home this fall. Federal goodwill is a backdrop, and provincial and municipal permission remains the whole game on the ground. If a data centre proposal lands near your own operation, take the five expectations into the process and ask for answers in writing. (64% of Canadians Want Data Centre Limits. The Builds Continue.)
The principles carry no expiry date, no review date and no enforcement calendar anywhere in the federal document. Every deadline that matters in this file belongs to a council agenda, a provincial connection queue or a regulator’s docket, and the running record of those dates lives in Canada’s data centre map: what is built, what is blocked, what is waiting. Those dates get set in provincial capitals and in town halls across this country. Ottawa cannot move a single one of them, and no signature in Toronto changes that arithmetic.
