Custom app for CO2 registration and measures on the project
A project for which a CO2-related award advantage has been obtained requires a project file that substantiates the requirements for that specific project. It is precisely these projects that end up in the sample. What counts then is not what was stated in the tender, but what actually happened on site.
Why the project is the hardest part
A project with an award advantage is one in which the CO2 Performance Ladder played a role in the tender, regardless of whether that advantage was decisive. Before each ladder assessment, the organisation compiles a demonstrably complete list of these projects, and the certifying body takes a sample from it.
For projects started with an award advantage, emissions must be mapped, and at higher levels also quantitatively. This means consumption and deployment must be known per project, not merely added up at company level.
Here lies the practical problem. Fuel is filled at a pump card not linked to any project, equipment moves from one location to another, and a generator runs at a site where nobody logs the hours. At the end of the quarter there is a total, but no allocation that holds up.
The same applies to the measures. The tender contains commitments about how work is carried out on this project. Whether those have been honoured shows in what is recorded on site, and usually nothing is. The project file can also form the basis for the conversation with the client about ambition during execution.
How we build this
The core is the link between consumption and project. Every litre, every operating hour and every measure belongs to a location, and that assignment has to happen at the moment itself.
Whoever arrives on site links themselves to the project. After that, everything they record attaches to it automatically.
Litres filled, operating hours and equipment deployed, scanned where possible and entered where necessary.
What was promised in the tender becomes an item on site that someone signs off, with a photo attached.
What has been recorded flows into the file for this project, where the substantiation for the assessment is built up.
What the app does in practice
Assignment to the project carries the whole. What else you need depends on your equipment fleet and on the number of projects with an award advantage.
Getting the fuel onto the right project
Litres are booked to the site where the work is being done, not to the pass or the branch.
Operating hours per machine
Equipment that moves takes its hours with it to the new project rather than disappearing into a total.
Measures as checkpoints
What has been promised becomes a point with an owner, signed off on the day it was due.
Works without signal
Construction sites and routes rarely have coverage. The app works offline and synchronises as soon as there is a connection.
Evidence for the measure
An electric crane or an adapted way of working is shown more quickly with a photo than with an explanation afterwards.
Project status
Which measures have been signed off and which have not, while the project is still running and there is still time to act.
Who we build for
Who does the recording differs from project to project. Four situations.
Executors
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 simply won't happen.
Project managers
They made a promise in the tender and want to know during delivery whether it is being kept.
KAM coordinators
They build the file from which the sample is drawn and depend on what has been recorded on site.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
The handbook is revised, equipment is replaced and projects differ in what has been promised. Measures, equipment types and fields should be configurable and not hard-wired into the app.
Why Appfront
A total is not a project file
The assessment concerns specific projects. Consumption that exists only at company level does not help there.
Allocation happens at the moment itself
Allocating after the fact is guesswork. We let the link come about at the point of refuelling and running the equipment.
Promised is not done
What the tender states must happen on site. We turn that into checkpoints rather than good intentions.
We do not calculate your footprint
Conversion using emission factors is a separate track. For that we have CO2 accounting software.
Security and privacy
What is recorded on site concerns projects you have won with award advantage and what you promised in doing so. That is commercially sensitive information. We set access by role and by project, show a machine operator only their own records, and log every inspection. What is stored locally on the device is encrypted and can be remotely wiped if a device is lost.
For this subject, the reliability of the moment is the crux. 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 irreversibly with time, place and person, even when synchronisation happens later, and make any correction a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about CO2 recording on projects
Because for started projects with award advantage, emissions must be mapped, and at higher levels quantitatively too. A company total does not answer that question.
Those from the list of projects for which CO2-related award advantage was obtained. Before each assessment, the organisation demonstrably compiles that list to be complete.
By letting the link come about at the moment of refuelling, at the machine and on site, rather than allocating a total across projects after the fact.
Yes. Construction sites and routes rarely have coverage. The app works offline and synchronises once a connection returns, keeping the original timestamp.
In the project file and the certification file. We describe this on our page about software for the CO2 Performance Ladder.
Yes, and that is often necessary, since some 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 for which you received a tender advantage and look up the fuel consumption and operating hours assigned to it. If that turns out to be an allocation after the fact, that is what the audit will find. We build this as a standalone app and as part of a broader app development project.