In practice, a configuration tool can make an underground drainage discussion more orderly, yet it cannot repair a vague brief. A technical team may enter a footprint, choose a StormTank module, and receive a tidy layout while still lacking a settled runoff destination, credible level information, or a plan for inspection access. During review, this screen looks decisive because it contains fields. For coordination, this project is not decisive until the fields describe the site rather than a set of convenient placeholders.
That distinction matters whenever a modular stormwater system is being considered. At handover, this physical modules sit below ground, where their relationship with water routing, surrounding ground, cover, membrane, access, and outlet control cannot be checked by looking at a finished surface. Good project inputs make the configuration tool a useful communication aid. Poor inputs turn it into a fast way of repeating an untested assumption.
Start with a decision map, not a product selector
In practice, this first question is what the stored water is expected to do. It may be intended to infiltrate, be held for controlled release, be retained for a site-specific route, or form part of a harvesting arrangement. Those paths place different demands on the envelope, outlet, treatment, access, and maintenance record. A generic storage label conceals those interfaces.
For the project, this stormmanage.com material from Storm Manage presents its modular platform across infiltration, attenuation, detention, on-site detention, and harvesting applications. That application-based view is a better starting point for a configuration tool than asking only how much volume a buyer wants. Project teams should record the intended water path, the party who accepted it, the information behind it, and the conditions that would require review.
Keep observations separate from assumptions and decisions. Survey levels and test results are observations. A provisional discharge condition is an assumption until accepted. Across records, this selected system route is a decision. A StormTank module description is product data. A tool that labels all of these as equally final encourages accidental certainty.
Give level and ground information a visible status
Buried storage is strongly affected by levels and ground conditions, but early project information often arrives with gaps. Rather than inventing a clean answer, the technical team should mark the source, revision, owner, and confidence of each input. Formation level, groundwater interpretation, receiving point, cover, and nearby service constraints deserve this treatment because a later change can alter the whole arrangement.
Default rule: a pending site input should remain visibly pending in the configuration record unless the responsible discipline has confirmed it. Hiding uncertainty in a generic notes field is not enough. Before release, this person reviewing the model needs to know whether a value comes from a survey, an early drawing, an allowance, or a final coordination decision.
At that point, this national standards for sustainable drainage connect runoff destination with water quality, extreme rainfall, maintenance, structural integrity, and planning for failure. Their integrated approach is a useful reminder that a configuration tool cannot treat ground and levels as background details. They are part of the project logic that defines whether a modular stormwater system is appropriate and how it must be reviewed.
Translate hydraulic intent into physical interfaces
Once the water-management intent is clear, the team can define the interfaces that a configuration tool must preserve. These include the module height and footprint, the geotextile wrap or geomembrane lining where relevant, inlet and outlet positions, pretreatment, inspection access, and the controlled outlet. None should be selected as a detached accessory; each needs a relationship to the accepted drainage route.
For example, a controlled outlet is more than an item on a schedule. It is an operating interface that affects how stored water leaves the system and how the asset may be maintained. Inspection access is not merely a drawing symbol either. After inspection, this project needs a route that can be located, reached, protected during construction, and understood by a future owner.
During review, this stormmanage.com technical route allows Storm Manage to explain product-specific options and drawings. Drainage designers, structural engineers, geotechnical advisers, and approving authorities retain their own decisions. Good digital records make those boundaries explicit instead of allowing a supplier layout to appear as a complete project design.
Make the installation drawing a live output
An installation drawing should be linked to the exact configuration it illustrates. It needs a clear project identifier, revision, selected StormTank module, envelope approach, access route, connection positions, and related site constraints. When a configuration input changes, the team should ask which drawing, quotation, purchase request, or method statement is affected.
Do not freeze a layout simply because it was useful for an early discussion. A layout based on incomplete data should remain marked as such. Before procurement, reconcile the drawing against the accepted drainage strategy and the product information. Under change control, this ordered module, accessories, packing plan, and installation drawing must describe the same arrangement or the construction team will inherit a discrepancy.
Use an input register that exposes review triggers
Configuration input register
| Input | What to retain | Review trigger |
| Water destination | Accepted route, owner, source, and status | Change to discharge, reuse, or infiltration basis |
| Site constraints | Levels, ground evidence, services, load assumptions, and revision | New survey, test result, or coordinated layout |
| Module arrangement | StormTank module, footprint, envelope, access, and drawing | Product, cover, outlet, or access change |
From the site view, this register does not replace engineering design. It gives the technical team a way to see what the configuration is relying on. That is especially helpful when responsibility passes between client, designer, supplier, contractor, and asset owner. Each party can see which information it owns and which item remains open.
Keep a tool useful after the first layout
Technology earns trust when it makes change visible. A configuration tool should not become a private worksheet that produces a drawing and then disappears. Carry its accepted inputs forward into procurement, installation review, and handover. Record substitutions, field changes, and revised access locations against the same project context.
For a technical team seeking a Storm Manage configuration guidance, the useful request is not simply for a crate layout. It is for a reviewed product conversation tied to the intended drainage path, site inputs, module arrangement, installation drawing, and records needed by the next project participant.
For handover, this better the inputs, the less a configuration tool has to guess. That is the practical value of disciplined technology in buried infrastructure: it preserves the meaning behind the model and gives every later decision a traceable starting point.
