Measurement and Verification Kit (M and V Made Practical)

Prove impact without overcomplicating: baseline → measure → normalize → report

Decision KitsM&V Kit45 min

What you'll accomplish

  • Define what "impact" means (kWh, fuel, demand, cost, emissions, comfort)
  • Set up a baseline and post-project measurement plan
  • Choose the simplest acceptable method (start basic, improve later)
  • Produce an auditable M&V memo for each project or program
  • Avoid the most common failure: "we think it worked, but we can't prove it"

Who this is for

Facilities/engineering teams

Executing projects

Sustainability teams

Reporting reductions

Finance teams

Validating ROI and savings

Anyone accountable for

"Did it actually work?"

Prerequisites

Utility Data Pipeline Starter KitMetering Strategy PlaybookOptional

Quick start (45 minutes)

Pick one completed or planned project and do:

  • Fill the M&V Plan (Template 1)
  • Define baseline period (Template 2)
  • Define post period (start date + duration)
  • Decide normalization approach (Template 3)
  • Set reporting cadence (Template 6)

Beginner rule (non-negotiable)

If you didn't define a baseline before the change:

  • • you can still measure,
  • • but your proof will be weaker,
  • • and you should document that honestly.

Choose the simplest method that's defensible

Method A

Basic pre/post (fastest)

Use when:

  • •change is large
  • •usage is stable
  • •you can accept higher uncertainty
Method B

Pre/post with simple normalization

Use when:

  • •weather or occupancy varies
  • •you want stronger proof without heavy modeling
Method C

Submetered measurement

Use when:

  • •you can isolate the system (HVAC, lighting, EV chargers)
  • •you want high confidence

Beginner rule: Start with Method A or B, then move to C for high-stakes projects.

Step-by-step

1

Define what you're measuring

Pick 1–3 primary metrics: electricity kWh, fuel use (therms, gallons), peak demand (kW), cost ($), emissions (calculated from activity), comfort/complaints (count), maintenance tickets (count).

2

Define baseline period

Recommended: 12 months of utility bills if available, OR at least 3–6 months if moving quickly. Document: start date, end date, data sources, data quality (measured/allocated/proxy).

3

Define post period

Document: "change implemented on" date, stabilization period (e.g., 2–4 weeks), measurement window (3 months / 6 months / 12 months).

4

Decide normalization (only if needed)

Normalize for: weather (hot/cold variations), occupancy/operating hours, production volume. Start with: "we compared same months year-over-year" or "degree-day adjusted months" or "kWh per occupied day."

5

Build the proof package

Include: baseline dataset link, post dataset link, assumptions and normalization notes, calculation outputs, limitations.

6

Report and close

Create a short "impact note": what changed, what happened, what we learned, what scales next.

Templates included

Template 1 — M&V Plan (copy/paste)

M&V Plan

Project:
Site:
Change implemented date:
Objective (plain English):
Primary metrics:
- kWh
- fuel
- demand
- cost
- comfort/tickets (optional)

Method selected:
[ ] A: Basic pre/post
[ ] B: Pre/post with normalization
[ ] C: Submetered

Baseline period:
Post period:
Stabilization period:
Data sources + evidence links:
Normalization approach (if any):
Owner:
Reporting cadence:

Template 2 — Baseline Dataset Columns (minimum viable)

| Site | Period start | Period end | kWh | Fuel (if applicable) | Notes | Evidence link |
|---|---|---|---:|---:|---|---|

Template 3 — Normalization Log (copy/paste)

| Project | Factor | Why it matters | Data source | Method used | Notes/limitations |
|---|---|---|---|---|---|

Template 4 — Savings Calculation Worksheet (copy/paste)

| Metric | Baseline (avg) | Post (avg) | Delta | Notes |
|---|---:|---:|---:|---|
| kWh |  |  |  |  |
| fuel |  |  |  |  |
| kW |  |  |  |  |
| $ |  |  |  |  |

Template 5 — QA Checklist (copy/paste)

M&V QA Checklist

- Baseline period defined and linked
- Post period defined and linked
- Evidence links open
- Billing periods do not overlap
- Any gaps documented
- Normalization assumptions documented
- Results reviewed by owner + approver

Template 6 — Impact Note (copy/paste)

Project Impact Note

Project:
Site:
Summary of change:

Results:
- kWh change:
- fuel change:
- cost change:
- comfort/tickets change:

Confidence:
- High / Medium / Low
Why:

What we learned:
What we will scale next:

Common pitfalls

  • ✗No baseline period defined
  • ✗Not recording "implementation date" (can't align post period)
  • ✗Cherry-picking months (credibility killer)
  • ✗Mixing data sources without documentation
  • ✗Treating cost changes as savings without explaining rate effects

Change log

v1.0 (2026-01): Latest release