How it works
Connect what's already there. Inspectr builds the context, runs the work, keeps the right decisions with your team, and gets better from every result.
01 — Connect the building
Inspectr reads the systems, files and field data your buildings already generate. Connectors for the common platforms, plus documents and exports for everything else.
No cleanup project first. No rip-and-replace.
Inspectr works with partial registers, inconsistent naming and gaps in history — and closes those gaps as it runs. Your systems of record stay exactly where they are.
02 — Build the context
Inspectr connects work orders, BMS trends, meters, asset records, manuals, contracts, standards and field evidence — so every agent works from the same building context.
What Inspectr knows
And it keeps getting richer.
Every closeout, inspection, photo and correction adds to that context.
The equipment record builds itself.
Inspectr profiles equipment from the data you already have, then keeps it current as work happens.
What goes in
Photos, work orders, manuals, nameplate data and existing registers.
What comes out
Make, model, serial, capacity, service history, condition and remaining useful life.
Every closeout, photo and inspection keeps the record current.
See how the equipment record gets built→03 — Run the work
An agent picks up a signal, reasons over the full context, and produces work that is ready to act on — not a recommendation to go investigate.
Reactive
BMS
Capital
Output lands where the work already lives — your CMMS, your inbox, your files — with the evidence and reasoning attached.
Complete equipment records from photos and existing data.
Asset-specific PM schedules from equipment data and history.
CapEx plans built from what is installed and what is failing.
Work orders with asset context, likely issues, and scoped job plans.
Structured condition reports and repair plans from photos.
SLA tracking, repeat failures, vendor drift, and cost patterns.
PCAs with lifecycle models and reserve analysis.
Voice and video diagnostics for technicians on site.
04 — Control what matters
You set where autonomy ends. Every agent runs in one of three states, and you can move work between them as trust builds.
Auto
Low-risk, repeatable work runs on its own — enrichment, PM updates, evidence assembly, routine diagnosis.
Review
Consequential changes wait in the Activity Center: capital plans, cost thresholds, anything client-facing.
Escalate
Exceptions, conflicts and low-confidence calls go to a named owner with the evidence already attached.
Approve in the Activity Center and Inspectr writes back to the source system — the work order updated, the PM schedule changed, the file filed. Every action keeps its evidence trail, and the same review works from your inbox or a text message.
05 — Learn from the work
Correct something once and Inspectr carries that judgment forward. There are no rules to write and no configuration project — the reviews your team already does are the training.
Use 18-year useful life for RTUs, not 15
Flag findings over $25K for executive review
Apply regional labor rates instead of national averages
Group reports by building system, not by trade
Route compliance risks to the regional lead
Require approval before changing a capital plan
Every action leaves Inspectr with more building context and more operating knowledge than it had before.
Ask for a view and Inspectr builds the analysis on the spot: electricity against expected, SLA by vendor, out-of-hours load by store. Every chart runs on live building context. Every metric drills into the agent — ask why it moved, get the records behind it.
Which warranties expire this quarter? Which vendor keeps closing jobs without photos? Answers come back with the records behind them, and every deliverable can be pressure-tested the same way.
RTU-02 warranty expires June 18. 3 service events in the last 90 days — worth reviewing open issues before the window closes.
Boiler B-01 warranty expires June 24. No recent failures, but the last PM was marked incomplete.
Elevator controller warranty expires June 29. Vendor documentation is missing from the asset record.
Start from a library of proven workflows, or describe your own. Inspectr turns it into a repeatable process that runs in the background and delivers where the work lives — a digest in your inbox, records updated in your CMMS, a file in the right folder. Approvals stay where you want control.
getting started
Point Inspectr at the data you already have. Usable outputs can start coming back in as little as the first week, with role-specific agents running in the background soon after.
Start with the workflow costing your team the most time or money.
CMMS, BMS, meters, documents or files. No cleanup project first.
Review the output, tune the standard, then move repeatable work to autopilot.
Start with one workflow, connect what's already there, and let the work your team reviews become the standard the operation runs on.