Monitoring the Archdiocese of Baltimore portfolio

Why monitor buildings without daily occupants?

A building still needs oversight when it is vacant. Plumbing, heating, and building conditions continue to matter even when there is no resident or staff member nearby to notice a change. For an operator responsible for several properties, a scheduled visit is only one part of understanding what is happening on site.

The University of Maryland reported in November 2025 that SenseGuard began after a connection at the Archdiocese of Baltimore raised the need to monitor unused buildings. That account describes temperature, humidity, and water-presence sensors communicating across multiple buildings.

Sources: University of Maryland: CS Majors Launch Platform to Protect Vacant Properties

Three conditions across multiple sites

The Archdiocese pilot covers water, temperature, and humidity. Together, these readings give the operator different ways to notice an environmental issue: water at a monitored location, a temperature moving beyond the chosen limit, or humidity that warrants investigation.

The readings belong in the same operating view. SenseGuard brings site information into a web and mobile dashboard, with threshold alerts delivered through the configured notification channels. The purpose is practical: connect a reading to a location and give the responsible team information they can act on.

What SenseGuard reports from the pilot

SenseGuard reports over six figures in damages caught during the Archdiocese pilot. The $100k+ figure on our site expresses the floor of that reported result. It is not a per-building return, an insurance payout, or a promised outcome for another property.

The public account does not include an incident-by-incident cost breakdown or an independent loss valuation. We therefore describe the result as company-reported damages caught. The University of Maryland separately confirmed the active pilot and design-partner relationship in its May 2026 Demo Day coverage; that article does not validate the dollar figure.

Sources: University of Maryland: Fifth Annual Mokhtarzada Hatchery Demo Day

What another portfolio can take from this

The useful starting point is the coverage question: which rooms or buildings are least likely to produce a quick human report? Build a candidate list from those locations, then decide which conditions need a sensor and who will respond to an alert.

For a new deployment, we recommend documenting the site name, monitored location, reading, threshold, and responsible contact together. Agree on the response before the first alert arrives. This is planning guidance for an operator evaluating monitoring, rather than a claim about the Archdiocese team’s internal procedures.

Start with the buildings you manage

A SenseGuard demo can start with your portfolio: vacant units, mechanical rooms, storage areas, and other locations where a missed condition matters. We can discuss sensor coverage, installation, dashboard access, and alert thresholds against that list. The pilot offers a documented example of multi-site monitoring; your deployment should be planned around your own buildings and response team.