Top OSD Tank Manufacturers in Australia (2026) is a useful search only if “top” means suitable for a defined project, not a universal league table. This guide compares 11 companies with current evidence of an on-site detention product or supply route for Australian work, then shows what engineers and buyers still need to verify before a name reaches a tender list.

The shortlist is non-exhaustive, it mixes Australian manufacturers, Australian operating entities and one overseas export supplier, and inclusion isn’t evidence of council approval. Storm Manage publishes this article and is one of the listed suppliers; every company receives an identical set of profile fields, and Storm Manage isn’t ranked first.

An OSD system is also not necessarily a manufactured tank. Depending on the authority and site, storage can involve tanks, pipes, landscaped surface areas, reuse storage or a combination. The company list therefore covers one procurement pathway inside a wider drainage design, while the project hydraulic engineer and responsible authority retain the design and approval decisions.

Top OSD Tank Manufacturers in Australia: Quick Comparison

Eleven companies met the August 2026 inclusion rule: a current company-controlled page showed an OSD product or a supply pathway relevant to Australian projects. The table identifies the route and its evidence boundary; it doesn’t rate performance, price, ownership or approval readiness. That non-ranking boundary follows Australian Competition and Consumer Commission guidance that comparisons can mislead when they are inaccurate or unfair.

Evidence capsule: the table contains 11 selected profiles and five system families, but those numbers describe this editorial sample, not the whole market. Every availability signal comes from the named company’s own current material. Company-controlled evidence can establish offer and scope; it can’t independently establish comparative superiority or project acceptance.

How We Selected These OSD Tank Companies

A company qualified when its own current material showed an OSD product or service accessible to Australian projects on 25 August 2026. We excluded suspended sites, duplicate identities and businesses for which current Australian availability couldn’t be verified, and accepted no paid placement. The same evidence boundary keeps the comparison aligned with Australian Competition and Consumer Commission guidance on accurate and fair comparisons.

“In Australia” has three distinct meanings here: locally manufactured, supplied through an Australian entity, or exported to Australian projects. The profile and table label the route because an Australian web presence doesn’t prove local production, while overseas production doesn’t by itself prove that engineering, freight or support will fit an Australian job.

This is The Four-C OSD Fit Lens. A supplier is “verified” only where the relevant evidence exists for the actual site; “clarify” means the required input or document is missing; “fail” means a stated product boundary conflicts with the project. Unknown is never a pass.

Four-C decision rule: A supplier comparison is only valid after the project’s council, hydraulic, structural and construction constraints are fixed.

The publisher relationship matters. Storm Manage sells modular crate systems, so this article may help readers reach its product pages. That’s why supplier specifications are treated as first-party statements, why no winner is declared and why the same “verify next” field applies to Storm Manage.

Evidence capsule: Australia’s competition regulator says comparative claims can mislead when a comparison is inaccurate or unfair. That doesn’t ban a useful shortlist; it raises the standard for scope disclosure. Here, “top” means selected for due diligence under a published method, not independently proven to be the 11 highest-performing suppliers.

Company Profiles: OSD Systems, Strengths and Boundaries

These profiles translate different supplier terminology into the same five questions: what system is offered, how the company serves Australia, what makes it worth investigating, what the current first-party page actually supports and what remains unproven. Each profile is a starting hypothesis, not a purchase recommendation.

ACO Australia, StormBrixx Geocellular Systems

ACO Australia presents StormBrixx SD and HD as polypropylene geocellular systems with different published load, cover and maximum-depth data. That split is useful because it prevents the phrase “heavy duty” from floating free of a named grade. ACO’s own material also places conditions around groundwater and depth, so the strongest reason to investigate the range isn’t one headline number; it’s the existence of grade-specific decision data.

Shortlist ACO when an inspectable modular arrangement and more than one structural grade may suit the footprint. Ask for the exact grade proposed, the calculation and applicable loading case, minimum and maximum cover, groundwater assumption, access arrangement and the distinction between stated design life and project asset life. Product-table figures remain ACO claims until checked against the project design.

Atlantis Corporation, Flo-Tank and Titan Modular Systems

Atlantis Corporation publishes modular detention applications for Flo-Tank and Titan systems, including a 35 m³ Brisbane Flo-Tank example. This first-party case reference shows one system scale and configuration, but it isn’t independent proof that those details suit another soil profile, traffic case or authority.

Investigate Atlantis for irregular footprints or heavy-duty modular storage where project cases help an engineer frame questions. Request the case design basis, module configuration, liner or geotextile boundary, access and pretreatment, long-term structural method and local supply responsibility. Don’t turn recycled-polypropylene or project-volume statements into an approval claim.

Atlan Stormwater, Precast and Geocellular OSD Systems

Atlan Stormwater offers several families, including AtlanVault, MegaVault, AtlanCube, AtlanChamber and TankStor. The portfolio can be useful when a buyer wants to compare precast vaults, larger modular vaults and geocellular storage without beginning with separate companies. SPEL Stormwater states that it changed its name to Atlan Stormwater in July 2023, so SPEL isn’t counted as a twelfth supplier.

The breadth also creates a procurement risk: a group-level capability statement doesn’t specify which product family appears in the quote. Require the exact family, storage and outlet boundary, load basis, access and cleaning method, manufacturing/supply entity and project drawings. Treat the rename evidence as identity evidence only, not technical validation.

Industrial Plastics, Custom Fabricated HDPE and Polypropylene Tanks

Industrial Plastics advertises fabricated HDPE and polypropylene OSD tanks, including custom shapes for constrained spaces. Welded fabrication can be relevant where a basement, service corridor or irregular footprint makes standard moulds or precast units awkward. Its page also discusses access and coordination for traffic and soil loads, pointing to a project-specific route rather than a universal catalogue tank.

Shortlist the company when custom geometry is a genuine constraint. Verify material grade and traceability, design temperature, welding procedure, qualified personnel records, testing, connection details, structural design owner and how traffic, lateral soil pressure and groundwater are handled. Any DVS or ISO language remains a company claim until the underlying certificate, scope and currency are reviewed.

Landscape Tanks, Above-Ground Modular Concrete OSD

Landscape Tanks presents an above-ground modular concrete concept intended to combine detention with a boundary, landscape or retaining function. The proposition is materially different from hiding storage below a car park: it may reduce buried access and excavation while asking the architectural and civil design to accept a visible, integrated structure.

Investigate it when the site can use above-ground volume and a wall footprint carries value. Ask for structural design, waterproofing, controlled-outlet and overflow details, access, finish, foundation and interface responsibilities. The company page makes patent statements; unless patent-register evidence is separately reviewed, those statements should remain attributed rather than becoming an independent patent-ownership conclusion.

Panthers Concrete Tanks, Precast Concrete OSD Tanks

Panthers Concrete Tanks publishes standard capacities of 8,000, 14,500, 18,500 and 22,500 litres, with different residential and commercial roof-load options stated on its page. Standard steps can simplify early layout work, while grouped tanks may extend volume. The figures remain product-page claims and don’t remove the need for project engineering.

Shortlist Panthers for conventional precast storage when crane access, lifting sequence and standard dimensions suit the programme. Request the exact roof/load option, reinforcement and structural basis, inlet and outlet levels, group connection arrangement, base preparation, lifting plan, watertightness evidence and delivery boundary. A capacity match without a workable lifting route isn’t construction fit.

Polymaster, Poly Retention and Detention Tanks

Polymaster’s first-party page presents Australian-made retention and detention configurations across a stated 200 to 50,000 litre range. A standard moulded tank may suit residential or light-commercial work where a controlled outlet and accessible footprint align with the engineer’s calculations. The broad range doesn’t mean every size is suitable for every burial, load or OSD duty.

Ask which volume is permanently reserved for detention, which volume supports reuse, and where the outlet and overflow sit. Confirm above-ground or underground status, anchoring needs, vehicle exclusion or structural cover, inlet arrangement and maintenance access. A rainwater tank with an added outlet isn’t automatically an approved OSD design.

Puraflo, Corrugated Steel OSD Tanks

Puraflo advertises corrugated steel OSD tanks for New South Wales and South East Queensland, with standard and custom dimensions, a flexible polyethylene liner and roughly 5,000 to 60,000-plus litre options. It also states that orifice sizing is project-specific. Those details make the page useful for defining questions, but each number is still an attributed company statement.

Investigate Puraflo for above-ground, partly buried or buried storage where custom steel geometry fits the site. Request the coating and corrosion design, liner material and seam details, burial and backfill limits, groundwater position, anchoring, access, outlet responsibility and the hydraulic engineer’s interface. Don’t compare a lined steel shell price with a complete installed concrete or crate scope.

RainCycle, Precast Concrete OSD Design-to-Install Supply

RainCycle advertises concrete OSD design, manufacture and installation, including Australian prefabrication and customisation. A coordinated service can reduce handoffs when the contract clearly names who owns hydraulic calculations, structural design, production, delivery and installation. The company’s broad compliance language isn’t used here; only its product and service-scope statements support inclusion.

Shortlist RainCycle when a precast route and bundled service may fit. Ask for the responsible designers, calculation and drawing deliverables, approval exclusions, crane and site-access assumptions, outlet equipment, commissioning, as-built documents and maintenance handover. “Design to install” should be unpacked into named deliverables before commercial comparison.

Storm Manage, Exported Modular PP Crate Systems

Storm Manage is the publisher of this comparison and a China-based export brand, not an Australian manufacturer. It focuses on modular polypropylene underground storage for detention, attenuation, infiltration and rainwater applications, with accessories, technical drawings, container-loading support and project cooperation. Its Australian relevance is an export supply pathway that still requires Australian hydraulic, structural and approval work.

Storm Manage supplied the following figures for this article on 25 August 2026: an 8,000 m² Shenzhen production base supporting the brand, about 5,000 m³ monthly and more than 60,000 m³ annual finished-module capacity, eight injection-moulding machines from 1000T to 2000T and more than 12 mould sets. The company also reports batch compression, dimensional, material-ratio and unit-weight checks. This article didn’t independently audit the underlying production records, so these remain attributed operational statements rather than comparative proof.

Storm Manage also supplied a typical production lead time of 15–30 days after order confirmation and an optimised nested-loading figure of up to 330 m³ of installed storage per 40HQ. Both are planning inputs, not binding promises; the signed quotation must state the exact product mix, production window, container plan and delivery basis. Verify project grade, load and groundwater assumptions, Australian design responsibilities, inspection terms and complete delivered scope through the OSD tank hub.

Versatile Tanks, Joint-Free Concrete OSD Tanks

Versatile Tanks advertises square and rectangular joint-free concrete tanks for OSD and detention uses, plus nationwide delivery. Compact rectangular geometry can be worth investigating where a circular tank wastes a constrained footprint. The current reviewed page didn’t provide enough bounded detail to infer a standard capacity, structural rating or universal service life.

Ask for the exact dimensions and usable detention volume, structural and waterproofing design, inlet and outlet configuration, lifting and access plan, delivery route, loading assumptions and warranty exclusions. The company’s manufacturing and delivery statements support inclusion; the project engineer must still determine whether the proposed unit works in the actual location.

Modular Crates, Concrete, Poly, Steel or Fabricated HDPE?

Material is a project constraint, not a quality ranking. Modular crates maximise geometric flexibility, precast concrete offers familiar buried construction, moulded poly suits standard smaller forms, corrugated steel offers configurable shells, and fabricated HDPE or PP can follow constrained geometry. Loads, water, access and installation route decide which family survives.

Can a plastic detention tank be installed under a car park?

Yes, a plastic system can be proposed below a car park when the exact product grade, installed geometry, cover, backfill, pavement and long-term structural method are checked for the relevant vehicle loading. “Trafficable” isn’t a complete design value. Groundwater and temporary construction loads also matter, and some systems require measures outside the tank supplier’s standard scope. Have the project engineer review grade-specific data and installation limits rather than a generic compression result.

Authority guidance also prevents a reflex preference for burial. The Northern Beaches OSD specification says underground storage shouldn’t be used where surface storage can be provided and then sets hydraulic, cleaning, access and structural requirements for underground arrangements. That’s a local rule, not a national ban, but it shows why available surface space belongs in the material decision.

Evidence capsule: City of Casey identifies below-ground tanks or pipes, landscaped surface storage, reuse tanks, controlled-discharge tanks and combinations. The list matters because it breaks the false choice between five manufactured materials. It doesn’t transfer Casey’s requirements to another council; it shows that system form precedes supplier choice.

For a structured comparison before issuing enquiries, use the OSD material selector. It’s a screening aid, not a substitute for the engineer’s design.

Council and Engineering Evidence to Request Before Shortlisting

A council-ready evidence pack names the applicable project inputs, product grade, structural basis, layout, outlet interface, inspection access and responsible designer. That turns the material selector’s screening result into a council-ready document request. A brochure marked “compliant” isn’t enough because the published national standard, jurisdictional adoption, council conditions and approved drainage design may not point to the same edition or document set.

Standards Australia lists AS/NZS 3500.3:2025 as the current published Part 3 for stormwater drainage. That publication fact must be separated from legal or contractual application: New South Wales currently identifies NCC 2022 Amendment 2 and says it will adopt NCC 2025 on 1 May 2027. Other jurisdictions can take different paths.

What size stormwater detention tank do I need?

The required size comes from the approved hydraulic design, not a household rule of thumb. The engineer assesses catchment areas and surfaces, design rainfall, allowable discharge, outlet behaviour, levels and local requirements, then establishes the detention volume and system response. Early tools can translate an already determined volume into a preliminary module count, but they don’t generate council approval. Use the detention volume module estimator only after the design volume is known.

Rainfall inputs need their own currency check. The Bureau of Meteorology says its 2016 design rainfalls exclude future climate-change effects and points users to Australian Rainfall and Runoff guidance. Nominal tank volume therefore doesn’t prove that a model contains the project’s applicable climate allowance.

Use the OSD tank design and installation guide to define interfaces, and the New South Wales OSD council compliance guide when that jurisdiction is relevant.

Traffic Loads, Cover Depth, Groundwater and Maintenance Access

Four site conditions can eliminate a system before price matters: the real load case, allowable cover, maximum groundwater and practical maintenance access. Those are the installation interfaces the evidence pack must name. A catalogue compression figure lacks the installed boundary. Ask which grade, calculation, soil and pavement model, safety factors and life basis support the proposed arrangement.

ACO’s own SD/HD tables illustrate the point: separate grades carry different figures and caveats, so “ACO StormBrixx” isn’t itself a structural answer. The same discipline applies to every material. The correct evidence is the named product and installed layout checked against the project load case, not the largest number in a brochure.

Maintenance can also become a worker-safety issue. Safe Work Australia lists tanks and pits among common confined spaces and describes risk assessment, entry permits, signage, communication and rescue duties where confined-space work applies. The actual space and task determine classification; a product label doesn’t.

Evidence capsule: one 2026 Hornsby planning condition assigns OSD design to a chartered civil engineer and includes a 5% annual exceedance probability check and a named 50 mm minimum outlet-control pipe in that condition. Those figures belong to that decision, not every project; their value is showing how specific approval evidence can become.

For trafficable applications, use the OSD load-class reference alongside the actual project calculation, and see highway and car park drainage for application context.

How to Compare OSD Tank Quotes and Supply Scope

An inaccurate or unfair quote comparison may mislead buyers. Make quoted OSD tank prices comparable only after storage basis, accessories, liner or membrane, drawings, outlet scope, freight, lead time, installation and exclusions are standardised. The OSD load-class reference and project calculation carry into that comparison. No reliable Australia-wide installed-price band survived this review because these boundaries vary too much. A precise generic number would create false confidence.

1. Fix the storage basis: state whether the volume is gross vessel capacity, effective detention volume or installed system volume, and identify any stone or inaccessible volume.
2. List physical scope, including modules or tank body, connectors, end caps, membrane or liner, geotextile, vents, access, silt control and inlet/outlet items.
3. Name the engineering scope: layout drawings, structural calculations, hydraulic interface, certifications, revisions and approval responses.
4. Fix delivery basis by recording Incoterm, port or site, unloading, crane or assembly, packaging, container count and damage responsibility.
5. Separate production lead time from sea freight, customs, local delivery, inspection and document approval.
6. State exclusions. Earthworks, base, backfill, pavement, anchoring, pumps, outlet controls, installation and commissioning are common gaps.

For Storm Manage’s export route, the company reports 15–30 days as a typical production lead time after order confirmation and up to 330 m³ of installed modular storage per 40HQ under optimised nesting. Those first-party figures help container planning; they aren’t a delivery promise until the exact product mix, order, port, vessel and destination programme appear in the quotation.

Storm Manage prefers FOB Shenzhen, Yantian or Shekou and says Qingdao or Ningbo can be coordinated for project needs. The buyer still needs ocean freight, insurance, Australian import and local delivery responsibilities defined. Use the OSD tank cost and sizing guide to keep calculation intent separate from this supplier shortlist.

Which OSD Manufacturer Should You Shortlist?

Choose three or four candidates by scenario, then mark each Four-C dimension verified, clarify or fail. Use the normalised supply boundary from the quote comparison as the commercial input. A company can be strong for a constrained basement and irrelevant for an above-ground boundary wall. The framework selects questions and disqualifiers; it doesn’t create a universal winner.

Apply The Four-C OSD Fit Lens in order. Council fit comes first because a technically credible product is still unusable if the documentation can’t enter the approval path. Civil fit tests storage, outlet, load, groundwater and maintenance assumptions. Construction fit checks whether it can be built. Commercial fit compares the complete supply and risk boundary.

Don’t average a fail into three passes. A missing groundwater responsibility isn’t rescued by a good lead time, and an inaccessible tank isn’t rescued by a familiar material. “Clarify” is the correct state when an input is genuinely unknown; obtain it before scoring.

What Is Changing for Australian OSD Procurement in 2026?

The main 2026 change is documentation risk, not proof that one material became superior. Buyers must reconcile the current published drainage standard with the code edition, council conditions and project documents that actually apply. That makes evidence currency and jurisdiction part of product selection.

AS/NZS 3500.3:2025 is current at the standards publisher, while New South Wales says NCC 2022 Amendment 2 remains current there until its planned NCC 2025 adoption on 1 May 2027. A reusable national specification can therefore be wrong for a live project even when its standard citation is newer. Record both the source and applicable edition decision.

Local conditions remain concrete. Hornsby’s 2026 material assigns design responsibility and project-specific discharge controls, while a NSW planning record documents an OSD location problem involving overflow, accessibility and maintenance. These aren’t universal design values; together they show that product choice, location and approval evidence can’t be separated.

Measured search language is supporting context only. The local DataForSEO series stored as keyword-trends.json covers August 2025–July 2026: “stormwater detention tank” was 53.7% higher in the last six months than in the preceding six, while “underground OSD tank” was 10.5% higher. This is a first-party workflow measurement, not independently audited market data; other phrasing moved down, exact long-tail volume was unmeasured, and the series doesn’t prove market or sales growth.

