Utility data collection for energy consultants and ESCOs

A consulting practice or ESCO rarely serves one building. It serves dozens of clients, each with several utility accounts, each account sitting behind a different login on a different portal. Every month someone on the team has to gather electricity, gas, and water data for all of them, reconcile the formats, and get it clean enough to feed an audit, a benchmarking model, or a client dashboard. That data-gathering step, not the analysis, is where most consulting hours quietly disappear.

Buildings are a large enough problem to justify the effort. Building operations account for 30% of global final energy consumption and 26% of global energy-related emissions, and in Canada the built environment makes up about 17% of total greenhouse gas emissions. The advisory market built around that is real: even a decade ago the U.S. energy service company industry booked roughly 5.3 billion dollars in annual revenue. The bottleneck for scaling that work is not expertise. It is data collection.

Why data collection is the hidden bottleneck

The manual pattern looks the same across most practices. A staff member logs into each client portal, downloads a PDF bill or a usage export, and keys the numbers into a spreadsheet or an energy tool. Multiply that by the number of accounts and the number of months, and the cost is obvious. Government guidance on energy data collection notes that manual keying introduces transcription errors and that teams under time pressure often capture only total cost and total consumption, dropping the line items (demand, delivery, rate class, taxes) that the analysis actually needs. The U.S. Department of Energy's best-practice guidance on energy data collection treats streamlined, automated access as a prerequisite for reliable reporting, not a nice-to-have.

There is also the access problem. A consultant does not own the client's utility accounts. Every collection method has to respect that the client is the account holder and the party who authorizes access. The three practical routes below each handle that differently.

The volume compounds quickly. A single commercial client might carry a dozen accounts across electricity, gas, and water, and a mid-sized practice can be responsible for hundreds of accounts in total. At that scale, the difference between a portal that has to be visited by hand and a feed that arrives on its own is the difference between a service you can grow and one that caps out at whatever your team can key each month. The manual approach also fails silently: a bill that never arrives is simply absent from the spreadsheet, and nobody notices until a client asks why a month is missing from their report.

The three ways to get client utility data

Authorized utility connections (Connect My Data)

The cleanest route is a standardized, authorized connection to the utility. The Green Button standard was built for exactly this: a customer authorizes a third party to receive their usage data directly, in a common format. In Ontario this is now a regulatory requirement. Under O. Reg. 633/21, electricity and natural gas utilities had to implement Green Button Connect My Data and Download My Data by November 1, 2023, and 55 Ontario utility platforms have since been certified. Most provide up to 24 months of historical billing and interval data. Once a client authorizes the connection, new reads flow to you without another login.

Green Button downloads (Download My Data)

Where a live connection is not available, the same standard supports a Download My Data XML export. It is less automated, since a person still retrieves the file, but the format is consistent and machine-readable, which removes the transcription step. It is a solid fallback for accounts on smaller utilities or in regions without a mandate.

Bill digitization for legacy and PDF accounts

Plenty of accounts will never expose a clean feed. Older utilities, sub-metered tenants, and water or steam providers often deliver only a PDF or a paper bill. Here the answer is bill digitization: extract every line item (consumption, demand, delivery, rate, taxes, service dates) into structured fields. This is the step where reasoning over the bill structure matters, because two bills from the same commodity can lay out their charges completely differently.

Turning raw data into audit-ready and client-ready outputs

Collection is only half the job. Data from three routes and many utilities arrives in different units, calendars, and rate structures. Before it feeds an audit or a client dashboard it has to be normalized: aligned to consistent units, mapped to a common account and meter model, and validated so obvious gaps and outliers are flagged rather than silently averaged. The payoff is that the same clean dataset can serve an audit workup, a benchmarking comparison, and a monthly client report without re-keying.

Delivery format is where a consulting practice either scales or stalls. If the clean data can leave the platform by API, CSV, or SFTP, it drops into whatever the practice already runs: an audit model, a BI tool, or a white-label dashboard the client sees under the consultant's brand. That is what turns data collection from a per-client chore into a repeatable service line.

Standardize the account and meter model

The detail that makes multi-client data usable is a consistent account and meter model underneath everything. Each utility names its accounts, meters, and rate classes its own way. If those identifiers are not mapped to a common structure at ingestion, every downstream query has to reconcile them by hand, and a client with a meter swap mid-year will quietly break a year-over-year comparison. Mapping once, at the point of collection, is far cheaper than untangling it in every report. Our note on normalizing multi-meter energy data covers the mechanics.

Set a collection cadence that matches the engagement

Not every engagement needs the same refresh rate. A one-time audit needs a clean historical pull, ideally a full baseline year or two. An ongoing benchmarking or reporting retainer needs new reads every cycle without a person fetching them, which is where authorized connections earn their keep. Deciding the cadence per client, and matching the collection method to it, keeps the practice from over-engineering a one-off audit or under-serving a recurring account.

Build versus buy for a consulting practice

Some firms try to build the collection layer themselves, wiring up utility connections and a bill parser in-house. It is doable, but it becomes a software product the firm now has to maintain: new utility formats, changing portals, and validation edge cases never stop arriving. Most practices are better served treating acquisition and cleaning as infrastructure and spending their differentiated hours on analysis and client advice. If you are weighing that tradeoff, our note on build versus buy for utility data management walks through the real maintenance cost.

The same clean feed also supports the measurement work that retrofit and savings programs depend on, which we cover in measurement and verification data for retrofit programs.