Emissions reporting for a heavy fleet is mostly an activity-data problem rather than a carbon-accounting one. The conversion factors are published and the arithmetic is straightforward; what stops fleets producing a defensible figure is that nobody can say with confidence how much fuel each machine burned, how many hours it ran, or how much of that time it spent idling. The number then gets estimated from bulk fuel purchases divided across the fleet, which is defensible only until an auditor asks how it was derived. The fix is upstream of the report entirely, and you can review what your own fleet currently captures in a free 30-minute session.
Emissions Audit Coming? The Problem Is the Activity Data
Runtime hours, idle share, and fuel per asset logged against the machines themselves, so the reported figure rests on records rather than on a fleet-wide average.
What the Figure Is Actually Built From
Each link depends on the one before it. The chain usually breaks at the first or second, not at the calculation.
Fuel consumed, per asset
The foundation of any combustion emissions figure. Bulk site purchases divided across machines is an allocation, not a measurement.
Usually breaks because: fuel is issued at site level and never attributed to the machine that burned it.
Operating hours, per asset
Meter readings captured regularly enough to establish how much each machine actually worked in the period.
Usually breaks because: readings are taken sporadically, so the period boundaries are guesses.
Idle share of those hours
Time running without productive output, which burns fuel and produces emissions for nothing.
Usually breaks because: nothing distinguishes working hours from idling hours in the record.
Conversion to emissions
Published emission factors applied to fuel volume. The most straightforward part of the exercise.
Rarely the problem: if the inputs above are sound, this step is arithmetic.
Why Idle Time Deserves Separate Attention
Idle running is the one component of fleet emissions that carries no production benefit at all. Every other litre burned moved material or did work; idle fuel produced emissions, consumed money, and accumulated engine hours that bring services forward, all for nothing.
That makes it the most defensible reduction to commit to in a report. Reducing total emissions usually means doing less work or replacing equipment. Reducing idle means doing the same work with less waste, which is a commitment you can actually deliver on without a capital programme.
It is also visible without new hardware on many machines, since the gap between engine hours and productive hours tells most of the story once both are being recorded.
Start Logging Before the Audit, Not During It
Fuel per asset, meter readings, and idle indicators captured as part of the inspection your operators already complete.
What to Have in Place Before You Are Asked
Fuel issued recorded against the receiving machine rather than the site tank.
Meter readings captured on a consistent cadence, so period figures are measured rather than interpolated.
A clear asset list stating which machines are owned, hired, or contractor-operated, since that determines where they appear in reporting.
Consistent period boundaries, so the same start and end dates apply to fuel, hours, and any comparison against last year.
A written note of how anything estimated was estimated, because auditors accept estimates far more readily than unexplained numbers.
Frequently Asked Questions
Which emissions scope does our own equipment fall under?
Fuel burned by equipment you own or control is generally direct combustion, which sits in Scope 1. Equipment operated by a contractor on your project typically appears in your Scope 3 and in that contractor's Scope 1. Confirm the treatment with whoever prepares your disclosure, since boundary decisions vary by framework. We can show you how the underlying data is captured on a call with our team.
Do we need telematics on every machine?
No. Fuel issued per machine and meter readings captured during inspection cover the essentials. Telematics improves idle measurement specifically, but it is not a prerequisite for reporting.
Is an estimated figure acceptable?
Often yes, provided the method is documented and applied consistently. What causes problems is a figure nobody can explain, not an estimate that is clearly labelled as one.
How far back can we reconstruct data?
Only as far as your records genuinely support. Reconstructing a year retrospectively from fuel invoices produces a weaker figure than starting proper capture now and reporting honestly on the transition.
What is the quickest improvement to make?
Attributing fuel to individual machines rather than to sites. It is the single change that most improves the quality of everything downstream of it. Start with a free trial.
Fix the Inputs and the Report Writes Itself
Attribute fuel to machines rather than sites, capture meter readings on a consistent cadence, separate idle from productive hours, and document how anything estimated was arrived at.