Evidence capsule: one current publication date, one state adoption date and two measured query changes are useful only inside their boundaries. The procurement action is simple: date-stamp the governing documents, require suppliers to name the product revision and recheck the authority path before freezing the shortlist.

Frequently Asked Questions

These answers define common boundaries. They can’t replace a hydraulic calculation, structural design, work-health-and-safety assessment or council decision for a particular site.

Next Step: Issue One Evidence-Bound Request

Reduce the 11-company longlist to technically plausible candidates, mark every Four-C field verified, clarify or fail, and send one controlled request to the survivors. The request should make the engineer’s design inputs visible and force every commercial scope onto the same page.

For a modular crate review, send Storm Manage the required storage volume, available footprint, cover, traffic case, groundwater information, inlet and outlet details, delivery port, required documents and whether the company-stated ceiling of up to 330 m³ per 40HQ is relevant. We can return a project-specific configuration and export scope for engineering review; we can’t replace the responsible Australian designer or authority. A current council checklist, such as the City of Casey OSD design checklist, shows why design inputs and submission evidence need to travel with the request.

Request an OSD configuration review

Updated 25 August 2026. Written by XCX and reviewed for Storm Manage. Supplier product details are attributed first-party statements unless an authority source is explicitly named. Storm Manage’s production, quality-control and logistics figures are company-supplied first-party information.

Stormwater detention tank manufacturers are the companies that own the moulds, run the production line and can answer a specification question from their own records, as distinct from the resellers, importers and catalogue sites that use the same word. Vetting them is a documents problem before it is a price problem. Two companies can quote the same storage volume, both call themselves manufacturers, and only one can produce the test data, the drawings and the delivery commitment that a buried asset with a design life of 50 years needs. This guide shows which evidence separates them.

Nothing here ranks brands. We build modular stormwater storage ourselves, so a vendor-authored vendor ranking would be worth nothing to you. What follows instead is the buyer-side screen: the questions, the standard numbers and the paperwork that any supplier can either answer on the spot or cannot answer at all.

Detention, retention or infiltration: what you are actually buying

Detention holds stormwater runoff briefly and releases it at a controlled rate through an outlet. Stormwater retention keeps a permanent pool. Infiltration passes water into the ground. Your drainage report has already decided which one you need, and the word it uses is not always the word your supplier uses.

The line between the first and the third is physical, not commercial. Connecticut’s state stormwater manual puts it plainly: underground structures may be used as detention facilities if they are fully enclosed or used with a liner to prevent infiltration or interaction with groundwater, while open-bottom structures or perforated pipe should be designed as underground infiltration systems. Enclosure decides the category. Detention and infiltration systems are not separated by catalogue heading; the same crate becomes one or the other according to whether it is wrapped in an impermeable membrane or in a permeable geotextile.

That distinction governs the stormwater management system scope on your project. If your permit requires you to slowly release a computed volume at a computed rate, you are buying detention and the outlet control is the regulated component. England’s national standards for sustainable drainage put a number on the same idea, requiring that systems half empty their runoff volume within a maximum of 24 hours after a 3% annual exceedance probability event. US practice varies by jurisdiction, and your own local regulations set the equivalent drain-down requirement, but the shape of the constraint is the same everywhere: a storage volume paired with a release rate.

Read your own report for three phrases before you contact anyone. “Attenuation” and “detention” mean the same control function for managing stormwater. “Retention” sometimes means a permanent pool and sometimes, confusingly, means volume removed from the system entirely. “Infiltration” means the surrounding soils take the water, which turns the soil report into a governing document. Getting this wrong costs weeks, because a supplier will quote what you ask for. Start at the stormwater detention tank hub if you need the category map, or at soakaway crate infiltration systems if your report calls for infiltration rather than detention.

Vault, pipe, chamber or crate: four underground stormwater storage types manufacturers sell

Four construction families dominate underground stormwater storage in the US. They are precast concrete vaults, corrugated metal pipe, moulded arch chambers and injection-moulded modular crates. Buyers call all four stormwater tanks; the trade calls them storage tanks, vaults, chambers or crates depending on who wrote the datasheet. Site depth, cover requirements and excavation footprint usually eliminate two of them before you speak to a single supplier, which also limits who can quote.

Void ratio is the figure people compare, and it is the one most often misinterpreted. Storage volume is not the void of the unit alone. The Federal Highway Administration’s ultra-urban BMP report notes that storage volume for underground detention is controlled by the net void volume of the installed system, inclusive of bedding and surround stone at around 30 to 40 percent voids. A crate advertised at 95 percent void does not provide storage at 95 percent across the excavation, because the stone jacket around it does not share that figure. Ask any supplier to state which of the two numbers their sizing uses.

Material family carries its own service life question. Corrosion behaviour splits the four types sharply, and practising engineers are blunt about it.

Practising engineers in r/civilengineering describe the same split in their own terms: corrugated metal pipe corrodes in coastal soils, arch chambers win on cost in flat coastal areas, and the same pipe is less efficient on storage volume against system footprint, harder to install, and in some cases made to order only against an upfront deposit.

Note the last clause, because it is a procurement condition worth asking about, hiding inside a technical opinion: some build types are made to order against a deposit, so the supplier’s tooling position changes your programme, not only your unit price. Galvanized steel systems bring a zinc-loss calculation. Polyethylene and polypropylene units require a creep calculation. Precast units need crane access and a lifting plan. None of these is a flaw; each is a different question you must ask.

Water storage terminology shifts by market, and the same product answers to several names. The UK term, attenuation tank, and the Australian term, on-site detention (OSD) tank, describe the identical control function.

Residential and above-ground detention: when a smaller system is the right call

Not every site needs a buried system. Aboveground storage on a residential or light commercial plot is cheaper to inspect, cheaper to clean and easier to modify later. Underground storage earns its cost when land values make the surface footprint the binding constraint — which is precisely the trade-off behind the demand shift covered further down. For plot-scale work, see commercial and residential development drainage.

The Detention Supplier Type Map: ten kinds of company that call themselves a manufacturer

Ten different company types answer to the word “manufacturer” in this category, and they differ in one decisive way: whether they own the tooling. All of them market stormwater management solutions; only some of them make anything. A company that owns moulds can answer a weight-tolerance or material-ratio question from its own records. A company that does not must ask someone else, or guess.

This isn’t a slur on resellers. Federal contracting rules expressly contemplate a qualifying nonmanufacturer supplying another firm’s end product, and distributors that stock stormwater products carry real value in availability, local knowledge and service. Supplier type doesn’t decide whether you may buy from someone. It decides which evidence they can produce themselves, and therefore how long your answer takes and how much of it is second-hand.

The industry’s own equipment association draws that line in its membership rather than in its marketing: its published member directory carries stormwater equipment manufacturers as a membership class of their own. Whether a supplier belongs in that class is a question you can put to it directly, and the answer is checkable.

Run any quoting company through the first column and the last. If “who owns the mould making this part?” gets more than one back-and-forth, you’re talking to a reseller, and every technical answer you get thereafter will arrive on someone else’s schedule. Customizable variants — heavy-duty, shallow, connectors, end caps — only exist where tooling exists to make them.

The Supplier Proof Stack: product evidence, project evidence, supply evidence

The minimum evidence set has three layers, and most buyers request only the first. Product evidence proves the part performs. Project evidence proves it fits your site. Supply evidence proves it arrives when your programme needs it. A supplier strong in one layer and silent in another is a predictable source of delay.

Layer 1, product evidence. A named compression test standard, a long-term creep figure, a material declaration stating virgin or recycled polypropylene, and a per-unit weight tolerance. The weight tolerance matters more than it looks: for a moulded part, mass is the cheapest available proxy for wall thickness, and wall thickness is what carries load.

Layer 2, project evidence. A stage-storage table, a load-class calculation stated at your cover depth, a layout drawing to your excavation shape, and a connection detail for your inlet and outlet. Generic literature doesn’t satisfy this layer; the deliverable is project-specific by definition.

Layer 3, supply evidence. A stated lead time, container yield, port options, and a written description of the quality control regime. On an imported system this layer decides your programme.

There is a fourth layer, one experienced specifiers add and newcomers miss: acceptance evidence. Many state and municipal agencies maintain approved-product lists or local certification routes, and a product that cannot enter that channel cannot go on that project, however good its test data. Some state agencies run a formal technology evaluation programme with independent reviewers, a quality assurance project plan and a technical evaluation report, which is what regulator-run acceptance looks like at its most structured, though those programmes typically govern treatment technologies rather than detention storage. Find out early which acceptance route applies where you’re building; it has a lead time of its own. Our stormwater project input readiness checklist sets out what to have in hand before the first supplier call.

Decision point: if a supplier answers Layer 1 fully and can’t produce Layer 2 for your specific excavation shape, you’ve found a catalogue seller, not a project partner, and the gap will surface at the worst moment, when the layout is already frozen.

Detention load ratings: a compression number with no test named is not a specification

A datasheet that says 400 kN/m² tells you almost nothing on its own. The question that separates a real specification from a marketing figure is which test produced the number and over what duration, because short-term crush strength and long-term design strength are different measurements taken under different standards.

European practice splits them explicitly into two documents. BS EN 17150:2019 is the test method for the short-term compression strength of boxes; BS EN 17151:2019 is the test method for the long-term compression strength of the same products. Two standards exist because one number cannot do both jobs. If a supplier quotes a compression figure and cannot say which of the two produced it, the figure cannot be checked against a 50-year design life.

The consequences are documented. ASCE’s Civil Engineering Source reported a failure investigation in which the manufacturer’s literature gave 0.40% creep at 90 days and nothing at all on long-duration buckling resistance. In that case the installation deviations, including compaction plant far heavier than the stated limit, were held immaterial, and the conclusion that carried was that an unsuitable product had been specified on the strength of short-term laboratory compression data. ASCE also records that the experts disagreed: the claimant’s causation expert considered the construction deviations contributory, while two others held that a correctly installed system should not have failed. That disagreement is the argument for collecting the documents up front. You cannot know in advance which reading of your own failure would prevail.

Industry standards are versioned, and the version matters as much as the test number. With no US standard covering open-cell modular crates, the UK’s CIRIA guidance is the default design method for this product family: C737, Structural and geotechnical design of modular geocellular drainage systems, supersedes C680, and C753, the SuDS Manual, covers the surrounding drainage design. C680 certificates are still in circulation across this category, ours included, which is why the question to ask any supplier — and to ask us — is which edition the certificate was issued against, and whether the test has been re-run to C737. A test performed to C680 is a real test to a real method; what changes is which document your reviewer expects to see named. Separately, ASTM F2418, currently F2418-25, active as of 24 March 2025, is a specification for polypropylene corrugated wall stormwater collection chambers, meaning arch-shaped units. It does not govern open-cell modular crates, so a crate supplier citing it is citing the wrong standard for the product in the box.

Can modular detention tanks carry AASHTO HS-20 and HS-25 traffic loads?

Usually yes, at a stated cover depth, and that qualifier is the whole answer. Every load badge in this category quotes the HS-20 or HS-25 designation, and buyers sometimes hear that as outdated shorthand. It is not, and the reason is historical.

AASHTO replaced the older H-20 S16 designation with HS-20 in 1965, and HS-20 remains in use for load-factor rating of existing structures. The HL-93 model adopted in the 1994 AASHTO LRFD specifications uses that same design truck, axle loads of 8, 32 and 32 kips, roughly 36, 142 and 142 kN, combined with a 0.64 klf design lane load. Keep that separate from the federal gross vehicle weight ceiling of 80 kips, or 40 tons, which limits what a truck may legally weigh rather than what your tank is designed against.

So the badge is not the problem. What the badge does not tell you is the load model applied, whether a lane load was included, and the cover depth the rating was computed at. Ask the supplier: at what cover depth, and against which load model, was this rating calculated? If your site has shallow zones as well as deep ones, ask for the same rating restated at 300 mm and at 600 mm.

Worked example. Say a fire lane crosses your tank and your civil drawing gives 900 mm of cover over the crate. You ask for the load class at 900 mm, not the headline rating. The supplier returns a calculation showing HS-20 wheel loads distributed through 900 mm of compacted fill plus the lane load, with the governing compression figure taken from the long-term standard rather than the short-term one. You now have three checkable things: the depth matches your drawing, the load model matches your traffic case, and the strength figure matches the design life. If any one of the three is absent, the rating is not yet a specification for your site. For load-class context see highway and car park drainage load classes or work through the US load class model selector.

What detention suppliers publish — and what they leave out

We audited what supplier-side pages in this category actually disclose. On the measurement date we scored nine supplier-side pages spanning the four channels a US specifier meets — national manufacturer, distributor, regional installer and specifier-facing catalogue — plus our own page, against one identical list of evidence items. This is a census of nine named pages, not a sample of the industry.

No vendor is named, linked or cited here and the counts are anonymised. One of the nine is our own page. It’s counted in every column below, and we say plainly where it’s the exception rather than quietly lifting it out of the frame.

Read rows four and five together, and do not let anyone merge them into a single number. At page level, one page in nine names a standard designation anywhere — and that page is ours. At claim level, of the five other pages that publish a load rating or a void ratio, not one names the test that produced that particular figure. The first count says designations are rare. The second says the numbers buyers actually compare are mostly untraceable. Neither count says manufacturers hold no test data.

That distinction carries the whole section. This audit measures what’s published on a public product page, not what sits in a supplier’s files. A company may hold excellent long-term test data and never post a line of it, which is why the question belongs in your RFQ rather than in your browser. Several of the gaps are industry-wide rather than red flags: no page in the sample published a lead time, and none published a quality-control regime. Treat a missing figure as a question to ask, and treat an evasive answer to that question as the signal.

Second finding: the same product, two answers, depending on which seller you read. A national distributor’s page publishes one crate line at 12 in to 10 ft of cover, about 300 mm to 3.0 m; a regional installer’s page publishes the same line at 6 in to 16 ft, about 150 mm to 4.9 m. Void ratio diverges the same way: the same line appears at 95% on one page and at 90% on the other, and one of the two publishes both figures for that line on the same page. Neither seller is lying. Both are publishing their own summary of one manufacturer’s data, and underground chamber lines move through regional representatives rather than direct sale, so the summary you read depends on who typed it. Normalising the numbers is a buyer task, and it can’t be delegated to whichever page ranked first.

Decision point: ask which test produced the number, then ask at what cover depth it holds. A supplier who answers both from their own records is a different counterparty from one who forwards a brochure.

Storage capacity, catchment and hydraulics: what the manufacturer owes your engineer

The manufacturer owes you product performance data and a stage-storage table showing how the units store stormwater runoff in the proposed layout. Your engineer owns the catchment analysis, the design storm, the required storage volume and the outlet sizing. Confusing the two is the most common scope gap in an underground stormwater storage RFQ.

Three volumes get used interchangeably and aren’t the same: gross excavation volume, installed system volume, and net storage volume. Outlet control is where the regulated performance lives; Philadelphia’s stormwater manual lists meeting drain-down time requirements and controlling the discharge rate among the functions of outlet controls within a subsurface detention system. Local ordinances set the numbers, keyed to a design rainfall event, and plenty of them are more stringent than the state minimum. Heyworth, Illinois, for instance, requires 9,100 cubic feet of detention storage per acre, about 258 m³, at a release rate of 0.90 cfs per acre for tributary areas up to 2 acres, reducing to 6,200 cubic feet per acre, about 176 m³, at 0.60 cfs per acre at 5 acres. Those figures are that municipality’s, not a national rule, and yours will differ, but they show the form the requirement takes.

Worked example. Your engineer computes 300 m³ of required storage. A crate module of 0.4 m³ gross at 95 percent void gives 0.38 m³ of storage each, so 300 ÷ 0.38 ≈ 790 modules. At a 1.2 m system height that’s roughly 264 m² of tank footprint before bedding and surround. Now apply the caution from the build-type section: if your sizing must use net installed void including the stone jacket rather than unit void, the module count and the footprint both rise. Ask which basis the supplier’s number uses, then substitute your own volume and module size. The footprint arithmetic itself lives in the void ratio footprint comparator, and full sizing methodology and budget modelling sit in the stormwater detention tank cost and sizing guide; this section defines only who owes what.

Do manufacturers provide stage-storage tables with detention designs?

Reputable ones do, per project, once the layout is fixed. What they can’t provide is the design storm or the catchment areas; those come from your engineer’s hydrological model, whether that runs in HydroCAD stormwater modeling system or another package, and the manufacturer’s table is an input to it rather than a substitute for it. Ask for the table in CAD as well as PDF so your engineer can place it.

Groundwater, buoyant forces and backfill: the site conditions that disqualify a supplier

A high ground water table turns an empty tank into a buoyant body. If groundwater can reach the system, the supplier must produce an uplift calculation and a wrap specification for your ground conditions, not a strength figure alone. Suppliers who cannot do this are not wrong for every site; they are wrong for yours.

Some jurisdictions prescribe the calculation. Delaware’s post-construction standards require, for watertight underground detention facilities, an anti-flotation analysis in high water table areas, and state that anchors shall be designed to counter the pipe and structure buoyancy by at least a 1.2 factor of safety. That safety factor is Delaware law, not a national norm — do not carry the number to another state — but it shows that resisting buoyant forces can be a regulated computation rather than a supplier preference. Delaware also separates the two design cases directly: non-watertight facilities must sit no lower than the seasonal high water table, while watertight ones get the anchor calculation.

The wrap choice follows the same logic as the category decision in the first section. Impermeable geomembranes make the unit detention and keep groundwater out; permeable geotextile makes it infiltration and lets the surrounding soils participate. Backfill materials and compaction are specification lines, not site preferences; regional standard details govern bedding, backfill and minimum cover under vehicular loading. Contaminated ground and karst geology each add a screening step before any product is selected.

What separation is required between groundwater and the tank invert?

The required separation is set locally and is a permit condition, not a product property. Delaware’s rule for non-watertight facilities is the seasonal high water table itself, and two feet, about 600 mm, above bedrock. Your local regulatory manual will state the equivalent figure.

Get it before your engineer draws the layout, because raising a tank late in design usually costs storage volume you then have to find elsewhere on the site.

Cost, container yield and lead time: normalising two quotes that look nothing alike

Two quotes for the same storage volume differ mostly because they include different things. Normalise both to cost per cubic metre of installed storage, then list what sits outside the tank price: wrap, connectors, freight, excavation, backfill and install labour. Only then are you comparing suppliers rather than comparing scopes.

On an imported modular system, container yield is the dominant delivered-cost driver, more than unit price, because freight is charged by the box and not by the cubic metre of storage. Nested stacking is what converts one into the other.

