Measurement and verification without the spreadsheet grind

Measurement and verification, or M&V, answers a simple question that is surprisingly hard to prove: did this project actually save the energy it was supposed to? Financing, incentives and internal budgets all depend on the answer, yet most teams still assemble it by hand from exported bills and meter files.

The method itself is well established. The widely used International Performance Measurement and Verification Protocol sets out how to compare a baseline against post-project consumption while adjusting for weather and operating changes. The friction is upstream of the method: the data.

Why the data is the bottleneck

A credible M&V result needs a clean baseline, a defined measurement period, and adjustments for the things that change independent of the project, mainly weather and occupancy. Each of those depends on consistent, granular data that lines up across meters and time.

• Baselines drawn from monthly bills alone miss the load shape that interval data reveals.
• Weather adjustment needs matching local weather data aligned to the billing periods.
• Multi-meter sites need every meter reconciled to the same calendar before anything can be compared.

Making M&V routine

The fix is to treat data preparation as a repeatable pipeline rather than a one-off scramble:

1. Bring every bill and meter feed into one structured store, with the raw source kept for audit.
2. Normalize units, periods and meters so a portfolio lines up on one calendar.
3. Attach weather to each period automatically so adjustments are consistent.
4. Keep the baseline and measurement period defined once, then refresh as new data arrives.

Which IPMVP option fits

The protocol offers four approaches, and the choice decides how much measurement you need. Options A and B isolate the retrofit itself, measuring either the key parameters or all of them at the equipment. Option C works at the whole facility from utility meter data. Option D uses a calibrated simulation where there is no usable baseline, for example in a new build or after several overlapping changes.

For a building portfolio, Option C is usually the practical choice, because the meter data already exists and the savings are large enough to be visible at the whole-building level. Its weakness is that everything else in the building also lands in the same meter, so the adjustments have to be right and the exceptions have to be visible. Where a single piece of equipment is being proved and the saving is small relative to the building, isolation is the honest answer instead. MartinAI's guide to IPMVP and measurement and verification works through the options and the baseline arithmetic in more depth.

What M&V software actually has to do

Software marketed for energy savings verification tends to be judged on its charts. The parts that decide whether a result stands up are less visible.

• Hold the baseline period, the model and its coefficients so the same comparison is repeated every month rather than rebuilt.
• Attach weather to each billing period automatically, using a consistent base temperature.
• Track non-routine events, such as a tenant change or a new load, and record the adjustment made for each.
• Keep the source bill or meter file attached to every figure, so a challenged number can be traced to a document.
• Report cumulative savings, not just a monthly delta, because that is the figure a finance team or an incentive program asks for.

VE-MAP is built around that pipeline. It reads utility bills and standardized data, reconciles them, and gives you the baseline and reporting views without the monthly spreadsheet rebuild. The point is not a new method, it is making the proven method something you can run every month without dread. The method itself, a degree-day baseline (Environment and Climate Change Canada defines heating degree-days against an 18 degree Celsius base) and a CUSUM chart of cumulative savings, is explained in weather normalization, CUSUM and RETScreen M&V, and the way it appears each month in how to read a monthly energy review report. The use cases page shows the portfolio types we run it for.