A UK developer may feel that drainage progress becomes tangible when a modular stormwater system appears on the layout. The tank has a footprint, the quantity surveyor has a line item, and the supplier can discuss delivery. Yet a drawing can look advanced while the drainage submission remains exposed. If the runoff destination, infiltration evidence, controlled outlet, exceedance route, or maintenance owner is unresolved, the tank footprint may be precise without being ready.
Readiness should therefore be judged by decisions and evidence, not by how complete the plan looks. A soakaway crate requires a defensible infiltration route. An attenuation tank requires a lined storage concept and an agreed release path. Both sit inside a wider drainage strategy that must address water quality, extreme events, safe operation, and long-term maintenance.
The practical consequence is that sizing comes later than many project programmes assume. The designer needs a coherent destination and hydraulic basis before the supplier can configure useful storage. Developers who protect that sequence reduce redesign, improve tender comparisons, and give planning reviewers a clearer account of why the proposed system behaves as shown.
Settle the runoff destination before fixing storage
Runoff destination tells the project what kind of underground system it is designing. Water may be collected for an agreed non-potable use, infiltrated to ground, released to a surface-water body, or discharged to an accepted drainage network. Each route has different evidence, permission, and control requirements. Storage volume alone cannot decide among them, including when stormmanage.com modules are under review.
England’s national standards for sustainable drainage set out a runoff-destination hierarchy and require higher-priority destinations to be used to the maximum extent practicable before moving lower. They also connect surface-water design with everyday rainfall, extreme rainfall, water quality, amenity, biodiversity, structural integrity, maintenance, and failure planning. A drainage submission is stronger when it explains this whole chain rather than presenting the underground tank as an isolated compliance object.
The destination decision should appear in the design narrative and the commercial brief. If infiltration is proposed, state the evidence status and any constraints. If a controlled discharge is proposed, identify the receiving route and the party responsible for agreeing the basis. If reuse contributes to the strategy, document the use, controls, overflow, and operating owner. A supplier can then configure the module package against a stated purpose.
Use site evidence to choose soakaway or attenuation
It is tempting to treat a soakaway crate and attenuation tank as two purchasing options with different wraps. The site decision is more fundamental. Infiltration depends on the ground accepting water without creating unacceptable groundwater, foundation, or pollution risk. Attenuation assumes water will be stored within a sealed envelope and released through a controlled route. The same modular core does not erase that difference.
Storm Manage’s infiltration-versus-attenuation guide asks whether testing shows the ground drains, whether groundwater is safely below the proposed base, whether a suitable outfall exists, whether discharge is restricted, whether nearby foundations or contaminated ground constrain the site, and whether traffic will pass above the system. Those are readiness questions because each can alter the selected configuration or rule it out.
A developer should ask the drainage team to label the status of each answer. “Testing planned” is not the same as “infiltration accepted.” “Outfall shown” is not the same as “receiving owner agreed.” This distinction keeps a provisional option from being treated as the approved basis during cost planning. It also tells stormmanage.com which quotation assumptions must remain visible.
Where evidence changes, the design should return to the decision point. Trying to preserve an early tank footprint after the hydraulic route changes can force awkward depth, membrane, outlet, and access compromises. A readiness review makes that dependency explicit before procurement hardens it.
Coordinate surface use, access, and exceedance
An underground tank earns its place by preserving usable land, but the surface above it still imposes design duties. Landscaping, a residential drive, a car park, and a service yard create different structural and access contexts. The project must coordinate finished levels, cover build-up, traffic, construction loads, inspection points, nearby services, and the method by which maintenance personnel will reach the system.
Exceedance needs equal attention. No drainage system should be presented as if a buried void eliminates all flood risk. The design needs a safe response when inflow exceeds the selected event, an outlet obstructs, or another component fails. That route belongs on the coordinated site plan rather than in a late note hidden behind the tank schedule.
Access should be drawn for the tasks expected during operation. An inspection riser placed because it fits a module grid may not provide useful reach to an inlet, pretreatment device, or flow control. The maintenance plan and layout should be tested together, with the future owner involved before the design is frozen.
Run a drainage readiness review
A short review can identify whether the submission is ready for module sizing and supplier engagement. It should record both evidence and ownership.
Drainage readiness review before the tank footprint is fixed
| Review point | Evidence to see | Reason it affects the tank |
| Runoff destination | Design narrative and agreement status | Defines infiltration, storage, outlet, or reuse path |
| Ground and groundwater | Site investigation and interpreted testing | May enable or prevent infiltration and affects buried design |
| Hydraulic basis | Catchment, rainfall, discharge, storage, and exceedance assumptions | Controls usable storage and outlet behaviour |
| Structural envelope | Traffic, cover, pavement, construction, and groundwater inputs | Controls module grade and surrounding build-up |
| Operation | Pretreatment, access, maintenance, records, and owner | Protects storage and outlet performance after handover |
The review does not need every design detail to be finished. It needs a transparent boundary between confirmed inputs, reasonable design development, and unresolved dependencies. That boundary should be carried into the quotation request so no supplier appears cheaper by silently assuming away a difficult interface.
Make maintenance part of approval readiness
A maintenance plan should explain more than a suggested inspection interval. It should identify the asset owner, access route, relevant components, observable signs of trouble, safe working requirements, records, and response process. It should show how sediment is kept away from the storage volume and how the controlled outlet can be inspected and cleared.
Storm Manage’s residential-development application guidance positions the StormTank module as a quantity-management component within a broader sustainable drainage management train. It distinguishes free-draining ground that may support infiltration from clay, high groundwater, or constrained land that may require attenuation, while also noting that water quality, amenity, and biodiversity depend on other parts of the strategy.
This boundary is valuable in a submission. It prevents the underground tank from being credited with treatment or wider benefits that must be delivered elsewhere. It also helps the developer ask a clearer supplier question: which module, envelope, access, and documentation fit the accepted system, and what remains outside the supply scope?
Freeze the footprint only after the interfaces agree
The supplier stage should begin with the accepted storage objective, available footprint and depth, structural context, membrane or geotextile path, inlet and outlet arrangement, inspection access, documentation requirements, and known programme constraints. Quotes can then be checked against the same basis. Any deviation should be raised as a design change, not absorbed as a purchasing detail.
A developer approaching Storm Manage project support can use that package to request a configuration discussion without transferring design responsibility. Storm Manage can provide product-specific information, layout support, drawings, and supply details for its modular stormwater system. Site testing, hydraulic and structural decisions, planning approval, and maintenance ownership stay with the appropriate project parties.
Readiness is achieved when the proposed tank is the visible result of agreed drainage logic. It is not achieved when an early module grid forces the rest of the design to catch up. By settling destination, evidence, hydraulic behaviour, structural envelope, access, exceedance, and ownership first, a UK developer gives both the submission and the procurement package a much stronger foundation.
