Consumption per project Measure signed off Works without coverage

Custom app for CO2 registration and measures on the project

A project on which CO2-related tender advantage was obtained requires a project file with the substantiation of the requirements for that specific project. Those are exactly the projects that end up in the sample. What counts then is not what was in the tender but what happened on site.

Appfront
Live

Why the project is the hardest part

A project with tender advantage is one where the CO2 Performance Ladder played a role in the tender, whether or not that advantage was decisive. Before each Ladder assessment, the organisation draws up a demonstrably complete list of those projects, and the certifying body takes a sample from it.

For projects started with tender advantage, the emissions must be mapped, and at higher levels also quantified. That means consumption and deployment must be known per project, not just totalled at company level.

That's where the practical problem lies. Fuel is bought on a card that isn't tied to a project, equipment moves from one site to another, and a generator runs somewhere nobody records the hours. At the end of the quarter there is a total, but no breakdown that holds up.

The same goes for measures. The tender contains commitments on how work will be done on this project. Whether they were kept shows in what was recorded on site, and that is usually nothing. The project file can also be the basis for the conversation with the client about ambition during delivery.

How we build this

The core is the link between consumption and project. Every litre, every running hour and every measure belongs to a site, and that allocation has to happen at the moment itself.

1
Select the project on arrival

Anyone who arrives on site links themselves to the project. Everything they then record is automatically attached to it.

2
Recording consumption and deployment

Litres refuelled, running hours and equipment deployed, scanned where possible and entered where necessary.

3
Signing off measures

What was promised in the tender becomes a point on site that someone signs off, with a photo as evidence.

4
Pass on to the project file

What is recorded lands in this project's file, where the supporting evidence for the assessment is built up.

What the app actually does

Assigning to the project carries the whole thing. What else you need depends on your equipment fleet and on the number of projects with a tender advantage.

Refuelling on the right project

Litres are booked to the site where the work is done, not to the fuel card or the branch.

Running hours per machine

Equipment that moves takes its hours with it to the new project instead of disappearing into a total.

Measure as a checkpoint

What was promised becomes a point with a person responsible, signed off on the day it applied.

Works without signal

Construction sites and routes rarely have coverage. The app works locally and syncs as soon as there is a connection.

Photo with the measure

An electric crane or an adapted working method is demonstrated faster with a photo than with a statement after the fact.

Project status

Which measures have been signed off and which have not, while the project is running and something can still be done about it.

Who we build for

Who does the recording differs per project. Four situations.

Contractors

They see what actually happens on site and are the only ones who can link consumption to the right project.

Machine operators

They refuel and log the hours. If linking to a project takes more than one action, it doesn't happen.

Project managers

They made a promise in the tender and want to know during execution whether it is actually being delivered.

QHSE coordinators

They build the file from which the sample is drawn and depend on what has been recorded on site.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The manual gets revised, equipment is replaced and projects differ in what was promised. Measures, equipment types and fields should be configurable and not hard-wired into the app.

React Native or native iOS and Android Offline storage with synchronisation Scanning of equipment and fuel cards Running hours and consumption per project Configurable measures per project Photo with timestamp and location Operation with work gloves Roles for execution, project and QHSE Integration with your equipment and project administration History per project and per machine

Why Appfront

A total is not a project file

The assessment concerns specific projects. Consumption that only exists at company level doesn't help there.

Assignment happens in the moment

Allocating afterwards is guesswork. We make the link happen at the point of refuelling and running.

Promised is not done

What is in the tender has to happen on site. We turn it into checkpoints rather than good intentions.

We don't calculate your footprint

Converting with emission factors is a separate track. For that we have CO2 accounting software.

Security and privacy

What is recorded on site concerns projects you won with a tender advantage and what you promised in them. That is tender-sensitive information. We set access per role and per project, show an operator only their own records, and log who views what. What is stored locally on the device is encrypted and can be wiped remotely if a device is lost.

For this subject, reliability at the moment of recording is the point. A measure signed off after it became known that this project was in the sample is no longer evidence but a risk. We record entries and sign-offs immutably with time, location and person, even when synchronisation happens later, and make a correction a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.

Frequently asked questions about CO2 tracking on projects

Because emissions must be mapped for projects started with a tender advantage, and at higher levels quantitatively too. A company-wide total does not answer that question.

Those from the list of projects on which CO2-related tender advantage was obtained. Before each assessment, the organisation draws up that list and can demonstrate it is complete.

By making the link at the moment of refuelling, at the machine and on site, rather than dividing a total across projects afterwards.

Yes. Construction sites and route sections rarely have coverage. The app works locally and syncs as soon as a connection is available again, preserving the original timestamp.

In the project file and the certificate file. We describe this on our page about software for the CO2 Performance Ladder.

Yes, and that is often necessary, because part of the equipment on a project is not yours. See our approach to building an app.

How much fuel went into that one project?

Take a project on which you gained a tender advantage and look up the fuel consumption and running hours assigned to it. If that turns out to be a distribution after the fact, that is what the sample will find. We build this as a standalone app and as part of a broader app development project.

Edit content