CSRD for Buildings: Continuous Data, Not Annual Snapshots

CSRD and buildings: why annual numbers no longer pass the audit

For years, the energy and emissions line in a sustainability report was an estimate dressed up as a number. You took twelve monthly bills, applied a national emissions factor, multiplied, and wrote down a figure nobody was ever going to check. CSRD ended that. Once your sustainability disclosures sit inside the annual report and an auditor has to sign off on them, the question changes from “what number did you publish” to “show me how you arrived at it.” For building portfolios, that is a harder question than most teams expect, because the way buildings have always produced their energy data was never built to survive an audit.

The scope of who has to answer it narrowed in 2026. The Omnibus simplification package lifted the thresholds, so mandatory reporting now lands on the largest organisations: roughly those above 1,000 employees and EUR 450 million in turnover, a far smaller group than the directive first covered. If you run a large property portfolio, an institutional estate, or sit inside a corporate group above those lines, you are still in scope, and the data bar did not move with the thresholds. It got more concrete.

So here is what CSRD actually expects from the buildings in your portfolio, why the data most of them produce today does not survive an auditor, and what continuous measurement looks like once you map it onto the meters you already own.

What CSRD expects from building operators

CSRD does not regulate buildings directly. It regulates the company that owns or operates them, and it asks that company to report its sustainability performance against the European Sustainability Reporting Standards (ESRS) with the same rigour as its financial statements. The standard that lands hardest on real estate is ESRS E1, climate change, which covers energy consumption and greenhouse gas emissions. That is where your buildings show up.

In practice, three expectations matter for an estate team. First, your energy and emissions figures have to be measured, or built from a method you can defend, rather than guessed. Second, they have to be assured: an independent auditor reviews them, currently to a limited-assurance standard, which means they will sample your evidence and expect it to hold. Third, the picture has to be complete and consistent across the portfolio, so a building that quietly stopped reporting half its submeters in March is a problem, not a rounding error.

The shift underneath all three is from annual to continuous. A report is still filed once a year, but the data behind it can no longer be a once-a-year reconstruction. Scope 2 emissions, the ones from the electricity and district heat your buildings buy, are the clearest case. Getting them right means knowing not just how much energy each building used, but when, because the carbon content of the grid changes by the hour. A single annual factor papers over all of that, and an auditor is increasingly within their rights to ask why.

Where building data falls short of audit grade

Walk into the data behind a typical portfolio’s energy report and you find the same three weaknesses almost every time.

The first is manual meter reads. Someone photographs a meter, types the number into a spreadsheet, and that spreadsheet becomes the source of truth. It works until it doesn’t. Readings get missed, transposed, or estimated when nobody could get to the meter that month. There is no timestamp beyond “around the end of January,” and no way to prove the figure was not edited afterwards. For limited assurance, a spreadsheet of hand-keyed numbers with no traceable origin is exactly the kind of evidence that draws a question.

The second is estimated factors standing in for measurement. Where a building has no submetering, consumption gets apportioned by floor area or headcount. Where actual grid data is missing, a flat national emissions factor fills the gap. Each estimate is reasonable on its own. Stacked together across a portfolio, they turn the reported number into a model with no measured spine, and a model is hard to assure because there is nothing underneath to sample.

The third is gaps between measurements. A meter read in January and another in December tells you the total and nothing about the eleven months in between. If a chiller ran inefficiently all summer or a submeter dropped offline in spring, the annual figure absorbs it silently. The data has no resolution, so it cannot show the auditor that it is continuous, and it cannot show the operator where the energy actually went.

None of this is negligence. It is what building data looked like when the only consumer of it was a utility bill. CSRD changed the consumer, and the old data shape no longer fits.

Continuous measurement, concretely

Continuous measurement sounds like a slogan until you map it onto the meters already in your buildings. Most of the hardware is there. What is usually missing is a layer that reads it constantly, keeps the record, and turns the readings into something a disclosure can be built from.

Start with the meters and submeters you have. Electricity, district heating, gas, and water meters mostly already pulse or report digitally. A sensor-intelligence layer ingests those readings on a continuous basis instead of once a month, so every figure carries a timestamp and a source. That alone moves the data from “typed in from a photo” to “logged automatically and traceable,” which is the single biggest change an auditor notices.

Then handle scope 2 properly. Instead of applying one annual emissions factor to a year’s worth of consumption, match each building’s measured electricity use against the grid’s carbon intensity at the time it was used. In the Nordics this matters more than almost anywhere, because the Swedish, Norwegian, and Finnish grid mix swings widely between clean hydro and nuclear and dirtier imported power depending on the hour and the season. A building that runs its heaviest loads when the grid is clean has genuinely lower scope 2 emissions than one that runs them at peak, and only time-matched data can show it. A flat factor erases the difference, usually to the building’s disadvantage.

