CivilBolt.ai
STORM WATER DRAINAGE

Construction Project Management Software for Indian Storm Water Drainage Contractors

Built for the contractors Indian cities drain through.

Smart Cities Mission, AMRUT 2.0, and municipal corporation drainage projects. Chainage-wise invert tracking, gradient verification, cross-drainage structure logs, and monsoon-delay EOT letters drafted from the contract you uploaded.

Talk to a construction expert

Smart Cities + AMRUT

Primary funding sources, each with distinct QA and reporting requirements

Invert-level wise

Quantity tracking from manhole to manhole, gradient-verified

Cross-drainage

Utility-crossing logs linked to BOQ items and site drawings

IS: 640, IS: 4111

Drain design codes referenced in every Civil Brain answer

WHAT GOES WRONG

Storm drains look simple. The disputes are never about the drain.

A storm water channel contract is mostly earthwork, lining, and manholes. Then the invert-level survey doesn't match the BOQ gradient, a utility crossing delays one reach for six weeks, and the monsoon season ends before the drainage network can be tested. All three happen on the same project.

  • Invert-level survey doesn't reconcile with BOQ gradient

    The BOQ specifies a 1:200 gradient. The cross-sections show a 1:185 gradient at chainage 3+200 because the existing road carriageway climbed. The contractor excavated to specification. The PMC says the gradient deviates. Nobody has the original ground-level survey linked to the BOQ calculation. The dispute takes three months.

  • Utility crossing found at chainage 4+750, nowhere in the drawing

    An OFC duct runs 800mm below the proposed drain invert at chainage 4+750. It is not in the drawing. Relocation takes six weeks and a separate order from the telecom utility. The contractor stops work on the entire reach. The delay is real; the paperwork to prove entitlement is not.

  • Monsoon arrives before testing, but the contract requires flow tests

    The contract requires flow testing during a rainfall event of at least 25mm/hr. Drain construction finishes in October. The next qualifying rainfall is June. The contractor can't get RA bill certification until the test happens. Eight months of retention held.

  • Concrete channel surface finish rejected, no rectification log

    The PMC rejects surface finish on 340 metres of lined channel. The contractor rectifies over three days. The PMC accepts but the joint measurement record doesn't reflect the rejected-and-rectified sequence. At RA bill stage, the PMC deducts the 340 metres as unmeasured.

HOW IT FITS

From BOQ chainage to flow-test-certified RA bill.

Storm water work generates measurement disputes at every manhole. CivilBolt threads invert levels, gradient calculations, utility-crossing logs, and test events into a single project record. The RA bill carries the evidence it needs.

  1. Step 01

    Upload the awarded contract and drawings

    BOQ, special conditions, typical cross-sections, alignment drawings, utility-crossing schedules. Civil Brain reads CPWD or municipal corporation specifications, IS code references, and cross-drainage provisions in the contract.

  2. Step 02

    Project organised by reach and manhole chainage

    Each drain reach gets its own record: invert-in, invert-out, gradient, cross-section type, lining specification, and utility crossings noted. BOQ items map to reaches, not to abstract cumulative lengths.

  3. Step 03

    Site logs capture rejections, rectifications, and delays

    PMC rejection logged at the reach level with date, inspector, and reason. Rectification entry linked. Utility-crossing delay logged as a delay event with the affected chainage and the responsible authority. Each entry timestamped, each linked to the EOT claim it will support.

  4. Step 04

    EOT letters and RA bills generated from the same record

    Utility-crossing delay letter drafted from the contract's force majeure or contractor-risk clause, with the daily log entries as supporting evidence. RA bill pulls the accepted reaches with the rejection-and-rectification history attached.

COMMON ON STORM WATER PROJECTS

Contract modes used on Indian storm water drainage projects.

Smart Cities and AMRUT projects typically run on BOQ item-rate with PMC oversight. Larger municipal packages for underground box drains or retention infrastructure occasionally go EPC. World Bank and ADB-funded urban drainage work uses FIDIC-aligned conditions.

BOQItem-Rate (Bill of Quantities)
EPCEngineering, Procurement & Construction
TurnkeyDesign-Build for drainage system packages
FIDICMDB Harmonised (ADB, World Bank-funded urban projects)

Run a real storm water tender through CivilBolt.

30 minutes with a construction expert. Send us a Smart Cities, AMRUT, or municipal corporation drainage tender. We'll process it on the demo and show you the chainage-wise BOQ setup, the utility-crossing delay workflow, and the IS code traces.

See the PM workspace