How Data Center Projects Adapt to Utility Conflicts

When data center developers also serve as utilities, structural tension is baked into the business model. The question isn't whether conflicts of interest exist — it's whether the industry has found a workable way to manage them.

For now, the answer appears to be geographic separation. Firms are steering data center projects outside the service territories of their utility clients, creating enough physical distance to sidestep the most obvious conflicts. It's a pragmatic solution, but it raises deeper questions about how long this approach can hold as data center demand continues to accelerate and suitable sites become harder to find.

The Conflict Hiding in Plain Sight

Data centers and utilities are deeply interdependent. A hyperscale facility can draw 100 to 500 megawatts of power — equivalent to the load of tens of thousands of homes — and that demand lands directly on the utility serving the region. When the same advisory or development firm has financial relationships with both the data center operator and the local utility, the potential for compromised decision-making is real.

The core tension: a firm advising a utility on grid capacity planning shouldn't simultaneously be developing a massive new load that stresses the same grid.

This isn't hypothetical. As energy infrastructure firms have diversified into data center development, overlapping client relationships have multiplied. A utility client might rely on a firm's grid planning expertise while that same firm is quietly acquiring land and negotiating interconnection agreements for a competing load project nearby. Whether decisions are made transparently or not, the appearance of conflict is enough to create regulatory and reputational risk.

The utility service area becomes the fault line. Step outside it, and the most direct conflicts dissolve — at least on paper.

Steering Around the Service Territory

The primary strategy firms are using is location arbitrage: site data centers in regions where their utility clients don't operate. It sounds simple, and in principle, it is. But execution is considerably more complex.

Data center siting is never just about avoiding conflicts. Sites need access to fiber routes, proximity to demand centers, available water for cooling, and — most critically — transmission infrastructure capable of delivering power at scale. Finding a location that checks all those boxes *and* sits outside a utility client's footprint requires a sophisticated site selection process.

What looks like a conflict-avoidance strategy is also, by necessity, a rigorous infrastructure due diligence exercise.

Some regions have emerged as natural beneficiaries of this dynamic. Markets like the Carolinas, parts of the Midwest, and certain Texas submarkets have attracted data center investment partly because they offer grid capacity and available land without the territorial complications that plague more developed markets like Northern Virginia or Phoenix. For developers navigating client conflicts, these secondary markets offer a clean slate — no overlapping relationships, no awkward disclosures.

The insider reality: many firms have quietly built internal firewalls between their utility advisory practices and their infrastructure development teams. These aren't just ethical guardrails — they're business necessities, because a single high-profile conflict allegation can unwind years of client trust on both sides of the business.

Where Location Strategy Gets Complicated

The geographic separation approach works until it doesn't. Several pressures are already testing its limits.

First, the sheer scale of data center development means the industry is running out of easy locations. The top-tier markets are constrained, and firms are increasingly looking at areas where their utility relationships are harder to avoid. As the map of viable data center sites shrinks, the overlap with utility client territories grows.

Second, interconnection queues are backlogged across the country. The average wait time for large load interconnection has stretched to four years or more in some regions. That timeline pressure pushes developers to pursue sites in markets where they already have relationships and local knowledge — which often means utility client territory.

Third, states are getting more sophisticated about scrutinizing energy infrastructure conflicts. Regulatory bodies in several states have begun examining whether development firms are adequately disclosing their multiple roles in energy markets. The informal geographic workaround that's functioned reasonably well in a less-regulated environment may face more formal scrutiny as data center power demand becomes a mainstream policy issue.

What Successful Developments Actually Look Like

The projects that have navigated these dynamics most cleanly share a few characteristics. They were sited early — before interconnection queues became severe — in markets where the developer had no active utility advisory relationships. They secured power through bilateral agreements with generators or through direct participation in wholesale markets, reducing dependence on a single utility's cooperation. And they were transparent with all parties about the developer's business relationships.

The Midwest has seen several examples of this approach working well. Data center campuses in rural Ohio, Indiana, and Illinois have been developed by firms that deliberately chose those markets to avoid conflicts with utility clients concentrated in mid-Atlantic and Southeast territories. The sites offer reasonable power costs, available land, and transmission access — and they come with clean conflict disclosures.

What's notable is that geographic separation, done right, isn't just conflict avoidance. It's also genuine value creation. Secondary data center markets benefit from the investment, utilities in those regions gain significant new load that supports rate base growth, and developers build relationships that don't carry the baggage of conflicted advisory roles.

Where This Heads Next

The geographic separation strategy buys time, but it isn't a permanent solution. Three developments will reshape how the industry handles data center utility conflicts over the next several years.

Regulatory formalization is coming. The current approach relies heavily on informal norms and voluntary disclosure. As data centers become central to state energy planning conversations, regulators will almost certainly impose more explicit requirements around conflict disclosure and management. Firms that have built robust internal processes will be better positioned than those that have relied on geographic distance alone.

Technology is changing the siting calculus. Advances in long-distance high-voltage direct current transmission, combined with the growth of offshore wind and remote solar resources, are expanding the viable power supply options for data centers. A facility no longer has to be sited near existing transmission infrastructure if new transmission can bring renewable power from remote generation. This could paradoxically open more locations — or it could deepen conflicts if firms are developing both the generation assets and the data center loads in the same regional footprint.

Consolidation will create new conflict vectors. As the infrastructure development industry consolidates, the largest firms will inevitably accumulate utility relationships that span multiple service territories. The strategy of simply stepping outside a client's footprint becomes harder to execute when your client list covers a significant portion of the national grid.

The firms that will handle this best aren't just the ones with the most disciplined geographic strategies today. They're the ones building genuine institutional separation between their utility advisory and infrastructure development functions — the kind that can withstand regulatory scrutiny, not just informal review.

For any stakeholder in data center development or utility infrastructure, the practical takeaway is this: treat conflict management as a structural business design problem, not a case-by-case judgment call. The developers and advisors who formalize their firewalls, disclose proactively, and build site selection processes that account for relationship geography won't just avoid problems — they'll be the ones that earn the trust to operate at scale when the market gets more crowded and the regulatory environment gets tighter.

Geographic separation is the right instinct. But instincts need to become systems.

Explore more about data center projects and utility conflicts on InfraSale Marketplace.

[INTERNAL LINK: data center development]

[INTERNAL LINK: utility infrastructure]

[INTERNAL LINK: conflict management strategies]