Governance Analysis #1: How Are Competing Datacentre Proposals Evaluated When Grid Capacity Is Limited?

Ontario’s electricity grid has finite transmission and generation headroom. Datacentres are projected to drive up to 13% of new electricity demand by 2035. Any robust datacentre framework must account for a scarce electricity capacity and continue to figure out what happens when the promises don’t materialise? 

The draft Playbook establishes that datacentres will compete for grid connection based on:

• System Impact Assessment (SIA): Technical connection feasibility and cost recovery for dedicated infrastructure.
• Strategic Priority Assessment: Alignment with economic development, digital sovereignty, and community benefit.
• Proponent Generation: Incentives for “bring your own power” (BYOP) and behind-the-meter assets.

However, actual decision-making mechanisms remain opaque due to the absence of published scoring methodologies. If Project A offers 500 MW with 1,000 construction jobs, and Project B offers 50 MW with dedicated compute allocation for domestic research and SMEs, how does the province prioritise? Without an objective scoring rubric, allocation relies on discretionary approvals that risk undermining long-term innovation and grid reliability.

Evaluating proposals strictly on a site-by-site basis ignores cumulative regional constraints.¹ Once a substation or transmission corridor is committed to a hyperscale facility, local housing electrification, transit, and advanced manufacturing may be locked out. Furthermore, placing datacentres into higher electricity rate classes does not mitigate their flat, 24/7 baseload draw.² The framework must incorporate peak-load shedding and dynamic flexibility mandates during extreme weather and system-peak events.

The Lovelace Threshold: A Governance Diagnostic To Shift Focus On Upstream Conditions

It identifies where governance reaches a structural ceiling where a policy regime fails because it attempts to regulate downstream outputs while leaving upstream physical conditions unmeasured and unbounded.

When connection requests of 7,000 to 10,000+ MW in queue requests knock on transmission corridors that can physically absorb only a fraction of that load, the traditional “first-come, first-served” model collapses:

• The Downstream Approach: The Playbook evaluates downstream vendor promises (projected job creation, capital investment, cooling designs, and Canadian ownership intentions).
• The Upstream Reality: Physical carrying capacity dictates feasibility (finite substation headroom, transmission congestion, peak-hour marginal emissions, and the cumulative lockout of regional transit and housing).

Because the Playbook offers no pre-published quantitative thresholds or regional carrying-capacity caps, it crosses the Lovelace Threshold: approvals risk being granted based on discretionary vendor commitments rather than verifiable physical headroom.

Vulnerability Management for Policy Design (VMPD): Governance Diagnostic To Prevent Downstream Failure

It examines upstream governance weaknesses to prevent downstream policy failures by mapping how structural vulnerabilities propagate into systemic risks. VMPD examines this framework through five sequential examinations:

1. Legibility: what conditions does the framework depend on but cannot see?

Vulnerability: Grid headroom and watershed capacity, but cannot see cumulative regional load, peak-demand marginal emissions, or queuing lock-in. It creates a structural vulnerability where projects could be evaluated in silos, furthermore blinding decision-makers to regional tipping points and impacting communities.

Mitigation: Establish a mandatory, publicly updated Cumulative Regional Carrying-Capacity Dashboard that tracks remaining transmission corridor headroom, localised watershed draw, and marginal peak-demand emissions, requiring every connection assessment to evaluate cumulative regional impacts rather than treating projects in isolation.

2. Architecture: which actors will be held accountable but are absent from coordination?

Vulnerability: Municipal councils and local utilities would absorb emergency, road, water, and service strains, yet are explicitly excluded from consent or veto power in provincial scoring. This could disconnect on-the-ground fiscal accountability from provincial grid allocations.

Mitigation: Institute a statutory Municipal and Local Utility Concurrence Register within the evaluation workflow, requiring binding infrastructure impact sign-offs and council-approved host agreements before any formal transmission capacity is allocated.

3. Specificity: where is ambiguity ignoring the cost of the governed?

Vulnerability: The three strategic pillars lack published weights, scoring rubrics, or baseline thresholds, meanwhile terms like “digital sovereignty” and “meaningful local benefits” remain vague. This ambiguity creates administrative discretion that shifts long-term reliability and rate risks onto the public.

Mitigation: Publish an enforceable Standardised Scoring Matrix with explicit weights and quantifiable evaluation metrics like minimum domestic compute allocations, verifiable capital expenditure ratios, and non-negotiable minimum passing thresholds prior to reviewing any project applications.

4. Pattern Responsibility: what pattern recognition is assumed but not assigned?

Vulnerability: Assumes speculative queue-squatting and capacity hoarding will be caught, but assigns no clear institutional body to monitor multi-site queuing patterns or enforce milestones. This allows speculative developers to tie up critical headroom, locking out housing and clean industry.

Mitigation: Designate the system operator with an explicit Queue-Monitoring Mandate empowered to enforce non-refundable security deposits, non-transferable queue positions, and strict “use-it-or-lose-it” commercial operation milestones that trigger automatic capacity revocation upon default.

5. Recourse: what mechanisms exist for affected parties³, and are they actually accessible?

Vulnerability: Public input ends at draft consultation; there are no ongoing audit dashboards, accessible dispute mechanisms, or clawbacks if promised jobs and local benefits fail to materialise. This makes host communities vulnerable and leave no formal recourse once irrevocable grid access is granted.

Mitigation: Embed mandatory Conditional Capacity Agreements with contractual clawbacks, dynamic tariff surcharges, and an independent community dispute mechanism that can reduce or revoke allocated megawatt capacity if audit dashboards show promised jobs, investments, or local benefits are not delivered. These are not Memorandums of Understanding (MOUs).

Summary

The Playbook is a good policy promise, but it treats interconnected strains on power, water, land, and community resources as isolated matters divided among separate authorities, with no accountable architecture for the cumulative system. Such fragmented governance produces systemic unaccountability. By instituting transparent carrying-capacity caps, municipal concurrence, and enforceable performance clawbacks, Ontario can transition from discretionary allocations to a resilient, community-supported digital infrastructure policy.

---

1. Cumulative community and environmental impact is out of scope for this governance question.
2. Assigning datacentres to higher static rate classes fails to reduce their continuous 24/7 baseload draw. To address system-peak risks, Ontario’s framework could look to models like PJM and EPRI that pair interconnection with dynamic tariffs, interruptible load requirements, or mandatory peak-load shedding during extreme weather events.
3. The affected parties in this case include all levels of government, the American and Canadian proponents, local, and Ontario’s – especially residents and small businesses.