Four people review a map and photographs of air, rail and road travel at a wooden table, with notebooks and a suitcase nearby.
Illustrative travel planning, not an actual itinerary or verified programme result.
Diagram text description

An overhead synthetic scene shows four people around a wooden table. A large map lies among printed aircraft, railway and road photographs, notebooks, pens and coloured notes; a rolling suitcase is at the right. No readable company name, actual booking identifier, emissions figure, reduction target or certificate appears. The retained scene introduces programme planning, not evidence of real employees, travel modes, measured performance or a working travel integration.

A corporate travel carbon footprint is useful when it explains which employee business journeys are included, how their emissions were estimated and what changed between reporting periods. Adding travel invoices gives a financial total; it does not, by itself, produce an emissions inventory. The programme result needs a defined boundary, reconciled activity, suitable conversion factors and a comparison that keeps changes in coverage visible.

Start with the questions a travel manager and finance reviewer must answer together. Which journeys actually happened? Which systems captured them? Are two records the same trip? Does a lower emissions-per-trip figure mean fewer emissions overall? Those questions connect the calculation to decisions about meetings, routes, suppliers and policy.

This guide follows a fictional two-year programme through that process. It separates gross emissions from intensity, shows how an added expense feed and a changed factor affect the reported total, and ends with a filled report. The objective is a baseline someone else can reproduce, not a persuasive reduction claim assembled from an unexplained dashboard.

Decide what the travel programme includes

Define the reporting entities, employee population and dates before collecting totals. The GHG Protocol's Category 6 guidance distinguishes employee business transport supplied by third parties from company-controlled vehicles and ordinary commuting. Controlled vehicle fuel and electricity belong in the applicable scope 1 or scope 2 accounting; some leased vehicles fall elsewhere, depending on the reporting boundary. Employee commuting is a separate Category 7 activity.

A travel-policy label is therefore not an accounting classification. A company car used for a customer visit and a third-party train ticket can serve the same commercial purpose while entering different inventory categories. Document the routing decision rather than excluding the company car from the organisation's accounting altogether.

The Category 6 guidance allows hotel stays to be included optionally. Choose and disclose that treatment consistently. A programme can track hotels separately for management even when its stated transport baseline excludes them. Meals, guest travel and other expenses also need explicit treatment; appearing on an expense form does not automatically make them eligible transport.

Keep an exclusion register with the reason, owner and destination in the wider inventory where relevant. Missing eligible travel is a coverage gap, not a deliberate boundary exclusion and certainly not zero emissions.

Build one source inventory from many systems

Build an inventory of source systems before building an inventory of emissions. Agency bookings, corporate cards and employee expenses describe overlapping parts of a journey. A card payment can settle a ticket already present in the agency feed; counting both makes the programme larger on paper without adding any travel.

SourceUseful evidenceReconciliation decision
Travel agencyTicket, route, traveller and statusMatch changes and refunds to the original booking
Rail providerPassenger distance and journey dateCheck whether the agency already supplied the ticket
Card or finance feedMerchant, payment and amountUse to locate missing travel, not as another completed journey
Expense claimOff-channel journey and mileageMatch receipts and separate eligible mileage from other costs
Hotel feedStay dates and room nightsKeep separate under the declared hotel policy

Table 1, shown one row at a time. Every field is retained.

Row 1

Source
Travel agency
Useful evidence
Ticket, route, traveller and status
Reconciliation decision
Match changes and refunds to the original booking

Row 2

Source
Rail provider
Useful evidence
Passenger distance and journey date
Reconciliation decision
Check whether the agency already supplied the ticket

Row 3

Source
Card or finance feed
Useful evidence
Merchant, payment and amount
Reconciliation decision
Use to locate missing travel, not as another completed journey

Row 4

Source
Expense claim
Useful evidence
Off-channel journey and mileage
Reconciliation decision
Match receipts and separate eligible mileage from other costs

Row 5

Source
Hotel feed
Useful evidence
Stay dates and room nights
Reconciliation decision
Keep separate under the declared hotel policy

Preserve the original identifiers and create a programme journey reference above them. Store completed, cancelled, exchanged and refunded statuses rather than inferring travel from payment alone. A refund is evidence to investigate; it does not prove every leg was unused.

Reconcile source totals and exception counts each period. Where an identifier is absent, retain the matching evidence and review decision. An unresolved possible duplicate stays visible for review instead of being silently deleted or counted twice.

Calculate each mode with suitable evidence

Calculate each mode using evidence that matches the selected factor. Passenger distance, vehicle distance, fuel and money are not interchangeable quantities. Convert them deliberately before adding the resulting emissions mass, rather than applying a single average travel rate to the whole ledger.

