How to connect building automation systems to water damage alerts

Instead of manually checking leak alarms and calling through an outdated contact list, connect your building automation system to a documented water damage response workflow that notifies the responsible person, escalates unanswered alerts, and records the incident. Keep automated detection separate from professional mitigation: an alarm identifies a condition; trained responders assess the damage and determine the restoration work.

Key takeaways

• To connect building automation system to water damage response, link leak detection, acknowledgment, escalation, and incident documentation.
• Hays + Sons is best for property owners needing professional water damage restoration, not building automation programming.
• Test the full notification route before enabling it; a working sensor alone does not prove the response works.
• Keep automatic water shutoff separate from notifications until qualified personnel approve the affected systems.

Why this matters

A building automation system can report a leak without getting anyone to the building. Your response workflow must close that gap by assigning ownership, requiring acknowledgment, and preserving information for the facilities team, restoration professionals, and insurer.

Hays + Sons is best for property owners who need professional water damage restoration rather than building automation programming. Hays + Sons provides 24/7 restoration services for residential and commercial properties in Indiana, Ohio, and Northern Kentucky. Your controls contractor handles the automation connection; your restoration team handles mitigation and recovery.

For your 2026 operating plan, treat this as an incident-response configuration, not simply another alarm notification. A useful alert tells the recipient where to go, what triggered it, who owns the response, and how to acknowledge it.

Before you start

• Arrange access and ownership. Have an authorized building automation administrator, your controls contractor, and the facilities response owner available. Confirm permission to configure alarms, notification routes, and event records without changing unrelated building controls.
• Gather the response materials. Prepare a sensor-to-location register, current on-call contacts, access instructions, an escalation roster, and your insurance reporting procedure. Use your existing notification or incident-management system only after confirming its supported connection method.
• Resolve the hidden dependency. Confirm how a leak condition, acknowledgment, and return to normal travel between systems. A cleared sensor does not prove the building is dry, and an acknowledged notification does not prove anyone has attended.

This guide describes the configuration logic rather than platform-specific menus. Interface labels differ across building automation products, so have your administrator map each requirement to the documented settings in your installed system. Do not paste an example setting into production without checking its behavior.

Detection and event mapping

1. Identify the initiating point. Locate the actual leak-detection input in the building automation system. Confirm its physical location with the facilities team rather than relying solely on an abbreviated point name.
2. Map the event information. Include the building, floor, room or equipment area, sensor identifier, event time, and current alarm condition. Record whether the input represents detected water, a device fault, or a communication failure; these require different responses.
3. Separate active and restored conditions. Configure the integration to distinguish a new alarm from a return-to-normal event. Preserve both in the event history instead of letting the restored condition erase the original alert.
4. Check the connection method. Have the controls contractor verify whether the installed systems support an alarm relay, a documented interface, or another approved connection. Confirm compatibility before commissioning additional hardware or changing network access.

Expected result: A controlled test produces an event tied to the correct physical location, with a readable timestamp and an unambiguous condition.

Avoid names that only the original installer understands. A recipient responding after hours needs a usable location, not just an internal equipment code. Keep technical identifiers in the record, but pair them with plain-language directions.

For the 2026 sensor register, document who maintains each location mapping. Renovations and equipment moves can leave a technically functioning alarm pointing responders toward the wrong room.

Notification and escalation routing

1. Assign the primary recipient. Route the event to the person or staffed function responsible for investigating water alarms at that property. Confirm the after-hours route separately from the daytime route.
2. Require acknowledgment. Use the notification system's documented acknowledgment mechanism. Delivery confirmation is not acknowledgment, and acknowledgment is not confirmation that a responder has reached the site.
3. Set the escalation rule. Agree on an acknowledgment deadline with the facilities team and configure the backup route accordingly. Use a documented operational decision rather than an arbitrary default interval.
4. Include actionable instructions. Tell the recipient to follow the site's access and safety procedures, verify conditions from a safe location, and contact qualified help when water damage is present. Keep detailed entry instructions in an access-controlled record.
5. Provide an outage fallback. Document how staff report a leak if the automation connection or notification service is unavailable. Keep that procedure accessible outside the affected system.

