How to measure emissions from Trips: Flights included: Client flights to/from point of departure

What counts as Trips: Flights included: Client flights to/from point of departure

Flights to and from the trip's point of departure that the tour operator purchases and includes within the package price the client pays. Reported in passenger.km or spend for the flight the operator books on the client's behalf.

The included/excluded distinction reflects who purchases the flight, which determines the correct Scope 3 category: because the operator purchases this flight as an input to the package it sells, it maps to Category 1 (purchased goods and services), unlike the excluded-flights page, which maps to Category 11. Keep a clear internal rule, by product line or booking flow, for which trips include flights, so activity data collection matches how each trip is actually priced.

What activity data you need

Collect the most specific physical unit available. Unit definitions are in Appendix I — Description of Units.

• passenger.km
• $ Spend
• £ Spend

Which emission scope it falls under

Trips: Flights included: Client flights to/from point of departure activity data typically maps to Scope 3 Category 1 under the GHG Protocol. Confirm organisational boundary and ownership before reporting.

Sub-types available in the platform

All 6 sub-types available in the platform.

• Air Travel: Average
• Air travel: Average: UK
• International air
• UK Domestic air
• UK Long haul air
• UK Short haul air

Common questions

How do we know whether a trip's flights are included or excluded?

Check your own product pricing and booking flow: if the flight cost is bundled into the package price the client pays, it's included; if the client books and pays for their own flight, it's excluded.

What if flights are included for some passengers but not others on the same departure?

Split the departure into included and excluded flight legs by passenger, entering each group under the matching activity page rather than treating the whole departure as one category.

Should connecting flights be reported as one leg or several?

Use the total route distance for the journey where your booking system supports it; if only per-leg data is available, sum the legs to reach the same overall passenger.km figure.

How does this interact with our own business-travel bookings for trip leaders?

Trip leader or staff travel is a separate business-travel entry (Category 6), not part of the client-facing package - keep staff flights out of this page.

Is spend or passenger.km the more reliable unit for this activity?

Passenger.km is generally preferred where route data is available, since it maps more directly to a distance-based factor than fare, which varies with booking class and timing.