ActivityPossible calculation basisCheck before multiplying
AirPassenger distance with an appropriate flight factorRoute, cabin assumptions and any additional aviation treatment
RailPassenger distance and relevant rail factorCountry, service assumptions and passenger-based unit
RoadVehicle distance, passenger distance or fuelOccupancy basis, vehicle type and whether distance is already shared
Optional hotelsRoom nights or the chosen supported methodGeography, hotel basis and whether the unit is per room or person
Spend-only recordsQualified mode-specific spend estimateCurrency, price year, category and factor coverage

Table 2, shown one row at a time. Every field is retained.

Row 1

Activity
Air
Possible calculation basis
Passenger distance with an appropriate flight factor
Check before multiplying
Route, cabin assumptions and any additional aviation treatment

Row 2

Activity
Rail
Possible calculation basis
Passenger distance and relevant rail factor
Check before multiplying
Country, service assumptions and passenger-based unit

Row 3

Activity
Road
Possible calculation basis
Vehicle distance, passenger distance or fuel
Check before multiplying
Occupancy basis, vehicle type and whether distance is already shared

Row 4

Activity
Optional hotels
Possible calculation basis
Room nights or the chosen supported method
Check before multiplying
Geography, hotel basis and whether the unit is per room or person

Row 5

Activity
Spend-only records
Possible calculation basis
Qualified mode-specific spend estimate
Check before multiplying
Currency, price year, category and factor coverage

The official guidance describes fuel-, distance- and spend-based approaches. A spend method can support a qualified estimate; a fare increase alone is not evidence that physical travel increased. Do not multiply a provider's already calculated emissions by another emissions factor, either.

Retain the factor source, version, geography, gases and unit with each result. Disclose whether aviation effects beyond the chosen greenhouse-gas basis are included. Check whether upstream fuel emissions are inside a factor before combining datasets. Only add results with an understood, consistent boundary; do not conceal differences behind the shared label CO2e.

Set a baseline that can be compared next year

A baseline is a versioned description of the programme, not just last year's number. Freeze its entities, eligible modes, source coverage, calculation methods, factors and denominator definition. Keep the source extracts and the decisions needed to reproduce that version. A later spreadsheet export should not overwrite the evidence for the earlier published result.

Decide in advance how to assess new information. An omitted eligible expense feed, a corrected duplicate or a changed reporting entity can alter comparability. Record the reason, size of the effect where calculable, reviewer and treatment under the organisation's chosen restatement policy. Not every change requires the same response, but every material comparison needs an explanation.

Keep two views where they answer different questions: the reported inventory under the applicable reporting-year method and an explicitly labelled matched-method analytical comparison. The latter can help isolate activity changes, but it is not permission to ignore required reporting methods or to replace current factors with whichever version makes performance look better.

Before describing a trend, ask whether both years cover the same eligible population and sources. If they do not, either reconstruct a defensible comparison or state the limitation. A visually tidy trend line cannot repair a missing baseline.

Read absolute totals beside intensity

Fictional programme example: Alder Services uses record TR-8 to compare calendar 2024 with calendar 2025 for employee business travel by third-party air, rail and road transport. Hotels are excluded in both years; controlled fleet and commuting are routed elsewhere. Entities are unchanged. These invented activity and factor values illustrate arithmetic, not actual travel, measured company performance or published conversion rates.

TR-8 baseline closes on 31 December 2024. TR-8 comparison closes on 31 December 2025. The shared analytical factor set F-v1 uses 0.100 kg CO2e per passenger-km for air, 0.020 for rail and 0.200 kg CO2e per vehicle-km for road. All assume the same simplified operational transport basis; upstream fuel emissions and an additional aviation non-CO2 uplift are excluded. This teaching boundary is not a complete assessment of travel's climate impact.

ModeRestated 2024 activityF-v1 result2025 activityF-v1 result
Air100,000 passenger-km10,000 kg CO2e120,000 passenger-km12,000 kg CO2e
Rail50,000 passenger-km1,000 kg CO2e100,000 passenger-km2,000 kg CO2e
Road15,000 vehicle-km3,000 kg CO2e20,000 vehicle-km4,000 kg CO2e
Gross observed totalAgency plus submitted expenses14,000 kg CO2eSame observed source types18,000 kg CO2e

Table 3, shown one row at a time. Every field is retained.

Row 1

Mode
Air
Restated 2024 activity
100,000 passenger-km
F-v1 result
10,000 kg CO2e
2025 activity
120,000 passenger-km
F-v1 result
12,000 kg CO2e

