Personal usage trends
Make authorized unit data readable across recent periods and personal baselines.
Optional resident add-onUseful utility insight,
Useful utility insight,
one unit at a time.
Where authorized unit-level metering is available, a focused resident experience can help occupants understand personal patterns and take practical action.
Building analysis comes first; resident access is evaluated separately.
My utility viewUnit 1204 · June
Personal usage trendWithin range
82Compared with your recent baseline
ElectricityShift flexible use after 11 p.m.
WaterNo unusual change detected
Seasonal noteCooling demand increased this week
Only authorized unit data is shown. Building comparisons are aggregated.
Why a resident layer
Building visibility for management. Personal clarity for residents.
Building-level analysis helps management understand overall performance. An optional resident layer can translate authorized unit data into a simpler view of personal trends, unusual changes, and relevant opportunities.
Management viewPortfolio, building, utility, and operational priorities.
Resident viewOnly the personal or aggregated information authorized for display.
Resident experienceSimple enough to use.
Simple enough to use.
Specific enough to matter.
The experience is designed around decisions a resident can understand and influence—not an operations dashboard reduced to a smaller screen.
Meaningful changes
Surface notable personal changes without overwhelming residents with technical detail.
Rate-plan guidance
Explain lower-cost electricity periods where supported plans and interval data apply.
Bill understanding
Explain common usage and billing factors in clear, resident-friendly language.
Possible water signals
Show personal water patterns only where authorized submeter data supports the view.
Practical guidance
Offer relevant conservation opportunities shaped by the data that is actually available.
Data readinessCapability follows
Capability follows
the available meter data.
Not every building can support every resident feature. The add-on should match the utility type, authorization, and level of data actually available.
Electricity
Often the strongest starting point
Unit-level billing or smart-meter access may support personal trends and time-based guidance.
- Personal usage history
- TOU or ULO guidance where applicable
- High-usage period review
- Recent-baseline comparison
Water
Available when units are submetered
Authorized unit-level water data may support personal trends and possible abnormal-use indicators.
- Personal water trend
- Recent-period comparison
- Possible unusual-use indicator
- Conservation guidance
Gas & heating
Often shared at building level
When heating is central, resident information may focus on building-level trends and education.
- Seasonal explanation
- Weather-informed communication
- Building trend education
- Unit support where available
Privacy-conscious by design
Resident utility information must stay in the right hands.
Resident features should use only authorized data, avoid exposing another unit or occupant, and rely on aggregated comparisons where a benchmark is appropriate.
No unit-to-unit exposureResidents do not see identifiable information from another home.
Authorized access onlyCapabilities follow approved data access and building permissions.
Purpose-limited viewsShow only what supports the intended resident experience.
Aggregated comparisonUse grouped information when a building benchmark adds value.
A staged rolloutProve building value.
Prove building value.
Then evaluate resident access.
The resident add-on is a later capability, introduced only where suitable data, authorization, privacy, and practical value are confirmed.
Building pilot
Validate core utility analysis and management reporting for one property.
Data & permission review
Confirm unit-level availability, authority, and appropriate use.
Resident experience
Introduce only the capabilities the building can support responsibly.
Not required for the core platform. Building-level Utility AI can deliver value without a resident rollout.
Begin at the building level
Request pilot Explore resident value in the right order.
Request a core building pilot first. Unit-level data and resident capabilities can be reviewed later when they are relevant.