Most IT organizations have a sustainability policy. Few have the data to back it up. The policy lives in a PDF somewhere, and the fleet runs on a mix of refresh schedules inherited from previous budget cycles, educated guesses about device age, and energy consumption figures no one has ever actually measured. That delta between stated commitment and operational reality is where most IT carbon reduction programs stall.
Closing it requires three concrete disciplines: measuring what your fleet actually consumes, making hardware refresh decisions based on real device health rather than calendar age, and ensuring end-of-life means recovery and reuse rather than disposal. Each of these is achievable today with the HP Workforce Experience™ Platform (WXP), and each builds on the last.
Why sustainable IT is now a business priority
Sustainable IT has moved from a reporting checkbox to an operational imperative, driven by three converging pressures that IT decision-makers now own directly.
The first is regulatory. The EU’s Corporate Sustainability Reporting Directive (CSRD, Directive EU 2022/2464) requires in-scope companies to report on environmental impacts with verified data, including Scope 3 emissions covering the manufacturing, use, and disposal of IT equipment. Under the EU’s Omnibus I amendments, which entered into force in March 2026, CSRD reporting now applies to companies with more than 1,000 employees and over €450 million in net turnover, a scope cut back from original estimates north of 50,000 companies, but still enough that most large enterprises operating in or selling into the EU need audit-ready, device-level data to support their disclosures. Organizations without reliable fleet telemetry will find it increasingly difficult to produce that data.
The second is cost. Energy draw from endpoint fleets is a real operating expense. A fleet of several thousand devices running inefficient power profiles, or keeping aging hardware at full power through workday hours, carries measurable energy costs that compound annually. Identifying and addressing high-consumption device segments produces direct budget savings, not just carbon credits.
The third is supply chain resilience. Extending device life delays procurement cycles, reducing exposure to component shortages and price volatility in hardware markets. Planned refresh cadences are also easier to budget and execute than reactive replacements triggered by mass hardware failure.
Taken together, these pressures make sustainable IT a business operations discipline, not just a compliance exercise.
How to measure fleet power consumption
Fleet-level energy reporting used to mean extrapolating from manufacturer spec sheets, theoretical maximum draw, with no visibility into actual consumption across power states. Device-level telemetry has changed that.
WXP surfaces actual power consumption through the Sustainability Dashboard.
- Power Consumption Measurement (PCM) uses a dedicated hardware telemetry chip built into the motherboard, capturing power drawn across all device states (active, sleep, shutdown) at roughly 97% accuracy. It’s currently supported on HP G11 commercial platforms running Windows 11 23H2 or later.
- Estimated Consumption (EC) reads BIOS telemetry to model power draw instead, with accuracy that HP documents per device model, generally 70%–89%. EC covers a broader range of hardware without a PCM chip, making it more widely applicable for mixed-generation fleets. Devices supporting neither method are excluded from reporting.
The dashboard presents three views: Power Consumption by Model (a bar chart ranking device families by energy use), Power Consumption by Location (a geographic heatmap surfacing site-level patterns), and a Device Details table with a Power Measurement column flagging whether each reading came from PCM or EC.
The Carbon Footprint report goes further, presenting lifetime device emissions in kg CO₂ equivalent broken across lifecycle stages (manufacturing, distribution, active use, end-of-life) using country-level carbon intensity factors, useful for CSRD-style disclosure because it shows where emissions concentrate.
Start by pulling the kWh trend by model over a 90-day window, sorted by average consumption. In most fleets, a small number of models account for a disproportionate share of energy draw, often older hardware without modern power management, or high-performance configurations in roles that don’t need them. That sorted view becomes your prioritization list for the refresh and lifecycle decisions covered next.
Smarter hardware refresh for a lower carbon footprint
Hardware refresh planning sits at an uncomfortable intersection: replace too early, and you waste the embodied carbon locked into manufacturing; replace too late, and you run aging hardware that draws more energy, fails more often, and drags productivity.
Calendar-based cycles (replace everything at year three or four) are predictable and easy to budget, but imprecise. A two-year-old device might have a degraded battery and thermal issues that make it a genuine liability; a four-year-old device might show clean health metrics and active warranty coverage. A blanket policy treats both the same.
WXP Smart Refresh replaces that calendar logic with telemetry scoring. It calculates a Refresh Urgency Score for every enrolled device and sorts it into Refresh Now, Refresh Soon, or Healthy, weighing:
- Device health: performance degradation, crash frequency, and thermal behavior
- Battery health: meaningful capacity loss, especially once warranty has expired
- Device age: weighted more heavily for older devices showing even minor degradation
- Warranty status: to avoid replacing machines still covered for service
You can run Smart Refresh against predefined strategies, “Experience first (Recommended),” “Cost saving,” or “Performance driven”, or build a custom strategy with precise thresholds, such as replacing devices older than four years, out of warranty, with battery health below a defined threshold.
Before a device reaches Refresh Now, HP Device Life Extension (DLE) Services, available as a Care Pack, offers a structured intervention: battery replacement (when full-charge capacity drops to 90% or below), a memory upgrade of up to 8GB, and a refresh of BIOS, firmware, drivers, and the platform image. Avoiding new manufacturing sidesteps the emissions stage that accounts for the largest share of a device’s lifecycle carbon, Our own data shows that extending an average PC’s lifecycle by two years delivers a 30% lower carbon footprint than buying new.
Together, Smart Refresh and DLE turn refresh planning into a continuous discipline: extend what’s viable, replace what isn’t, and let telemetry justify the call.
Responsible asset disposition and circular IT
The third pillar often gets the least attention because it falls at the end of the visible ownership period. A device exits the fleet and, too often, the sustainability story ends there—whether it reaches a certified recycler, sits in a storage closet, or enters an uncontrolled disposal channel, it often goes untracked.
Our approach to the device lifecycle is built around five circular economy principles:
- Design circular products, services, and solutions
- Use recycled and renewable materials, giving materials a second life and expanding lower-impact sourcing
- Manufacture in ways that consider people and the planet
- Repair, refurbish, and reuse, extending product life and capturing more value
- Recycle products and components to establish a circular loop
The Device-as-a-Service (DaaS) model operationalizes these at scale. Every device is tracked through provisioning, active use, health monitoring, and end-of-life return, so retired devices enter a controlled recovery path rather than disappearing from the asset register. WXP visibility runs throughout, tracking health, battery wear, and thermals to prevent premature decommissioning and generate carbon avoidance data for Scope 3 reporting.
For organizations managing the refresh cycles covered in the previous section, DaaS creates a natural handoff: devices Smart Refresh flags as end-of-life feed into HP’s Asset Recovery Services, where certified data sanitization (aligned to ISO 27001, NIST 800-88, and other recognized global standards) and material recovery happen under documented chain of custody, producing defensible disposition records for audit and regulatory reporting.
The circular model also surfaces value linear disposal misses: refurbished devices carry residual market value that offsets procurement costs, and hardware that can’t be refurbished gets smelted and granulated, with recovered materials feeding back into HP’s manufacturing supply chain instead of landfill.
Continuity of tracking is what makes this work, the sustainability gains only show up in your reporting if end-of-life assets move through a documented, certified process.
Frequently asked questions
What is sustainable IT?
Sustainable IT is the practice of reducing the environmental impact of IT operations across the full device lifecycle, from how devices consume energy during active use to how refresh cycles are planned to avoid premature replacement of viable hardware, and how end-of-life assets are recovered and returned to productive use. A procurement decision that favors energy-efficient hardware is one input, and sustainable IT operations is the ongoing discipline that determines whether that hardware is actually managed in a way that delivers lower environmental impact over time.
How do I measure my organization’s IT carbon footprint?
Fleet-level carbon measurement starts with device telemetry. Hardware-based measurement (PCM) captures actual power draw across all device states at roughly 97% accuracy against true electrical consumption, on HP G11 commercial platforms running Windows 11 23H2 or later. BIOS-based software estimation (EC) extends coverage to a broader range of devices, with accuracy that HP documents per device model, generally in the 70%–89% range. Both methods feed sustainability reports in the HP Workforce Experience™ Platform (WXP).
What is the difference between green hardware and sustainable IT operations?
Green hardware is a procurement decision, choosing devices built with recycled materials, Energy Star certification, or lower-wattage components. Sustainable IT operations is an ongoing discipline that determines what actually happens after those devices are deployed. It covers how energy-management settings are configured and enforced across the fleet, whether refresh cycles are driven by real device health or arbitrary timelines, whether life-extension services are applied to viable hardware before retirement, and whether end-of-life assets move through certified recovery channels.
A fleet of energy-efficient hardware managed with ad-hoc refresh cycles and informal disposal practices will underperform a mixed-generation fleet managed with continuous telemetry, planned lifecycle extension, and documented asset recovery. The hardware decision is one input, and operational discipline compounds it into measurable reductions over time.
How does device lifecycle management reduce IT’s environmental impact?
Device lifecycle management reduces environmental impact by delaying the embodied carbon payback period and replacing reactive action with planned action. Every device carries manufacturing-stage emissions, the carbon cost of raw material extraction, fabrication, and logistics before the device ever reaches a user. Extending a device’s active life delays when those emissions must be incurred again for a replacement unit: HP’s own data shows a 30% lower carbon footprint for an average PC when its lifecycle is extended by two years, compared with buying new.
WXP makes planned lifecycle management operationally practical by surfacing health, battery, age, and warranty data that show which devices genuinely need replacement, which can be extended through DLE services, and which are performing well enough to remain in service without intervention. That data-driven approach converts lifecycle management from a theoretical best practice into a measurable reduction in both carbon output and IT operating costs.
What is the difference between PCM and EC power measurement?
Power Consumption Measurement (PCM) uses a dedicated hardware telemetry chip on the device motherboard to capture actual power draw across all states, at roughly 97% accuracy against true electrical consumption. Estimated Consumption (EC) reads BIOS telemetry to model power draw, with accuracy that HP documents per device model, generally in the 70%–89% range. PCM applies to HP G11 commercial platforms running Windows 11 23H2 or later, while EC covers a broader range of HP hardware, making it the more widely applicable method for mixed-generation fleets.
How does the DaaS model support Scope 3 emissions reporting?
Under the Device-as-a-Service model, every device is tracked through its full lifecycle, from provisioning to end-of-life return, so retired devices enter a controlled recovery path with a documented chain of custody. HP’s Asset Recovery Services provides certified data sanitization aligned to ISO 27001, NIST 800-88, and other recognized global standards, and the resulting disposition records are audit-ready for Scope 3 regulatory reporting. Fleet visibility through WXP runs continuously throughout that cycle, generating carbon-avoidance data that connects operational decisions to reportable emission reductions.
How do I prioritize which devices to refresh first for carbon impact?
Pull the kWh trend by model over a 90-day window in the WXP Sustainability Dashboard and sort by average consumption. In most fleets, a few device models account for a disproportionate share of energy draw, often older hardware without modern power management or high-performance configurations deployed to roles that don’t need them. That sorted view, combined with WXP Smart Refresh telemetry scoring across device health, battery health, age, and warranty status, gives you a prioritization list where the highest-consuming and lowest-health devices surface together as the clearest candidates for replacement or DLE intervention.
How to activate fleet energy tracking this week
Deploying the WXP Insights Agent to your existing fleet gives you a defensible kWh and carbon baseline within a single synchronization cycle.
For large fleets, deploy via SCCM or Group Policy, both install a small chain of prerequisites (the Visual C++ Redistributable and two supporting Analytics components) ahead of the main WXP Insights installer, with your tenant’s Company PIN (CPIN) passed as a parameter so devices enroll automatically. For smaller deployments or a pilot test, one command, WXPInsights.exe /silent CPIN=YOUR_COMPANY_PIN HIDETRAY=True, installs it silently on a single machine.
The dashboard populates within a daily sync cycle. Set your date range to 90 days for a meaningful baseline rather than a single day’s snapshot, and segment by device model first, then location, the model view shows which hardware families to prioritize for Smart Refresh, while the location view flags sites diverging from the fleet average.
That baseline is the starting point for every initiative that follows: refresh decisions, lifecycle extensions, and disposition programs all need a measurable outcome to connect to.
Final thoughts on sustainable IT
Closing the gap between a sustainability policy and a fleet’s actual environmental impact comes down to three disciplines: measure what your devices actually consume, make refresh decisions from device health data rather than the calendar, and route every retired asset through a certified, trackable recovery path. None of these pay off as a one-time audit. The organizations seeing real reductions are the ones treating measurement as continuous, re-running Smart Refresh scoring and carbon reporting on a regular cadence so each decision compounds on the last.
