CarbonTrack was not designed in a boardroom. It was built during a placement at a major UK industrial site after watching the annual travel data scramble firsthand.
Every year the same thing happens at manufacturing and engineering companies across the UK. Someone — usually in finance, operations, or compliance — receives 200 to 300 rows of travel data from across the business. It arrives in their inbox as a spreadsheet. Sometimes as several spreadsheets. Sometimes as email chains.
They spend two weeks manually looking up DEFRA factors, estimating distances, running calculations in Excel, and producing a number that goes into the annual SECR report or a PPN 06/21 Carbon Reduction Plan. The number is as accurate as the person doing it. The methodology is as defensible as their notes in a column labelled "workings".
I watched this happen during my placement at a major UK manufacturer. The security and admin team were logging travel in a spreadsheet. Nobody was sure who was responsible for the DEFRA calculations. The person who did it last year had left.
That is not an edge case. That is standard operating procedure for most companies in this size bracket. And when SECR reporting is a legal requirement and PPN 06/21 compliance is the difference between winning or losing a government contract — "we did our best with a spreadsheet" is not a defensible position.
CarbonTrack fixes this. Employees log trips as they happen. The platform does the DEFRA calculation, stores the formula permanently, and generates the compliance document when you need it. The Finance Director signs a document they can actually defend.
Currently finishing a placement at a major UK manufacturer. Built CarbonTrack because I saw the problem firsthand and had the technical skills to solve it.
seyi@usecarbontrack.co.uk
If your company processes 100+ travel entries a year for SECR or PPN 06/21 compliance — CarbonTrack was built for you.