Custom software for the certificate file of the CO2 Performance Ladder
Before every ladder assessment, you draw up a demonstrably complete list of all projects on which you gained a CO2-related award advantage. The certifying body draws its sample from that list. A single project that was not recognised as such makes the list incomplete, and the assessment uncomfortable.
What the ladder asks of your file
The CO2 Performance Ladder has five levels, and its requirements stem from four perspectives: insight into your own energy flows and emissions, reduction through measures and targets, transparency in internal and external communication, and participation in initiatives with other authorities and companies. Levels one to three concern your own organisation; level four focuses on reduction in the supply chain and on innovation, and level five on demonstrably achieving ambitious targets, partly in cooperation with others.
The certificate is valid for three years from the date of issue, with an annual ladder assessment no later than twelve months after the initial one. A certifying body assesses and determines the level.
From level three, online publication is mandatory, and it happens in two places at once: on the organisation's own website and on the organisation page at the scheme manager. Continued availability of that published information is part of the requirement, not a consequence of it.
A project with an award advantage is a project in which the ladder played a role in the tender. It does not matter whether the advantage was decisive or how the ladder was requested. That is a broader definition than companies usually apply, and that is exactly where the gaps in the list arise. Each such project requires a project file with the substantiation of the requirements for that specific project.
How we build this
The requirement is the core. Every requirement belongs to a level and a perspective, has an owner and a rhythm, and calls for a piece of evidence that has to come from somewhere.
Which requirements apply to your level, who is responsible for them and what evidence goes with them.
On intake, it is determined whether the ladder played a role in the tender. That decision belongs there, not just before an audit.
Some activities have an annual follow-up and some a six-monthly one, with a margin of one month at most.
The complete project list and the file for each requirement are ready at the moment the body asks for them.
What the software actually does
Managing requirements and projects carries the whole. What else you need depends on your level and on the number of projects you tender.
Requirements with an owner and evidence
For each requirement: who completes it, which document demonstrates it and when it is due for updating.
Recognising award advantage
For every tender won, the question of whether the ladder played a role, with the answer recorded rather than reconstructed later.
Project file per project
The substantiation of the requirements for that specific project, including the measures that were promised.
Six-monthly follow-up monitored
An activity that must be completed annually and six months before that, with a margin of one month at most either way.
Publication in two places
What is published where and since when. Continued availability is the requirement, so disappearing is a problem.
Preparing the assessment
The complete list of award advantage projects and the evidence per requirement, ready in one go instead of in a final sprint.
Who we build for
Who manages this differs per organisation. Four situations.
QHSE coordinators
They carry the file and notice at every assessment that the evidence is scattered across the organisation.
Sustainability managers
They steer on reduction and want the certificate to follow from the work, not the other way round.
Tender teams
They win the tenders in which the ladder played a role, and so are the source of the project list.
Management teams
They sign off on the targets and want to know whether the level used in the tender is sustainable.
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 handbook is being revised, harmonisation decisions are being published and levels are shifting. Requirements, rhythms and levels should be configurable rather than hard-coded.
Why Appfront
The project list is the most vulnerable part
The definition is broader than people think, because whether the advantage was decisive is irrelevant. We ask that question for every award.
Evidence can't be collected at the last minute
Half-yearly follow-up with a one-month margin can't be made up afterwards. We build the rhythm in.
Publishing isn't done after a single time
The requirement is permanent availability in two places. A page that goes offline costs you a level.
We don't calculate your footprint
Collecting consumption data and converting it with emission factors is a discipline of its own. For that we have CO2 accounting software.
Security and privacy
Your certificate file contains tender information: which projects you won, with what advantage, and what you promised. That is commercially sensitive, even within your own organisation. We set access per role and per project, give an auditor temporary and limited access, and log that access. Integrations run through secure connections to your existing software.
For this topic, the reliability of the moment is the point. A project that is only flagged as an award advantage project after the sample is taken, or a measure added to a project file after the fact, undermines exactly what the assessment tests. We record decisions and documents immutably with a timestamp and the person responsible, and we 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 the CO2 Performance Ladder
Insight into your own energy flows and emissions, reduction through measures and targets, transparency in internal and external communication, and participation in initiatives with other authorities and companies.
Levels one to three concern CO2 management and reduction targets within your own organisation. Level four focuses on reduction in the supply chain and on innovation, and level five on demonstrably achieving ambitious targets, partly in collaboration with others.
When the CO2 Performance Ladder played a role in the tender. Whether the award advantage was decisive, or how the ladder was requested, is not relevant.
The certificate is valid for three years from the date of issue, with an annual ladder assessment no later than twelve months after the initial assessment.
From level three in two places: the organisation's website and the organisation page at the scheme owner. Permanent availability of that information is part of the requirement.
No. Collecting consumption data and converting it with emission factors is a separate track. For that we have a separate page on CO2 accounting software.
Is your list of award advantage projects complete?
Take the tenders you won over the past year and determine for each one whether the ladder played a role, regardless of whether it was decisive. If that turns up a project that wasn't on the list, your previous list was not demonstrably complete. We build this as a standalone application and as part of a broader software development project.