The output is a sensor-to-disclosure path you can point at. The reported energy figure for a building traces back to specific meter readings at specific times. The scope 2 figure traces back to measured consumption matched against published grid intensity. Nothing in the chain is invented, which is exactly the property assurance is looking for, and it is the same continuous foundation that the ESG-reporting-from-sensor-data approach is built on.

The overlap with EPBD and building certification

The work CSRD asks for is not a standalone project, and treating it as one is how portfolios end up paying for the same data three times.

The same continuous energy data that satisfies your CSRD disclosure is what the EPBD’s building automation requirement asks for. The recast directive obliges large non-residential buildings to monitor, log, and analyse their energy use on an ongoing basis, which is the same measured backbone CSRD wants behind the report. If you are already building toward the EPBD 2026 BACS requirement, you are most of the way to audit-grade CSRD data, and the reverse holds too.

Certification schemes draw on the same well. BREEAM In-Use, LEED, and Nordic Swan all reward, or increasingly require, evidence of actual operational performance rather than design intent. A continuous record of energy and emissions feeds a certification submission as readily as it feeds a sustainability report. One measured foundation, several reporting obligations on top of it. That is the case for treating the sensor layer as infrastructure rather than as a line item against any single regulation, and it is the logic behind the wider compliance picture a building portfolio now has to manage.

Building an audit-ready evidence trail

The word that matters here is evidence. Assurance is not satisfied by a confident number. It is satisfied by being able to walk backwards from the number to the thing that was measured, and to show the path was not tampered with along the way.

Three properties make a building’s data audit-ready. It has to be timestamped, so every reading is tied to a specific moment rather than a vague month. It has to be traceable, so the figure in the report links back through the calculation to the raw meter reading it came from. And it has to be exportable, so when the auditor asks for the underlying data on a sampled building, you produce it in minutes instead of reconstructing it from emails and spreadsheets.

This is where grounded inference matters. The trustworthy version of a sustainability number is one where the system never quietly fills a gap with a plausible-looking guess. When a submeter drops offline, an audit-ready layer flags the gap and records how it was handled, rather than smoothing over it so the annual total still looks tidy. An auditor can forgive a missing reading with a documented treatment. What they cannot forgive is a number that looks clean because the system was built to hide its own gaps.

Build the trail once and it serves every reporting cycle after. The first CSRD report is the hard one, because it is where the data shape changes. From the second onward, the evidence accumulates automatically, the annual scramble disappears, and the same record that proves compliance also tells you which buildings are drifting and where the energy is going. The annual number stops being something you reconstruct under deadline and becomes something you can already see.

CSRD did not really ask buildings to report more. It asked them to be able to prove what they report. For a portfolio, the honest way to do that is to measure continuously and keep the record. The report writes itself from there.

Frequently asked questions

Does CSRD apply to my building portfolio?
CSRD applies to the company that owns or operates the buildings, not to the buildings themselves. After the 2026 Omnibus changes, mandatory reporting is concentrated on the largest organisations, broadly those above 1,000 employees and EUR 450 million in turnover, or non-EU groups with significant EU turnover. If your portfolio sits inside a group above those thresholds, your buildings’ energy and emissions data feeds its ESRS E1 disclosure. Confirm your group’s status, since national transposition of the Omnibus changes ran into 2027.

What building data does CSRD actually require?
The climate standard, ESRS E1, covers energy consumption and greenhouse gas emissions, including scope 2 emissions from purchased electricity and district heat. For buildings that means measured energy use across the portfolio and emissions figures built from defensible data, all of it complete enough and traceable enough to pass independent assurance.

Why aren’t annual estimates good enough anymore?
Because sustainability figures now sit inside the assured annual report. An auditor reviews them to a limited-assurance standard and samples the evidence behind them. Hand-keyed meter reads, area-based estimates, and flat annual emissions factors are hard to assure because there is no measured, timestamped record underneath to verify. Continuous measurement gives the auditor something to check.

What is scope 2 time-matching and why does it matter for buildings?
Scope 2 emissions depend on how much electricity a building uses and how carbon-intensive the grid was when it used it. Matching measured consumption against grid carbon intensity hour by hour gives a more accurate figure than applying one flat annual factor. In the Nordics, where the grid mix swings between clean and dirty power through the day and the seasons, time-matching can materially change a building’s reported scope 2 emissions.

Can I reuse CSRD data for EPBD and building certification?
Yes. The continuous energy monitoring CSRD relies on is the same measured backbone the EPBD building automation requirement asks for, and the same operational evidence that BREEAM In-Use, LEED, and Nordic Swan increasingly expect. One sensor foundation can feed all of them, which is why it is worth building once rather than per regulation.

See continuous, audit-ready evidence on a sample of your data. Request a demo.