Organizations make public commitments around water stewardship, community impact, and environmental responsibility. What rarely gets built is the operational infrastructure to honor them. That is the distance The Loregnard Group was founded to close.
The Work
The pledges exist. The sustainability reports are filed. The announcements have been made. What is harder to find is the operational architecture built to back them up: who owns the commitment at the execution level, how it moves through the organization, and what exists when a community, a regulator, or an investor looks closely and asks for the record.
That distance does not surface gradually. It arrives at the worst possible moment. The operators who are not caught in that moment made a different choice earlier.
Every organization that comes into an engagement has something already in place. A sustainability report. A community relations function. Someone responsible for the regulatory conversation. The question is not whether those things exist. It is whether they are connected to each other in a way that closes the distance between what was committed to and what the world outside the organization actually experiences.
The engagement starts with a diagnostic. What is actually in place, what commitments are on record, and where the distance between the two lives. The work that follows is built around what the diagnostic surfaces, not what was assumed in advance.
The methodology is consistent. The context changes. The accountability distance between public commitment and operational reality shows up the same way whether the operator is building a data center or a clean energy facility, whether the market is in North America, the Caribbean, or Africa.
The accountability conversation is happening in boardrooms, at regulatory tables, and on conference stages across multiple continents. The Loregnard Group participates in that conversation actively, bringing the same rigor to a public stage that it brings to a client engagement.
The Loregnard Group was built out of a pattern observed across more than twenty years of building execution infrastructure inside complex, high-stakes environments: commitments made at the leadership level stall before they land, not from carelessness, but because the operational architecture to carry them was never designed. The methodology behind this work was developed and stress-tested across big tech, public higher education, and one of the largest urban school systems in the world.
AI infrastructure accountability is where that work is most consequential right now. The Loregnard Group works with AI data center operators and energy developers building at scale in communities where that distance is creating compounding risk.
The practice operates across the United States, the Caribbean, and Africa.
If you have ever asked AI to help you with something you probably would have paid someone else to handle, welcome to my world. I had AI help me figure out my toddler’s sleep schedule. I used it to build out a workout routine and a skincare regimen. In my mind I was saving money. Why pay for something when I could just ask ChatGPT, or drop it into Claude, or run it through Grok?
Then one day I asked myself a different question. Not about my subscription cost. About the hidden one. Because there is always the fine print, right? I kept seeing jobs posted for data centers. My first thought, honestly, was: data centers? What are those? So I dove in. And I stopped cold.
What I found was not in the headlines we are used to seeing about AI. It was not about privacy or job displacement or whether we are becoming too dependent on machines to think. It was something older and more fundamental than any of that. It was water.
A simple search brought me to the numbers. With that discovery came something unexpected, a quiet embarrassment at how little I had thought to ask. Have I gotten so used to everything being available that I have lost the ability to think about the mechanics behind it? If I am being honest, the answer is yes.
A typical large data center uses up to 5 million gallons of water per day, the equivalent of the daily water supply of a town of 50,000 people. Google consumed approximately 5.6 billion gallons of water in 2023, a 24 percent increase from the prior year, driven largely by AI infrastructure expansion. More than 160 new AI data centers have been built across the United States in the last three years, the majority of them in regions already facing significant water stress. The International Energy Agency’s 2025 Energy and AI report identified water as a critical and underregulated input in AI infrastructure globally, a resource being consumed at scale with almost no visibility to the people whose daily lives depend on it.
There is a feeling I know well. It is the feeling of learning something that was always true, always documented, always available, and realizing that nobody made sure it reached you. The data on AI water consumption is not classified. It is in annual sustainability reports, in municipal permit filings, covered by Bloomberg, Brookings, and the International Energy Agency. It has been there. But it was never designed to reach us.
The companies driving this buildout know exactly what they are consuming. This is not ignorance. It is not incompetence. It is a calculated bet that enthusiasm for AI will outpace the questions nobody is asking yet. That bet has worked before. It is working now. It will stop working the moment the spotlight lands.
Communities have always paid the bill for infrastructure decisions made above them. AI infrastructure is not creating this pattern. It is funding it at scale and at speed. The question of who gets hit next is no longer predictable by geography alone. A farming community watching its groundwater compete with a server cooling system did not see this coming. A suburb that welcomed a data center for the tax revenue is now watching reservoir levels fall.
The bill is always paid by the ones who cannot afford it. Until suddenly the bill is large enough that nobody can afford it. And by then the infrastructure is already in the ground.
The regulatory window to shape what comes next is open right now. The European Union has enacted mandatory water use disclosure requirements for data centers. Singapore is requiring operators to reduce cooling demand. In some markets, legislators passed bills requiring data center operators to report water consumption to local water suppliers, only to see them vetoed after industry lobbying. The bill is gone. The need it was trying to address is not.
Two things can be true at the same time. AI is useful. It has changed how I work, how I access information, how I navigate systems that were not built for people like me. I am not here to argue against it. I am here to argue that the benefits we are experiencing should not come at the exclusive expense of communities that had no seat at the table when the decisions were made.
When I look at my son I know he will grow up in a world I cannot fully fathom. AI will be woven into all of it. That is not something I fear. But readiness requires more than access to the tools. It requires that the infrastructure powering those tools is sustainable enough to still be running when he needs it. The price of progress is high. My son will not have the luxury of not knowing that price.
Let this be your catalyst.
Every engagement starts the same way: a conversation about scope, runway, and timeline. What you are working with, where the distance lives, and what closing it looks like before someone else defines the terms.
The Loregnard Group works with operators and developers in the United States, the Caribbean, and Africa. We look forward to starting a conversation.