ESG and IT projects: Why sustainability is becoming a project management responsibility in hospitality

There is a version of the ESG (Environmental, Social and Governance) conversation that belongs entirely to the C-suite. Net-zero commitments, sustainability reports, investor disclosures, and board-level governance structures. That conversation is real and important. But it is increasingly distant from the people who actually deliver the technology projects that determine whether any of those commitments get met.
In hospitality, IT projects touch almost every dimension of a hotel's environmental and social footprint. The systems that manage energy consumption, the platforms that track water usage, the infrastructure decisions that determine how much hardware gets replaced and how often, the procurement processes that choose between local and global cloud providers. These are project management decisions, not just sustainability policy decisions. And in most hotel groups, nobody has connected those two things.
This article argues that ESG is no longer something that happens above the project level. It is something that project managers in hospitality IT need to build into the way they scope, plan, and deliver work. Not as a compliance exercise. As a design principle.

The hotel industry is one of the more energy-intensive sectors in the global economy. A large resort consumes significant quantities of electricity, water, and gas every single day. Guests expect heating, cooling, lighting, laundry, food service, and connectivity at standards that are difficult to deliver with a low environmental footprint. That is the operational reality.
What makes this directly relevant to IT project managers is that the systems used to manage these resources are technology systems. Building management platforms, energy monitoring tools, smart room controls, and utility dashboards are all IT infrastructure decisions. When a hotel group decides to upgrade its building management system, that is a project. When it chooses a cloud provider for ist central reservation platform, that is a project. The ESG implications of those decisions are real, measurable, and often ignored because the person running the project is focused on scope, budget, and timeline, not kilowatt hours or carbon reporting.
Beyond the environmental dimension, hospitality also has significant social obligations. Staff welfare, fair labour practices, supply chain transparency, and community impact are all ESG considerations that intersect with technology decisions. Workforce management systems, payroll platforms, and procurement tools all carry social consequences depending on how they are configured and who governs them. Project managers are often the last people to think about this, and the first people whose decisions make it concrete.

Most project charters in hospitality IT define success in terms of system functionality, go-live date, and budget adherence. Few include any reference to the environmental or social outcomes the project is expected to support. This is where the gap starts.
Adding ESG considerations to scope does not require a separate workstream or a specialist resource. It requires asking a small number of additional questions at project initiation. What is the expected energy consumption of the new infrastructure, and how does it compare to what it replaces? Does the chosen vendor have a published sustainability policy? Are there configuration choices that affect resource usage, and has anyone evaluated them? Will the project create or eliminate any roles, and how is that being managed?
These are not complicated questions. They are just questions that nobody currently asks because they are not on the standard checklist. Adding them to the project charter is a straightforward change with meaningful consequences.

Technology procurement in hotel groups is generally driven by two criteria: cost and functionality. Sustainability credentials are rarely evaluated, and when they are, they tend to be treated as a tiebreaker rather than a genuine selection factor.
This is changing, partly because corporate travel buyers and institutional investors are starting to ask hotels about their supply chain ESG practices, and partly because regulation in several major markets is beginning to require more transparency about procurement decisions. Project managers who control vendor selection have an opportunity to build sustainability criteria into evaluation scorecards now, before it becomes a compliance obligation.
In practice this means asking vendors for data on their own carbon footprint, their approach to data centre energy efficiency, their hardware recycling policies, and their labour practices in service delivery. Most reputable technology vendors now publish this information. The problem is that hotel IT project managers rarely ask for it.

Hardware refresh cycles, data centre choices, network infrastructure decisions, and server procurement all have environmental implications that extend well beyond the project timeline. A decision made in a three-month project can have consequences that run for five to ten years.
Cloud migration projects are a good example. Moving workloads from on-premise servers to a cloud provider can significantly reduce a hotel group's direct carbon footprint, but only if the cloud provider is operating on renewable energy and the migration is designed to eliminate rather than replicate existing infrastructure. In practice, many cloud migrations end up adding cloud costs on top of existing on-premise costs rather than replacing them, which worsens both the financial and environmental position.
Project managers who understand this dynamic can push for infrastructure decisions that are evaluated over their full lifecycle rather than just their upfront cost. This is not a technical skill. It is a governance habit.

The social dimension of ESG is the one that project managers in hospitality IT are most likely to affect directly, and least likely to think about explicitly. Technology projects change jobs. They eliminate some tasks, create others, and restructure workflows in ways that have real consequences for the people doing the work.
A new property management system that automates the night audit function does not just improve efficiency. It changes what the night audit team does. A mobile check-in platform that reduces front desk interactions does not just improve the guest experience. It affects what front desk roles look like over time. These are not reasons to avoid technology change. They are reasons to plan it responsibly, which means including workforce impact assessment in the project scope and designing transition support for the people most affected.

One of the genuine difficulties with ESG integration in IT projects is measurement. Energy consumption, carbon emissions, water usage, and social impact are not naturally produced as outputs of a standard project management process. They require data collection systems that most hotel IT teams do not currently have in place.
This does not mean the problem is unsolvable. It means the measurement infrastructure needs to be built, and IT project managers are well placed to build it. Energy monitoring integrations, utility dashboard implementations, and sustainability reporting tools are all IT projects. The irony is that the systems needed to measure ESG performance are themselves the kind of technology investments that require good project management to deliver.
A practical starting point is to identify, for each significant IT project, the two or three sustainability metrics that are most directly affected and to define a baseline and a goal before the project begins. This does not need to be precise to be useful. A rough estimate of current energy consumption for a system being replaced, compared to the expected consumption of its replacement, is more information than most hotel groups currently have.

For IT project managers and technology leaders in hospitality who want to start integrating ESG into their project practice, the following three steps offer a grounded entry point:

• Add an ESG impact section to your standard project charter template. It does not need to be long. Three questions are enough to start: What is the expected environmental impact of this project compared to the current state? Does the primary vendor have published sustainability commitments? Will this project affect any staff roles, and how is that being managed?
• Include sustainability criteria in vendor evaluation scorecards. Assign a weighting, even a small one, to vendor ESG credentials in technology procurement decisions. The act of asking for this information signals to the market that it matters, and it creates a record of due diligence that is increasingly relevant for corporate reporting purposes.
• Build post-implementation ESG review into your lessons-learned process. At project close-out, capture whether the sustainability outcomes defined at initiation were achieved. If they were not, document why. This creates the institutional memory that allows ESG practice to improve over time rather than starting from scratch on every project.

ESG is not a distraction from project management. It is an extension of it. The skills required to integrate sustainability considerations into a technology project are exactly the skills project managers already have: scoping, risk assessment, stakeholder engagement, and outcome measurement. The only thing missing is the habit of applying those skills to a wider set of questions than the ones currently on the checklist.
In hospitality, where the operational footprint is large, the technology dependency is growing, and the pressure from guests, investors, and regulators is increasing, that habit needs to develop quickly. The project managers who develop it first will not just be delivering more responsible projects. They will be delivering more credible ones.
The next time a hotel group launches a technology project, the sustainability question is worth asking at the start. Not because it is required. Because the answer will affect the outcome in ways that matter, and those ways are easier to manage if they are part of the plan from day one rather than an afterthought at close.