Worked example. Take the 300 m³ requirement from the previous section. At 330 m³ of installed storage per 40HQ container, that project ships in a single container. Halve that yield — an illustrative figure for a non-nesting product, not a measured one — and the same project needs two containers, so the freight line doubles while the storage delivered stays identical. Run your own volume against each supplier’s stated yield before comparing unit prices; on export projects this single division changes the ranking more often than the price per module does.

Price bands published by suppliers themselves circulate widely for this category, generally in the region of $8.50 to $17.00 per cubic foot installed. Treat them as directional only: no public authority publishes installed-cost data for this category, and the sources quoting these bands largely cite one another rather than an independent survey, so the range indicates order of magnitude and nothing finer. A cost-effective outcome comes from normalising the scope, not from the lowest headline number.

One procurement screen belongs at the front of this section rather than the back. If any part of your project is federally assisted — for example through a state revolving fund — federal domestic-sourcing conditions may apply to the materials you install, and that can constrain your supplier list before any technical criterion does. Privately funded commercial and residential development is generally unaffected. Establish which category your funding falls into before you shortlist, because discovering it later invalidates the shortlist rather than adjusting it.

Decision point: normalise to installed cubic metres, then divide by container yield. On imported systems the second division moves the ranking more often than the first.

Maintenance and access: the ten-year question nobody asks at RFQ

Ask who inspects and cleans the system ten years after handover, and whether the layout allows it. Access provisions cost almost nothing to add while the drawing is open and are impossible to retrofit once the tank is buried. This is the criterion that most reliably separates suppliers, and it is the one least often raised at quotation stage.

The difficulty is well documented and it is structural, not a product defect. The US EPA’s storm water technology fact sheet on on-site underground retention and detention (EPA 832-F-01-005, published 2001) states flatly that these systems are more difficult to maintain and clean than aboveground systems. That document is a quarter of a century old, so treat it as the origin of the observation rather than as current guidance. The current-practice weight sits on Philadelphia’s manual, which explains why in operating terms: subsurface practices require strict adherence to regularly scheduled inspections because the maintenance needs are not easily visible, and they carry additional maintenance costs due to access limitations and Occupational Safety and Health Administration requirements. The same manual notes that vaults can be periodically cleaned by vacuum, whereas removing accumulated sediment from stone and grid storage systems is much more difficult.

Neglect has a specific failure signature. Sediment and debris accumulate until available storage no longer meets the permitted detention volume, and the shortfall appears downstream as surcharge rather than as anything visible on site, so the system is out of compliance long before anyone notices. In the worst cases the first visible sign is structural: a stormwater maintenance contractor’s published case account from Springfield, Virginia describes a parking lot sinkhole that ended in full reconstruction of the detention system rather than a local repair.

Do not assume newer approaches are cheaper to keep. A master’s thesis on low impact development maintenance costs reports that the common assumption that these systems cost less to maintain than conventional stormwater systems had not been demonstrated across the installations observed. Specify inspection ports, access chambers, jetting channel geometry and pre-treatment, and ask the supplier to mark them on the layout. Where reuse is part of the brief, a rainwater harvesting system reuse options arrangement changes the pre-treatment requirement rather than removing it, because harvesting for non-potable water supply adds filtration duties of its own.

What is changing in US stormwater storage procurement

The change that matters to a buyer is not volume growth; it is that land values have made surface footprint the constrained resource on many sites, which pushes storage underground. That shift changes what you must verify, because a pond has no manufacturer to audit while an underground system does. Selecting the supplier becomes part of the design risk.

Regulatory calendars, being redrawn around more severe weather, are pushing the same way. New Jersey required municipalities to update local stormwater control ordinances by 16 July 2024, with modeling criteria that result in smaller stormwater BMPs and therefore maximise developable area on a site. At the federal level, EPA has proposed the 2026 Multi-Sector General Permit to replace the 2021 MSGP for industrial stormwater discharges, a permit cycle worth tracking if your site falls under it. Condition data points the same direction: ASCE’s 2025 Infrastructure Report Card graded stormwater at D, and reports that the 20-year need for large stormwater systems in EPA’s 2022 Clean Watersheds Needs Survey rose to $115.3 billion from $23.8 billion in 2012. Manual editions move on a calendar of their own as well: King County’s Surface Water Design Manual, for instance, runs on the 2021 edition as amended in 2024, so confirm which edition governs the review where you are building before you order, because the acceptance route rather than the datasheet decides what a reviewer will sign.

Our own demand measurement covers the underground half of that picture, and it is rising. Comparing the 6 months to July 2026 against the prior 6 months, measured 21 August 2026: underground detention system rose 22.0% at 480 searches per month; three phrasings in the underground storage and detention cluster rose 49.1% each at 210 per month; stormwater detention vs retention rose 31.8% at 210 per month; stormwater detention tank rose 16.7% at 110 per month. Two underground phrasings moved the other way in the same window, down 15.7% and 20.0%, so the cluster is not uniformly rising. The series measures the underground cluster only and says nothing about ponds. We publish no market-size or growth-rate figure for this category: the available reports disagree by more than an order of magnitude, and a number we can’t stand behind is worse than no number.

What to do differently at shortlist stage: add the acceptance route and the funding-source check to your first screening call, alongside the technical questions. Both can eliminate a supplier for reasons no datasheet reveals, and both take weeks to resolve if you find them late. Where the site must also meet low impact development targets, see LID and EPA BMP compliance requirements for the regulatory framing.

Frequently asked questions (FAQs)

What is the difference between a stormwater detention tank and a retention tank?

A detention tank holds runoff temporarily and releases it at a controlled rate, ending empty between storms. A retention tank holds a permanent volume of water. Detention is defined by its release rate and drain-down time, while retention is defined by the volume it keeps.

The practical consequence is at the outlet: on a detention system the outlet control is the regulated component. Detention and retention are sometimes combined in one facility, but they remain separate functions with separate outlets, and your drainage report decides which one your permit requires.

What are stormwater detention tanks made of?

Four material families dominate: precast concrete for vaults, galvanized or coated steel for corrugated metal pipe, and polypropylene or polyethylene for moulded arch chambers and modular crates. Plastic systems are specified in virgin or recycled resin, and the ratio matters because it affects creep behaviour over the design life.

Ask for the material declaration as a percentage rather than as a description, and treat the unit as a structural water tank carrying soil and traffic load rather than as a plumbing vessel.

How do I verify a stormwater detention tank manufacturer’s load rating?

Ask for the rating restated at your cover depth, together with the load model used and the compression figure it relies on. An HS-20 or HS-25 designation names the AASHTO truck configuration assumed; it does not tell you the cover depth or whether a lane load was included. Then check that the governing strength figure comes from a long-term compression standard rather than a short-term crush test, since only the former speaks to a service life of 50 years.

Is geotextile fabric required around a detention tank?

Usually yes for permeable wraps, but the wrap type is the real decision: geotextile lets water pass into surrounding soils, while an impermeable geomembrane keeps it in and keeps groundwater out. Which one you need follows from the drainage report, not from the catalogue.

Infiltration needs the permeable wrap; a detention system that has to stay watertight needs the membrane, and the supplier should state which one is on the layout drawing.

Can a detention system be installed under a fire lane or crane path?

Yes, if the supplier produces a load calculation at the cover depth you actually have and the design accounts for the specific loading case. Fire lanes and crane paths are governed by different load patterns than car parks — a crane outrigger applies a concentrated point load that no highway truck designation covers. If the answer arrives as a datasheet rather than a calculation, it has not answered the question.

Give the supplier the loading case in writing rather than asking whether the product is rated for traffic, and require the calculation showing how the load distributes through your cover depth to the units below.

Do detention tanks need washing out twice a year?

Frequency depends on the sediment load reaching the system and on what pre-treatment is installed, so no universal interval applies. Inspection, however, should be scheduled regardless, because sediment accumulation reduces storage capacity invisibly and the shortfall shows up downstream rather than on site.

How long does manufacturing and delivery take for an imported modular detention system?

Our standard lead time is 15 to 30 days after order confirmation, plus sea freight to your port. Container yield governs how many boxes ship: a 40HQ, roughly 12 m of internal length, carries up to 330 m³ of installed storage volume when the modules nest.

Ask any importing supplier for the lead time and the container yield in writing, because together they determine your programme far more than the unit price does.

Conclusion: where to go next

Run your shortlist through the three-layer Proof Stack and the tooling question from the Type Map. If a supplier answers all three layers for your specific site — lead time and container yield included — you have a manufacturer. If they answer only the first, you have a catalogue.

The two columns where no page in the sample scores — a lead time and a documented quality-control regime — are the two we are publishing here: compression performance verification, dimensional tolerance checks, virgin and recycled polypropylene ratio control and per-unit weight consistency, with a lead time of 15 to 30 days after order confirmation. We run our own moulds, in standard, heavy-duty, shallow-crate, connector, end-cap and accessory tooling, so the answers come from our records rather than from someone else’s brochure. Send us your stormwater management needs — required storage volume, cover depth and traffic case — and we will return the stage-storage table and load calculation for your layout: request your stage-storage table and load calculation.

References & Sources

1. Connecticut Stormwater Quality Manual, Chapter 13, Underground Detention — CT DEEP / UConn NEMO
2. National standards for sustainable drainage systems (SuDS) — GOV.UK
3. Philadelphia Water Department Stormwater Management Guidance Manual v3.4, §4.8 Subsurface Detention — water.phila.gov
4. 7 Del. Admin. Code §5101-11.0, Post Construction BMP Standards — Cornell LII
5. EPA Storm Water Technology Fact Sheet: On-Site Underground Retention/Detention (EPA 832-F-01-005, 2001) — US EPA NSCEP
6. TxDOT Bridge Inspection Manual, Chapter 6 §1 Load Ratings — txdot.gov
7. FHWA Ultra-Urban BMP Report, underground detention — environment.fhwa.dot.gov
8. BS EN 17150:2019, short-term compression strength of boxes — BSI Knowledge
9. CIRIA C737, Structural and geotechnical design of modular geocellular drainage systems (supersedes C680) — susdrain
10. ASTM F2418-25, Polypropylene Corrugated Wall Stormwater Collection Chambers — ASTM International
11. ASCE Civil Engineering Source, underground plastic stormwater detention systems — asce.org
12. ASCE 2025 Infrastructure Report Card, Stormwater — infrastructurereportcard.org
13. Heyworth, Illinois Municipal Code, stormwater detention requirements — American Legal Publishing
14. MAG Standard Detail 24-C, underground storage bedding and backfill — azmag.gov
15. EPA proposed 2026 Multi-Sector General Permit — epa.gov
16. New Jersey stormwater rules and regulations — NJ Future GI Toolkit
17. STRUCTURE magazine, AASHTO vehicle live loading — structuremag.org
18. Underground detention system maintenance challenges — Stormwater Professionals Group
19. LeBarron, Low Impact Development maintenance cost study — spokanecity.org
20. BS EN 17151:2019, long-term compression strength of boxes — iTeh Standards
21. King County Surface Water Design Manual, 2021 edition as amended 2024 — kingcounty.gov
22. 13 CFR §121.406, nonmanufacturer rule — Cornell LII
23. Build America, Buy America Act requirements across EPA programs, including the State Revolving Funds — epa.gov
24. Stormwater Equipment Manufacturers Association member directory — stormwaterassociation.com

Prepared by the Storm Manage technical team from our own production records and the public sources listed above. Production, quality control and logistics figures are our own first-party data and are labelled as such. Demand figures are our own measurement, with the window and measurement date stated in text.

The difference between soakaway and attenuation tank configurations is the runoff destination. In the two standard configurations, a soakaway infiltrates surface water through a permeable wrap, while an attenuation tank stores runoff behind an impermeable liner and releases it at a controlled rate through an agreed outfall. Hybrid, overflow and multi-destination systems exist, so confirm the drainage strategy as well as the physical build. Storm Manage supplies project configurations for both soakaways and attenuation systems; exact crate model, load class, wrap and accessories are project-specific.

Soakaway or attenuation tank: where the water actually ends up

Destination is the whole difference. A soakaway tank sends surface water down into the surrounding soil, where it remains on site. An attenuation tank holds that water back, then passes it on at a rate the receiving sewer or watercourse can accept. Both are underground systems for managing stormwater; only one disposes of it.

Storm Manage supplies project configurations for both soakaways and attenuation systems; exact crate model, load class, wrap and accessories are project-specific. The drainage purpose is determined by the project design, including the wrap and outlet. Excavation, bedding, geocellular modules and cover depth still have to follow that design.

A surface-water soakaway is not a septic tank. It receives roof, driveway or car park runoff for infiltration, while a septic tank belongs to a foul-water treatment regime. Keeping the evidence separate helps reduce the risk of applying a foul-drainage test to a surface-water design.

Destination basis: CIRIA’s susdrain infiltration guidance.

The Wrap-and-Outlet Test: how to tell which system you are looking at

Two questions classify a standard crate-field build on site. Question one: how are the crates wrapped? Question two: is there an outlet pipe fitted with a flow-control device? A permeable geotextile membrane points to infiltration, while a welded liner points to storage. Answering both gives four common outcomes; where they do not match the approved drainage strategy, they are design-review flags rather than automatic build errors.

Apply the test as a diagnostic rather than conclusive proof. A controlled outlet indicates storage but does not settle the classification on its own. Partial infiltration, controlled overflow and multiple final destinations can be intentional when the hydraulic design documents them. If the wrap and outlet appear to conflict, check the drainage strategy before calling the build wrong. See the related wrap and flow control guide.

Field-test basis: England’s National Standards for sustainable drainage systems.

How a soakaway system works, and what it needs from the ground

Soakaway design is a bet on ground conditions rather than a product choice. Rainfall enters the underground storage void and infiltrates into the surrounding soil at whatever rate that soil allows. Excess rainwater that the soil can’t take simply backs up the inlet and surcharges at the surface.

Granular fill and geocellular crates provide different usable storage because their specified material void ratios differ. Where the required net storage is the same, the selected product has a higher declared void ratio and other excavation constraints are comparable, a geocellular tank may require less excavation. In the worked examples below, 95% is an explicit project-specific assumption for illustration, not a market-wide specification.

Emptying speed matters as much as capacity. Royal Borough of Windsor and Maidenhead guidance expects the half-drain time of an infiltration feature to be within 24 hours of the end of a 1 in 30 (3.3%) event including climate change; this is a local criterion, and each project must use its applicable acceptance criteria. A longer drain-down time can leave less capacity for back-to-back storms or heavy rainfall. Silt blinding can slow infiltration and extend drain-down time in soakaway schemes. See the related soakaway crate page.

Drain-down basis: Royal Borough of Windsor and Maidenhead infiltration guidance.

How an attenuation tank works, and why it needs flow control

Stormwater attenuation tanks primarily address a discharge-rate problem by providing temporary storage. These storage tanks temporarily hold runoff from a catchment during peak inflow, then allow water to pass through an orifice plate or vortex device. The permitted flow rate controls the rate at which water leaves; required storage follows from the inflow hydrograph, permitted outflow and other project assumptions.

The approved drainage design determines the flow path and diversion arrangement. Compare online and offline layouts with the coordinated site space; the drainage designer selects the final arrangement.

Attenuation tanks used to manage surface water are project-specific underground storage systems. In an attenuation tank installation, the coordinated hydraulic design determines how water is discharged and which inlet, outlet and control details apply. The terms online attenuation system and offline attenuation system describe alternative project layouts; the drainage designer should confirm the intended flow path. An attenuation tank with rainwater harvesting is a combined-use configuration and needs its own hydraulic, water-quality and control design.

Orifice size is a practical constraint on controlling the flow at the source. A permitted discharge of a few litres per second may imply a small opening, so blockage risk must be assessed. US 8,555,924 B2 describes one vortex flow-control device in which, once the pressure head above it exceeds a certain value, the inflowing water generates a vortex within the housing, restricting outflow; the patent also states that its outlet is less prone to blockage than an equivalent orifice. This is a description of that patent, not a claim about every vortex control. Downstream capacity is the point of the exercise: a river or reservoir, or more usually a surface water sewer in the main system, has a ceiling, and attenuation exists to keep the site below it and to prevent flooding elsewhere. Where the receiving network is already at capacity, the drainage design must assess the residual risk of localised flooding. See the related attenuation tank page.

Flow-control basis: England’s National Standards for sustainable drainage systems.

The Specification Split: soakaway and attenuation compared over 14 parameters

Fourteen design parameters separate attenuation tanks and soakaways once the crates are out of the equation. Use the table as a system-design review aid, paying particular attention to sizing input, site testing and failure modes. The crate structure must still be designed for the project load case using the selected product’s declared properties and the project’s structural build-up.

Under England’s 2025 National Standards, the proposed final destination affects the evidence and design inputs required for the drainage strategy; selecting particular hardware does not by itself establish approval or compliance.

Comparison basis: CIRIA’s susdrain infiltration guidance and England’s National Standards.

Sizing: different primary inputs within one design-event framework

Soakaway and attenuation sizing use different primary inputs inside the same climate-adjusted design-storm framework. Soakaway sizing begins with an infiltration value measured on the site. Attenuation sizing begins with a permitted discharge rate agreed for the receiving system. Neither can be inferred from the other, yet both designs must address urban creep, exceedance routing and failure during the selected design events.

Direction one, an illustrative soakaway serving an assumed 200 m² of surface water runoff. Use an assumed infiltration rate of 1 × 10⁻⁵ m/s for this arithmetic; the actual value must come from approved site testing. The 1 × 10⁻⁶ m/s value below is a sensitivity case only, not an acceptance threshold. Assuming a project-specific 95% void ratio for illustration, a crate block 6.0 m × 2.0 m × 1.2 m gives 14.4 m³ gross and 13.7 m³ stored; a real design must use the selected module’s declared value. For the assumed geometry, perimeter 2 × (6.0 + 2.0) = 16.0 m and half depth 0.6 m give an infiltrating area of 9.6 m². Outflow is 1 × 10⁻⁵ m/s × 9.6 m² = 9.6 × 10⁻⁵ m³/s, which is 0.096 l/s. Half of 13.7 m³ is 6.85 m³, so the half-drain time is 6.85 ÷ 0.000096 = 71,400 seconds, or 19.8 hours. The 24-hour criterion cited above is a local criterion; the 19.8-hour and 198-hour results apply only to the assumed geometry, and no universal infiltration cutoff follows from them. At 1 × 10⁻⁶ m/s, the same assumed block would take about 198 hours.

Direction two, an attenuation tank serving 0.50 ha of impermeable area. England’s national standards set the permitted rate as the greater of the 50% annual exceedance probability greenfield rate or 3 l/s per hectare, so the floor here is 0.50 × 3 = 1.5 l/s. Over a 60-minute critical duration the tank can release 1.5 l/s × 3,600 s = 5,400 litres, or 5.4 m³. If the design event puts 20 mm onto the impermeable area, inflow is 5,000 m² × 0.020 m = 100 m³. Storage is therefore 100 − 5.4 = 94.6 m³. Using the illustrative 95% void ratio from direction one, the required gross crate volume is about 100 m³. Substitute the selected module’s declared void ratio before procurement.