Row 2

Mode
Rail
Restated 2024 activity
50,000 passenger-km
F-v1 result
1,000 kg CO2e
2025 activity
100,000 passenger-km
F-v1 result
2,000 kg CO2e

Row 3

Mode
Road
Restated 2024 activity
15,000 vehicle-km
F-v1 result
3,000 kg CO2e
2025 activity
20,000 vehicle-km
F-v1 result
4,000 kg CO2e

Row 4

Mode
Gross observed total
Restated 2024 activity
Agency plus submitted expenses
F-v1 result
14,000 kg CO2e
2025 activity
Same observed source types
F-v1 result
18,000 kg CO2e

For example, 100,000 passenger-km × 0.100 kg CO2e per passenger-km gives 10,000 kg CO2e for baseline air travel. Summing the three mode results gives 14,000 kg, or 14 tonnes. The corresponding 2025 calculation is 12,000 + 2,000 + 4,000 = 18,000 kg, or 18 tonnes. Keep passenger-km and vehicle-km in their own rows; they are not a meaningful combined distance denominator.

The denominator is completed employee business trips, not individual legs, tickets, employees or kilometres. A reconciled journey register contains 200 completed trips in restated 2024 and 400 in 2025, including multimodal trips only once. At F-v1, intensity is 14,000 ÷ 200 = 70 kg CO2e per trip, compared with 18,000 ÷ 400 = 45 kg per trip. The rate falls by 25 kg, or 35.7%, while the gross total rises by 4 tonnes, or 28.6%. Those are different questions, not contradictory results.

The first published 2024 result was agency-only: 100,000 air passenger-km, 50,000 rail passenger-km and 10,000 road vehicle-km produced 13 tonnes across 180 trips. A subsequently reconciled expense feed added 5,000 road vehicle-km and 20 completed trips: 5,000 × 0.200 = 1,000 kg. That known coverage correction raises the observed baseline to 14 tonnes and 200 trips; it does not mean employees took extra journeys after publication.

Fictional matched-factor travel totals rise from 14 to 18 tonnes CO2e while intensity falls from 70 to 45 kg per completed business trip.
Fictional TR-8 baseline ending December 2024 and comparison ending December 2025. Illustration prepared November 2026. Gross total and intensity answer different questions.
Diagram text description

Two separate panels compare the fictional TR-8 programme under common factor set F-v1. The gross panel shows restated 2024 emissions of 14 tonnes CO2e and 2025 emissions of 18 tonnes. The intensity panel shows 70 kg CO2e per completed trip for 200 trips in 2024 and 45 kg per trip for 400 trips in 2025. These are labelled values, not bars or a shared geometric scale; tonnes and kg per trip must not be added. Both views cover agency and submitted expenses, with unknown off-channel completeness. The lower rate accompanies a higher total and does not establish policy effectiveness or a whole-programme reduction. The separate 18.8-tonne F-v2 reporting view and 13-tonne original baseline are explained in the article rather than substituted into this matched-factor comparison.

For 2025 reporting, fictional F-v2 changes the air, rail and road factors to 0.110, 0.018 and 0.190 in the same respective units and assumed emissions basis. The unchanged 2025 activity then gives 13,200 + 1,800 + 3,800 = 18,800 kg CO2e. Holding that activity fixed, the factor effect is 18.8 − 18 = 0.8 tonnes. The original-to-current bridge is 13 + 1 + 4 + 0.8 = 18.8 tonnes: known coverage, matched-factor activity and factor effects, in that defined order. This is an accounting bridge, not a unique causal attribution; another decomposition order can allocate interactions differently.

The 4-tonne matched-factor activity increase comprises 2 tonnes from air, 1 from rail and 1 from road. The doubled trip count and changed average journey mix do not prove any policy caused the lower intensity. Open decision: reconcile off-channel bookings and unsubmitted expenses in both years, then assess whether their missing activity is material enough to require further baseline restatement. Consequence: keep the observed-coverage comparison provisional and make no whole-programme reduction or policy-effect claim while that gap remains unquantified.

Find travel hotspots in observed data

Find hotspots by inspecting the observed programme, not by importing a universal ranking. Group emissions by mode, route, business purpose and frequency, then examine the evidence quality behind the largest groups. A high total can reflect many short journeys, a few long ones, incomplete supplier coverage or a different calculation method.

In fictional TR-8, air has the largest calculated mode subtotal within the recorded data. That observation does not establish the customer's actual largest source, nor does it establish air's share of an unobserved complete programme. The next management question is whether the recorded air journeys serve repeated destinations, unavoidable site work or meetings that could plausibly be combined.

