Challenge
Turning utility data into actionable carbon insights
CarbonHub, a standalone enterprise SaaS platform for complete, organization-wide carbon accounting that integrates seamlessly with EnergyCAP.
Role: UI/UX Designer
Team: 2 UX Designers, PM, Engineering Leads, 1 SME
Tools: Figma, Miro, Maze
Organizations needed a centralized and flexible system to track all emissions.. EnergyCAP’s existing workflows supported utility-driven scope 1 and 2 emissions but offered no way to manage additional emissions types (such as purchased goods and services, business travel, and employee commuting) or create custom reporting structures. As a result, many organizations relied on spreadsheets or external tools, creating fragmented workflows, inconsistent reporting, and a lack of visibility across their full emissions picture.
Structure
CarbonHub required a clear structural model. We defined how emissions should be grouped, stored, and reported based on industry standards and EnergyCAP's data model. We mapped emissions to familiar concepts, such as treating sources like meters and records like bills, which allowed us to build something new without abandoning patterns users already understood.
We defined 3 core objects for CarbonHub:
Collections - These group emissions sources and represent buildings, departments, or areas within a campus. Collections can also be nested to support hierarchical reporting structures.
Emissions Sources - These represent the entities that generate emissions, such as utility meters, EV chargers, or employee commuting. They serve as the connection point between activity data and emissions calculations. Meters in EnergyCAP could be linked directly to emissions sources in CarbonHub so that whenever a meter receives a new bill, CarbonHub can automatically generate a corresponding record.
Records - These represent each individual log or instance of emissions generated from a source. Records are foundation data the feed reporting analytics.
Solution
CarbonHub introduced a flexible hierarchy built around Collections, Sources, and Records, allowing organizations to create structures that fit their reporting needs rather than forcing them into a facility-based model. Users could manually enter emissions data or supplement EnergyCAP-generated emissions, enabling them to account for all emissions types, including those not associated with utility usage. The interface followed familiar EnergyCAP patterns, such as hierarchical navigation and object-based workflows, while incorporating modern visual elements and widgets designed specifically for emissions reporting. Integration with EnergyCAP allowed utility-based emissions to flow in automatically while still enabling CarbonHub to stand on its own.