Climate change is applied to the rainfall side of direction two, and this is where a single national percentage is misleading. Environment Agency guidance uses a management-catchment map, with central and upper-end peak rainfall allowances for 1% and 3.3% annual exceedance probability events across the 2050s and 2070s epochs. Treating “40%” as a national rule is therefore unsafe; use the value and scenario shown for the site’s management catchment. For additional context, see the related soakaway sizing page and attenuation sizing page; use the project calculations and have a drainage engineer confirm them.

Allowance basis: Environment Agency climate-change allowances.

The Ten-Point Infiltration Screen

This is an editorial pre-design checklist, not a statutory test; it lists evidence to obtain and a possible next action. One failed check can rule out full infiltration or require treatment, a hybrid design, attenuation, another destination or redesign. The resulting drainage strategy follows combined hydraulic, environmental, legal and maintenance evidence rather than a product preference.

Check 2 can carry programme risk. Unda, a drainage consultancy, describes a winter monitoring window running from about November to May and says that some local planning evidence requests can extend monitoring to a full annual cycle. Treat both points as a consultancy account of project practice, not a council statement or national rule, and confirm the required monitoring period with the local approving authority. Missing the required observation window can delay evidence collection, so schedule it before the geocellular crates are quoted. See the related BRE Digest 365 percolation guide and site-screening guide; the drainage designer and approving authority retain the design decision.

Site infiltration testing is performed at the proposed location and depth under a locally accepted method, and the approved result controls design. The drainage designer should keep surface-water infiltration evidence separate from foul-drainage evidence.

Groundwater basis: local-authority infiltration criteria and the Environment Agency scope statement.

The Project Kit Split: what changes on the bill of materials

Procurement is where the choice between attenuation tanks and soakaway tanks becomes concrete. Storm Manage supplies project configurations for both soakaways and attenuation systems; exact crate model, load class, wrap and accessories are project-specific. The tanks must still be checked against their project load case, and divergence starts at the wrap before continuing through the remaining project-specific line items.

• Wrap: permeable geotextile for infiltration; an impermeable liner system and its project-specified quality-assurance steps for storage.
• Flow control means an orifice plate or vortex unit, plus the chamber it sits in and its connections.
• Inspection provision: typical inspection provisions to confirm include a port over the crates for a soakaway and access to the control chamber and inlet catchpit for a tank; the project maintenance plan controls the final access arrangement.
• Ask the drainage designer whether upstream pretreatment (e.g. a silt trap or catchpit) is required and how it is sized and maintained.
• Design and approval effort: for a tank, an agreed discharge rate and hydraulic calculations; for a soakaway, a site-test result and any required monitoring record.

Compare quotations by the included membrane, welding, chamber and connections; this comparison alone does not establish correctness or price. Accessories sharing a container reduce crate space; actual yield depends on the packing plan. Storm Manage states a standard lead time of 15 to 30 days after order confirmation and up to 330 m³ of installed storage volume in a 40HQ under its best stacking arrangement; both figures are supplier information for planning purposes, not verified industry benchmarks. See the related project-cost page.

Wrap basis: CIRIA’s susdrain infiltration guidance.

Installation and maintenance differences on site

The following is a typical sequence only; approved product instructions and project method statements control the works. Installing an attenuation tank and building a soakaway share excavation, formation, bedding and load-class considerations, but the approved sequence is project-specific. How the crates are wrapped follows the approved system design. Either system may be designed beneath traffic only where the selected module, cover build-up and project load case permit. A lined attenuation build may also require welding, liner quality assurance, chamber setting and an outlet connection.

Complete the liner quality-assurance steps required by the approved product instructions and project method statement. Inlet and outlet levels, chamber preparation, backfill timing and access arrangements follow the approved project design.

Maintenance then splits along the same seam. Keep the control orifice and catchpit clear; blockage can contribute to surcharge or uncontrolled bypass where the design includes one. For a soakaway, monitor drain-down time through the inspection provision; a lengthening drain-down is an indicator to review the system condition. Confirm inspection and rodding access in the project maintenance plan; recovery options for a silted crate field depend on the installed access arrangement. See the related soakaway crate installation guide.

Maintenance basis: local-authority drain-down criteria.

Why this choice is getting stricter, not easier

Destination is a consented design parameter rather than a groundworks preference. Cost alone does not justify infiltration; the proposed discharge point needs supporting evidence, such as an accepted test result or agreed rate, before crates are specified. Planning authorities assess the risk of flooding created downstream, not the merits of the product. That makes the ten checks above a programme item rather than a formality.

Two regimes sit behind it, and they are not the same. In Wales, the Sustainable Drainage (Approval and Adoption) (Wales) Order 2018 has been in force since 7 January 2019 under the Flood and Water Management Act 2010. Its approval requirement applies to construction work with drainage implications covering 100 square metres or more. Separately, when a developer submits a request to adopt a drainage system, the approving body has eight weeks from the first working day after receipt to determine it, unless the body and developer agree an extended period. In England, the equivalent Schedule 3 provisions of the same Flood and Water Management Act 2010 have not been commenced; instead Defra published non-statutory National Standards for sustainable drainage systems in June 2025, updated in July 2025, which local planning authorities apply through the planning system.

Those English standards also correct an assumption worth stating plainly. The discharge hierarchy does not put infiltration first: priority 1 is collection for non-potable use, priority 2 is infiltration to ground, priority 3 is an above-ground surface water body, priority 4 is a surface water sewer, and priority 5 is a combined sewer. Appropriate evidence is required to use a lower-priority destination. Rainwater harvesting therefore sits above a soakaway in the order, not beside it. That same document expects systems to half empty their runoff volume within a maximum of 24 hours.

A dated public signal is investment and implementation, not a product-market forecast. The UK Parliament’s 2026 Flood resilience in England: Government Response states that at least £10.5 billion will be invested in flood and coastal resilience up to 2036 and commits to increasing the quantity, quality, adoption and maintenance of sustainable drainage systems in England. That does not prove growth in attenuation-tank sales; it explains why evidence, adoption and maintainability are receiving more scrutiny as urban development adds pressure to drainage infrastructure. Rainwater harvesting systems, infiltration and controlled storage may all form part of a stormwater system that works across the whole site. Tanks may provide one component, but managing stormwater still depends on the destination, treatment train, maintenance ownership and exceedance route. See the related CIRIA compliance guide for attenuation tanks. CIRIA’s C737 publication page states that C737 supersedes C680 and that structural designs should now be based on C737. Anyone building stormwater management systems around the earlier document should confirm which guidance their designer has used.

Legal and policy basis: the Wales 2018 approval and adoption Order and England’s 2025 National Standards.

Frequently asked questions

Ask Storm Manage about project-specific crate and accessory options

Request a project quotation

Storm Manage supplies geocellular crates and accessories. The discharge decision, the calculations and the approval belong to the project’s drainage designer and the approving authority.

FAQ policy source: England’s National Standards for sustainable drainage systems.

References and sources

1. Department for Environment, Food & Rural Affairs, National standards for sustainable drainage systems, GOV.UK, published 19 June 2025, updated 30 July 2025.
2. The Sustainable Drainage (Approval and Adoption) (Wales) Order 2018, WSI 2018/1074, made 10 October 2018, in force 7 January 2019, legislation.gov.uk.
3. Environment Agency, Infiltration systems: groundwater risk assessments, GOV.UK, updated 25 November 2020.
4. Environment Agency, Flood risk assessments: climate change allowances, GOV.UK, published 19 February 2016, updated 27 May 2022.
5. Infiltration systems, susdrain, CIRIA.
6. Royal Borough of Windsor and Maidenhead, Sustainable drainage systems guidance.
7. Peter Shakespeare, Percolation testing explained, Ground & Water consultancy article, 24 May 2023.
8. UK Parliament, Flood resilience in England: Government Response, 2026.
9. CIRIA, Structural and geotechnical design of modular geocellular drainage systems (C737).
10. BSI, BS EN 17150: short-term compression strength of boxes.
11. BSI, BS EN 17151: long-term compression strength of boxes.
12. BSI, BS EN 17152-1: specifications for stormwater boxes.
13. US Patent 8,555,924 B2: Vortex flow control device, priority 26 July 2007, granted 15 October 2013.
14. Unda, Groundwater monitoring for planning: requirements and delays (drainage consultancy source).

Written by XCX, Storm Manage.

Updated August 2026

Soakaway crate installation is where most of the risk in a stormwater infiltration system actually lives, not in the crate itself. Even a correctly specified, correctly manufactured crate can fail within 5 years if it goes into the ground with the wrong backfill, a torn geotextile wrap, or the wrong siting distance, while the same product installed to spec can run for its full manufacturer-stated 50-year design life. This guide covers the full lifecycle: what the product actually is, how the percolation test constrains the design, a short recap of the physical build sequence, and then the two things almost nothing else online covers: what to check before the trench is backfilled, and how to tell an installation defect apart from routine blockage after the fact.

One quick note on where this guide fits before the detail starts: if you landed here searching how to install a soakaway UK, soakaway installation cost, or soakaway blocked how to unblock, all three are covered below, sizing and the physical build sequence first, a full domestic cost range in the DIY-vs-professional section, and a dedicated fault-versus-blockage diagnostic table further down. And if you’re weighing up installing soakaway crates yourself against fitting soakaway crates through a contractor, the soakaway crate installation instructions in the step sequence below apply either way.

What Counts as a Soakaway Crate Installation (And What Doesn’t)

A soakaway crate installation is the placement of modular, injection-moulded plastic infiltration units, wrapped in geotextile membrane and buried below a drained surface, that store rainwater runoff temporarily and let it disperse into the surrounding soil. This guide covers surface-water (stormwater) soakaway crates specifically: roof drainage, driveways, car parks and similar hard-standing runoff.

That’s the same infiltration-first scope the UK’s National Standards for Sustainable Drainage Systems set out, and getting it right at the start of a soakaway project is what the soakaway drainage decisions later in this guide depend on.

Good stormwater water management starts with the same question every time, the one local building-control percolation guidance exists specifically to answer: is this ground actually going to accept the water? Loamy or sandy soil is generally favourable for infiltration; heavy clay soil is generally not, and that single variable does more to determine whether a project succeeds than the choice of crate brand ever will.

It doesn’t cover septic tank drainage fields or boiler condensate soakaways, which are a different category of structure with different sizing rules, different contamination risks, and often a different legal siting distance from any building. Industry reference material on soakaway design is explicit that a drainage field for treated effluent and a surface-water soakaway aren’t interchangeable, and mixing up the two rulesets is a documented source of siting mistakes.

Percolation Test: What It Actually Proves Before Any Crate Goes in the Ground

Whether the ground can accept water fast enough for a soakaway to work at all is exactly what a soil percolation test tells you, and how big the storage volume for the soakaway pit needs to be. Per Stratford-on-Avon District Council’s published building-control guidance, the standard method excavates a test hole at least 300mm square and roughly 300mm deep below the pipe invert, fills it with water, and measures the time for the level to drop from 75% full to 25% full, a 150mm drop. Divide that time (in seconds) by 150 to get Vp, the average seconds required for the water to fall 1mm.

Storm Manage’s own published lead time for this product runs 15 to 30 days from order confirmation, a figure worth having to hand when a project timeline depends on it. For small soakaways serving 25m² or less, UK design guidance allows a simplified worst-case rainfall assumption for a quick sizing check, for anything larger, the full BRE Digest 365 or the wider BS EN 752:2017 drainage-design series applies instead.

Vp itself is a time figure (seconds per mm of fall), not a velocity, so it isn’t quoted directly in m/s. What it feeds into is a separate soil infiltration-rate figure, derived from Vp using the BRE 365 method and typically expressed in m/s: broadly, the faster water infiltrates (the higher that rate), the more workable a soakaway is, and ground that drains too slowly needs an alternative disposal route instead (attenuation with a controlled outlet, or a sewer connection) rather than a soakaway. Separately, a related, independent UK drainage reference makes a practical point worth carrying into your own project planning: running the full formal percolation calculation is “not always feasible or necessary” for a quick go/no-go decision, a simpler trial pit, left overnight, is often enough to establish whether infiltration is realistic before you commit to the full test.

How Many Crates Does a Typical Installation Need?

There’s no fixed crate count independent of your site: the number is a function of your percolation result and your contributing drained area, not a lookup table. A practical rule used across UK guidance is to size storage volume from the drained roof or hard-standing area, the local design rainfall rate, and the measured infiltration rate together, then convert that volume into crate units for your specific product range.

Module dimensions vary by manufacturer. One published worked example, using a separate 50mm/hr design-rainfall assumption from a different reference than the simplified UK sizing assumption above (worked examples like this vary by source and storm-return-period basis, so treat the two as independent reference points rather than the same number), illustrates the underlying logic using that source’s own formula, Volume = Area x (rainfall rate / 3000), a shortcut method whose divisor bundles in that source’s runoff and duration assumptions rather than being a plain mm-to-m unit conversion: a 60m² drained area at that 50mm/hr assumption works out to roughly 1m³ of required storage (60 x (50/3000) = 1) by that method, before any adjustment for the specific crate module’s void ratio. Treat any generic “X crates per Y m² of roof” figure you see elsewhere as a rough starting point only, not a substitute for running your own numbers against your actual percolation result, which is exactly what Storm Manage’s installation page and its built-in sizing calculator are there to help with.

Where the site percolation test result is genuinely borderline, or the ground is a mix of clay lenses over more permeable strata, that’s a case for a project-specific sizing conversation with your supplier rather than a self-service calculation, the margin for error narrows considerably. As a rough planning reference, a typical domestic module measures around 1000mm × 500mm × 500mm, so even a modest 1m³ requirement translates into a handful of interlocked units, not a single oversized box.

Installation Sequence at a Glance

Installing a soakaway follows the same broad sequence whether you’re building a small domestic soakaway system or a larger plastic soakaway crates installation for a commercial site: excavate to the depth set by your percolation test and design, lay a compacted base layer, place and interlock the crates, wrap the assembly fully in geotextile membrane, connect the inlet and outlet pipework, then backfill and reinstate the surface. A modern soakaway crate system stores far more water storage volume per cubic metre of excavation than an old-style rubble pit, which is exactly why getting each step right matters more, not less. A published Tricel Stormwater case study (Killarney, Ireland, July 2024, 120m³ system serving a 12–13 house development plus car park) followed the same three-phase pattern: excavate and prepare a compacted base, install a geotextile/membrane/geotextile “sandwich” and assemble the crates within it, then backfill.

The number of crates and the overall size of soakaway you end up building both trace back to the sizing step covered above, there’s no shortcut that skips the size of your soakaway calculation and goes straight to a generic module count. Storm Manage’s crate range is manufactured to a stated 95% void ratio; a traditional rubble-filled pit typically runs well below that (commonly cited industry rule of thumb, not independently lab-verified in this round), meaning noticeably more usable storage per cubic metre excavated when the crate system is installed correctly, the qualifier “correctly” is doing real work in that sentence, which is exactly why the next two sections exist.

This is deliberately a summary, not a full how-to: Storm Manage publishes a detailed, layer-by-layer installation and design walkthrough with drawings and sizing tools for exactly this step, and repeating that depth here would just duplicate it. If you’re at the execution stage, Storm Manage’s own step-by-step installation and design walkthrough is the more useful next stop, this guide picks up from where that one leaves off.

The Pre-Backfill Verification Checklist

Once backfill goes in, almost everything about the installation becomes invisible. Torn geotextile corners, missing clips, an undersized base layer, none of it shows up again until the system starts underperforming, sometimes years later. That makes the pre-backfill stage the single most valuable inspection point in the entire project, and it’s the one step that almost no installation guide, manufacturer or independent, treats as a discrete checklist in its own right.

This list reflects a pattern the supplier side sees repeatedly: the most common, least visible cause of underperformance is an incomplete or damaged geotextile wrap at exactly this stage, not a defect in the crate itself. It’s also why the wider industry direction is toward building inspection access directly into the product rather than leaving verification to chance, and it lines up with the emphasis the UK’s national SuDS standards place on infiltration systems actually functioning as designed, not just being built to a drawing.

If you’re commissioning the work rather than doing it yourself, ask the installer for these photographs as a deliverable, not an afterthought, it costs nothing at the time and is the only record you’ll have once the ground is closed.

Installation Fault or Routine Blockage: A Diagnostic Table

Three genuinely different reasons can stop a soakaway draining properly, and each one calls for a different response. Confusing them wastes money: excavating and rebuilding a system that just needs its silt trap cleared, or repeatedly jetting a system that was never sited on suitable ground to begin with.

Is a Blocked Soakaway the Same as a Failed Installation?

No, and treating them as the same thing is the most common mistake in this diagnosis. By definition, a blocked soakaway is a maintenance event: silt, debris or root ingress has restricted flow into an otherwise sound system, and the standard fix is clearing the silt trap or jetting the inlet pipework. A failed installation is a structural or execution problem instead: a compromised wrap, inadequate compaction, or ground that was never suitable to begin with.

That last cause traces back to whether the site was ever properly tested against the standard percolation-test procedure in the first place, not a maintenance issue at all.

Independent UK drainage guidance treats this distinction as routine: an older soakaway that has stopped functioning is described as usually blocked with silt and mud, remediable in many cases by removing the fill and accumulated silt to rejuvenate the system, without needing a full rebuild. As noted above, the diagnostic table is a starting point for narrowing which category you’re actually in, not a substitute for a physical inspection when the cause isn’t obvious from the symptoms alone.

Who’s Accountable When It Fails: Manufacturer, Installer, or Owner

Most soakaway crate manufacturers, Storm Manage included, are explicit that their role stops at the product: engineering the crate, connector and wrap system to a stated specification, and providing installation drawings, not carrying out the physical, on-site build. In Storm Manage’s own words: “we don’t carry out on-site soakaways installations; our responsibility is to engineer the system and support the installation team.” That’s a reasonable division of labour, but it means the accountability question has three distinct parties, not one.

Product specification (void ratio, load class, material composition, and crate geometry that can itself be patented engineering, as with the Otto Graf percolation-block patent family) and accurate installation guidance sit with the manufacturer. The installer (whether a contractor or a competent DIYer) is responsible for executing that guidance correctly: compaction, wrap integrity, siting distance, connections. The owner or project developer is responsible for commissioning a percolation test and appropriate design before ordering, and for reasonable maintenance afterward. When a system fails, working out which of the three broke down is exactly what the pre-backfill verification records (see above) and the diagnostic table exist to support, without them, it becomes a much harder argument to have.

