A drainage submission is often treated as a drawing-package exercise until an authority comment, site constraint, or late architectural change stops the project. In practice, a guide to PUB drainage submission must start with one question: can the proposed development collect, convey, and discharge stormwater without creating flood risk, obstructing public drainage, or conflicting with the approved site layout?
For owners, developers, architects, and contractors, the objective is not simply to obtain clearance. It is to establish a drainage design that can be built, inspected, coordinated with other disciplines, and maintained after completion. Early technical coordination is usually less expensive than redesigning ramps, external works, detention facilities, or connection details after construction has begun.
What a PUB drainage submission is designed to prove
PUB drainage requirements apply to works that affect surface-water runoff, drainage reserves, public drains, roadside drains, culverts, and drainage connections. A new building, addition and alteration project, redevelopment, change in site levels, driveway revision, or substantial external works package can all trigger drainage review.
The submission needs to demonstrate that runoff is managed within the site and discharged through an acceptable arrangement. The authority will assess whether the proposed drainage system, discharge point, levels, clearances, and supporting structures are appropriate for the development and surrounding public drainage network.
This is why drainage cannot be finalized in isolation. The civil design must align with the architectural footprint, landscape plan, vehicle access, structural foundations, utility corridors, finished platform levels, and any flood-protection strategy. A technically sound drain route on a civil drawing may still be unbuildable if it runs through a lift pit, clashes with a retaining wall, or sits beneath a future utility trench.
Start with site information, not drafting
The quality of the first site review often determines whether the submission moves efficiently. Before detailed design begins, the project team should establish the existing drainage context: site boundaries, existing drains, drain sizes and levels where available, nearby public drains, drainage reserves, access conditions, proposed site grading, and discharge opportunities.
Topographical information is particularly significant. Drainage is governed by levels, so an inaccurate survey can create false assumptions about whether gravity discharge is feasible. This can affect ramp gradients, basement thresholds, external paving, landscaping falls, and the need for pumping or other engineered measures.
The team should also identify whether the proposal affects an existing drain, requires diversion, encroaches near a public drain, or depends on a connection that cannot be confirmed from record drawings alone. Where conditions are uncertain, a site investigation or verification survey may be required before the design is committed.
For redevelopment projects, existing infrastructure is frequently the critical constraint. An old drain shown on archived plans may have been altered, obstructed, or abandoned. Conversely, an unrecorded drain or service can appear during excavation. Allowing time for verification is a practical risk-control measure, not an administrative delay.
Core documents in a PUB drainage submission
The exact submission package depends on the project type, site conditions, and proposed works. However, a complete package commonly combines technical drawings, calculations, site information, and professional endorsements. The design should be presented clearly enough for the reviewing officer to trace the flow path from collection point to approved discharge.
A typical drainage package may include:
- Location, site, and drainage layout plans showing boundaries, existing and proposed drains, flow directions, connection points, drain sizes, and relevant reserves or public-drain interfaces.
- Long sections and cross sections that establish invert levels, gradients, cover, structural interfaces, and the relationship between proposed private drains and public infrastructure.
- Hydraulic calculations and design information supporting drain sizing, runoff assumptions, detention or retention measures where applicable, and the proposed discharge arrangement.
- Construction details for inspection chambers, catch pits, gratings, channels, silt-control provisions, outfalls, headwalls, and any special structures required by site conditions.
- Supporting plans that coordinate finished levels, vehicle crossings, retaining walls, landscape works, utility routes, and erosion or sediment-control measures during construction.
Drawings should distinguish clearly between existing and proposed works. They should also use consistent levels, references, and terminology across civil, architectural, structural, and mechanical plans. A submission can be delayed by relatively basic inconsistencies, such as a drain level that differs between the layout and section or a connection shown in one discipline’s drawing but absent from another.
Drainage calculations and level design need to agree
Hydraulic calculations are not separate from the drawings. The contributing catchment areas, runoff coefficients, drain dimensions, gradients, and detention assumptions must correspond to the physical layout shown. If the design changes after calculations are prepared, the calculations may need to be reviewed and updated.
Level design deserves the same scrutiny. Water follows the lowest available route, including routes that the designer did not intend. A driveway falling toward a building entrance, a planter without an overflow path, or a high point created by later paving can redirect runoff and create ponding. These issues may not be obvious on a plan view alone.
The correct approach depends on the site. A small landed-house addition may need a straightforward private-drain modification and connection assessment. A larger industrial, commercial, or mixed-use development may require more extensive runoff management, phased external works coordination, and careful interface planning with public drains. Basement developments and sites with constrained discharge levels require especially close coordination among civil, structural, architectural, and M&E teams.
Submission coordination is where avoidable delays occur
Most drainage comments arise from incomplete information, unresolved interfaces, or changes made after the drainage design has been issued. The best way to reduce rework is to appoint the relevant qualified professional early and treat drainage as a live design workstream through the design and construction stages.
The drainage designer should coordinate directly with the architect on roof plans, canopy drainage, finished floor levels, landscape surfaces, bin-center wash areas, and access ramps. Structural coordination is necessary for drain crossings, retaining walls, foundation conflicts, and the support of covers or slabs. M&E coordination is needed wherever pumps, discharge systems, services, or equipment rooms affect drainage levels and access.
Contractors also need a coordinated construction set. Approval drawings alone may not resolve every site installation detail. Before work starts, the team should verify actual drain invert levels, set-out points, connection locations, and the sequence of excavation, temporary drainage, and permanent works. This is particularly important during the wet season or where existing operations must remain active.
Common causes of PUB drainage submission comments
A well-prepared submission can still receive technical queries, especially on complex sites. However, repeated comments are often preventable. Common issues include unclear discharge points, missing or inconsistent levels, inadequate sections, unverified existing drain information, clashes with structures or accessways, and calculations that do not match the latest plan.
Another recurring issue is designing only for normal rainfall flow while overlooking local collection points. Low-lying vehicle ramps, loading bays, open courts, planter edges, and basement approaches need deliberate drainage treatment. The solution may involve grading, trench drains, sump arrangements, overflow paths, or a combination of measures, subject to the project design and applicable requirements.
Construction-stage drainage also matters. Excavation, exposed soil, stockpiles, and temporary diversions can create sediment-laden runoff if not managed properly. The permanent drainage design and the contractor’s temporary erosion and sediment controls should be reviewed together so that the project does not create downstream impacts while works are underway.
Managing approval through completion
Approval is a major milestone, but it does not replace construction verification. Any material departure from the approved drainage arrangement should be assessed before it is built. A revised platform level, relocated inspection chamber, altered ramp, or changed connection route can affect performance and may require further coordination or resubmission.
During construction, retain records of inspections, site measurements, test results where applicable, approved drawings, and changes made in the field. These records support completion processes, future maintenance, and later renovation work. Building managers should receive clear information on drain routes, inspection points, grating maintenance, pump systems if any, and areas prone to debris accumulation.
For projects involving multiple authority approvals, an integrated consultant can coordinate the PUB drainage scope alongside architectural, structural, fire safety, and other regulatory submissions. Aman Engineering Consultancy supports this process through drainage design coordination, authority submission management, technical review, and construction-stage rectification support.
A drainage design is successful when rainwater has a controlled path from roof and ground surfaces to discharge, the arrangement remains accessible for maintenance, and the project can proceed without late authority or site surprises. Address those fundamentals early, and the submission becomes a disciplined part of project delivery rather than a last-minute obstacle.