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

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

Flights that a client books and pays for independently to reach the trip's point of departure, and which are therefore excluded from the tour operator's own package pricing, but still tracked as part of understanding the trip's full footprint. Reported in passenger.km or spend for the client's flight to and from the meeting point.

This differs from 'Trips: Flights included' by package boundary, not by activity type: use this page when the flight cost sits outside what the client pays the operator for the trip itself, typically because the client arranges their own flights to reach a common departure point. Because this flight isn't part of the purchased package, it maps to Category 11 (use of sold products) rather than Category 1 - it reflects a flight the client takes to use the trip product, rather than one the operator purchased as an input.

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 excluded: Client flights to/from point of departure activity data typically maps to Scope 3 Category 11 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

Why does this map to a different Scope 3 category from included flights?

Because who purchases the flight determines the category: the operator purchasing a flight as a package input is Category 1, while a client's own flight to use the trip product is Category 11.

How do we get flight data for a journey the client books themselves?

Ask clients to confirm their departure route at trip registration, either as a simple form field or a booking confirmation upload, so you have route data without needing to manage the booking.

What if some clients on the same trip fly and others drive?

Record each client's actual travel mode and route where you collect it; where you only have aggregate estimates, apply a documented split based on typical client travel patterns for that departure point.

Should we estimate this if we don't collect it from every client?

Yes - a reasonable estimate based on typical client departure locations is better than omitting the activity entirely, provided you document the assumption and improve data collection over time.

Does this apply to all trip types or only long-haul packages?

It applies wherever clients arrange their own travel to a meeting point that's excluded from the package price, regardless of trip length - though it's most commonly relevant for longer or international trips.