--- title: Water Tank Monitoring Handover Checklist for Housing Societies description: Use this society water-monitoring handover checklist to document tanks, alerts, access, commissioning evidence and ongoing responsibilities. --- [Skip to content](https://www.towneve.com/resources/water-monitoring-handover-checklist#main) [![TownEve](https://www.towneve.com/hs-fs/hubfs/raw_assets/public/Towneve-Theme/assets/logo.png?width=164&height=70&name=logo.png)](https://www.towneve.com/) Menu - [Water Management](https://www.towneve.com/water-management) ⌄ - [How It Works](https://www.towneve.com/resources/how-it-works) - Solutions ⌄ - [For Builders](https://www.towneve.com/resources/builder-water-monitoring) - [Resources](https://www.towneve.com/resources) ⌄ - [Case Studies](https://www.towneve.com/resources/tag/case-studies) - [About](https://www.towneve.com/about) - [Contact](https://www.towneve.com/contact) [Log in](https://water.towneve.com)[Request an Assessment](https://www.towneve.com/contact/) 1. [Home](https://www.towneve.com/) 2. [Resources](https://www.towneve.com/resources) 3. Water Tank Monitoring Handover Checklist for Housing Societies [Guides](https://www.towneve.com/resources/tag/guides) # Water Tank Monitoring Handover Checklist for Housing Societies TownEve Editorial Team · September 28, 2026 Installing a water-monitoring system and handing it over are different milestones. An installation can show readings on a screen while the society still lacks a clear answer to basic questions: Who receives alerts? Which tank does each label represent? Who investigates missing readings? What happens when the facility manager changes? A good handover turns a working installation into an operating process that the next committee or maintenance team can understand. This checklist focuses on the records, responsibilities and demonstrations a housing society should retain after commissioning. 1\. Receive an agreed tank inventory The handover record should identify each monitored tank, its location, tower, water type and operational purpose. Where a society has separate drinking, domestic and recycled-water storage, the labels should make those distinctions unmistakable. Record the configured tank dimensions or volume model and any relevant assumptions. If the displayed volume is an estimate based on geometry, identify the reference measurements used. The inventory should distinguish monitored tanks from tanks outside the agreed scope. Ask the installer to walk the facility team through the inventory while showing the corresponding records in the application. A name that seems obvious to the installation team may not be obvious to a replacement facility manager. 2\. Keep the installed system diagram For a multi-tower deployment, a diagram should show how tank sensors connect to the relevant tower equipment, how tower modules communicate with the society-level master and how the master reaches the application backend. TownEve's current architecture uses a slave module per tower, RF communication to one society-level master and an internet connection from that master to the backend. The handover should identify actual equipment locations and power arrangements, not just a generic architecture picture. Document any site-specific RF coverage considerations and which person or supplier is responsible for the internet connection. The diagram is especially useful when several tanks stop reporting at once and the maintenance team needs to distinguish a shared path from a local tower issue. 3\. Demonstrate the readings and their meaning A handover should include a live walkthrough of the relevant tank views. Show how to identify a tank, read its current level, check the measurement timestamp and review its historical trend. Explain how level and estimated stored volume differ. A percentage may represent the configured operating range or tank geometry; the facility team should know the convention used for its deployment. A change in stored volume is not automatically a measurement of consumption when inflow and outflow occur together. The team should also understand the difference between a fresh measurement and a last-known reading. If telemetry stops arriving, the most recent value should not be treated as confirmation of the tank's present condition. 4\. Transfer alert settings and response ownership List the configured level conditions for each tank and the email recipients responsible for them. Include a backup contact and the society's escalation procedure. A generic instruction to “watch the dashboard” is not an alert-response plan. Demonstrate the difference between a low-level condition, a high-level condition and a telemetry-freshness problem. The first two describe monitored water levels. A freshness alert means the software has not received input for a configured period and the monitoring path needs investigation. TownEve provides configured level-based email alerts and telemetry-freshness monitoring. The handover should document the notification channels actually commissioned at the property, their recipients and the response process attached to each alert. Record who is authorized to change alert settings and how the committee approves material changes. If the operating pattern changes, thresholds may need to be reviewed against actual tank behavior. 5\. Establish accounts and role responsibilities Identify the society's administrator or designated account owner, the facility team, relevant committee members and any resident-facing access group. Confirm that each group sees the information appropriate to its role. TownEve supports individual accounts, role-based access and a resident-facing experience. The handover should document the agreed role assignments and the process for adding or removing people when staff, residents or committee members change. Do not put passwords into the handover document. Record the authorized account-management procedure and support contact instead. The aim is continuity of access without creating a new security risk. 6\. Preserve commissioning evidence The society should retain a record of what was tested and accepted. Relevant checks include correct tank identification, plausible levels at independently verified operating points where feasible, historical trend visibility, alert delivery and the ability to recognize missing telemetry. For multi-tower sites, record the RF coverage checks performed at the actual installation locations. For tanks with complex geometry, retain the assumptions used to estimate volume. Note any exceptions, deferred work or tank locations that require a follow-up assessment. A completed checklist is more useful when it includes the observed result, date, responsible person and unresolved issue, rather than only a tick mark saying “tested.” For each unresolved item, record the responsible person, corrective action and evidence needed for closure. 7\. Define the first response to missing data A missing-data alert is not a diagnosis of an internet outage. The facility team should know how to identify the affected tanks and their last reading times, then follow the approved troubleshooting path. A shared loss of readings may warrant checking the society-level master, its power and its internet connection. A single affected tower may warrant checking the tower module, sensor, power and local RF path. These are investigation clues, not automated root-cause conclusions. TownEve hardware can retain up to 150 readings during a connectivity interruption and upload retained readings after connectivity returns. The handover should document the fixed 30-second hardware reporting cadence, demonstrate the freshness alert and reconnection behavior, and explain that remote visibility is not live while the connection is unavailable. A full buffer represents up to approximately 75 minutes at the fixed cadence, provided the hardware remains powered and all 150 entries are retained. 8\. Document the equipment and support boundaries The handover should identify installed equipment, the agreed support contact and the process for raising a service request. Clarify who provides physical access to tanks and equipment, who performs qualified electrical work and who owns the property's connectivity arrangement. Keep warranty, maintenance and replacement terms with the commercial record. Do not assume that software subscription, connectivity, hardware warranty and post-warranty care all cover the same work. The signed proposal and service agreement should govern the actual scope. If a site-specific integration or future capability was discussed during sales, list it separately from the released, accepted installation. TownEve's external integrations are custom-scoped, and its pump-control layer is in development and testing. A roadmap discussion is not a commissioned feature. 9\. Rehearse an operating scenario Before signing off, ask the facility team to walk through an example. A tank crosses a configured low-level condition. Who receives the email? Who checks the current timestamp and historical trend? Who investigates the water system? Who communicates a verified update to residents? Run a separate example in which readings stop arriving. Who checks whether the issue is local or widespread? What independent level check is available if the water condition is urgent? Who contacts support? These rehearsals test whether the handover has transferred practical knowledge, not merely access to a dashboard. Any gaps should become named follow-up actions. 10\. Make the handover usable after people change A society committee and its facility staff may change while the monitoring installation remains in service. Keep the tank inventory, system diagram, alert register, access procedure, commissioning record and support details in the society's designated records location. Review ownership whenever a facility manager, committee representative or support arrangement changes. Confirm that alert recipients and account access still match current responsibilities. Retire obsolete contacts so notifications are not silently routed to people who no longer respond. The best handover document is not the longest one. It is the one a new authorized operator can use to understand the system, recognize an abnormal condition and find the right person to act. What TownEve can demonstrate at handover TownEve combines contactless monitoring of suitable overhead and underground tanks with live and historical levels, configured email alerts, role-based access, a resident-facing experience, geometry-based stored-volume estimates and telemetry-freshness monitoring. A deployment handover should show the features actually commissioned at that property and give the operating team a clear record of how monitoring, alerts, access, connectivity and support work together at that site. For a society planning a deployment, agreeing on handover requirements before installation helps the committee compare the proposed operational scope and makes commissioning easier to verify. FAQ What documents should a society receive after installation? At minimum, retain a tank inventory, installed-system diagram, accepted configuration and alert contacts, account-access procedure, commissioning results and support terms appropriate to the deployment. Should residents receive the same access as maintenance staff? Access should reflect responsibilities. TownEve supports a resident-facing experience and role-based accounts, while technical operations remain with the designated team. Does a dashboard reading prove that a pump is running? No. Tank-level data alone does not establish a pump's electrical state. Direct pump-state monitoring is in development. What if an alert recipient leaves the society? The authorized account or operations owner should update the recipient and escalation records as part of staff or committee handover. Can the society assume missed readings are stored during an internet outage? TownEve hardware can retain up to 150 readings and upload retained readings after connectivity returns. The time represented by that buffer depends on the fixed 30-second hardware reporting cadence, so the expected resilience should be verified during commissioning. Does commissioning mean every future outage will be prevented? No. Monitoring improves visibility and supports response, but water availability also depends on supply, equipment and human operations. Who should sign off the handover? The society should designate its authorized operational and commercial representatives under its own governance process. Technical acceptance should be informed by the people responsible for operating and maintaining the installation. Explore further ## Understand your water system. Plan the next step. Browse more practical resources or discuss your property's monitoring needs. [Request a Water Monitoring Assessment](https://www.towneve.com/contact/)[All resources →](https://www.towneve.com/resources) TownEve · CyberGrove Solutions Private Limited Water monitoring for residential communities. [About](https://www.towneve.com/about/)[Contact](https://www.towneve.com/contact/)[Privacy](https://www.towneve.com/privacy/)[support@towneve.com](mailto:support@towneve.com) ​ ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "TownEve Editorial Team", "url" : "https://www.towneve.com/resources/author/towneve-editorial-team" }, "dateModified" : "2026-10-04T15:48:41.835Z", "datePublished" : "2026-09-28T17:52:32.000Z", "headline" : "Water Tank Monitoring Handover Checklist for Housing Societies", "mainEntityOfPage" : { "@id" : "https://www.towneve.com/resources/water-monitoring-handover-checklist", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.towneve.com/hubfs/TownEve%20logo%20(1).png" }, "name" : "TownEve" } } ```