Platform
The activity data behind your emissions number, with its evidence
Your carbon number is only as defensible as the fuel, energy and freight data underneath it. Frontline is where that data is captured, owned and evidenced - before it reaches a calculation.
What data sits behind a defensible carbon number?
An emissions figure is only as defensible as the activity data underneath it: the fuel purchased, the electricity metered, the refrigerant topped up, the freight moved - each traceable to a source document, with a named owner and a reporting period. Frontline is where that activity data is collected and evidenced, not where it is converted into tonnes. There is no emissions-factor library in Frontline; it exports the activity dataset to whatever model, consultant or carbon platform performs the calculation.
- Every activity line carries its invoice, meter photo or manifest
- A named owner and submission deadline per stream, per site, per period
- Site teams and contractors submit through a link, without a licence
- Restatements keep what the figure was, what it became and who changed it
The problem
The calculation is the easy part
Multiplying litres by an emissions factor is arithmetic. Proving where the litres came from is the work - and it is the part that fails assurance.
Most organisations already have a spreadsheet that produces a carbon number. What they do not have is a defensible chain from that number back to a fuel invoice, a meter read or a freight manifest, with a named owner and a date. When an assurance provider samples a line, the answer is a search through inboxes.
The gap widens every year the boundary expands. Scope 3 in particular is not a data problem you solve by buying a calculator - it is a collection problem across sites, contractors and suppliers who have no reason to respond to a spreadsheet request.
- Every activity line traceable to a source document
- A named owner per data stream, per site, per period
- Change history on restatements, which assurance always asks about
What it does
The collection layer under the number
Activity data registers
Fuel, electricity, refrigerants, waste and freight as records with quantity, unit, period and site - the inputs, held as data rather than as tabs.
Evidence on the record
The invoice, the meter photo, the manifest attached to the line it supports. Sampling becomes a click instead of an email.
Owners and due dates
Each stream has someone responsible and a submission deadline per period, with reminders that fire before close, not after.
Collection from the source
Site teams and contractors submit through a link or a form on a phone. They do not need a licence, an account or training.
Completeness at a glance
What has landed, what is missing and who owes it - per site and per period - so close is managed rather than chased.
Restatement history
When a figure changes after close, the record keeps what it was, what it became, who changed it and why.
Where we stop
We are not trying to be your carbon calculator
Emissions factors change, jurisdictions differ, and organisations already have a model or a consultant they trust. Replacing that is not the job worth doing.
The job worth doing is the layer nobody owns: getting complete, evidenced, attributable activity data out of sites and contractors on a schedule, so that whatever model you run is fed something defensible. Frontline exports the activity dataset; your model or your tool does the arithmetic.
- Export by period, site, scope category and stream
- Feeds a spreadsheet model, a carbon platform or your assurance provider
- The evidence stays linked, so a sample resolves back to the source
Questions we get asked
Does Frontline calculate emissions?
No. There is no emissions-factor library in the product and we are not pretending otherwise. Frontline holds the activity data and the evidence behind it, and exports that dataset to whatever model or platform you already use to calculate.
Then why not just use a carbon platform?
Most of them assume the activity data arrives clean. If your problem is getting fuel figures out of forty sites and a contractor network every quarter, with evidence attached, that is a collection and accountability problem - the same one Frontline already solves for safety and risk data.
Can contractors submit without a licence?
Yes. They submit through a link. You track who owes what and when it landed; they do not need an account.
What about assurance?
Every record carries its full change history and its source document. That is what a limited or reasonable assurance engagement samples, and it is the part a spreadsheet cannot produce.
See it running on your own data.
Tell us what you run today. When your spot comes up you are looking at your own register, your own incidents and your own sites, not a canned demo environment.
- We take a few teams at a time
- Works with your existing exports
- No IT project