Workflow / From records to action

A clear path from
data to decision.

Start with what the building team already knows. Utility AI organizes the record, connects the relevant context, and shows what the evidence can support.

The initial pilot request does not require utility documents.

The operating path

Five checkpoints.
No black box.

Each stage adds useful context and keeps the source of every important finding visible.

01

Establish the property

Add location, building type, occupancy, major systems, amenities, and known changes.

02

Bring the utility record

Begin with recent bills; add historical, daily, hourly, or interval data when available.

03

Align the context

Connect supported rates, weather, billing periods, baselines, and operating events.

04

Review the evidence

Separate cost drivers, expected variation, and patterns that may deserve verification.

05

Prepare the brief

Present priorities, forecasts, assumptions, confidence, limitations, and next steps.

Progressive data depth

Begin light.
Strengthen the analysis over time.

The platform can create value from a small starting set, then use richer records to improve timing, attribution, and confidence.

StartUseful foundation

Bills + building profile

A focused first review of total usage, cost components, regional context, and known property conditions.

  • Recent utility bills
  • Basic property details
  • Location and providers
ExpandStronger attribution

History + operating context

Add comparable periods, occupancy, systems, maintenance, and retrofit events to explain more of the change.

  • Longer usage history
  • Weather and seasonality
  • Systems and events
DeepenFiner timing

Interval + submeter data

Where authorized and available, higher-resolution records support time-based patterns and deeper review.

  • Hourly or interval use
  • Time-specific signals
  • Authorized unit detail
Evidence model

The conclusion never outruns the data.

A possible anomaly remains a signal for review. Forecasts keep their assumptions. Missing or estimated readings stay visible. The result is useful because its limits are clear.

SourceWhere the observation came from

Attached

FindingWhat the available record suggests

Explained

ConfidenceHow strongly the evidence supports it

Visible

Next stepWhat management can verify or act on

Ranked
What management receives

A review built to move
the conversation forward.

The output separates observed facts, contextual interpretation, and recommended verification steps.

01

Executive summary

Priority observations in concise management language.

02

Cost & usage trends

Separate patterns across relevant utilities and periods.

03

Context review

Relevant rates, weather, conditions, and operating events.

04

Assumptions & confidence

Data limitations and evidence strength made explicit.

Pilot flow

One building.
Four practical moments.

The first step is a fit review. Utility documents are requested later only when relevant and shared through an agreed process.

01

RequestShare the property and business question.

02

ConfirmIdentify the data that would add value.

03

ReviewPrepare analysis and supporting context.

04

DiscussWalk through findings and next steps.

Complimentary pilot

Start with the question that matters most.

Tell us what the building team needs to understand. We will review pilot fit and identify the most useful next data step.

Request pilot