Look at both totals and the opportunity to act. A small rail line is not automatically the best place to intervene merely because its records are clean. Equally, an uncertain road estimate may deserve better data before a travel restriction. Separate the action list from the data-improvement list so managers know whether they are changing journeys or improving the explanation of journeys already taken.

Decide which journeys can change

Choose interventions against the business purpose of the journey. Avoiding a trip through a suitable remote meeting, combining several appointments, changing a route or using rail can be useful options. None is a universal instruction to cancel work or substitute a mode regardless of geography, safety, accessibility and service needs.

Write down the feasible alternative before forecasting its effect. Compare the complete relevant journey, including access legs, additional nights and the number of travellers where those change. Check whether a longer trip genuinely replaces another journey or simply adds an appointment. A policy permitting rail is not evidence that staff used it or that programme emissions fell.

For a pilot, retain the business purpose, original option, chosen alternative and outcome. Use comparable methods when calculating the actual journeys, and distinguish an observed before-and-after result from a modelled alternative that never happened. Changes in workload and destinations can explain a programme trend even when an intervention worked locally.

Approve an action when its assumptions and operational consequences are clear enough for the responsible manager. Then review delivery and the resulting activity, rather than promoting a modelled saving to an achieved reduction.

Keep offsets apart from gross emissions

Keep the gross travel inventory separate from any offset purchase or compensation claim. A certificate does not remove a flight, railway journey or road kilometre from the activity register. Nor does its purchase change the conversion factor used to estimate those journeys' gross emissions.

Show the gross number first, together with its boundary and limitations. If the organisation holds a separate credit register, retain the quantity, instrument and reviewed purpose there. Eligibility, retirement and public claims need their own assessment; the travel ledger should not imply that buying an equivalent number of credits proves the programme is carbon neutral.

This separation also protects the management comparison. A team that buys more credits while travelling more has not demonstrated lower gross travel emissions. Managers need to see the activity trend and any separate financial or claims decision distinctly. Do not label a netted presentation as the measured travel footprint when it conceals the underlying gross result.

Explain incomplete coverage and model shifts

An unexplained change in the headline total can point managers in the wrong direction. Adding a supplier feed expands visibility; replacing a factor changes a model; correcting a duplicate changes a record. None necessarily means staff travelled more or less during the period being assessed.

For TR-8, the published-to-current increase is 5.8 tonnes, but only 4 tonnes sits in the defined matched-F-v1 activity comparison. The 1-tonne known coverage correction concerns journeys previously omitted from 2024, and the 0.8-tonne factor effect concerns unchanged 2025 activity. Report that bridge beside the totals rather than leaving readers to attribute all 5.8 tonnes to travel behaviour.

Do not turn known source coverage into a claim of complete coverage. Agency and submitted expense records can match across years while both miss off-policy bookings. A percentage of transactions reconciled within those feeds is not the percentage of all eligible travel captured. If the missing population cannot be quantified, say so and identify the follow-up evidence needed.

Freeze each published version and issue a documented revision when review changes it. Keep both the original number and the restated comparison accessible, so the next annual report explains a revision instead of quietly replacing last year's baseline.

Run a monthly review and annual sign-off

Use monthly review to catch errors while source owners can still explain them. The travel owner confirms journey status and unusual routes; finance reconciles payments, claims and credit notes; the calculation owner checks units and factors. Assign unresolved records a named owner and due date instead of carrying them invisibly into the annual total.

At each close, retain an exception list, source coverage statement and versioned calculation output. Check changes in supplier methodology before combining its emissions with internally calculated rows. Compare the mode totals with activity indicators to identify a possible duplicate, missing feed or unit error; a reconciliation is a prompt to investigate, not an automatic reason to adjust the result.

Annual sign-off should allow a reviewer who did not build the calculation to reproduce the totals and inspect material assumptions. Confirm the boundary, factor versions, denominator, restatement decisions and unresolved gaps before approving the report. Keep management actions and their supporting evidence beside, but distinct from, the signed inventory.

The monthly cadence is a proposed operating approach, not a universal reporting obligation. Its purpose is to make annual review manageable and to prevent an unexplained year-end number from becoming the organisation's accepted history.

What a useful travel report actually shows

Fictional filled programme report: TR-8 records Alder Services' calendar 2024 baseline and calendar 2025 comparison for third-party employee air, rail and road business travel. The same entities and hotel exclusion apply to both years. This is the report corresponding to the worked example above, not another scenario or evidence of a real company's performance.

