Audit-grade at source.

The report layer has caught up. The source layer has not.

In the last twenty-four months, software for ESG reporting has matured into a recognisable category. Watershed, EnergyCAP, EQS, Workiva and IntegrityNext all now describe themselves with some variant of audit-ready lineage or audit-grade data for the disclosures required under the Corporate Sustainability Reporting Directive (CSRD) and the European Sustainability Reporting Standards (ESRS). The output layer is rigorous. The lineage tools are real. The methodology is documented.

The source layer is not. Building-level waste data, the input that ESRS E5 explicitly requires for material flows, is in most operating portfolios still produced by hand. Monthly estimates. Hauler reports. Mixed-stream figures back-cast onto fraction percentages no one measured. Spreadsheets prepared on quarterly cycles, populated from invoices that describe collection volumes, not disposal events.

The result is a documented inheritance problem. Audit-grade in the report layer. Anecdotal at the origin. The integrity of the disclosure cannot exceed the integrity of the source. That sentence is the entire problem.

What audit-grade is supposed to mean.

The term has two operative requirements. First, the data has to be traceable to a primary source with a verifiable measurement method. Second, the chain of custody from that measurement to the final disclosure has to be reconstructable on demand. Both requirements are written into the assurance scopes that limited and reasonable assurance providers are applying under CSRD, and both are explicit in the technical guidance issued by EFRAG for ESRS implementation.

For energy, water and Scope 1 fuels, the source layer was instrumented years ago. Meters. Sub-meters. BMS objects. Logged events with timestamps. The primary source exists. The chain of custody is short.

For waste, the source layer is mostly absent. ESRS E5-5 asks for incoming and outgoing material flows by fraction, by mass. ESRS E5-4 asks for resource inflows by type. Neither point can be populated to assurance standard with an estimate. The number has to exist before the report can be assured.

The gap. Where audit-grade ends and the building begins.

A representative example. A commercial occupier produces an annual sustainability statement. The waste fraction breakdown reads: 38 percent paper and card, 19 percent plastic, 12 percent glass, 31 percent mixed residual. The breakdown was extrapolated from the hauler's quarterly invoice, which carried total tonnes and a single contamination flag.

There is no measurement of the disposal event. There is no record of what was actually placed where, when, in what condition, by whom. The breakdown is a calculation, not an observation. Under reasonable-assurance scoping, that distinction matters. Under limited assurance it still matters, because the assurance provider has to evidence the methodology that produced the figure, and the methodology is back-extrapolation from collection-side data.

The report layer can render that data with precision. It cannot ennoble it.

A simple architectural answer. The source layer is a building decision.

The fix is not in the software. The fix is in the building. Specifically, in the object the occupant places material into.

nicelium™ is the upstream layer. It records the disposal event at the moment it happens. Fraction. Mass. Time. Contamination state. Liquid presence. The output is a stream of measured events, not an estimate. The event is logged, addressable, timestamped and durable.

That stream is the primary source the assurance framework asks for. It travels into Watershed, EnergyCAP, EQS, Workiva, IntegrityNext or any other ESG software stack as upstream data, in formats the report layer is built to ingest. The report layer continues to do what it does well. The source layer is no longer the hole in the audit.

The data points the source layer needs to populate.

ESRS E5-4 (resource inflows): mass and composition by material type.

ESRS E5-5 (resource outflows, waste-related): mass by fraction, hazardous and non-hazardous split, contamination, route to recovery.

ESRS E1-6 (Scope 1 emissions, indirectly): on-site combustion of mixed residual streams that should not have been combusted, traceable to the disposal events that produced them.

Each point requires an instrumented disposal event. Each is reachable only if the source layer measures it. The data points are public. The instrumentation is the open question for most occupied portfolios.

The contamination problem the report layer cannot see.

Contamination is the single highest source of audit risk in waste reporting. A 60 percent contamination rate in a mixed-recycling stream means the figure on the page is wrong by a factor that no report-layer calculation can correct. The hauler downgrades the stream. The recovery rate collapses. The disclosure reads optimistic. The assurance provider notes a finding.

Inside nicelium™, contamination is recorded at the disposal event. The validated brand metric: contamination below 9 percent at point of disposal, with material purity at 99 percent on the separated fractions. Those figures are observations from instrumented events, not estimates from invoices. The number on the page reconciles to the number in the building.

This is the practical meaning of audit-grade at source. The contamination is observed, logged and addressable. The downstream calculation inherits a measured input.

Source layer and report layer compose. They do not compete.

The instinct in the category has been to position the source layer against the report layer. That framing is incorrect. Source and report occupy different positions in the same data path.

Madaster describes the building as it was constructed. Watershed and its peers describe the reporting period as it closes. nicelium™ describes the operating phase as it unfolds, event by event. Each layer answers a question the other cannot.

For the buyer, the implication is procedural. Choose the report layer that fits the reporting infrastructure. Then instrument the source. Without the second step, the first is partial.

What to specify into a retrofit or a new build.

Three lines on the spec are enough.

One. A waste-stream source layer, BMS-integrated, producing logged disposal events by fraction, mass, contamination state, liquid state and time. Mapped to ESRS E5-4 and E5-5 data points.

Two. An open data path from the source layer into the ESG reporting platform of record. Field-level mapping documented in the commissioning package.

Three. An assurance brief for the source layer measurement method, in a form a Big Four or Tier 1 assurance provider can accept under ISAE 3000 or ISAE 3410 scoping.

Those three lines move the building out of the back-extrapolation regime and into the primary-source regime. The report layer does the rest.

Audit-grade is upstream first.

A report can only be as accurate as its inputs. Anecdotal at the source is anecdotal at the auditor. The category vocabulary has moved towards audit-grade. The next move is to define where audit-grade actually begins.

It begins in the building. It begins at the moment a fraction is separated. It begins where the disposal event is observed, measured and logged.

That is the source layer. That is where the work is.

The source layer is a building element, not an appliance. It is specified at the same stage as a sub-meter, a flow meter or a BACnet-bound sensor object. Late retrofits are possible. Early specification is cleaner.

Sources and references

EFRAG ESRS implementation guidance. European Sustainability Reporting Standards technical guidance for E5 data points.

Watershed. Best ESG reporting software 2026. Category landscape for ESG report-layer software.

Deloitte. CSRD and ESRS Omnibus updates. Post-Omnibus scope and assurance scoping.

‍

‍

____

Proiect cofinanțat de Uniunea Europeană prin Programul Creștere Inteligentă, Digitalizare și Instrumente Financiare 2021-2027 (PCIDIF), cod MySMIS 335006.Beneficiar: S.C. AI FOR GOOD SRL.