“Nine times out of ten, a failed crate soakaway didn’t fail because of the crate; it failed because the geotextile wrap was incomplete or the compaction was rushed at Layer 2. We tell every distributor the same thing: follow the layer sequence exactly, because the crate is only as good as what’s around it.”

— Senior Application Engineer, Storm Manage

One further point worth flagging honestly: some suppliers, including Storm Manage’s own published material, note that industry structural-design guidance for geocellular systems has moved from an older reference (CIRIA C680) to a newer one (CIRIA C737). We haven’t independently verified the supersession against a second source this round, so treat it as Storm Manage’s stated position rather than an independently confirmed fact when it matters to a compliance submission, check directly with CIRIA or your structural engineer for a project that depends on it.

DIY or Hire a Contractor: A Threshold Table

On suitable ground, with a straightforward percolation result, a small domestic soakaway is within reach of a competent DIYer with two people and a weekend. Larger, commercial, or trafficked installations are a different proposition, not because the crate assembly itself is complex, but because the consequences of a mistake scale with the site.

Cost is a secondary factor to the table above, not the primary one, but it does move with scale: Storm Manage’s own published guidance cites local UK trade and installer-forum estimates of roughly £1,500 to £2,500 (installed) for a typical domestic crate soakaway, covering both labour and materials, while a commercial installation is priced per project against the specific volume and access constraints. If you land on “professional,” sizing and kit selection for the specific product range is a separate decision from the execution question this guide focuses on: sizing and kit selection guidance and a six-check evidence framework for choosing a kit before you order cover that ground.

Legal Siting Rules and Building Regulations Compliance

UK building-control guidance, administered by local authorities, is consistent on the core siting minimums for a standard surface-water soakaway: at least 5 metres away from any building or road (5m), and 2.5 metres (2.5m) from any boundary, with additional restrictions where the site is in an area of unstable land, near the water table, or close enough to another soakaway or drainage field that the ground’s overall soakage capacity would be exceeded. These aren’t guidelines, a soakaway sited too close to a building, or not sufficiently away from the building it’s meant to protect, can be required to be repositioned. Cover depth follows a similar application-based rule: 150mm minimum for garden or lawn use, rising to 350mm for light traffic such as a domestic driveway.

Where a system carries a higher load class (D400-rated, for trafficked surfaces), the siting and cover-depth requirements interact with the structural design in ways that a nominal rating alone doesn’t resolve. Shallow and deep installations under the same nominal load class can be governed by different transient, permanent and lateral loading conditions, so a single “D400 means X depth” rule of thumb isn’t reliable, and a duty label by itself doesn’t confirm suitability for a specific buried application without checking it against the actual cover depth, pavement construction and construction traffic expected on site.

Load class selection should be made independently of cover depth, the two are related but not interchangeable decisions, and mistakenly combining them is a frequent error. For quick reference, the table below maps common real-world application scenarios to the load-class family each typically falls under:

Worth being precise about scope here: these EN 124 classes rate the surface-level covers, gratings and access points sitting above the installation, the standard that applies to anything a wheel or foot actually contacts, not the buried crate structure itself, which carries its own separate compressive/structural rating from the crate manufacturer and needs checking against that spec independently. Note that the same D400 label appears across the last four rows, yet the cover depth, backfill specification and construction-traffic tolerance a structural engineer would sign off on can differ meaningfully between a retail car park and a public highway. That’s the practical meaning of the “duty label alone doesn’t confirm suitability” point above, the class name is a starting point for the conversation with your engineer, not the end of it. Storm Manage’s heavy-duty soakaway D400 guide goes into D400 specification in more depth than this section can.

For a system that’s already in the ground, where you’re checking retroactively rather than planning a new installation, the practical version of this compliance check is simpler than it sounds: pull the original design drawing (or the pre-backfill verification photos, if you have them) and measure the as-built distances against the table above, rather than assuming the original plan was followed exactly on site. This is the retrofit angle most siting-rule content skips, because it’s written for people planning a new installation, not auditing one that already exists.

What’s Changing in 2025-2026: The England SuDS Standards Update and What It Means for Installations

England’s National Standards for Sustainable Drainage Systems were updated on 30 July 2025, the first major refresh in a decade. It’s worth being precise about what that update does and doesn’t do: per industry drainage-sector commentary, it remains non-statutory in England, meaning compliance is enforced through planning conditions rather than a direct legal mandate.

It applies specifically to England, Wales operates under a separate, statutory Schedule 3 SuDS approval regime that isn’t the same framework. Treating this as one uniform “UK requirement” is a real, common imprecision worth avoiding, since the practical compliance path genuinely differs by nation.

For a soakaway crate project specifically, the update’s most direct relevance is at the planning-approval stage administered day-to-day by local authorities, the same kind of local building-control office that signs off on the percolation testing and siting this guide covers, where the update reinforces infiltration and source-control drainage as the preferred approach over piping water straight to sewer. We haven’t found clear evidence in this round that the update extends new retrospective compliance obligations onto already-completed installations, if you’re checking an existing system rather than planning a new one, the siting and design rules in the sections above remain the operative reference, not the 2025 update specifically.

Getting the England/Wales distinction wrong carries a real risk for a live project: citing the wrong regime in a planning submission, England’s non-statutory update instead of Wales’s statutory Schedule 3 process, or vice versa, risks the submission being sent back for correction and resubmission, adding avoidable time to the planning timeline for no reason other than citing the wrong document.

Frequently Asked Questions

OSD Tank Hub is an owner-facing guide to the decisions, records and handovers around an Australian detention project. Engineering responsibility stays with the designer. Your job is to provide trustworthy site information, identify the decision-maker for each step, protect the accepted design during construction and keep the evidence the future asset custodian needs.

On-site detention temporarily stores stormwater runoff and releases it at a controlled rate. The on-site detention system sits within the wider drainage system. This stormwater management function can reduce pressure on downstream drainage and flooding risk, but it doesn’t guarantee that flooding won’t occur. This wider asset includes the inlet, storage, controlled outlet, overflow path, access points and the records that explain how each part should be inspected. For the technical flow path, see Storm Manage’s guide to how stormwater detention systems work.

Updated August 2026 · Australian English · Owner and project-client guidance

Start With the Property Question: Is OSD Part of This Site?

With that owner role clear, begin by searching the approved records before making assumptions from surface appearance. Whether this is an existing property or an urban development project, OSD systems might be above or below ground. Approved development consent, drainage plans and maintenance records are more reliable than visible entry points or plaques alone.

Start a brief evidence checklist. Search for the development consent and its drainage conditions, approved civil or stormwater drawings, title or covenant information where relevant, building or strata records, previous inspection reports, maintenance schedules, asset registers and any identified pits or plaques. Write down what you found, where you found it and whether it appears up-to-date. A missing file raises unanswered questions rather than proving the non-existence of an OSD asset.

Local information varies. As a named example, City of Parramatta’s stormwater engineering guidance connects underground storage with service loads, drainage behaviour, surface inspection, access, ventilation and downstream conditions. Those topics help an owner identify useful records and questions; they aren’t a nationwide checklist.

Northern Beaches Council’s engineering specifications list a dedicated OSD technical specification within the authority’s own water-management documents. This is another reason to identify the relevant council and current local controls before treating any document list as universal.

If the property is in New South Wales and you need the detailed pathway discussion, view the separate NSW council and Sydney Water OSD guidance. Keep this first step more modest: identify the probable asset, gather existing records, name the responsible authority and address the gaps with a qualified adviser.

The OSD Responsibility Relay: Who Decides What?

OSD projects work best when each decision is made by the responsible party and the next party receives usable evidence. The OSD Responsibility Relay maps owners, engineers, approval authorities, suppliers, installers, commissioning parties, custodians, maintainers and future recipients. Weak handovers leave the next person working from assumptions. The technical questions in City of Parramatta’s engineering guidance show why storage loads, drainage behaviour, inspection access and cleaning access must remain with the qualified technical team.

This transfer isn’t always a straight line. A supplier request might loop back to an engineer; a newly revealed service might return to the design team; an authority comment might affect several parties. Use one simple test: can the next decision-maker see the current approved basis, the open question, who’s responsible for the answer and what has changed?

Owners should avoid two shortcuts. Don’t push the supplier to quietly assume the engineer’s design role, and don’t let a site change become the new basis simply because construction has moved on. Document the problem, pause the affected work where appropriate, and send it back through the relevant technical and approval team.

Read an OSD Plan Without Redesigning It

Owners don’t need to redo the hydraulic calculations, but they should recognise the terms that frame the discussion. Some drawings call the storage a stormwater detention tank or on-site detention tank; treat that label as one storage element within the wider stormwater system, not the whole asset. Plan literacy also helps test whether the real site matches the approved configuration. Penrith City Council’s inspection guidance provides a useful component model: inlet, storage, controlled outlet and overflow, with screens used to reduce blockage risk.

• Catchment and impervious area: the surfaces contributing to runoff. Ask if roof areas, pavement, and buildings have been reflected correctly in the approved plans.
• Storage or SSR: the detention volume required by the design basis. Ask where it will be provided and what space or cover constraints protect it.
• Permissible site discharge: the controlled flow rate according to the design basis. Ask which approved document contains this value and don’t take values from other projects as reference.
• Controlled outlet, orifice or orifice plate: the device controlling the release. Ask how it will remain identifiable, accessible and protected from blockage or alteration.
• Overflow path: the route the water will take if the controlled system is blocked or overwhelmed. Ask if site works proposed later will alter it.
• Discharge point: the location where water leaves the site via the controlled system. Ask if there have been changes in the downstream infrastructure, easements, or connections.
• Access and maintenance schedule: how to inspect the site, the routine, and who owns those records.

Different drawings, council documents, suppliers and search results use overlapping language. Use this 9-Category OSD Terminology Map to turn unfamiliar wording into the next owner question. It is a vocabulary check, not a design or product-selection shortcut.

Useful owner observations often aren’t quantitative. They might include, “The architectural plans now show a driveway across this area,” or, “This proposed fence would block the existing access.” These comments let the technical team review the design against the real site without shifting design responsibility to the owner.

Build the Eight-Input Owner Brief Before You Ask for a System

Use the Eight-Input Owner Brief as a pre-design record, not as the design itself. It packages what an engineer and supplier need to know about site conditions, clearly separates evidence from assumption and reveals missing decisions early. One document with referenced files is far more useful than a lengthy email filled with half-checked data.

1. Site and authority: Provide full street address and local government area and identify water or relevant approval authority as applicable.
2. Development scope and stage: describe what work will be undertaken and what phase the project is currently in (e.g., feasibility, approvals, detailed design, construction, completion).
3. Available records: List relevant approved drawings (by issue date and name), relevant consent conditions, land title details, survey plans, and any previous drainage documentation (by file name and date).
4. Impervious-area changes: document known or assumed changes to roofs, paving, driveways and other hard surfaces, then label each one existing, proposed or uncertain.
5. Downstream constraints: document the known discharge point, easement, connection or downstream concern, but leave hydraulic decisions to the designer.
6. Physical use constraints: document proposed traffic, cover, buildings, landscaping, services, access, land use and available space.
7. Programme and responsibility: name who procures, installs, inspects, records variations and coordinates approval evidence.
8. Future custody: name the expected asset owner, handover format and person or organisation that will maintain the master record.

This distinction matters because an unlabelled assumption can pass through several handovers until someone treats it as approved site data. When the brief says, “Discharge point assumed from an old sketch – engineer to verify,” the uncertainty stays visible.

Once the technical basis has been defined, cost and size can move to the centre of the discussion. Storm Manage keeps those commercial calculations on its dedicated OSD cost and sizing project tools, so they don’t burden this owner guide.

Move From Approval to Commissioning Without Losing the Evidence

Keep the approved design traceable through procurement, construction and commissioning. A practical sequence runs from the approved basis to construction information, recorded variations, completion evidence, then operating and maintenance information. Each step should point back to the decision it implements.

Start with a controlled issue of the approved drawings and associated conditions. When a supplier submittal is accepted, record the design or approval item it relates to. During construction, collect photographs and inspection evidence before important areas are covered. Note any service conflict, access change, surface-grade change or substitution against the current design and refer it to the responsible engineer and approval party.

Any undocumented variation carries two risks. The completed asset may no longer match the design evidence, and a future maintainer may inspect the wrong place or misunderstand how the system should function. A verbal agreement reached on site is even less durable after the project manager, developer or facilities provider changes.

Commissioning isn’t just a final tick. It is the point at which the project reconciles what was approved, what was installed, what was inspected and what the owner is being asked to maintain. Those component and access checks in Penrith City Council’s OSD maintenance guidance illustrate why the handover must identify what future inspections actually cover. Document names vary with the authority and project, so ask the responsible engineer or certifier to identify the required set instead of copying another development’s pack.

What Belongs in the OSD Handover File?

A durable document pack should let a future owner identify the asset, confirm the approved basis, arrange inspection and trace later work. Some records are commonly useful; others are authority or project dependent. Label the difference so a practical owner checklist doesn’t become a false statement about what every project must contain.

The emphasis on accessible maintenance information is consistent with Penrith City Council’s inspection and maintenance guidance, which treats inlet, storage, outlet, overflow and screens as parts of the maintained system.

Put a one-page custody record at the front. Name the master-file location, current custodian, backup location, last update date and transfer recipient. Update it after a sale, strata transition, facilities-management change or substantial repair. A folder that exists but has no owner is still a handover failure.

Store records in a readable format for whoever comes next. Keep final signed or approved documents, not just links to contractor portals that may expire. Where the authority or project requires specific registered, certified or named records, add them to this practical core; don’t expect the core to replace them.

Maintain the System You Actually Own

Base the maintenance routine on the approved system and its schedule, not a generic interval lifted from another site. Translate that schedule into named ownership, accessible records and repeatable inspection entries. The work maintains the asset; the log preserves evidence across its life.

Useful logs should include the inspection date, rainfall or incident context, inlet condition, accessible storage observations, outlet or screen condition, visible overflow evidence, access condition, action taken and any qualified reviewer involved. Record the date and contractor details for each repair or cleaning action too.

According to Penrith City Council’s WSUD inspection and maintenance guidance, a below-ground OSD system includes the inlet, storage, controlled outlet and overflow, with screens used to reduce blockage risk. An empty-looking surface area doesn’t prove that the outlet is clear.

Access is a fundamental part of the asset. City of Parramatta’s engineering guidance connects underground storage with inspection, cleaning access, drainage behaviour, ventilation and service loads. An owner doesn’t need to check unsafe or inaccessible areas personally; the owner needs to keep access available and arrange the right competent party.

After an unusual rain event, building work, paving changes or an observed incident, record the context before arranging a review. Don’t enter a confined space or reach into a chamber to check a suspected blockage. The approved maintenance information and site risk controls should determine who performs the work and how.

Visible Warning Signals and When to Escalate

A warning sign is a reason to investigate further – record it, take photographs and arrange the right review – not a root-cause finding. Similar observations can have hydraulic, structural, maintenance or site-interface causes. Compare the condition with the approved behaviour and maintenance records before deciding the next step. This component-based escalation approach follows the inspection logic in Penrith City Council’s OSD maintenance guidance, rather than assuming one visible symptom proves one cause.

This table isn’t an instruction to alter an orifice, force-clear an obstruction, excavate around a buried system or make a structural repair. It defines the owner’s response: protect the area, preserve evidence and send the question to the party qualified for the suspected issue.

From Owner Brief to Supplier Proof

You are ready for commercial system review when you can show the engineer-defined performance basis, current drawings, authority path, local constraints and who manages each handover. Supplier proof should answer those defined needs; it shouldn’t be used to invent the needs after purchase.

• Current engineer-defined storage, discharge, overflow and interface basis
• Confirmed authority and approval-stage requirements
• Known traffic, cover, land-use, access, space and service constraints
• Traceable proposed configuration and supporting product records
• Named installation, inspection and commissioning responsibilities
• Agreed handover format, maintenance schedule owner and asset custodian

Once the inputs are ready, review the OSD Tank Hub solution and project tools. Storm Manage describes its production base, delivered-project history and export reach on the page about Storm Manage. Treat those as first-party company statements; project acceptance still depends on the responsible engineer and authority.

Reviewed first-party figures state that the Shenzhen production base was established in 2013, spans 200,000+ square metres, has supported more than 1,000 delivered projects and serves customers in more than 30 countries. These figures describe the company, not approval or performance for this project.

FAQ: Owner and Project-Client Questions

How can I tell whether a property already has an OSD system?

What OSD documents should I receive at project handover?

Can I change a driveway, landscaping or structures above an OSD system?

Who should keep OSD maintenance records in a strata or commercial property?

What should I do if water ponds, an outlet appears blocked or overflow marks appear?

References & Sources

1. Camden Council – Water Sensitive Urban Design
2. Penrith City Council – WSUD Inspection and Maintenance Guidelines
3. City of Parramatta – Stormwater Engineering Design Guidelines
4. Northern Beaches Council – Engineering Specifications
5. South Australian Department for Environment and Water – Rainwater, detention and retention guidance

Updated 31 July 2026.

While many resources simply say “get council approval”, this usually leaves out the hardest part of the process: the compliance journey isn’t a single approval, but a sequence of 6 separate tasks, a number of which don’t happen until after you’ve been issued your Occupation Certificate. Let’s walk through this OSD sequence in chronological order: design & sizing, engineering certification, legal instrument, construction sign-off, Occupation Certificate issuance, and ongoing maintenance.

What NSW Council OSD Compliance Actually Requires: Six Stages From Design to Ongoing Compliance

NSW council OSD compliance isn’t one job but six: design & sizing, engineering certification, legal instrument (Section 88E covenant and restriction), construction sign-off, Occupation Certificate issuance, and ongoing maintenance.

This guide groups the process into five functional areas — design and sizing, engineering certification, legal instruments, Occupation Certificate deliverables and ongoing maintenance — while tracking six distinct tasks.

How much detail and council investigation this sequence demands varies by site. Where a flood, overland-flow, heritage or contamination control applies, or the proposed discharge reaches Sydney Water’s network rather than council’s, the application may require specialist review or input from a second authority. Applicable planning controls, the consent authority and the network owner determine that pathway and the required signatories. Build time for possible council delays into the programme when extra review is required. Across projects, the goal remains the same: stopping the additional runoff a new development generates from causing downstream flooding or nuisance discharge onto neighbouring properties.

Whether OSD is required depends on the applicable planning controls and consent conditions. Changes in impervious area are commonly a key design input, so a renovation or granny flat can still require a stormwater review, but the threshold and exemptions must be checked with the relevant council for the property.

Requirements vary by local government area (LGA). Homeowners comparing new builds or a duplex on an already-buildable lot should ask the relevant council whether the controls require OSD or another stormwater compliance response. That applies in Western Sydney and across Sydney, but the answer comes from site-specific controls, not a regional shortcut. Apply the same verification rule to councils across New South Wales.

