Some sites have submitted data; some sources are still missing
Check expected activities by site and month, with an identified owner. Distinguish missing submissions from activities with genuine zero use.
Carbon Footprint for Organization (CFO)
For people coordinating GHG inventories across manufacturing sites
Consolidate site emissions dataCheck coverage before reporting
Organize activity records and evidence by site, track missing sources and trace relevant Scope 1, 2 and 3 totals. Prepare an organizational inventory within an agreed reporting boundary.
Click the image to open the sample system
This is a browser-based prototype with local changes, fictional data and emission factors, and simulated user roles. Reports have not been independently verified.
Sample application
Track missing data and review records before consolidation
Select a site and month in a fictional five-site packaging company. Inspect data gaps, enter and submit records for review, then open the reporting package to check boundaries and unresolved issues.
Distinguish missing data from zero
Review evidence and request corrections
Inspect issues that affect report readiness
Identify missing data before consolidating totals
Figures are available, but their sources are unclear
Keep quantities, units, document references, evidence and calculation factors with each record so reviewers can trace the inputs.
Submitted records are approved, but the inventory still has gaps
Review data coverage alongside internal approval status and reasons for exclusions before using the consolidated total in a report.
Organizational carbon inventory workflow
From activity data to a traceable reporting package
Define the boundary, assign data owners and review the inventory before reporting.
Start with existing records
Bills and invoicesCSV filesActivity records
ERP and IoT are optional data sources. Integration scope must be agreed separately.
- 01
Set the boundary
and reporting periodIdentify the organization, sites and emission sources included.
- Responsible role
- CFO reporting team
- Output
- Boundary and reporting period
- 02
Define data needs
and ownersSpecify the data needed and who provides it for each source.
- Responsible role
- CFO coordinator
- Output
- Data checklist with named owners
- 03
Collect activity data
and evidenceRecord quantities, units, dates and supporting documents.
- Responsible role
- Data owners
- Output
- Activity records and evidence
- 04
Calculate with
traceable factorsLink activity data to formulas and emission factor sources.
- Responsible role
- GHG inventory preparer
- Output
- Calculations and source references
- 05
Review the inventory
internallyCheck completeness, then approve or return records for correction.
- Responsible role
- Internal reviewers
- Output
- Reviewed or returned records
- 06
Assemble the
reporting packageBring calculations and evidence together for external verification.
- Responsible role
- CFO coordinator
- Output
- Reports with supporting evidence
EF means emission factor per unit of activity. This diagram describes a workflow; it does not guarantee verification outcomes.
DATA TRACEABILITY
Trace a total back to its source record
One record shows why quantity, units, reporting period and the emission factor must be checked together before consolidation.
Fictional demo example, not a customer result or an official emission factor.
ACT-1-006Sample data
- Site / period
- Main factory · January 2026
- Activity / unit
- Purchased grid electricity · kWh
- Document reference
- DOC-1-006
- Factor version
- DEMO-1.0 · Fictional
100,000kWh
×0.500kgCO₂e / kWh
=50.000tCO₂e
The result, 50,000 kgCO₂e, converts to 50.000 tCO₂e. Approving this record does not establish that the reporting period is complete.
Start with existing data. Connect where it helps.
Traceable data matters regardless of how it reaches the system. Choose collection methods by emission source, frequency and organizational readiness.
Start with existing records
Use energy bills, fuel logs, waste weigh tickets and procurement records. Identify the source, unit, period and data owner. The demo supports manual entry, CSV import and evidence attachments.
Available in the demoConnect business systems as volume grows
Assess data from ERP, accounting, procurement, logistics or suppliers. Agree data mapping, import frequency and duplicate checks before implementing a connection.
Assess and implement per projectUse IoT where frequent readings are useful
Assess electricity or fuel inputs from metering systems. Define checks for periods, coverage and duplicate counting before implementing the connection. IoT is not required to start CFO accounting.
Optional; implemented per projectCalculation boundaries must reflect actual operations
Start with organizational activities and reporting objectives, then select suitable methods and evidence. Sample data in each scope do not establish coverage of every factory emission source.
Scope 1: Direct emissions
Examples include fuel used by equipment or vehicles within the organizational boundary and refrigerant leakage. Identify actual sources and activity data.
Scope 2: Purchased energy
Examples include purchased electricity, steam, heat and cooling. The demo uses location-based reporting with fictional factors.
Scope 3: Other value-chain activities
Screen 15 categories for relevance, significance and reasons. The demo calculates selected sample activities, not every method in every category.
Define implementation around your data and working process
Before deployment, DigitechX will assess required data, responsibilities, review steps and reporting outputs to define a system and development scope that can be tested.
Review one reporting period
Use the site list, activity sources, sample files and reporting objective to identify existing data and collection gaps.
Specify the system and responsibilities
Agree the shared database, access permissions, evidence storage and backup, import methods and necessary integrations.
Test before use in actual reporting
Check calculations, applicable factors, boundaries, coverage and exports with the responsible staff. Define independent verification separately from system implementation.
ERP/IoT connections, a shared database and real user authentication are not part of the current demo. They require assessment and implementation within the project scope.
Questions before starting a project
Do we need IoT or a new ERP system first?
No. Start with activity records and evidence such as bills, documents and CSV files. If particular sources need frequent collection or substantial repeated work, assess existing-system or device integration against its value and cost.
What should each site submit, and who owns the data?
Identify sources within the boundary, such as energy, fuel, refrigerants, transport or waste, then assign the actual owner of each source. Inventory coordination and review may be separate responsibilities; department names need not be the same across factories.
If all submitted records are approved, is the inventory complete?
Not necessarily. Check the expected sources, sites and reporting periods as well. A source with no submission must remain visible as outstanding or have an appropriate documented exclusion reason.
Does the software replace consulting or TGO-related verification?
No. It supports data preparation and internal review. Inventory methods, consulting and independent verification must be defined for the intended purpose and applicable criteria. Approving records or exporting a report is not TGO certification.
Can output intensity be used directly for CFP, CBAM or carbon credits?
Not automatically. An internal organizational indicator does not replace a product-level study, reporting for goods covered by CBAM or a carbon-credit process. These have distinct boundaries, methods and requirements.
What is needed to estimate price and implementation time?
Prepare the number of sites, reporting periods, data-source list, sample files, involved roles and required outputs. Data preparation, configuration, integrations and any additional services can then be assessed as separate items.
Assess the system using your factory's existing records
Bring your site list, sample files and reporting objective to DigitechX to define data collection, review steps and an implementation scope appropriate to your organization.