A rainwater system handover checklist should start before installation. The practical aim is simple: the receiving team must be able to identify the installed assets, find the current records and understand who deals with each open issue. A folder of product brochures alone cannot answer those questions.
This guide is for developers, project managers and facilities teams preparing to take over a modular underground system. It focuses on information and coordination. The project designer, relevant authority and appointed operator must establish the actual inspection, commissioning and acceptance requirements.
Define what the operator is taking over
Begin with a short system description agreed by the project team. Does the installation retain rainwater for reuse, control discharge, or support infiltration? Which equipment and external connections belong to the package? A product name does not describe the whole installation.
Leiyuan’s underground rainwater tank range includes modular components used within a wider water-management design. The final arrangement also depends on the specified containment, connections and site conditions. Therefore, the handover record should identify the installed configuration, rather than repeat a generic catalogue description.
Write the scope in terms the next team can follow. For example, distinguish the storage structure from separately supplied pumps or controls. If a landscape contractor maintains the surface while another contractor services equipment, record that boundary explicitly.
Build a rainwater system handover checklist around records
CIRIA’s SuDS adoption handover checklist brings together asset information, maintenance records and a condition review. It includes as-constructed information and a maintenance plan. It also recognises that phased construction can require separate handovers. These are useful organising principles; the project’s own agreement determines what must be submitted and accepted.
For day-to-day document control, use a compact index such as the example below. The entries are a suggested working format, not a completed project record.
| Record | Useful reference | Question to close |
|---|---|---|
| Installed layout | Drawing number and revision | Does it match the handed-over area? |
| Asset list | Unique asset code | Can the operator locate each item? |
| Product documents | Model and document version | Are these for the supplied components? |
| Operating records | Procedure or report reference | Who maintains and updates it? |
| Open actions | Issue number and owner | What evidence will close the item? |
Keep superseded drawings separate from the issued set. A dated index helps the receiving team recognise the current package without opening every file. Also agree where the authoritative copy will live after the contractor’s temporary project folder closes.
Make each asset easy to find
An asset code connects the rainwater system handover checklist to the physical site. Use the same asset code on the drawing, the asset list and any permitted identification label. A reference such as “north tank” may become unclear when a second phase adds another installation nearby. A consistent project code is easier to carry into future inspection reports.
Consider a hypothetical record for an inlet inspection point. Its entry could link a location drawing, a photograph taken before covering and the relevant inspection record. The photograph should have a date and viewpoint. It supports identification; it does not replace the inspections or evidence required by the project specification.
Agree these records early enough for the responsible team to capture them. Otherwise, a missing location reference may only become apparent after the surrounding work is complete. Keep personal contact details and commercially sensitive records in the controlled project package, rather than a public-facing manual.
Turn maintenance instructions into assigned work
The susdrain management guidance describes an owner’s manual covering component locations, functions, maintenance and records. It also highlights access and the effects of later alterations. Maintenance needs vary with the system and its catchment, so a generic calendar should not become the operating plan without project review.
Ask the receiving team to review the instructions before acceptance. For each applicable task, identify the responsible organisation, the approved procedure, the required competence and the place where results are recorded. Access arrangements and safe working methods belong in that review too. This checklist is not an instruction to enter a tank or carry out an inspection without the appropriate arrangements.
Then test the information with a practical question: if an operator reports an unexpected condition, can the team find the correct asset and route the issue to the responsible party? That short exercise can reveal a missing reference or an unclear responsibility before the first routine visit.
Close open actions without losing their history
Use an action register to separate a submitted document from an accepted one. Give each outstanding item an owner, a required response and an agreed review date. When it closes, link the supporting evidence and record who accepted it.
For example, a drawing revision issued during construction may affect only one area. Record that area and the related change reference. Do not mark the entire system accepted merely because a revised file has arrived. Similarly, retain the agreed boundary between a completed phase and work that remains under construction.
Review the rainwater system handover checklist together
Bring the current layout, package scope and proposed operator to the discussion. Use the rainwater system handover checklist to agree the document index and responsibility boundaries while changes are still manageable. For systems serving planting, the earlier guide to rainwater harvesting for landscape irrigation explains the wider design questions that precede this information handover.
For a Leiyuan product discussion, contact the Greening Solution team with the project location, proposed system purpose and current layout reference. Identify the product information you need for the handover package, so the request stays tied to the actual project scope.