Because the applicable pathway is set by planning controls and the project’s circumstances rather than a visual site check alone, the applicant or consultant should confirm it before lodgement. For regulated building work, verify the professional and design-practitioner registrations that apply to the project; for other work, confirm the engineer qualifications and certification wording required by the relevant council or authority. If the discharge authority is unclear, use Storm Manager’s NSW discharge authority finder as a starting point, then confirm the result with the relevant authority.

Stage 1, OSD Design & Sizing: DRAINS Software, SSR and PSD Explained

Permissible Site Discharge (PSD) and Site Storage Requirement (SSR) are not statewide constants. PSD is the rate at which runoff from a site may leave for the approved drainage system, while SSR is the storage volume the design must provide. Your engineer must use the value or calculation method required for the site, not a generic online range. For example, Mid-Coast Council’s published guideline adopts 75 L/s/ha in its stated context; that council-specific figure should not be treated as a NSW-wide default.

Your engineer will usually model the site’s stormwater behaviour with specialist hydrology software such as DRAINS rather than relying on a simple manual rule. Inputs can include impervious area, catchment characteristics, site levels and the approved discharge point. These are site-specific inputs for assessment by a suitably qualified civil or hydraulic engineer: how much runoff the catchment generates and how to control its release before it reaches the downstream network.

Since what DRAINS actually spits out for your specific catchment is highly site dependent, view the following as simply working our way through the possibilities as opposed to a mathematical calculation you can conduct.

Sizing needs drainage design as well as hydraulic design inputs – your site’s contour, hard surfaces (roof and driveways), soil type and catchment data all feed into the same DRAINS model your engineer builds. So why size it so accurately?

In simple terms, capturing stormwater on site and releasing it at the approved rate avoids sending a sudden runoff peak into existing drainage infrastructure. That is the condition OSD is intended to control because unmanaged peaks can contribute to downstream erosion and flooding.

Good stormwater design coordinates roof, driveway and landscape runoff with the on-site detention system and its approved discharge point. Where the design connects to council drainage or another public network, effective stormwater management limits the peak stormwater runoff that can overload downstream assets; it is not a substitute for the local DCP or Water Sensitive Urban Design (WSUD) requirements.

For a 600 m² suburban block, a statewide rule of thumb is not a safe sizing method. Site-specific modelling must apply the actual roof and paved areas, levels, catchment assumptions, discharge point and current council requirements. Two similar-looking blocks can therefore produce different approved discharge rates and storage volumes.

Stage 2, Engineering Certification for Council OSD Approval

Once your engineer has provided a sizing figure, the next step is to confirm who is authorised to certify or declare the relevant work. The Design and Building Practitioners (DBP) scheme applies to professional engineering work on regulated building classes, currently Class 2, certain Class 3 and Class 9c buildings. A professional engineer may also need the relevant design-practitioner registration to prepare regulated designs or make compliance declarations. Other projects remain subject to the qualifications and certification requirements specified by the council, certifier or approval authority. Before lodgement, confirm the project’s building class, the required registration or accreditation, and the exact person authorised to sign each document.

Certification commonly has pre- and post-construction stages. Before construction, the applicable approval pathway may require a chartered civil engineer to certify that the design meets the calculated PSD and SSR requirements. After construction, it may require signed Work-As-Executed (WAE) plans from a registered surveyor and a Certificate of Hydraulic Compliance. Submit the documents to the council, certifier or water authority identified in the project’s approval conditions.

Which authority reviews a particular part of the project depends on the discharge location and approval pathway. Confirm that point early rather than assuming; Storm Manager’s Approval Pathway Matrix provides a starting point, but the council and relevant water authority remain the controlling sources for the site.

Stage 3, Registering Your Section 88E Positive Covenant

One concept that often receives only brief treatment in online OSD guides is Section 88E. A missing or delayed title instrument can stall an otherwise compliant project before an Occupation Certificate. A Section 88E positive covenant is recorded against the title of a property in NSW under the Conveyancing Act 1919 and can place an ongoing maintenance obligation on the owner and subsequent owners. Unlike an informal assurance, the registered covenant remains attached to the title when ownership changes.

What Is a Positive Covenant and Restriction for a Stormwater OSD System?

For systems within its approval scope, Sydney Water’s OSD guidance says storage must accommodate runoff up to a 100-year Average Recurrence Interval (ARI) event. It also specifies a flat stainless-steel orifice plate at least 200mm by 200mm and 3mm thick, with an orifice diameter of 40mm or more, and requires the covenant agreement to be registered on the title so the obligation is not lost when ownership changes. If title registration is a consent requirement, missing evidence can prevent the relevant approval stage from being completed.

Stage 4, Construction and Occupation Certificate Compliance Deliverables

Before an Occupation Certificate can be issued, the approval conditions may require three related deliverables: Work-As-Executed (WAE) drawings prepared and signed by a registered surveyor to show what was actually built; a Certificate of Hydraulic Compliance confirming that the constructed system conforms to the certified design; and evidence that any required Section 88E positive covenant has been registered on the title, usually shown by a current title search. Check the project’s consent conditions for the exact documents and signatories.

• Work-As-Executed (WAE) drawings — prepared and signed by a registered surveyor to show the as-built system
• Certificate of Hydraulic Compliance – the build conforms to original design PSD’s / SSR’s
• Confirmation of registered Section 88E covenants – extract from title search to show the instrument is in force not just drafted

Costs at this stage depend on the council and the current fee schedule. For example, The Hills Shire Council’s published 2025–26 fees and charges lists $50,000 for an OSD Compliance Certificate for design and construction including two inspections, $664 for amended plans or modification of an application, and $454 for each additional inspection. These are council- and year-specific figures, not a statewide price guide.

Stage 5, Ongoing OSD Maintenance Obligations After Occupation

OSD duties continue after occupation. Council material references the UPRCT Handbook for the Management and Inspection of On-site Storm Water Detention as a practical maintenance framework. Keeping a simple management plan and dated log helps owners and contractors protect access points and record inspections. The handbook schedule calls for residential systems to be inspected every six months and after heavy rainfall, commercial and industrial systems every three months and after heavy rainfall, and cleaning at least annually or every six months depending on use.

Penrith City Council publishes an OSD inspection and maintenance sheet with dated fields, condition checks and post-heavy-rainfall items. Canada Bay Council states that owners of private detention and storage tanks are responsible for their management and maintenance to keep the system compliant with council requirements.

Who Is Responsible for Maintaining an OSD System After Occupation?

• Record all your service inspection dates, discoveries, repairs performed in a dated inspection logbook
• Review of the UPRCT cadence – every 6 months residential, every 3 months commercial/industrial, and after every large rain event
• Clean at least once a year – more frequently if a site has heavy leaf litter, is near construction activities or is in a large catchment
• Don’t change the system without checking the approval conditions — an altered orifice, storage volume or layout may require engineer and authority sign-off

Neglected maintenance can allow sediment, debris or damaged components to reduce system performance. It can also make it harder to demonstrate compliance during a council inspection or later building work. During a sale or later approval, a solicitor or certifier can see the registered title restriction and may ask how the obligation has been managed, so keeping records is prudent even where a specific logbook format is not prescribed.

Why OSD Compliance Requirements Differ Between NSW Councils

OSD compliance requirements differ between NSW councils because planning controls are local rather than one statewide formula. Even neighbouring councils can specify materially different PSD methods for similar blocks; the difference reflects their adopted controls and drainage context, not a value that can be transferred from one site to another.

Each NSW council applies its own stormwater planning controls alongside state and national requirements, so PSD, SSR and construction conditions can vary. In one cited Georges River Local Planning Panel determination, the conditions used a project-specific peak-discharge formula and required childproof fencing for open above-ground storage where peak design depth exceeded 300mm. A cited Hornsby Local Planning Panel determination used storage capacity sized to a 50-year ARI storm, restricted discharge to the five-year pre-development value, and added a 50 L/s limit per gutter discharge point. These are examples from individual determinations, not universal council policy values.

A council-hosted copy of the Upper Parramatta River Catchment Trust On-site Detention Handbook provides technical background for some Sydney-area OSD practice. Treat it as background, not as a substitute for the current controls, consent conditions and specifications that apply to the site.

Stormwater on-site detention is the underlying subject, but the controlling requirements still depend on the project. They may appear in the applicable DCP, a council specification or project-specific consent conditions. In practice, locate the controlling document for the property and use its PSD/SSR method rather than borrowing a value from another council or development.

The Practical NSW Council OSD Compliance Checklist (Stage by Stage)

Breaking OSD compliance into a submission-ready checklist makes it easier to track the certification, plan and PSD/SSR items shown on council on-site detention requirements pages. The table below turns each stage into practical sub-steps.

For quick reference: Mid-Coast Council’s cited guideline uses 75 L/s/ha in its stated context; Sydney Water’s cited guide specifies a flat stainless-steel orifice plate at least 200mm by 200mm and 3mm thick, with an orifice diameter of at least 40mm; the UPRCT handbook schedule calls for six-monthly residential and three-monthly commercial or industrial inspections; the cited Hornsby determination limits gutter discharge to 50 L/s per outlet point; and the 2025 revision to AS/NZS 3500.3 raised the Clause 3.6.2 valley-gutter catchment limit from 20 m² to 40 m². In the cited Georges River determination, the 300mm fencing threshold applies to that project-specific condition only.

Sourcing a Council-Compliant OSD Tank: What to Confirm Before You Order

Once your compliance parameters are locked in, choosing among the available OSD solutions is a matching exercise. Start with the certified design, then compare Storm Manager’s OSD tank range against the required storage volume, load class, access and maintenance provisions, outlet arrangement and installation constraints. Where Sydney Water’s specification applies, confirm that the outlet assembly meets its stainless-steel orifice-plate requirements. Also check every project-specific material or construction condition with the engineer and approval authority. Do not order from a generic capacity estimate: obtain engineer sign-off on the PSD/SSR design and confirm the applicable DCP and consent conditions first.

For a starting-point comparison of possible approval routes, consult the Authority Approval Pathway Matrix and review the product-level details in Storm Manager’s NSW council compliance hub. Final acceptance depends on the certified design and the relevant authority; company history is available on the Storm Manager profile.

2025-2026 Regulatory Currents: What’s Changing for NSW OSD Compliance

AS/NZS 3500.3:2025 updates stormwater-drainage clauses in the plumbing and drainage standards series. One published change to Clause 3.6.2 doubles the permissible valley-gutter catchment area from 20 m² to 40 m². At council level, Ballina Shire Council endorsed amendments across four DCP chapters on 27 November 2025. That example is evidence of DCP change activity, not proof of a particular OSD clause change.

Online tracking through the NSW Planning Portal’s DA Application Tracker makes application progress visible. These developments do not create one new statewide OSD formula, but they reinforce a practical control: verify the edition of every cited standard, the current council DCP and the project’s consent conditions before finalising design and submission documents. Current-document checks are a basic part of sustainable stormwater planning.

That valley-gutter catchment limit has doubled from 20 m² to 40 m². The change does not automatically invalidate an existing design, but it is a clear reason to confirm which edition of the standard applies before lodgement or revision. Council DCP chapters move on their own schedules, so standards checking should be a standing item on the compliance checklist rather than a one-off task.

Frequently Asked Questions

This guidance draws on publicly available material from Mid-Coast Council, Penrith Council and Canada Bay Council. The Georges River and Hornsby examples come from published Local Planning Panel business papers, not standalone council policy documents. Councils update their DCPs on independent schedules, so determine the requirements for your property before preparing a development application instead of treating the examples above as a generic standard. This article accompanies Storm Manager’s OSD Tank Compliance Guide, which adds product-selection detail and an authority pathway matrix.

Scope note: this is a procurement and coordination framework for surface water systems, not a drainage design. Requirements vary by country and authority. Below, the current English National Standards for Sustainable Drainage Systems, updated on 30 July 2025, provide an example of system-level thinking rather than a global rule or a substitute for a qualified drainage engineer.

The number on the crate is only the first number

Soakaway crate dimensions and module type describe the product, not the finished underground envelope. Connection methods, inlet and outlet positions, site levels, cover, formation and maintenance access still determine whether the assembled system fits.

Similarly, a product-specific void ratio provides one indication of a module’s capacity per unit volume. If a product is published with 95% void space, about 5% of its gross volume is occupied by the structural shell. Its catalogue data may pair that figure with design rainfall, acceptable outflow and contributing impermeable area; the 95% value belongs to that product, not to every crate. For projects in England, the national drainage standards show why module capacity must sit inside a wider hydraulic, water-quality and maintenance basis.

That distinction prevents a common comparison mistake. Two modules can look similar on a product sheet yet create different installed envelopes; a shallow option may appear to solve a space constraint until the complete soakaway system, connections and required cover are drawn together.

The Six-Check Crate Fit Register

Before deciding which crate goes where, complete six project checks. They turn “which is the right crate size?” into six site-specific evidence questions. This register does not design the system, but it exposes a nearly-right product before an unanswered assumption reaches procurement.

Engineering decision rule: a supplier can configure modules around a declared design basis, but the crate schedule should not become the design basis.

Used this way, the register also prevents an international guide from overstating local rules. England’s current standards address new infrastructure and development within their stated scope; the government announcement described the 2025 change as the first update in a decade. Retrofit work in another jurisdiction may have different approval, climate, discharge, groundwater, land-rights and adoption requirements. Start with the governing authority, not with a borrowed rule of thumb.

Installed geometry: the difference between a crate and a system

Installed geometry is the space left after every interface and constraint is shown, not the sum of bare module dimensions. That arrangement must coexist with formation, cover, pipe levels, connection zones, wrapping, inspection access, utilities and a practical construction sequence. Layouts that fit in a clean drawing box may not fit in the excavation.

Consider an illustrative warehouse-yard retrofit. A buyer identifies a rectangular area and asks for a shallow soakaway crate kit. Utility survey results then place an existing service through the proposed footprint, while the drainage connection fixes the inlet level. Revised geometry may need a different aspect ratio, another location or a non-infiltration outcome. Nothing about the nominal crate volume changed; the system boundary did.

Ground evidence must be equally specific. Buckinghamshire Council’s local guidance, for example, calls for infiltration testing at the proposed location and effective depth and discusses groundwater, contamination, separation, sediment and maintenance. Its numerical limits are local examples. Transferable practice is to record the percolation test method, location, depth and reviewer instead of relying on a nominal soil type or writing only “soil drains well.”

The Size-to-Site Boundary Map: a 9-Situation Project Matrix

When a buyer presents a site observation, the Size-to-Site Boundary Map shows the next evidence required. It is deliberately qualitative: it routes the question to the right owner without pretending that a blog can calculate storage, infiltration performance or structural capacity.

Another illustrative case shows why hydraulic intent belongs in the map. The current English standards provide one jurisdiction-specific example: new development may need infiltration where ground evidence supports it, restricted discharge where infiltration is unsuitable, or storage linked to rainwater harvesting. Those outcomes can change the membrane strategy, outlet, overflow, controls and inspection route. Calling every underground crate assembly a “soakaway” can hide that decision.

Read a duty claim as evidence, not as a blanket promise

Duty claims support product screening only within their stated test and installation assumptions. Searches for soakaway crates for driveways often collapse that distinction into a simple label. A rating does not independently verify the complete underground system for a driveway, loading yard or landscaped area; project review still includes cover, pavement, formation support, groundwater, construction traffic, lateral restraint and installation sequence. Buckinghamshire Council’s component guidance is a local example of why those site conditions remain part of the project evidence.

Separate two evidence packages in the submittal. Supplier evidence should identify the product, material, relevant conformity or test information, module geometry, connector arrangement and declared assumptions. BSI’s catalogue entry for BS EN 17152-1:2019, for example, identifies specifications for PP and PVC-U storm-water boxes used in infiltration, attenuation and storage systems. That product-standard scope does not replace project evidence verifying the assembled system against the actual ground model, load case, geometry, construction method and governing rules.

For product options intended for demanding applications, a buyer can review Storm Manage’s heavy-duty crate information as supplier evidence. Site-specific verification remains with the project designer, who should reject any comparison that removes the assumptions attached to a rating.

A project-ready kit should make its assumptions visible

Project-ready kits are controlled supply packages tied to a declared function, drawing revision and installation boundary. They are not simply crates plus a roll of non-woven geotextile. Each request should state whether the system infiltrates, attenuates, detains or supports rainwater reuse, because the interfaces and water-control components can differ. The English national standards provide one official example of treating function, treatment, construction and maintenance as connected requirements.

Susdrain’s system framing is useful here: sustainable drainage considers water quantity, water quality, biodiversity and amenity, while conveyance, attenuation, storage and infiltration are different functions. That is why a geotextile membrane, silt trap, inlet, outlet, vent, inspection point or impermeable interface should be selected by function rather than copied from a generic component list.

Maintenance handover should name the future operator, access route, inspection method, cleaning provision and funding responsibility. The BSI catalogue describes BS 8582:2013 as covering planning, design, construction, operation and maintenance for development-site surface water systems. Where a system crosses shared or third-party land, the project team should also resolve land rights and easements under the applicable law. Suppliers cannot infer those arrangements from a crate count.

An illustrative distributor order shows the commercial consequence. Although the product schedule may be ready, the tender drawing carries an old revision and the maintenance chamber has moved. Freezing shipment against the wrong drawing can create a correct product package for an obsolete layout. Project-ready orders therefore record the accepted revision, connection schedule, accessory scope, packaging basis and the person authorised to release production.

What should a request for quotation contain?

A useful request for quotation should contain the six evidence boundaries and controlled supplier deliverables. Attach the design basis, available envelope, connection schedule, load and cover assumptions, water-control function, wrapping intent, inspection provisions, programme, delivery location and required drawing format.

• Identify unknown fields as open actions; don’t transpose them into covert supplier assumptions.
• Identify the revision that controls the price and the revision that will authorise production.
• Separate project approvals from product evidence and commercial acceptance.
• Ask for installation drawings and accessory identification suitable for site handover.

From evidence register to configuration

Configuration should begin when the six checks have named evidence, owners and open actions. Late-stage configuration is where an incomplete register becomes expensive: a crate schedule may be technically plausible yet wrong for a revised connection level, maintenance route or drawing issue. A signed register and controlled drawing revision provide the release evidence Storm Manage needs to compare module formats, accessories, drawings and shipping arrangements without substituting product selection for project design. Where the English framework applies, retain the current national standards in the controlled project evidence set.

Use the Soakaway Crate Sizes & Kits solution page for that product-level handoff. It owns the sizing and kit discussion; this guide owns the evidence boundary that should exist before that discussion. For site execution planning, keep the separate soakaway crate installation guidance with the approved project drawings.

If the project brief is still uncertain about infiltration, attenuation, detention or harvesting, return to the modular soakaway crate system overview and confirm the water outcome with the responsible drainage designer. Product dimensions become decision-ready only after the system purpose and boundaries are stable.

