Effective water monitoring combines two things: reliable visibility into the monitored tanks and clear ownership of what happens when the system reports something unusual.
In a housing society, the people who see a dashboard are not necessarily the people who inspect equipment. The committee may oversee the service, facility staff may investigate conditions and residents may need timely, verified updates. If these responsibilities are left implicit, a delivered alert can still go unanswered.
A workable monitoring process assigns ownership before an incident occurs. Maintain a responsibility register for primary and backup alert recipients, technical investigation and resident communication.
Start with the three kinds of responsibility
First is monitoring ownership. Someone needs to check that the configured alerts reach an actively maintained recipient and that the monitoring feed is current.
Second is operational response. Someone needs authority to review the relevant tanks, coordinate approved physical checks and escalate a water-system problem to qualified personnel. The operational escalation path should connect to the society’s water-supply incident response procedure.
Third is communication. Someone needs to tell the committee or residents what has actually been verified, without converting an early indicator into an unsupported claim.
One person may hold more than one role in a small property. In a large society, the roles may be divided across the facility manager, technical team and committee. The key is to name the responsible people rather than assuming that everyone who received the email will respond.
Separate a level alert from a data alert
A configured low-level email alert means the monitored reading reached the relevant threshold. It is a reason to review the tank and the site's supply context. It does not independently prove a pump failure or establish exactly when residents will lose water.
A telemetry-freshness alert is different. It means the software has not received input for a configured period. The last-known value is not confirmation of the tank's current physical condition.
These alerts may require different first actions. A level alert calls for water-system assessment; a missing-data alert calls for monitoring-path troubleshooting and, where needed, an independent physical check. Both need an assigned owner.
TownEve supports configured email alerts and telemetry-freshness alerts. The society can build its escalation process around the channels commissioned for the deployment and assign a clear primary and backup responder.
Design an escalation path, not just a mailing list
An alert can be delivered successfully and still fail operationally if its recipient is unavailable. Decide who is primary, who is the backup and when an unresolved observation should be escalated.
The escalation path should be proportionate to the property's procedures and the condition involved. A low-level condition on a relevant supply tank may require a different response from a nonurgent question about an estimated volume display.
The facility team should know how to reach the technical person responsible for the water system and the support contact for monitoring equipment. These may be separate providers.
Do not assign residents responsibility for electrical, mechanical or other specialist intervention merely because they can view a tank level.
Give every tank an unambiguous identity
An alert that says “Tank 2” may be hard to act on when a society has several towers, underground tanks and water types.
Use a naming convention that identifies the actual location and purpose. Drinking, domestic and recycled-water systems should remain distinct. The same identifier should appear in the application, tank inventory, installation record and incident log.
The recipient should be able to identify the physical asset without guessing which tank the message refers to.
Define the first response to a low-level alert
A practical first response is to confirm the tank identity and reading timestamp, review the historical trend and check relevant upstream or related tanks where monitored.
The facility team can then follow the property's approved process to verify physical conditions and investigate the water-supply arrangement. The record should distinguish what the chart showed from what the team independently confirmed.
TownEve's historical readings provide context for investigation and escalation. Direct pump-state monitoring and remote pump operation are being developed as separate layers that can add equipment-specific context and control as they are validated.
Define the first response to stale data
When a reading stops updating, check which tank feeds are affected. One affected tank may suggest a different investigation path from an entire tower or multiple towers becoming stale.
TownEve's architecture uses tower-level modules communicating by RF with one society-level master, which uploads readings through an internet connection. Depending on the affected scope, the technical team may investigate the sensor, local power, RF communication, master or internet path.
This investigation sequence helps the team narrow the problem while preserving independent verification for urgent physical conditions. TownEve hardware can retain up to 150 readings during a connectivity interruption and upload retained readings after connectivity returns. At the fixed 30-second reporting cadence, a full buffer represents up to approximately 75 minutes when the hardware remains powered and all 150 entries are retained. Remote readings are not live during the interruption.
Give the committee a defined oversight role
The committee may need visibility into repeated incidents, alert-response gaps, unresolved support issues and decisions about system expansion.
That does not require every committee member to receive every technical alert. Too many recipients can obscure accountability if each assumes someone else is responding.
A short periodic review can summarize meaningful incidents, verified causes, actions taken and outstanding follow-ups. Keep operational response with the people authorized to perform it.
TownEve supports role-based access. The society should configure access to match its actual governance rather than equating viewing permission with authority to operate equipment.
Decide what residents need to know
Residents may benefit from access to relevant tank-level information and from clear updates when a supply issue is verified. But a dashboard reading and a service announcement are not the same thing.
A low tank level does not necessarily mean every apartment is without water. A stale reading does not mean the tank is empty. An estimated volume does not by itself establish how long supply will last.
The person responsible for resident communication should state the observed condition, the verified operational impact and the next planned update when appropriate. Avoid publishing unconfirmed causes or guaranteed restoration times.
Keep the resident-facing view focused on information that is useful and appropriate for that audience.
Plan for weekends and staff changes
An alert process that works only when one named employee is on duty is fragile. Record backup contacts and the handover procedure for absences.
When a facility manager, committee representative or support provider changes, review the alert recipients, account access and escalation contacts. Remove access that is no longer appropriate and confirm that the new owner understands the monitoring process.
The tank inventory and operating procedure should remain with the society, not only in an individual's inbox.
Test the process during commissioning
Commissioning should confirm more than sensor readings. Verify the tank names, configured conditions, intended email recipients and the team's understanding of what each alert means.
Where appropriate and safe, demonstrate a level-alert workflow and a missing-data workflow. Ask the recipient to explain the first action and escalation path.
The team should also know how to identify a stale reading in the application. A screen showing the last-known level is not proof of live telemetry.
Document the test results and any unresolved responsibility gaps before the operational handover is considered complete.
Use an incident record that separates facts from assumptions
For each meaningful alert, record the tank identifier, observation time, reading freshness, trend, initial response, independent findings and final action.
“The domestic overhead tank fell below its configured threshold” is a monitored observation. “The pump tripped” is a cause that should be entered as verified only when the facility team has supporting evidence.
This distinction makes later reviews more useful. It also helps prevent an assumption from one incident being repeated as a fact during the next.
Where TownEve fits
TownEve provides contactless level monitoring for suitable overhead and underground tanks, historical trends, configured email alerts, telemetry-freshness monitoring and role-based access.
The technology supplies observations to the people designated by the society. The society's operating process determines who investigates, who escalates and who communicates a verified outcome.
FAQ
Who should receive water-level alerts?
The society should nominate an active primary responder and appropriate backup, based on its facility-management structure and operating procedures.
Should every committee member receive every alert?
Not necessarily. Oversight and operational response are different responsibilities. A defined owner can be more useful than an unstructured distribution list.
Does a low-level alert mean the pump has failed?
No. It indicates a configured level condition. The cause needs investigation and verification.
What should staff do if readings stop updating?
Check the last reading time, investigate the monitoring path and independently verify the physical level if the current condition matters.
Can residents be given access?
TownEve supports a resident-facing experience and role-based access. The society should determine which information is appropriate for residents.
Can an alert automatically turn a pump on?
TownEve currently uses monitoring and alerts to support the operating response. Remote pump operation is a separate development layer being tested for site-specific control.
What should happen when a facility manager leaves?
Review alert recipients, access permissions, escalation contacts and the operating handover so responsibility does not remain with a departed person.