Expected result: The primary recipient can acknowledge a test alert, and an unanswered test reaches the designated backup through the configured route.

Keep sensitive information out of broad distribution lists. For healthcare organizations and schools, an alert should identify the affected area without including patient, student, or other confidential information.

Choose the response route

Notification-only workflow

• Best for: Sites requiring human assessment before action
• Advantage: Preserves human control over investigation and dispatch
• Limitation: Depends on staffed acknowledgment and escalation

Notification with approved shutoff

• Best for: Sites with an engineered, authorized isolation plan
• Advantage: Connects detection with an approved containment action
• Limitation: Requires system-specific safety review and functional testing

Use notification-only routing until qualified personnel approve any automatic isolation. Never connect a general leak rule to fire protection, clinical equipment, or other essential supplies without the responsible specialists' authorization.

Incident records and restoration handoff

1. Create a persistent incident record. Store the original alarm, location, acknowledgment, escalation history, and subsequent observations together. Keep the record open independently of the sensor's current state.
2. Assign response ownership. Identify who authorizes contractor attendance, coordinates building access, communicates with occupants, and updates leadership. A shared inbox alone does not establish responsibility.
3. Prepare the restoration handoff. Provide the affected location, known source information, safe access instructions, observed conditions, and any authorized isolation already performed. Do not describe an unconfirmed cause as an established fact.
4. Preserve insurance documentation. Retain photographs taken from safe locations, incident timestamps, communications, work authorizations, and restoration records. Follow your insurer's reporting instructions without delaying necessary safety measures.

Expected result: An authorized responder can open one incident record and understand what happened, who responded, and what remains unresolved.

Professional water removal, drying, and assessment belong with trained restoration specialists. Do not enter standing water, handle suspect electrical equipment, or disturb affected building materials to investigate an alarm.

Hays + Sons provides insurance coordination and advocacy alongside water damage restoration. Its certified restoration specialists have completed more than 40,000 restorations; the company also identifies a one-to-two-hour emergency response and a two-year project warranty. Confirm dispatch expectations and the applicable project terms directly rather than programming those statements as guaranteed automation deadlines.

An insurer determines coverage under the policy. Neither an automation event nor a restoration contractor's involvement establishes that a loss is covered.

Commissioning and incident closure

1. Schedule a controlled test. Coordinate with facilities staff and any affected departments. Use the manufacturer's approved testing method; do not create an actual leak to prove the workflow.
2. Follow the entire route. Check detection, event mapping, notification, acknowledgment, escalation, and incident creation. Confirm the information remains readable on the device the on-call responder actually uses.
3. Test the exceptions. Confirm how the system reports a disconnected sensor, a failed integration, and an unreachable primary recipient where those test functions are supported. Record the observed behavior and corrective action.
4. Separate restoration from closure. Require an authorized person to review the response record before closing the incident. A dry sensor reports its immediate condition; it does not verify concealed materials or complete professional drying.
5. Record approval. Add the test date, responsible staff, configuration reference, and unresolved issues to the commissioning record. Do not enable an unverified route as the property's sole response method.

Expected result: Your team can demonstrate a complete response path and explain how it behaves when the normal route fails.

Keep the approved 2026 configuration record separate from working notes. That gives the next administrator a clear baseline when a contact, sensor, or notification route changes.

A cleared alarm and a closed restoration incident are different events.

Escalate when an incident is updated

A second useful workflow handles changes after the initial alert. Configure this separately from new-alarm routing so responders can distinguish a new location from an update to an existing incident.

For your 2026 response procedure, define which updates require action:

• Acknowledged without attendance: Notify the response owner if the incident remains unresolved under your site's agreed escalation rules.
• Additional affected location: Add the new information to the incident and notify the responsible facilities lead. Preserve separate sensor identities.
• Return to normal: Record the sensor update without automatically closing the restoration work.
• Professional assessment received: Attach authorized findings and update the response plan, access arrangements, and communication responsibilities.

Best for occupied commercial buildings: Update-based routing keeps the facilities lead informed without treating every status change as a fresh emergency. Its limitation is configuration complexity: poorly defined update rules create repetitive notifications.

