Why sustainability matters for software and IT companies
Software and IT services have long been perceived as “clean” industries. There are no smokestacks, no heavy machinery, and no visible waste streams. Yet the sector’s environmental footprint is substantial and growing. Data centers alone account for roughly 1.5% of global electricity consumption, and that figure is projected to rise as demand for cloud computing, AI workloads, and digital services accelerates. For IT companies subject to the Corporate Sustainability Reporting Directive (CSRD), understanding where emissions originate and how to measure them is now a regulatory obligation, not just a reputational choice.
The CSRD requires large EU companies and listed SMEs to report under the European Sustainability Reporting Standards (ESRS). Many software firms meet the size thresholds, especially those with 250 or more employees or significant EU revenue. Even companies below the thresholds face indirect pressure from enterprise customers who need Scope 3 supplier data for their own CSRD disclosures. This guide walks through the main emission sources, compliance requirements, and practical strategies for IT companies preparing their sustainability reporting.
Cloud infrastructure and data center emissions
For most SaaS and IT services companies, cloud infrastructure represents the single largest source of carbon emissions. These emissions fall into different GHG Protocol scopes depending on the company’s operating model.
Scope 2 (purchased electricity): Companies that operate their own data centers report the electricity consumed as Scope 2 emissions. The carbon intensity depends heavily on the energy grid where the facility is located. A data center running on the Nordic grid (high renewable share) produces significantly fewer emissions per kilowatt-hour than one on a coal-heavy grid.
Scope 3 (cloud services): Companies that rely on cloud providers such as AWS, Azure, or Google Cloud report those emissions under Scope 3, Category 1 (purchased goods and services). All three major hyperscalers publish carbon reporting tools, but methodologies differ. AWS provides customer-level carbon footprint reports, Google Cloud operates on 100% renewable energy matching, and Azure offers a sustainability calculator. Reconciling these different approaches into a single, auditable Scope 3 figure requires careful methodology alignment.
Key metrics to track:
- Total energy consumption (kWh) by data center or cloud region
- Power Usage Effectiveness (PUE) for owned facilities
- Carbon intensity per unit of compute (tCO2e per server-hour or per transaction)
- Renewable energy percentage across all infrastructure
Dcycle’s automated data collection integrates with cloud provider APIs and energy management systems to consolidate these metrics into a single reporting platform, reducing manual data gathering and reconciliation effort.
Employee-related emissions and remote work
Software companies are typically people-intensive businesses. Employee-related emissions often represent the second largest category after cloud infrastructure, particularly for companies with large engineering teams distributed across multiple offices and remote locations.
Commuting and business travel
Employee commuting falls under Scope 3, Category 7. For companies with office-based teams, commuting surveys and transport mode data are necessary to calculate this category. Business travel (Category 6) adds flights, rail, and hotel stays. Many IT companies reduced business travel significantly during the pandemic, but levels have partially recovered, especially for sales teams and customer-facing roles.
Remote work considerations
Remote work shifts commuting emissions to household energy consumption, which falls under Scope 3, Category 7 as well. Measuring this requires estimating the additional energy employees use at home for heating, cooling, lighting, and equipment. Several methodologies exist, including the EcoAct homeworking emission factors and the UK Government’s enhanced capital allowance approach. The choice of methodology affects the final figure substantially, so consistency across reporting periods is essential.
Office operations
Office buildings contribute through electricity (Scope 2), heating and cooling (Scope 1 or 2 depending on the energy source), water consumption, and waste generation. For multi-tenant buildings, allocation methods based on floor area or headcount are typically used. Companies should also account for office equipment, furniture procurement, and IT hardware deployed on-premises.
Hardware lifecycle and electronic waste
IT companies purchase significant volumes of hardware: laptops, monitors, servers, networking equipment, and peripherals. The embodied carbon in these devices, meaning the emissions generated during manufacturing and transport, falls under Scope 3, Category 2 (capital goods) or Category 1 (purchased goods and services), depending on accounting treatment.
E-waste management is an increasingly scrutinized topic under ESRS E5 (Resource use and circular economy). Companies should track:
- Total hardware purchased by category and weight
- Average device lifespan and refresh cycles
- Percentage of devices refurbished, recycled, or sent to certified e-waste processors
- Data destruction and security compliance alongside environmental disposal
Extending hardware refresh cycles from three to five years, adopting refurbished equipment programs, and partnering with certified recyclers are practical steps that reduce both costs and environmental impact.
CSRD applicability and reporting requirements
The CSRD applies to software and IT companies that meet the standard size thresholds: more than 250 employees, more than EUR 50 million in net turnover, or more than EUR 25 million in total assets (two of three criteria). Following the Omnibus simplification proposals, some thresholds may be adjusted, but the core obligation remains for large companies.
Material ESRS topics typically relevant for IT companies include:
- ESRS E1 (Climate change): Scope 1, 2, and 3 emissions, transition plans, and climate risk scenarios.
- ESRS E3 (Water and marine resources): Relevant for companies operating water-cooled data centers.
- ESRS E5 (Circular economy): Hardware lifecycle, e-waste, and resource efficiency.
- ESRS S1 (Own workforce): Employee wellbeing, diversity, and working conditions, a priority for talent-competitive tech companies.
- ESRS G1 (Business conduct): Data privacy, cybersecurity governance, and ethical AI.
The CSRD resource hub provides detailed guidance on conducting materiality assessments and preparing disclosure documents for each ESRS topic.
Green software engineering practices
Beyond measurement and reporting, IT companies have a unique lever: they can reduce emissions by writing more efficient software. The Green Software Foundation’s Software Carbon Intensity (SCI) specification provides a framework for measuring the carbon impact of software applications.
Practical strategies include:
- Efficient architecture design: Choosing serverless or auto-scaling architectures that scale down during low-demand periods, avoiding always-on infrastructure that wastes energy during idle hours.
- Carbon-aware computing: Scheduling batch jobs, CI/CD pipelines, and non-urgent workloads during hours when the grid’s carbon intensity is lowest.
- Code optimization: Reducing unnecessary computation, optimizing database queries, and minimizing data transfer. Small improvements at scale can translate to meaningful energy savings.
- Right-sizing cloud resources: Regularly reviewing and adjusting virtual machine sizes, storage tiers, and reserved capacity to match actual usage patterns.
- Demand shaping: Designing user experiences that reduce energy consumption, such as dark mode interfaces, compressed media, and lazy loading.
These practices align business objectives (cost reduction) with environmental goals (lower emissions), making them easier to justify and sustain.
Practical strategies for reducing your IT carbon footprint
Software and IT companies can take several concrete steps to lower their environmental impact:
Cloud provider selection: Evaluate providers based on their renewable energy commitments, PUE ratings, and carbon reporting transparency. Consider multi-cloud strategies that route workloads to the greenest available regions.
Office optimization: Implement smart building controls for HVAC and lighting, switch to renewable energy contracts where available, and establish waste separation and recycling programs.
Supply chain engagement: Request carbon data from key suppliers, set procurement criteria that include environmental performance, and participate in industry initiatives like the Science Based Targets initiative (SBTi).
Employee engagement: Provide incentives for low-carbon commuting (cycling, public transport, electric vehicles), support remote work policies, and educate teams on sustainable practices.
Dcycle’s carbon footprint tracking platform helps IT companies consolidate data from cloud providers, office systems, travel platforms, and procurement records into a unified dashboard. This gives sustainability teams and CFOs a clear view of where emissions originate and where reduction efforts will have the greatest impact.
How Dcycle helps IT companies measure and report
Dcycle’s platform is purpose-built for companies navigating complex sustainability reporting requirements. For software and IT companies, the platform offers:
- Cloud emission tracking: Automated integration with major cloud providers to capture compute, storage, and networking energy consumption.
- Multi-scope consolidation: Combine Scope 1 (office heating), Scope 2 (electricity), and Scope 3 (cloud, commuting, travel, hardware) into a single auditable dataset.
- CSRD-aligned reporting: Pre-built templates aligned with ESRS disclosure requirements, including E1, E5, S1, and G1 topics.
- Audit-ready evidence: Full traceability from raw data to reported figures, with version control and approval workflows.
Request a demo to see how Dcycle can help your IT company build a robust sustainability measurement and reporting infrastructure.
Frequently asked questions
What are the main emission sources for SaaS companies?
For most SaaS companies, the largest emission source is cloud infrastructure (Scope 3, Category 1 if using a cloud provider, or Scope 2 if operating owned data centers). Employee commuting and business travel typically follow as the second and third largest categories. Hardware procurement, office operations, and upstream supply chain activities make up the remainder.
Does the CSRD apply to technology companies?
Yes. The CSRD applies to any EU company that meets the size thresholds (250+ employees, EUR 50M+ turnover, or EUR 25M+ assets, meeting two of three). Many mid-to-large software companies qualify. Non-EU tech companies with significant EU operations may also be in scope. Even smaller companies face indirect requirements through enterprise customer supply chain requests.
How do you measure cloud computing emissions?
Cloud emissions are measured using provider-specific carbon reporting tools (AWS Customer Carbon Footprint, Google Cloud Carbon Footprint, Azure Emissions Impact Dashboard) combined with energy consumption data and regional grid emission factors. For accurate Scope 3 reporting, companies should reconcile provider data with the GHG Protocol’s Scope 3 Category 1 methodology and document any estimation assumptions used.