Frequently asked questions

These answers define procurement boundaries rather than universal design rules. For work within the English framework, check the current national standards alongside the approving authority’s project requirements.

Are all soakaway crate sizes interchangeable?

No. Similar nominal storage does not make crate sizes interchangeable. Module geometry changes the installed footprint, connections, cover requirements and inspection access. Compare candidates against one controlled project basis, including levels, load assumptions and maintenance provisions, before treating either as suitable.

Why can two systems with similar storage volume need different layouts?

Equal nominal storage can produce different layouts because module proportions, connection positions and access requirements shape the complete envelope. One arrangement may fit the plan but clash with pipe levels; another may meet the levels but leave too little inspection space. Compare footprint, depth, cover, services, groundwater, treatment interfaces and construction sequence together.

Does a crate duty label decide whether it can sit under a driveway?

No. A published duty rating does not by itself confirm suitability for that location. The responsible designer must check the cited values and evidence against the site-specific load case, cover depth, pavement construction, sub-base and soil conditions, groundwater, construction traffic and planned maintenance. Acceptance applies to the verified installed arrangement, not to the label alone.

Do the same soakaway rules apply in every country and to both new builds and retrofits?

No. Approval paths and responsible parties differ by jurisdiction and project stage. New developments may need to follow current sustainable drainage policies, while retrofit projects must also account for existing infrastructure, utilities, site levels, property boundaries, operating assets and legacy installation standards. Rainfall methods, discharge limits, groundwater criteria and adoption rules may also differ. Check the relevant approving body, responsible designer and project-specific rules for approval and reliable long-term operation before applying any published example across geographical boundaries.

What should be confirmed before ordering a soakaway crate kit?

Confirm the six Crate Fit Register boundaries: jurisdiction and project stage; hydraulic basis and exceedance route; ground and groundwater evidence; installed geometry and loads; water-quality and maintenance provisions; and ownership, access and handover. Record the approving body, responsible designer, controlled drawing revision and supplier deliverables. Also identify unresolved utilities, construction loads, connection levels, treatment interfaces, inspection routes and delivery constraints. Keep each unknown visible as an assigned action before quotation review rather than allowing it to become a supplier assumption.

Reviewed by the Storm Manage technical team. Hydraulic, structural, geotechnical, regulatory and legal decisions concerning individual projects will still rest with the appropriate professionals and authorities.

Technical guide · Updated July 2026

Useful project briefs start with hydraulic behavior and responsibility, not a product label. This guide explains the water path, system forms, required interfaces, design inputs, installation evidence, and maintenance questions that should be settled before a supplier reviews a modular layout.

In practical terms, underground stormwater storage receives excess stormwater from urban areas or a roadway catchment, reserves the required stormwater volume, and meters discharge so a network is less likely to overload. Reducing downstream flooding, flooding and erosion may be a stormwater design objective, but the project model and approval process must verify the outcome.

Quick specs

1. What Is a Stormwater Detention Tank?

Stormwater detention tanks are engineered storage structures that receive runoff during a storm, hold it for a limited period, and release it at a controlled rate. Restricted outlets aim to keep post-development discharge within the criterion set by the drainage design and approving authority. Afterward, the tank draws down so storage is available for a later event.

Federal Highway Administration guidance describes tanks and vaults as below-ground storage used to control peak stormwater flows where surface space is limited. That definition matters because it describes a hydraulic job, not a particular material. Concrete vaults, pipe networks, chamber fields, and modular crate assemblies may all provide detention when configured for temporary storage and controlled release.

Detention is usually considered when development adds impervious area, the existing drainage network limits discharge, or valuable land can’t be dedicated to an open detention basin. Buried storage can sit beneath parking lots and release stormwater runoff into a storm drain, a dedicated surface-water network, or, where permitted, a combined sewer system. It remains only one way to manage stormwater. Civil or hydraulic engineers still have to coordinate the catchment, inflow points, downstream sewer or drainage system, overflow route, levels, maintenance plan, and approval evidence.

2. How Does a Detention Tank Store and Release Runoff?

On a drawing, the operating sequence looks simple, yet most avoidable problems occur at the interfaces. Sediment can arrive before the storage body. Inlets can distribute water unevenly. Small outlets can block. Overflow paths can be omitted from coordinated drawings. In practice, hydraulic performance depends on coordinating all four stages; treating the tank as an isolated box hides those failure paths.

1. Runoff enters through pipes, channels, or manholes sized and coordinated by the drainage designer.
2. Temporary storage fills while the downstream release is constrained. Air movement, inlet energy, and internal distribution may need explicit treatment.
3. Controlled discharge passes through an orifice, vortex device, weir, or another approved control. Because a small blocked opening can change the entire operating response, the control must remain accessible.
4. Drawdown occurs over the defined period, while a separate emergency path manages conditions beyond the design event or a blocked outlet.

A common assumption says that meeting one peak-discharge limit settles the downstream question. Receiving-channel evidence shows why the approved design may also need duration, erosive-flow, or stability checks.

What does stormwater detention mean?

Stormwater detention means holding runoff temporarily and releasing it after the inflow peak has passed. “Temporary” describes the water cycle, not the structure’s life. Buried tanks remain in place while active storage drains. Permanent storage, reuse, or infiltration indicates a different or combined function.

3. Detention vs Retention Tanks, Infiltration, Attenuation, and Harvesting

Authority guidance commonly distinguishes detention from retention, while project and vendor documents can group several water-management functions under “stormwater tank.” Define the required behavior in the brief instead of assuming the label carries one meaning in every market.

When specifications compare detention and retention tanks, stormwater retention must be defined by its intended water path. Some retention configurations store water permanently or for reuse, while detention capacity is intended to drain and become available for the next event.

US Environmental Protection Agency guidance separates controlled-release detention from retention or infiltration and places underground storage within a treatment train where water quality is part of the objective. By contrast, a reviewed cemetery project case uses one product family for several functions: detention, retention, treatment, and harvesting. Together, those sources show why functional wording matters. Project and supplier language may group systems that need different hydraulic details.

What is the difference between a stormwater tank and a detention tank?

“Stormwater tank” names what the structure handles; “detention tank” states one specific hydraulic role. Detention tanks hold runoff temporarily and drain through a controlled outlet. Other stormwater tanks might support harvesting, infiltration, permanent retention, treatment, or a combination. Specifications should name the required water path, not just the container.

State where inflow comes from, what volume is reserved for each function, how water leaves, what happens if the outlet fails, and who approves the design. Also identify whether treatment occurs upstream, whether the envelope must be sealed, and whether the owner can inspect and clean the system without entry. This prevents a supplier from solving a different problem than the engineer intended.

4. Detention Tanks and Vaults: Modular, Pipe, and Concrete Forms

FHWA guidance on underground tanks and vaults establishes the common hydraulic purpose; structural form and project interfaces still distinguish the options below.

Underground stormwater detention tanks create void space in different structural ways. None is universally “best.” The useful comparison is whether a form fits the project’s loading, geometry, groundwater, access, cleaning method, programme, local acceptance, and evidence requirements.

Common underground detention tanks include modular geocellular fields, poured-in-place concrete vaults, and corrugated metal pipe systems. Their versatility can preserve developable land when systems are installed beneath parking lots, but accessibility, soil conditions, structural loads, and the need for a sealed impermeable envelope still have to be resolved for the site.

Published in 2025, a review of geocellular modules emphasizes that both vertical and lateral behavior matter. One US patent granted that year likewise focuses on load path, lateral deformation, assembly, and shipment. Neither source proves that one product fits a site; both show why a single compression number or void percentage can’t carry the structural decision.

A common assumption ranks the highest void percentage first. Whole-system review can reverse that ranking when cleanout access, groundwater, lateral restraint, or authority evidence becomes the controlling boundary.

“Developing a functional stormwater management system requires a good understanding of existing conditions, a well-modelled design, and field experimentation for design confirmation.”

Practical reading: a format comparison creates a shortlist, not a design approval. Project engineers, geotechnical advisers, structural designers, suppliers, installers, and authorities each produce different parts of the final evidence.

5. Detention Systems: Components and System Boundaries

Storage is only the middle of a detention tank system. Complete scopes follow the water from catchment to receiving network and also follow people and equipment from inspection access to a safe maintenance method.

Philadelphia Water’s subsurface detention guidance is unusually direct about access and cleaning: grid systems can be harder to clean than vaults after sediment accumulates. In practice, the maintenance method should influence storage format and pretreatment before the footprint is fixed, not after the system is buried.

6. System Size Inputs and Project Data Before Review

Suppliers can arrange modules only after the project team defines the engineering problem. “Please quote 500 cubic metres” isn’t a sufficient design pack: it omits whether that number is active storage, the permissible discharge, levels, receiving-system limits, structural loads, groundwater, treatment duties, and approval basis.

Selection and monitoring criteria should identify the relevant water level, soil conditions, regulatory requirements, and applicable industry standards. If project documents cite an American Society of Civil Engineers reference, name the document and edition. A site near a wastewater treatment plant may also need interface, access, contamination, or owner-specific requirements stated explicitly rather than inferred.

1. For the hydraulic basis, supply the approved catchment, rainfall data, design events, required storage, allowable discharge, drawdown, and overflow case.
2. Receiving-system criteria cover downstream levels, capacity, surcharge, outfall condition, and any peak, duration, erosive-flow, or channel-stability requirement.
3. Water-quality duties identify target pollutants, treatment-train position, pretreatment, and separation from quantity-only storage.
4. Geometry records the available length, width, depth, inlet invert, outlet invert, cover, slopes, clashes, and construction tolerance.
5. Ground and water inputs cover soil, bearing condition, groundwater range, contamination constraints, infiltration permission, buoyancy, and dewatering assumptions.
6. Loads and design life include traffic, construction plant, buildings, landscaped cover, lateral loads, material exposure, and the governing structural basis.
7. Access and safety inputs state inspection points, cleaning equipment, isolation, lifting, ventilation, no-entry method, and responsibility for any confined-space assessment.
8. Approval evidence includes authority requirements, calculations, drawings, product data, testing, installation records, hold points, as-builts, and maintenance ownership.

Rainfall inputs must come from the basis currently adopted by the governing authority. NOAA Atlas 15 is under development and is intended to address nonstationary precipitation-frequency methods and future trends. Until a new dataset is issued and adopted for the project’s jurisdiction, preliminary development work shouldn’t be presented as the governing design standard.

Detailed calculation methods and budget drivers belong in the separate stormwater detention tank cost and sizing guide. This article keeps the boundary clear: identify the inputs and owners without publishing a second sizing worksheet or price table.

7. The 5-Boundary Detention Brief

This 5-boundary framework is a pre-supplier brief that checks whether project inputs and responsibilities are complete enough for meaningful system review.

The Five-boundary project screening grid below turns those checks into a reusable review prompt.

This method prevents one-variable selection. Tight footprints may favour modular grids, but difficult sediment removal may favour a more accessible vault. Heavy rigid structures may look stable, but groundwater can still raise buoyancy and waterproofing questions. Strong crate compression data may still sit outside the project’s lateral restraint, cover, or installation case. Each boundary can change the shortlist.

Philadelphia Water’s subsurface detention guidance is one reason maintenance access belongs inside the screening grid rather than in a later operations note.

Storm Manage reports an 40,000 sqm injection-moulding base with 200+ injection-moulding machines and more than 12 mould sets covering module and accessory variants. It also reports a typical 3–10 days lead time after order confirmation and container loading of up to 330 m³ of installed storage volume per 40HQ with optimized stacking. These are first-party capability statements; actual production allocation, module mix, packing efficiency, and delivery timing remain order-specific.

After the brief is complete, project teams can review modular stormwater detention tank systems against the defined hydraulic, structural, access, and evidence boundaries. That commercial step should follow the engineering brief, not replace it.

8. Geotextile, Installation Interfaces, Quality Checks, and Sign-Off

Wrapping is a hydraulic decision as well as an installation detail. Permeable geotextile can separate soil while allowing infiltration where the approved design permits it. Sealed detention applications may require a geomembrane and protective layers with controlled seams and penetrations. Hybrid functions need clearly divided zones. Substituting one envelope for another can change the discharge path.

Storm Manage states that its batch checks include compression-performance verification, dimensional-tolerance checks, Virgin PP or Recycled PP material-ratio control, and per-unit weight-consistency control. These checks can support product traceability and incoming inspection. They don’t verify the bearing surface, module assembly, field connections, membrane work, backfill, pavement, or the project engineer’s site-specific structural design.

Philadelphia’s stormwater review guidance requires key subsurface detention information to be documented before the system is covered. That’s a useful acceptance principle in any jurisdiction: identify irreversible checks, place them before backfill in the inspection plan, and name the person authorized to release each hold point.

For road and parking applications, the highway and car park drainage guide provides a related site-interface discussion. Governing project specifications and authority requirements still control.

9. Inspection and Maintenance After Commissioning

Maintenance should follow condition, site exposure, the approved plan, and authority rules rather than a universal calendar copied from another system. Inspection starts at the catchment and finishes at the outfall.

Long-term stormwater asset planning benefits from strategically placed surface access and monitoring points. Effective management does not mean frequent maintenance by default; it means inspection and cleaning frequencies respond to observed condition, sediment exposure, trigger events, and the approved maintenance plan.

• At the catchment and pretreatment stage, check debris, erosion, sediment loading, filter condition, sumps, and safe cleaning access.
• Inlets and inspection points reveal blockage, damage, unexpected standing water, displaced covers, and unsafe surface access.
• Storage observations include high-water evidence, drawdown, visible sediment, deformation signals, and leakage or infiltration inconsistent with the brief.
• Outlet-control checks cover obstruction, corrosion or damage, isolation, control-device condition, and downstream tailwater.
• Overflow and downstream reviews look for obstruction, erosion, evidence of exceedance, and effects on the receiving drainage system.
• Records capture the date, rainfall or trigger, observations, photographs, work completed, waste handling, unresolved defects, and responsible person.

A common assumption treats an access opening as a complete maintenance plan. In reality, the team must define reachable components, equipment, isolation, waste removal, surface working space, safety duties, and escalation for defects.

How is an underground detention system maintained?

Asset owners inspect accessible pretreatment, inlets, observation points, outlet control, overflow, and downstream condition, then remove debris or sediment through the method defined in the maintenance plan. No-entry cleaning is preferred where it can achieve the required result. Inspection should also compare observed drawdown with expected behavior, note high-water marks, trace unexplained leakage, and check whether upstream site changes have increased sediment or debris loading. Unexpected standing water, blocked controls, or damaged access covers trigger escalation before routine cleaning continues.

If entry could be needed, the owner and employer must assign the competent safety assessment, isolation, atmospheric testing, rescue, and permit duties required by the applicable jurisdiction. Maintenance plans should state trigger events, waste-disposal requirements, record retention, defect escalation, and who can authorize return to service. Records need enough detail to distinguish routine cleaning from a hydraulic, structural, or safety defect that requires engineering review.

An EPA enforcement summary updated in 2025 links alleged failures in permanent stormwater controls to requirements for inspection, maintenance, restoration, and accountability. Beyond that case, underground assets need a named owner, an accessible method, and records that survive the construction handover.

10. What’s Changing: Documentation, Land Use, and Regional Language

Near-term change isn’t one universal new tank. It’s the rising importance of traceable inputs, land-efficient layouts, current rainfall methods, structural evidence, maintenance ownership, and clear functional language.

Search demand and market forecasts can’t establish a technical trend by themselves. Defensible 2026 reviews start with dated government, water-authority, academic, and project evidence. They also state what isn’t yet adopted. That discipline matters because rainfall inputs, regulations, and terminology change at different speeds among overseas markets. A “stormwater attenuation tank” may describe a detention function in one market, but the project brief must still define the water path.

Frequently Asked Questions

An attenuation tank cost is a project-specific commercial figure built from a declared storage basis, system boundary, delivery point, responsibilities, exclusions, date, currency and tax treatment. Two quotations are not comparable just because each shows one total. This guide is for procurement teams that need to compare quote scope, not to publish price bands, calculate storage or replace a drainage design.

Ask “what has each supplier agreed to provide?” before asking which price is lower. That question keeps a stormwater quote useful through design review and internal approval.

What Does an Attenuation Tank Cost Estimate Actually Cover?

Start by labelling the estimate stage. Concept allowances, supply quotations, delivered figures, installed estimates and handover costs answer different questions; none should be silently substituted for another. For Storm Manage procurement buyers, the risk is an evidence gap because supplier labels can mask different boundaries. The method helps buyers investigate attenuation tank prices or installation cost without implying that one number fits every site.

Don’t let a supplier label conceal the stage. Ask whether the figure includes only an attenuation crate package, a sealed attenuation system, delivery to site, complete installation, or a handover-ready package.

The commercial label also cannot replace the design, construction, operation and maintenance responsibilities described in the National Standards for Sustainable Drainage Systems. Use that responsibility boundary to identify what remains outside the quotation.

Decision point: A lower total isn’t a lower attenuation tank cost until the estimate stage and included evidence are the same.

Freeze the SuDS Surface Water Drainage Basis and Exclude Soakaway Crate or Rainwater Harvesting Scope

Freeze the drainage basis before asking suppliers to compare anything. The brief should state the required storage basis, rainfall event, stormwater runoff destination, sewer or watercourse discharge parameters, loading context, ground conditions, drawing revision and known interfaces. If provisional fields stay hidden, the resulting supplier mismatch is a budget risk because quotations no longer share one basis.

The National Standards for Sustainable Drainage Systems describe how systems should be built, operated and maintained, but they’re England-specific and non-statutory. Local approval, adoption and maintenance-acceptance routes still need confirmation for the project jurisdiction.

An attenuation tank temporarily stores runoff for controlled release. By contrast, a soakaway infiltrates water into suitable ground, while combined rainwater harvesting and attenuation introduces reuse interfaces. Some modular products suit more than one arrangement, but quote boundaries aren’t interchangeable. For detention terminology or hydrology, use the stormwater detention tank cost and sizing guide; this article doesn’t calculate storage or rank drainage systems.

Engineering Note: Treat the drainage engineer’s design, the approving body’s discharge requirements and the asset-adoption or maintenance-acceptance route as controlling inputs. A product quote can document an assumption; it cannot approve the hydraulic design or acceptance pathway.

Scope check: Put the drainage basis and wrong-scope exclusions at the top of the request, not in a footnote.

Normalize Attenuation Storage Volume Before Comparing Cost per Cubic Metre

An attenuation tank cost per cubic meter (m3) can be useful only after every offer uses one declared, hydraulically comparable water storage basis. For Storm Manage quote reviews, that mismatch is a procurement risk because similar volume labels can hide different assumptions.

