TGO Criteria for Registering a Carbon Footprint Reporting Platform

Software has become the normal way organizations assemble a carbon footprint, and TGO has responded with criteria for registering reporting platforms. The criteria are published as a short infographic titled Criteria for Registering a Carbon Footprint Reporting Platform (หลักเกณฑ์การขึ้นทะเบียนแพลตฟอร์มการรายงานคาร์บอนฟุตพริ้นท์), issued by the Thailand Greenhouse Gas Management Organization (Public Organization). This article sets out what the document asks for, page by page, and then states plainly what is and is not confirmed about CarbonBiz in relation to it.

A note on the source: the document is a four-page graphic rather than a text publication. It has no visible edition date on the pages we hold, so we cite it by page only. The first page is a cover; the criteria are on pages 2 and 3; page 4 carries TGO's contact details.

#Who the criteria apply to

The criteria distinguish four kinds of platform: platforms for reporting the carbon footprint of an organization, of a product, of an event service, and of an individual (TGO Platform Registration Criteria, p.2). CarbonBiz is in the first group, so the organization-level evidence is what matters here, but the structure of the criteria is the same for all four.

#Part 1: preliminary mandatory criteria

The first section lists five preliminary mandatory criteria (เกณฑ์ข้อบังคับเบื้องต้น), each paired with the evidence TGO expects (TGO Platform Registration Criteria, p.2):

1. Reporting in line with TGO requirements and guidelines. The platform must be able to report results in accordance with TGO's requirements and guidelines for the relevant footprint type. Evidence: an assessment report that conforms to TGO's requirements and guidelines.
2. Data transfer to the TGO platform by API. The platform must be able to transfer data to TGO's platform so that TGO can aggregate it, through an Application Programming Interface. Evidence: documentation showing that the platform can transfer data to the TGO platform.
3. ISO 29110 or CMMI Level 3 certification. The platform must be certified to ISO 29110 or to CMMI Level 3 or higher. Evidence: a certificate issued by a certification body accredited under the International Accreditation Forum (IAF).
4. Declaration on confidentiality. The platform must declare that it has mechanisms to protect the confidentiality of users and their data. Evidence: documentation of those mechanisms.
5. No intellectual property or emission factor licensing conflicts. The platform must not operate in a way that conflicts with intellectual property law or with the licence terms for using emission factor databases. Evidence: a document showing this, which can be downloaded from the TGO website.

These five are gatekeeping conditions. Two of them, the software process certification and the emission factor licensing statement, are about the platform's organization and practices rather than its features.

#Part 2: platform registration criteria

The second section sets three registration criteria (เกณฑ์การขึ้นทะเบียนแพลตฟอร์ม), again with evidence (TGO Platform Registration Criteria, p.3):

1. Activity data. For an organization-level platform, the evidence is an example showing that activity data is collected separately for Scope 1, 2 and 3 and that reports can be produced by scope. Product platforms must show data collected by life-cycle stage; event platforms must show energy, travel, accommodation and waste data together with credit purchases; individual platforms must show energy, travel, food and drink data from daily routines.
2. Emission factors. The platform must be able to link data so that emission factors and global warming potential values are updated in line with TGO through an API. Evidence: documentation showing that the platform uses the latest version of the emission factors and GWP values.
3. Reporting format. The platform must be able to export data to produce reports in accordance with TGO's requirements and guidelines. Evidence: an example report that conforms to those requirements.

The page closes with a footnote that deserves as much attention as the criteria themselves: TGO does not certify the accuracy of results calculated by a platform until they have been verified by an external assessor and submitted to TGO for certification (TGO Platform Registration Criteria, p.3). In other words, registering a platform is about the platform's capability; it does not turn any individual organization's figures into TGO-certified figures. That still requires the verification process described in the TGO verification guideline.

#How CarbonBiz relates to the criteria

Here we separate what the product documentation supports from what has not been confirmed.

On the functional criteria, the CarbonBiz feature list (Feature List v3.4, 8 September 2026) describes capabilities that correspond to several items. Activities are recorded and reported separately by Scope 1, 2 and 3 with a 15-category breakdown of Scope 3, which is the kind of evidence criterion 2.1 asks for. The App generates the TGO CFO Version 04 forms Fr-01 to Fr-05, which corresponds to criterion 2.3. The feature list states that the Verification Readiness module is intended to serve as evidence for criterion 2.3 of TGO CFO platform registration (Feature List v3.4, category 66). The emission factor database records the standard version and GWP version of every factor, and system factors are updated centrally; however, an automatic factor synchronisation with TGO through an API, which is what criterion 2.2 describes, is listed in the feature list as an optional item not included in the delivered release, pending availability of a TGO emission factor API (Feature List v3.4, category 65, item 65.7).

On the preliminary criteria, the feature list describes an API for data exchange in general terms, but we have not seen documentation of a data transfer to TGO's own platform (criterion 1.2), and we have no document in hand for the ISO 29110 or CMMI certification (criterion 1.3), the confidentiality declaration (criterion 1.4) or the emission factor licensing statement (criterion 1.5).

The registration status of CarbonBiz as a TGO carbon footprint reporting platform is therefore not yet confirmed. This article will be updated when the owner provides the registration reference or the supporting documents. Until then, readers should treat CarbonBiz as a platform that produces TGO-format reports and supports the verification process, and should not read this article as a statement that it is registered.

#What this means for an organization choosing software

The criteria are a useful checklist even for organizations that will never register a platform themselves. Ask a vendor whether reports come out in TGO's form layouts, whether activity data is kept separately by scope, how emission factors and GWP values are versioned and updated, how confidentiality is handled, and under what licence the factor database is used. Then remember the footnote: whichever platform you use, your figures become TGO-certified only after an external verifier has checked them and you have applied to TGO.