Substances per process Justification per measure Reporting from your records

Custom software for ZZS reporting and reduction programmes

For each reduction option, the avoidance and reduction programme asks for the efficiency of the measure, its validation, and the reliability and cost of the technique. That is not text that comes together in an afternoon. It is a collection of considerations that is built up over years, or reconstructed just before the deadline.

Appfront
Live

What the duty to provide information requires of you

Substances of very high concern (SVHCs) are substances that are hazardous to people and the environment; PFAS and asbestos are well-known examples. Permit-required activities carry a duty to provide information: every five years, the company reports to the competent authority which SVHCs it emits to air and to water or the sewer, and which measures it takes to prevent and limit those emissions.

This report must be accompanied by an avoidance and reduction programme with prescribed content. It describes the options for avoiding emissions at the source, for example by phasing out the substance or adapting the process, and the options for reducing use and emissions within the current process.

Four things belong with each reduction option: how efficient the measure is, how that efficiency has been validated, how reliable the technology is in operation, and what it costs. A programme that only says what has been investigated, without those four, is not a programme but a list.

The emission data is also recorded in an emissions database. What ends up there arises in scattered places: during a measurement, during a malfunction, during a process change or when a seal is replaced. The report is a single moment; the registration beneath it runs on for five years.

How we build this

The core is the combination of substance and process. A substance without a process is a list, and a process without substances is a drawing. The report requires both at the same time.

1
Map substances per process

Which SVHCs can be released where, via which route to air or water, and under which permit condition.

2
Collect observations

Measurements, malfunctions and findings land with the substance and the point they belong to, rather than in separate files.

3
Substantiate measures

For each reduction option, the efficiency, validation, reliability and costs, supplemented as more becomes known.

4
Build the report

What has been recorded over five years forms the report and the programme, instead of a search after the fact.

What the software actually does

The link between substance and process holds everything together. What else you need depends on your processes and on whether you work with an in-house environmental coordinator or with a consultancy.

Substance register per process

Which SVHCs are present where and via which route they can be released. This is the foundation for everything that follows.

A measure with four answers

Efficiency, validation, reliability and costs are separate fields on the measure, because the programme requires all four.

Source approach alongside process approach

Phasing out or replacing is different from reducing within the current process. Both tracks should be visible separately.

Five years of history

Measurements, malfunctions and changes stay linked to the substance and the point, so the previous report can always be retraced.

Prepare the submission

Emissions per substance and per route, in the format the emissions database requires, built from what has been recorded.

Keep the substance list up to date

Lists are revised and substances are added. The system shows which new substance becomes relevant for which process.

Who we build for

Who builds the report differs per company. Four situations.

Environmental coordinators

They are responsible for the report and don't want to rebuild it from mailboxes and folders every five years.

Consultancies

Anyone reporting for several companies wants a single way of working and data recorded in the same way at every location.

Permit holders in industry

For them, the report is not a formality but the conversation with the competent authority about the years ahead.

Process and technology departments

They assess whether a reduction technique is reliable in operation, and that assessment belongs in the programme.

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

Substance lists are revised, conditions differ per permit and measurement methods change. Substances, routes and fields should be configurable rather than hard-coded.

Configurable substance and process register Emission routes to air and water Measures with justification fields Integration with your measurement systems Document storage per substance and measure Roles for environment, process and management History across multiple reporting periods Export to the emissions database Alerts for revised substance lists Audit trail on every change

Why Appfront

Four answers per measure, not one

The programme asks for efficiency, validation, operational reliability and cost. We build these as separate fields, so any gap is visible.

Five years is too long to remember

The justification builds up gradually over the years. If you don't build it up as you go, you end up making it up afterwards, and you find out at the first follow-up question.

The substance belongs to the process

A substance list without processes says nothing about emissions. We link them, because the reporting does the same.

We do not assess your emissions

Whether a measure is sufficient is a question for your adviser and the competent authority. We make sure the justification is in place.

Security and privacy

Your substance and process data reveal something about your recipes and your operations, and the reporting touches on your relationship with the competent authority. We set access per role and per location, give an adviser access only to the processes they work on, and log every access. Integrations run through secure connections to your existing software.

On this subject, what matters is the reliability of the moment. A measured value that was adjusted afterwards because the result disappointed is no longer evidence at the next report. We record observations and justifications immutably, with a timestamp and the person responsible, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about ZZS reporting

For activities that require a permit, a report to the competent authority is due once every five years, covering the SVHCs emitted to air and to water or sewer and the measures taken.

The efficiency of the measure, how it has been validated, the operational reliability of the technology and its cost. A measure without those four is not justified in the programme.

Avoiding at the source means phasing out the substance or changing the process. Alongside that is reducing use and emissions within the current process. The programme asks for both tracks.

Yes. PFAS is named as an example of a substance of very high concern, just like asbestos. Which substances are relevant for your site follows from your processes and your permit.

From measurements, malfunctions and findings on site. We describe that on-the-ground recording on our page about the on-site ZZS app.

No. The judgement on what is feasible and sufficient remains with your adviser and the competent authority. We build the file on which that judgement rests.

Can you justify why a reduction measure was dropped?

Take one measure from your previous programme that was not implemented, and look up its efficiency, validation, operational reliability and cost. If one is missing, that question will be open again in the next round. We build this as a standalone application and as part of a broader custom software development project.

Edit content