01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Use case · Utility metering and analytics
Spot leaks, high usage, and seasonal drift before the owner meeting.
Benchmark utility usage, detect high-usage alerts, compare seasonal performance, and route utility anomalies into property workflows.
Use-case proof path
Every use case should show the route from trigger to reviewed outcome.
Utility metering and analytics is framed with personas, trigger, preset workflow, proof, related modules, and a screenshot destination when one is available.
Inspect proof Open demo02
Proof
Screenshot, proof card, or demo path that makes the claim inspectable.
03
Boundary
What requires human review or source evidence.
Personas
Who opens this workflow.
property managerestate managerowner teamfield lead
Trigger
The operating moment.
Water, electric, gas, or HVAC usage changes materially, or monthly reporting needs context.
Preset
The concrete product starting point.
Utility analytics preset with meter source, baseline, seasonal comparison, anomaly threshold, field check, vendor task, and owner-safe note.
Workflow proof
Utility metering analytics
usage benchmark, high-usage alert, field follow-up.
Open screenshot boardProblem
property manager need one reliable intake path.
Water, electric, gas, or HVAC usage changes materially, or monthly reporting needs context.
Solution
A preset workflow that can be launched without a heavy rollout.
Utility analytics preset with meter source, baseline, seasonal comparison, anomaly threshold, field check, vendor task, and owner-safe note.
Outcome
IoT/property health fixture.
Benchmark utility usage, detect high-usage alerts, compare seasonal performance, and route utility anomalies into property workflows.
Workflow
From trigger to reviewed outcome.
- 01
Import, enter, or attach utility readings and bills.
- 02
Compare against prior period, prior year, weather, occupancy, and property baseline.
- 03
Flag leak, equipment, irrigation, pool, HVAC, or billing anomalies.
- 04
Route a field check or vendor packet with evidence requirements.
- 05
Add reviewed explanation to owner report or property readiness history.
Proof
What a buyer can inspect in demo or docs.
- IoT/property health fixture.
- Reporting chart gallery.
- Owner-safe anomaly summary with no guarantee language.
Related product areas
Where the workflow lives.
Product proof
Use-case workflow proof
A buyer can see the operating moment become a reviewed, owner-safe next step.
Blocked outputslive dispatch · owner approval writeback · provider writeback · customer screenshot publication
- Embed supports desktop and 390px mobile layout without horizontal scrolling.
- Copy names fixture-backed proof and avoids promises of live automation.
- Every frame has an explicit reviewed or local-only posture.
property_manager viewStatic view
01 / 04
Trigger
Service preset or owner request opens a synthetic workflow.
A buyer can see the operating moment become a reviewed, owner-safe next step.
Safe sample scenario · illustrative operational state only.
Boundary
Use cases explain workflows; they do not bypass governed operations.
Use-case pages describe controlled product workflows, presets, and reviewed proof paths. They do not dispatch vendors, send legal notices, approve payments, change reservations, monitor alarms, or create accounting records without the governed product surface and account entitlements.
Pilot access
Show the platform through one real operating story.
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
Recommended demo path
- Owner submits a winter maintenance concern.
- Manager reviews urgency, access, and authority.
- Vendor receives only the package-local scope.
- Field evidence becomes a reviewed owner update.
We respond with the recommended demo route, who should attend, and what production access would require.