Don’t treat the result as a universal market rate. First confirm the same critical-duration event, allowable discharge rate, surcharge assumptions and design revision; matching volume words alone don’t establish hydraulic equivalence.

Use one row per quotation to identify whether the stated value is a gross envelope, a nominal crate volume, an installed storage figure or another defined value. Also record the currency, tax treatment, quotation date and whether the unit figure covers supply alone or includes installation.

The England drainage standards require the allowable discharge rate and related design basis to be documented. They don’t provide a project price, which is why hydraulic inputs and commercial scope must remain separate comparison fields.

The values below show how to format aligned quote fields; they aren’t design recommendations and must be replaced by approved project values.

Even when each field looks aligned, request its definition before dividing a total by volume. That prevents false precision in a cost per m3 comparison.

Budget control: Normalize storage and hydraulic assumptions before normalizing any cost figure.

Map the Attenuation Tank System: Modular Crate, Liner, Geotextile and Membrane Scope

Map every physical component and its owner before comparing an attenuation tank system quotation. For a Storm Manage supplier review, a hidden component gap creates rework risk because one package can omit a critical interface.

Modular crate systems are only one part of the package; an impermeable liner or geomembrane, geotextile, connectors, access points and drawings may be included, excluded or provisional. Buyers should also distinguish sealed attenuation from infiltration-led scope.

Terminology check: Suppliers may describe similar boundaries differently, so retain their wording in a quote appendix and ask the designer to confirm equivalence before scoring price.

• Catchment and storage basis: record the catchment area, roof contribution, local rainfall data, storage capacity and volume of water; these fields describe surface water runoff and whether the design intends to temporarily store stormwater runoff.
• System type: distinguish stormwater attenuation crates, geocellular attenuation and underground stormwater storage from concrete tanks; none of those labels by itself proves a complete attenuation or storm attenuation package.
• Discharge: identify whether the design names a flow control chamber, vortex flow control, water discharge path and controlled rate, then specify whether the connection is 110mm or 160mm.
• Approvals and delivery: identify building control or its local equivalent, sustainable urban drainage systems requirements, commercial and industrial loading, installation time, and any quotation expressed per cubic metre of storage.
• Dimensions and materials: treat 700mm and 1000mm dimensions, tonne-based load statements and HDPE material descriptions as project-specific inputs, not defaults; a quote for water management, stormwater management, surface water management or drainage solutions still needs the same boundary checks.

Storm Manage describes an 200,000 m²+ production base, about 50,000m³ monthly output and more than 600,000m³ annual capacity, plus accessories, drawings and container-loading support. These are first-party capacity and supply-boundary statements, not project-performance guarantees. Use its attenuation tank system overview and design information to prepare questions, then obtain project confirmation.

Procurement note: A component list becomes useful only when every line says included, excluded, provisional or by others.

Assign Flow Control Systems, Orifice Plate, Inlet and Silt Trap Responsibilities

Assign responsibility for flow control, inlet, outlet, silt management, testing and handover in writing. For Storm Manage supplier reviews, this gap matters because the quotation may be complete for crates yet leave the hydraulic interface unresolved. The England standards connect design with construction, operation and maintenance; local guidance also stresses defined management responsibilities.

Use plain labels rather than unexplained abbreviations: responsible for design, supplies, installs and verifies or hands over. Apply them to the orifice plate or other flow-control arrangement, inlet and outlet connections, drainage pipe interfaces, silt trap provision, access chambers, testing and record information. Project drawings and the drainage engineer remain controlling.

Where site teams need a prompt for the interface conversation, Storm Manage’s flow-control interface guide can be used as a question list, not as a replacement for the approved design.

Key takeaway: A quote isn’t fully comparable while a flow-control or handover responsibility is unnamed.

Use the 12-Line Scope-to-Cost Boundary Ledger

The 12-Line Scope-to-Cost Boundary Ledger is a short procurement record for explaining why quotations differ. Complete it before negotiating totals. It works because it separates physical components from approval, logistics and acceptance dependencies that can otherwise be hidden inside a single line item.

For supply planning, Storm Manage’s current public planner displays 3–5 production weeks, with lead time confirmed per order, and up to approximately 330 m³ of installed storage per 40HQ with optimised stacking. These are current first-party planning indicators, not industry benchmarks or a guarantee for every configuration; customs, inland haulage and project-specific logistics remain separate considerations.

Key takeaway: If a difference can’t be placed on one of the twelve lines, its cost responsibility isn’t ready to be negotiated.

Run a Like-for-Like Attenuation Tank Supplier Quote Comparison

Run the comparison in six steps: qualify the source, normalize the storage and commercial basis, mark scope gaps, price only known gaps, tag uncertainty, then document the decision. This turns an attenuation tank supplier quote review into a controlled procurement exercise rather than a spreadsheet race to the lowest total.

1. Set aside quotations from like-for-like ranking when they omit the drawing revision, storage definition or validity period.
2. Check hydraulic equivalence before comparing nominal capacity or cost per m3.
3. Transfer every inclusion and exclusion into the twelve-line ledger.
4. Mark missing information as unresolved rather than estimating it from a competing quote.
5. Ask the supplier or responsible project party to close the material gaps.
6. Record the chosen basis, residual risk and next revalidation date.

For example, a non-priced Offer A may include delivery but exclude unloading and flow-control verification. Offer B may include installation but be silent on the drawing revision and acceptance records. Neither is complete until omissions are assigned. Useful comparators reserve green for a defined, evidenced inclusion.

Storm Manage teams working on a traffic-heavy supplier comparison can use the highway and car-park drainage application page to frame loading and access questions; it isn’t evidence that a particular site is approved for a given load.

Comparison rule: Compare documented scope gaps first, then commercial totals.

Choose the Right Cost Evidence: Guide, Calculator, Budget Quote or Installed Estimate

Use the least intensive evidence that’s fit for the next decision, then escalate as design uncertainty, interface risk, procurement commitment or contract exposure rises. This 4-Level Cost Evidence Ladder helps a buyer use guidance and online tools without mistaking them for an installed project estimate.

For current commercial support, use Storm Manage’s project-specific attenuation tank cost estimate and calculators. Record the input version, date and whether the output covers supply alone, delivery, installation or handover. That tool can structure an allowance, but can’t own an exclusion or confirm an approval route.

Evidence rule: Move up the ladder when uncertainty or commitment increases; don’t demand certainty from an early-stage tool.

2026 Revalidation: When an Older Quote Needs Rechecking

In 2026, Storm Manage supplier and procurement reviews should record quote age as a budget risk because commercial inputs are time-bound, not because a generic index predicts an attenuation tank price. The UK’s all-work construction-material index increased 2.1% in February 2026 compared with February 2025, but it’s an aggregate measure and can’t forecast an individual tank, crate package or installed system cost.

Use three simple revalidation triggers: the quotation validity date expires; the drawing, discharge or adoption basis changes; or logistics, programme or installation responsibility changes. The same principle applies to regulatory timing: the cited England standards are a design and management reference, not a statutory price list, and local requirements may differ. For a compliance-oriented input checklist, see SuDS compliance information.

Key takeaway: Date every commercial input and revalidate its scope when the design, approval route or logistics assumptions change.

FAQ: Frequently Asked Questions

These answers apply the same declared-basis principle. Questions such as “What are the common problems with attenuation tanks?” and “What’s the lifespan of an attenuation tank?” require project-specific design and maintenance evidence; they aren’t answered by an isolated supply price.

How much does an attenuation tank cost per cubic metre?

Figures expressed per cubic metre are comparable only when both quotations use the same water storage definition, hydraulic assumptions, system boundary, delivery point, date, currency, tax treatment and installation scope. Module supply figures aren’t installed project costs. Use the result as a controlled comparison field, not a universal market price, and record any basis still awaiting confirmation.

What should an attenuation tank quote include?

Usable quotes identify the design revision, required storage and discharge basis, proposed system, accessories, containment scope, inlet and outlet interfaces, delivery term, unloading, installation boundary, testing, documents, exclusions, validity period, currency and tax basis. They should distinguish confirmed, provisional and excluded responsibilities; for each provisional field, record who must confirm it, the evidence required, the deadline for confirmation, and what change in scope or budget the answer could trigger before commercial ranking begins.

Can you build over an attenuation tank?

Building over an attenuation tank may be possible only where the system, cover depth, pavement build-up, access and loading are designed for the intended use. Product ratings alone aren’t approval for a building or traffic area. Put the proposed use into the input pack and obtain written confirmation from the drainage and structural designers before treating it as an accepted quotation basis.

Can an online attenuation tank cost calculator set my final budget?

No. A calculator can support an early allowance when its assumptions match the project, but it can’t confirm groundworks, access, temporary works, local labour, interfaces, taxes or contractual risk. Record the inputs and drawing revision. Check whether the result covers supply alone, delivery or installation and whether storage is nominal or usable. Replace that allowance with a supplier budget quote once the system boundary is named, then with an installed estimate when civil works and contractual responsibilities are defined.

Is an attenuation tank a soakaway?

An attenuation tank is not a soakaway. Attenuation stores runoff within a controlled-release system, while a soakaway infiltrates water into suitable ground. Their containment, discharge route and approval basis differ, so buyers should not treat the two quotations as interchangeable.

What information does a supplier need for a budget quote?

A supplier needs the site and delivery location, drawing revision, storage and discharge basis, footprint and depth constraints, loading context, connections, containment, accessories, programme, delivery term, unloading plan and required documents. Mark unknowns so assumptions stay visible inside the quotation.

FAQ rule: Common questions usually require a declared basis and accountable scope, not an isolated price.

Conclusion: Record the Boundary Before You Record the Cost

Defensible budgets follow one sequence: label the estimate stage, freeze the drainage basis, normalize storage, map scope, choose evidence and record uncertainty. Storm Manage’s commercial page can support a project-specific attenuation tank cost discussion once the input pack is ready.

This guide uses current public first-party supply-planning information where stated, together with external technical sources; it doesn’t offer a price forecast, approval, sizing calculation or performance guarantee.

Key takeaway: Record the scope boundary first; only then can a cost become a defensible project input.

Reviewed by the Storm Manage technical team  |  (Updated July 2026)

An airport drainage system is a documented water path, not simply a line of inlets and pipes. It protects airside operations, pavement support, receiving waters, and the people responsible for responding when rain, snowmelt, debris, or service-area fluids interrupt that path.

1. What an Airport Drainage System Must Protect Before It Moves Water

FAA’s live record for Advisory Circular 150/5320-5D, Airport Drainage Design, lists it as active and describes its scope as surface storm drainage plus subsurface drainage for paved runways, taxiways, and aprons. Its scope prevents airport planning from being reduced to one visible grate or one downstream pipe.

Airport drainage is essential, but the design of airport drainage is context-led. A drainage system design for airport environments has to support runway safety, air traffic continuity, and operational safety and efficiency without reducing each outcome to a pipe schedule.

Common mistake: A drainage component isn’t a drainage path. Useful briefs name the source area, low-point evidence, pavement interface, route, destination, and owner of each handoff. That structure supports operational safety without pretending that one generic detail fits every airport.

2. Match the Drainage Type to the Airside Zone, Not to a Generic Site Plan

Assign the types of airport drainage system by zone and water path. ACRP stormwater hydrology guidance helps frame movement across and through the airport landscape. Airport drainage design has different questions at a runway edge, beneath pavement, at an apron stand, and at a landside swale. A zone register showing what enters, what must stay out, and who can inspect it is more useful than the phrase “drainage system in airport.”

Sound design of airport drainage systems should connect runways and taxiways, surface drainage, subsurface controls, and downstream management systems. It shouldn’t assume that every zone can use identical drain systems or meet stringent requirements through one standard detail.

Write the requirements of airport drainage system work against this register, with local airport and environmental rules taking precedence over a generic guide. This also prevents a service-area water issue from being treated as ordinary stormwater.

3. Set the Runoff Design Basis Before Sizing Any Drain

Runoff work has engineering value only after the team agrees on catchment limits, rainfall basis, surface response, flow route, downstream condition, and units. ACRP points airport users toward recognized hydrology methods, while EPA’s screening material stresses ranges of assumptions rather than one universal result. Use the calculation to expose decisions; don’t treat it as a stamped design.

When estimating runoff from heavy rainfall, distinguish a provisional peak from the large volumes of water that routing may spread over time. A high hydraulic loading signal or a surface runoff estimate is a prompt for an approved model, not a design answer by itself.

How do you estimate runoff for an airport drainage design?

Engineers can use a provisional Rational Method check where the governing engineer confirms it’s appropriate: Q = C × i × A. In customary units, Q is cubic feet per second when C is dimensionless, i is rainfall intensity in inches per hour, and A is area in acres. Its reliability depends on the locally approved rainfall event, mapped catchment, and chosen coefficient.

4. Use Grades, Catch Basins, and Drainage Channels to Control Surface Water

The FAA’s active airport drainage record places surface storm drainage for paved runways, taxiways, and aprons inside the circular’s scope. Within that boundary, surface collection begins with the slope and grade-to-low-point sequence, not an assumed spacing rule. Review the survey, then identify where water arrives, where it crosses pavement joints or edges, how catch basins and drainage channels receive it, and how a crew reaches the collection point after an event. Reviewed evidence doesn’t establish universal inlet spacing, grade, or inspection intervals, so those values belong to approved drawings and local criteria. Apply the same boundary to hydroplaning risk, runway flooding, and erosion of slopes: record the condition, then use the applicable airport criteria.

Can catch basins alone prevent runway ponding?

No. Catch basins collect at the low points created by the overall surface geometry; they can’t correct an unverified grade, obstructed approach path, damaged interface, or blocked downstream route. A practical walkdown follows the intended flow route in dry conditions, records sediment and debris paths, and checks whether access remains possible during an operating restriction.

5. Keep Water Out of the Pavement Support System

Surface water can appear controlled while subsurface water still reaches the pavement support system. The FAA drainage circular includes subsurface drainage for paved airside areas, which is a reminder to coordinate drainage drawings with geotechnical findings, pavement sections, observed groundwater, and the intended discharge route.

For subsurface drainage systems, use a short cross-section review: identify the surface entry point, the possible below-surface migration path, the intercept or subdrain concept, the outlet elevation, and the inspection evidence. Adequate subsurface drainage supports pavement durability by reducing the chance of a wet subgrade and weakened pavement foundations. Exact geometry and criteria remain project-specific; the guide can’t diagnose saturated and weakened pavement foundations or supply substitute values.

Airport runoff management needs integrated attention to quantity, chemistry, and toxicity.

6. Trace the Conveyance Route to Treatment, Storage, or a Controlled Outfall

Conveyance is a continuity check. Channels, underground pipes, ditches, shallow open channels, controls, and outfalls should form one traceable hydraulic route. ACRP treatment guidance notes that airport stormwater objectives can include peak-flow control, infiltration, temperature, attenuation, and removal of sediment, deicers, nutrients, bacteria, and metals. The objective must be named before a route can be judged. For a broader planning sequence beyond the airside boundary, the SuDS drainage development guide connects source, control, and downstream approval questions.

5-Step Airside Water-Path Decision Map

Definition: A five-step review that follows source area, collection point, pavement protection, conveyance/control, and the final storage, discharge, or inspection handoff.

1. Source: identify rainfall, wash, deicing, or other water at its origin.
2. Collection: confirm grade, low point, and access.
3. Protection: flag pavement support and erosion exposure.
4. Conveyance: trace every level change, control, and access point.
5. Destination: confirm treatment, storage, approved outfall, or an unresolved handoff.

Common mistake: “Treatment” has no single airport meaning. Peak-flow, sediment, and deicer objectives can require different control logic. Name the objective and responsible owner before calling the route complete.

7. Treat Aprons and Aviation Service Areas as High-Constraint Drainage Zones

Apron drainage should begin by separating four pathways: ordinary stormwater, washwater, aircraft-deicing discharges, and pavement-deicing runoff. They may share geography, but they don’t automatically share a collection, treatment, isolation, or permit decision. In the United States, the federal 60% available aircraft-deicing-fluid collection requirement applies only to a defined subset of qualifying new cold-climate airport sources; existing-airport requirements remain permit-specific.

General aviation airports and larger hubs may de-ice aircraft or encounter aviation fuels under different operating and permit conditions. Whether a discharge is compliant is an environmental compliance decision for the applicable authority. Preserve those boundaries so stringent requirements aren’t copied from the wrong airport class.

8. When Airport Rainwater Needs a Storage Design Handoff

Move to a separate storage review when the provisional water balance, constrained site, groundwater condition, downstream limit, or access requirement can’t be resolved in the drainage concept. ACRP’s stormwater and bird-hazard research shows why a bigger tank doesn’t neutralize an airfield wildlife hazard. Where applicable, treat the FAA 7460 process, Airport District Office, and wildlife-hazard coordination as separate siting gates rather than as a capacity calculation.

9. Build Airport Stormwater Management Around Inspection Triggers

Airport stormwater management becomes visible when an inspection record connects a known low point to an owner and a response trigger. One regulated U.S. deicing-pad context includes a seasonal-start inspection, but that doesn’t create a universal interval. Set frequency through local procedures, seasonal exposure, past events, and asset condition. Preventing costly damage due to flooding while supporting safety and operational efficiency requires traceable evidence.

Drain-to-Dispatch Check

Definition: A field handoff record covering water-path owner, low-point evidence, access route, sediment or debris status, and the response trigger.

This named check is deliberately simple. It doesn’t set a universal schedule or declare an airside condition safe; it makes the evidence needed for the next decision easier to assemble.

10. Outlook: Approval and Maintenance Evidence Will Drive the Next Design Conversation

For 2026, the strongest drainage decision is an evidence decision: teams that preserve dated assumptions, water-path ownership, inspection findings, and post-event records can explain why a concept remains suitable when rainfall scrutiny or operating conditions change. The FAA page for AC 150/5320-5D was updated in May 2026 and still lists the circular as active, but that status doesn’t replace local criteria or project approval.

A 2024 peer-reviewed airport-runoff review supports an integrated view of runoff quantity, chemistry, contaminants, toxicity, and remediation choices. For a team planning work in 2026, the action is practical: recheck live authority records, retain the calculation inputs and limits, and add FAA 7460, Airport District Office, and wildlife-hazard coordination to the approval route whenever storage siting could affect airport safety.

The practical risk is a concept that works hydraulically but can’t show current approvals, inspection ownership, or wildlife-siting coordination.

Search-demand background only: an adjacent commercial query rose year over year in the project keyword data. That directional signal isn’t an engineering forecast and shouldn’t replace hydrology, environmental, or airport-operating evidence.

FAQs: Airport Drainage System Questions

What happens if an airport drainage system fails in heavy rain?

What is the frequency of inspections of the airport drainage system?

Are aircraft able to use a runway that has water on the surface?

Are all airport drainage systems the same?

What is the most demanding part of airport drainage maintenance?

What is airport stormwater management?