When a housing society has a water-supply problem, residents often receive an announcement only after the facility team has already begun investigating. The announcement may say that water is low or a pump needs attention, but it rarely gives everyone the same picture of what is happening in the tanks.
Shared water-level visibility can improve that information flow. It does not mean every resident should operate equipment or receive every maintenance alert. It means different people can see the information appropriate to their role, while the team responsible for water operations retains responsibility for responding.
What residents actually need to know
A resident's question is usually practical: Is there water in the relevant tank? Is the level changing? Is the displayed information current? Does the society have an update on an interruption?
These are not all answered by one percentage. A tank-level reading describes a measured condition at a point in time. A historical trend adds context. A reading timestamp helps distinguish live information from a last-known value. An operational explanation still requires the facility team to interpret the situation.
For example, a low overhead-tank level may justify an investigation, but it does not by itself establish that the building has run out of water, that a pump has failed or when service will return. Responsible communication should preserve that distinction.
One water system, different responsibilities
A residential property may have a committee, a facility manager, maintenance technicians and residents. Their information needs overlap, but their responsibilities are different.
The facility team needs to identify affected tanks, review trends and follow the site's response procedure. The committee may need a broader view of recurring conditions and whether the agreed operating process is being followed. Residents may benefit from visibility into relevant tank levels without needing access to technical configuration or operational controls.
TownEve currently supports individual accounts, role-based access and a resident-facing experience. A deployment should define which information each role needs, rather than assuming that everyone should have identical access.
A useful resident view is not a pump-control panel
Monitoring and control are separate layers. TownEve's released water-monitoring capability includes live tank levels, historical data and configured email alerts. Direct pump-state monitoring and remote pump operation are in development and testing.
Resident access to tank information should not be confused with authority to start or stop pumps. Any future control deployment requires site-specific electrical integration, safety logic, manual override, fail-safe behavior and commissioning. Operational permissions should be established explicitly.
For current deployments, the most useful resident-facing question is how information can be presented clearly and responsibly, not how many equipment controls can be exposed.
Why the timestamp matters
A dashboard can display a number even when fresh data is not arriving. Without checking when the last reading was received, a user may mistake a historical measurement for the tank's current condition.
TownEve monitors telemetry freshness and can alert the responsible team when the software stops receiving input for a configured period. A missing-data alert means the communication path or device needs investigation. It does not automatically establish whether the problem is internet connectivity, RF communication, power or another component.
A resident-facing explanation should therefore distinguish “last reported level” from a confirmed current reading whenever data is stale. The facility team should investigate the telemetry problem and use appropriate independent checks if a current physical level is needed.
How historical trends help the committee
A committee reviewing an incident needs more than the latest reading. A trend can show when a level began changing, whether the decline or rise continued and what the system recorded before and after the facility team's intervention.
That record can support better questions. Did several tanks show a related pattern? Was the condition visible before the complaint arrived? Was the response procedure clear? Are similar events recurring?
Historical tank levels provide evidence of level changes, not automatic explanations of their causes. A falling tank level cannot, by itself, identify a pump's electrical state. A high level cannot, by itself, prove that physical overflow occurred.
Committees should combine the recorded trend with maintenance observations and the incident log rather than assigning a root cause from a chart alone.
Communicating during a water interruption
When a supply problem occurs, a useful resident update separates three things: the observed condition, the investigation and the next communication.
An example of the observed condition is that a particular monitored tank has been declining. The investigation might involve the facility team checking transfer equipment or incoming supply. The next communication is a commitment to share a verified update after that check.
Avoid turning a plausible explanation into a confirmed diagnosis. Avoid promising a restoration time before the team has verified the cause and response. Monitoring improves visibility, but it cannot create water or eliminate every mechanical or supply failure.
A consistent update process can be valuable even when the society is still using email, notices or its existing resident communication channels. Do not assume that every communication channel is automatically integrated with the monitoring system.
Who receives operational alerts?
Not every user who can view a tank needs an alert each time it crosses a threshold. A configured low- or high-level email alert should reach the person responsible for responding, with a backup and escalation path appropriate to the site.
TownEve's configured email alerts are current production capability. WhatsApp and additional alert channels are in development. Resident-facing access is current, but the society should agree separately on who receives operational notifications and who communicates verified updates to residents.
A practical approach is to define the roles first, then configure monitoring and communication around them. This reduces confusion between visibility, responsibility and authority.
What to decide before launching resident access
Start by naming the tanks and water types in terms residents can understand. A property with drinking, domestic and recycled-water tanks should not present them as interchangeable. Confirm which tank information is relevant to each group of users.
Next, establish how the society will explain stale readings, temporary communication loss and planned maintenance. Decide who answers resident questions about the data and who is authorized to issue an operational update.
Then test the experience with representative users. Can a resident identify the correct tank? Can the facility team distinguish a level alert from a telemetry-freshness alert? Can a committee member understand a historical trend without mistaking it for a diagnosis?
Finally, document the permissions and handover process. Residents, committee members and facility staff change over time. The society should know who administers access and how permissions are reviewed.
Where TownEve fits
TownEve provides contactless monitoring of suitable overhead and underground tanks, live and historical level visibility, configured email alerts, role-based access and a resident-facing experience. Its multi-tower architecture connects tower modules to one society-level master using RF, with the master uploading readings to the application backend.
A site review can establish which tanks to monitor, which user groups need visibility and how the society will respond to alerts and communicate verified updates. The result is a clearer shared picture of the water system without blurring responsibility for its operation.
Frequently asked questions
Can residents view water levels through TownEve?
Yes. A resident-facing experience and individual role-based accounts are current production capabilities. The information available to each role should be configured for the deployment.
Can a resident use the dashboard to control a pump?
The current released product provides monitoring and alerts. Remote pump operation is in development and testing, and operational control requires site-specific safety engineering and permissions.
Does a low tank reading mean residents have no water?
Not necessarily. It describes the monitored tank's level. The facility team must interpret the condition in the context of the property's water system.
Can the committee review what happened before an incident?
TownEve provides historical tank-level data. Those trends can support investigation alongside maintenance records and other site evidence.
What if the displayed reading is old?
Treat it as a last-known measurement, not confirmation of the present level. TownEve can alert the responsible team when telemetry stops arriving for a configured period.
Will all residents receive WhatsApp alerts?
WhatsApp and additional alert channels are in development. Configured email alerts are the current production notification capability; recipients and escalation should follow the society's operating plan.
Does the resident view replace society communication?
No. Tank readings provide information about monitored conditions. Verified incident explanations, maintenance instructions and restoration updates remain operational communications.