What data is needed to achieve each methodology?

Created by Thrust Carbon, Modified on Thu, 23 Oct, 2025 at 3:29 PM by Thrust Carbon


This table sets out the data points required to achieve each quality of emissions methodology for each segment type:


Segment Type

OK

(Spend based)

Good

(DEFRA)

Better

(DEFRA+)

Best

(ICAO+)

Air

Cost

Currency

IATA Origin

IATA Destination

Date of flight

IATA Origin

IATA Destination

Carrier Code

Date of flight

IATA Origin

IATA Destination

Carrier Code

Flight number

Class of service*

Date of flight

Aircraft Type



Segment Type

OK

(Spend based)

Good


Better

Best

Hotel

Cost

Currency

Number of nights

Check in date


Country Code (ie. GB) 

Number of nights

Check in date


Country Code (ie. GB)

City Name

Property Name

Property Address

Number of nights

Check in date

GIATA code (to look up exact hotel)

Number of nights

Check in date

Segment type

OK  

(spend based)

Good

(DEFRA)


Better

(DEFRA or Country Specific Rail Factors)

Best

(DEFRA or Country Specific Rail Factors)

Rail

Cost 

Currency

Date of train

Distance traveled

Date of train

Origin & Destination***

Date of train

Distance traveled****

Origin & Destination***

Date of train

Segment type

OK  

(spend based)

Good

(DEFRA)


Better

(DEFRA+)

Best

Car Hire

Cost

Currency

Number of days rental

Distance driven

Cost

Currency

Distance driven

Car Type

Fuel Type


*Class of Service - Thrust assumes Economy if no class of service is given so that customers still benefit from ICAO+ emissions calculations

**The flight number allows us to access the seating configuration of the plane, and therefore reach an even closer calculation

***Origin & Destination - needs to be SNCF codes, UK station codes, coordinates, AMTRAK codes, or IATA codes.

****Distance traveled acts as a fall back if we are not able to determine the distance based on the origin/destination provided


Important Notes

Whilst capturing additional data with an Expense claim is a plausible way of achieving better calculations, there are considerations:-

  • Can Thrust Carbon retrieve the additional data points via the API

  • Can the additional data points be exported into reports so that the data can be uploaded to Thrust Calculator

  • All additional fields require the user to input data which is reliant on accurate selection/entry


Travel data is, and will remain, the most effective way of retrieving high-quality data to unlock the best calculation methods.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article