How FlowGuard Works
From first drop to handled incident.
When water hits the floor, most systems stop at the alert. FlowGuard keeps going. We route the alert to the right person, guide the maintenance response, escalate until someone acts, and document every second from detection to resolution.
Built for multifamily teams that need fewer surprises, faster response, and a cleaner record when ownership asks what happened.
For Operators
What property operators actually care about.
“Will my team actually see it?”
The alert has to reach the person who can act. FlowGuard routes the incident to the right maintenance contact and escalates if nobody responds.
“Will they know what to do?”
The action page gives the responder a simple sequence: acknowledge, en route, on site, contained, resolved.
“Can I prove what happened?”
Every step is timestamped. Notes, photos, responder actions, and resolution details become part of the incident record.
“Will ownership have a clean story?”
Instead of explaining a mess after the fact, you have a timeline that shows the team caught it, responded, and contained it.
“Will this make maintenance feel watched?”
No. FlowGuard is not built to embarrass your team. It backs them up and makes their response visible when they do the job right.
The Hero
Your maintenance team is the hero. FlowGuard gives them the playbook.
When water hits at 2am, the person who saves the property is not a dashboard. It is the maintenance tech who gets the alert, gets moving, finds the source, and stops the damage.
FlowGuard is built around that person. The alert lands on their phone. The response page tells them exactly what step comes next. Their actions are timestamped automatically. When the incident is over, the record shows they acted fast and contained the issue.
We do not watch your team. We back them up — and we make sure the record shows the work they actually did.
Incoming…
Live demo — tap the replies. Real responders do exactly this, by text.
The Flow
The response flow is simple on purpose.
Detected
0:00
Alerted
0:00
Acknowledged
0:21
En Route
2:38
Contained
14:11
Documented
14:12
Illustrative incident timeline. Actual response times vary by property, staffing, and severity.
Water detected
Sensors catch water early in high-risk zones.
Alert routed
The right responder gets notified immediately.
Acknowledged
Ownership knows a human has seen it.
En route
The team is moving.
On site
The responder is physically checking the source.
Contained
The water source is isolated or controlled.
Resolved
The incident is closed only after the response is complete.
Report generated
The timeline becomes a clean record for ownership, maintenance review, and insurance conversations.
No Ignored Alerts
An alert that dies on one phone is not protection.
People miss alerts. Phones die. A tech may be asleep, driving, or already handling another emergency. FlowGuard is built for that reality.
If the first person does not act, the alert moves. Tier 1, Tier 2, Tier 3. The system keeps pushing until a human acknowledges and starts the response.
Property managers do not need to wonder if anyone saw the alert. The system shows who acknowledged it and when.
Don’t take our word for it. Trigger the leak yourself — then try to ignore it.
On-call maintenance tech · M. Torres
Tier 1 · rings at T+0:05
Supervisor + backup · D. Reyes
Tier 2 · rings at T+5:00
Property manager · S. Whitfield
Tier 3 · rings at T+10:00
Then try to ignore it. See how far you get.
Demo timings compressed · tiers, contacts, and wait times are configured per property
The Record
The report is not paperwork. It is protection.
After the incident, FlowGuard turns the response into a clean record: detection time, acknowledgement time, containment time, responder actions, notes, photos, and resolution details.
That record helps property managers answer the questions that always come later: Who saw it? How fast did they respond? Was it contained? Were photos captured? What did we learn?
Reports support ownership, maintenance review, and insurance conversations. They are not claim determinations and do not guarantee coverage.
Status
Incident closedResponse time
33m 09s
6
Photo evidence
Tier 1
Escalation
Full
Audit trail
Incident timeline
Maintenance recap
- Source isolated at unit shutoff valve
- Wet-vac on site, area dried
- 6 photos captured and attached
*Modeled estimate based on response timing and zone risk. Illustrative only — not a claim determination, appraisal, or guarantee of avoided loss.
For Leadership
What this gives leadership.
Less guessing
You know whether the alert was acknowledged, who responded, and how long containment took.
Cleaner accountability
The record shows the process without turning maintenance into the villain.
Better renewal conversations
You can show a documented water-risk response program instead of hoping a carrier takes your word for it.
Fewer ugly surprises
Leaks still happen. The difference is how quickly they are caught, escalated, contained, and documented.
A team that looks prepared
The maintenance team gets a system that supports them, and leadership gets a record that proves the response.
The Honest Version
What FlowGuard is not.
FlowGuard is not a camera pointed at your maintenance team. It is not a magic sensor that solves water damage by itself. It is not a vague ‘smart building’ dashboard nobody checks.
It is a response system. It detects water, routes the alert, guides the responder, escalates if nobody acts, and documents the result.
Want to see how this would work on your property?
Book a free water-risk walk. We’ll walk your building, identify the highest-risk water zones, and show how the response path would work for your actual maintenance team.