Report fieldTR-8 filled value
Original baseline2024 agency-only: 13 t CO2e; 180 completed trips; F-v1
Restated baseline2024 agency plus submitted expenses: 14 t; 200 trips; F-v1
Matched analytical view2025: 18 t at F-v1; 400 completed trips
IntensityF-v1: 70 kg per trip in 2024; 45 kg per trip in 2025
Current-year reporting view2025 at F-v2: 18.8 t CO2e; not directly comparable with original 13 t
Change explanation13 + 1 known coverage + 4 matched-factor activity + 0.8 factor effect = 18.8 t
Source coverageAgency and submitted expenses; off-channel completeness unknown in both years
Method boundarySimplified operational transport CO2e; no upstream fuel or additional aviation uplift
Priority follow-upReconcile missing bookings and expenses before approving a whole-programme trend claim

Table 4, shown one row at a time. Every field is retained.

Row 1

Report field
Original baseline
TR-8 filled value
2024 agency-only: 13 t CO2e; 180 completed trips; F-v1

Row 2

Report field
Restated baseline
TR-8 filled value
2024 agency plus submitted expenses: 14 t; 200 trips; F-v1

Row 3

Report field
Matched analytical view
TR-8 filled value
2025: 18 t at F-v1; 400 completed trips

Row 4

Report field
Intensity
TR-8 filled value
F-v1: 70 kg per trip in 2024; 45 kg per trip in 2025

Row 5

Report field
Current-year reporting view
TR-8 filled value
2025 at F-v2: 18.8 t CO2e; not directly comparable with original 13 t

Row 6

Report field
Change explanation
TR-8 filled value
13 + 1 known coverage + 4 matched-factor activity + 0.8 factor effect = 18.8 t

Row 7

Report field
Source coverage
TR-8 filled value
Agency and submitted expenses; off-channel completeness unknown in both years

Row 8

Report field
Method boundary
TR-8 filled value
Simplified operational transport CO2e; no upstream fuel or additional aviation uplift

Row 9

Report field
Priority follow-up
TR-8 filled value
Reconcile missing bookings and expenses before approving a whole-programme trend claim

Read the mode detail with the summary: the F-v1 baseline is 10 t air, 1 t rail and 3 t road; the matched 2025 view is 12 t air, 2 t rail and 4 t road. F-v2 applies 0.110 kg per air passenger-km, 0.018 per rail passenger-km and 0.190 per road vehicle-km to the unchanged 2025 activity. That produces 13.2, 1.8 and 3.8 t respectively. The common-F-v1 view preserves interpretation; it does not replace the stated current-year reporting method.

The lower intensity accompanies higher gross observed emissions. It therefore proves neither an absolute reduction nor a policy's effectiveness. Open decision: the travel and finance owners must establish the missing bookings and expense population for each year and decide whether material omissions require a revised baseline. Consequence: until those checks resolve the unquantified gap, treat this as a provisional comparison of observed sources, not proof of a programme-wide reduction or a successful policy.

Choose an evidence system that preserves the trail

Choose an evidence system by what a reviewer needs to reconstruct, not by an assumed promise of automatic travel integration. A useful register connects a journey reference to its permitted source records, eligibility decision, unit, factor version, result and exception history. It also preserves the distinction between an observed booking and a completed trip.

Test the handoff with a small sample. Can the reviewer trace a refunded ticket, recognise an agency/card duplicate and reproduce a restated baseline without losing the old version? Can the report show an unresolved coverage gap instead of silently presenting it as zero?

These are requirements for the chosen process or tool, not claims that any particular provider already supplies them. Confirm actual access, export rights and working capabilities before relying on a platform for annual sign-off. The evidence trail must survive a change of staff or software.

Begin with a small baseline pilot

Begin with one defined entity, a complete reporting period and a manageable set of actual travel sources. Agree the eligible modes and hotel policy, reconcile completed journeys, select suitable factors and build both the gross total and a clearly defined intensity measure. Record the missing sources before discussing targets.

Ask a second reviewer to reproduce the result and explain one material change without assistance from the original preparer. Then choose whether to expand coverage, improve a weak method or test a feasible travel alternative. That sequence makes the pilot useful even when its first conclusion is that the available data cannot support a trend claim.

A trip register establishes individual records; a Category 6 assessment establishes the inventory boundary; a calculator converts supported inputs. Programme management brings those components together over time and uses them to make accountable decisions. Keep that distinction as the programme grows: the final deliverable is a traceable baseline, a candid comparison and a focused improvement list, not merely a lower-looking number.