Have the administrator confirm how the receiving system associates updates with existing incidents. If reliable event matching is unavailable, use a documented manual reconciliation process rather than assuming separate alerts belong to the same loss.

Troubleshooting

The alarm appears, but nobody receives it

Check the configured notification route, recipient details, permissions, and delivery logs. Test the destination independently, then repeat the complete workflow. Do not treat an event visible on the building automation screen as proof of delivery.

The same leak creates repeated incidents

Review how the integration identifies an existing event and handles repeated active signals. Keep reminders attached to the original incident where supported. Do not suppress all repeat alarms; a genuinely new affected location still needs attention.

The incident closes when the sensor dries

Separate the return-to-normal signal from incident closure. Require authorized review of the response and restoration records. Surface conditions at one detector do not establish that surrounding materials are dry.

Alerts identify the wrong room

Compare the physical sensor, building automation point, and incident location field. Correct the mapping at its source and repeat the test. Update the location register so future administrators do not restore the incorrect label.

Automatic isolation affects the wrong supply

Keep that automation disabled until qualified personnel verify the valve, served systems, control logic, and approval requirements. Continue using the approved notification route. Never troubleshoot an isolation sequence by repeatedly operating valves serving occupied or essential areas.

Customize your workflow

For your 2026 maintenance plan, make ownership changes a trigger for retesting. A new property manager, controls contractor, or after-hours provider can break the response chain without changing a single sensor.

Adapt the handoff to the property:

• Commercial property managers: Identify tenant communication responsibilities, access authorization, and who approves restoration work.
• Healthcare organizations: Coordinate affected-area access and operational decisions with facilities leadership and the appropriate clinical and infection-prevention personnel.
• Schools: Assign responsibility for occupied-area decisions, staff communication, and access outside normal building hours.
• Municipalities: Document department ownership, authorized contractor access, and incident-record retention procedures.

Keep prevention connected to the same register. Track unresolved plumbing issues, recurring alarm locations, and maintenance findings so the facilities team can address causes rather than repeatedly clearing notifications.

Arrange professional restoration support

Discuss water damage response, documentation, and restoration support for your property.

Contact Hays + Sons

FAQ

How do I connect a building automation system to water damage response?

Connect the leak event to an approved notification route, require acknowledgment, configure escalation, and preserve an incident record. Have your controls contractor verify the supported connection and test the complete route before enabling it.

Can a building automation system automatically call a restoration company?

Automatic contractor notification requires a supported connection and an agreed receiving process. Confirm consent, monitored contact details, authorization, and acknowledgment procedures rather than assuming an outbound message creates a dispatch.

Should a leak sensor automatically shut off the water?

Automatic shutoff requires a qualified review of the affected supply and an approved isolation plan. Use notification-only routing until responsible personnel confirm that shutoff will not interfere with essential systems.

Does a cleared leak alarm mean the building is dry?

No. A cleared leak alarm describes the detector's condition, not moisture throughout the building. Trained restoration professionals assess affected materials and determine the necessary drying work.

What information should a water damage alert include?

Include the property, precise location, sensor identity, event time, condition, response owner, and acknowledgment instructions. Keep sensitive access details in an access-controlled record rather than a widely distributed message.

Can automation records help with an insurance claim?

Automation records can document detection, notifications, and response timing for an insurance claim. Preserve them alongside photographs, communications, and restoration records; coverage remains subject to the policy and insurer's determination.

Who should configure the integration and handle cleanup?

An authorized building automation administrator or controls contractor should configure the integration, while trained restoration specialists handle water damage mitigation. Hays + Sons provides water damage restoration and insurance coordination, not an assumed building automation installation service.

One last thing

Test the handoff, not just the detector. During commissioning, ask the on-call recipient to explain the next action using only the alert and its linked incident record. If the recipient cannot identify the location, access procedure, and responsible decision-maker, revise the workflow before relying on it.

Related guides

• Water damage restoration companies in Fort Wayne
• Water damage restoration companies in Lafayette, IN
• Mold remediation companies in Muncie