A dispute over Pune Municipal Corporation tenders for stormwater drain cleaning has exposed a deeper problem in the way routine civic works are planned, divided and verified. The reported concern is not only that tender conditions were changed, but that work already undertaken by the civic administration could be repeated through councillor-funded allocations, creating a risk of duplicate execution and duplicate billing.
The issue concerns the cleaning of stormwater drains and nullahs before and during the monsoon. According to the report by Sakal, the municipal administration has already spent around Rs 40 crore to Rs 45 crore on such work. The same category of work is now reportedly being proposed again through the municipal budget’s ‘S’ list, under which 165 councillors suggest works in their respective wards.
The report alleges that tender conditions for these works were altered in a manner that departed from the conditions framed by the sewage department. The specific change cited is a requirement that contractors should own the machinery used for drain cleaning. The existing policy decision, according to Pune Municipal Corporation chief engineer Vishal Haribhakt, permits contractors to use either machines they own or machines taken on rent, provided the equipment is registered and meets the specifications fixed by the corporation.
Haribhakt said the same rules should apply to works proposed through the ‘S’ list. His statement is significant because it indicates that the corporation already has a formal technical framework for deciding what equipment may be used in stormwater drain and sewer-cleaning contracts. The reported dispute is therefore about whether ward-level works are being tendered under the same institutional framework or through conditions that could narrow competition.
The administrative background is important. The corporation traditionally undertakes pre-monsoon cleaning through its sewage department. This year, the tenders were reportedly issued at the regional-office level, while the disaster management department was assigned a coordinating role. The change was intended to address concerns that drains and nullahs were not being cleaned effectively and that contractors could receive payment without delivering adequate work.
The report says senior officials took a closer role this year and ordered repeat cleaning where earlier work was found to be inadequate. That creates an operational overlap that the tender system must be able to distinguish clearly. A drain may legitimately require additional cleaning after soil, stones or other material are carried into it during the monsoon. But a second contract for the same location must establish whether it is corrective work, new work or a repetition of work already paid for.
This distinction is central to the public-finance question. The reported ‘S’ list tenders are for works valued below Rs 10 lakh. According to the report, such contracts do not receive the same level of administrative scrutiny, particularly in establishing whether the work was actually completed. If the corporation’s existing pre-monsoon contract remains valid for a year, and subsequent ward-level tenders cover the same drains or chambers, the work orders, measurements, photographs and payment records must be matched location by location.
The corporation’s stormwater network is large. The figures cited in the report put the length of stormwater drains at 2,72,891 metres and the number of chambers at 59,739. These numbers show why manual oversight alone is difficult. They also explain why the corporation depends on tenders, contractors, regional offices and digital records to manage routine maintenance. At the same time, a large network increases the importance of accurate asset-level records. Without a common record of which drain or chamber was cleaned, on what date, under which contract and at what cost, the scale of the network can become an accountability problem rather than only an engineering challenge.
The reported use of geotagged photographs illustrates the limits of a digital control that is not supported by stronger verification. The report alleges that photographs can be presented with altered mobile-device dates, allowing one location to appear as though it was covered under two separate tenders. This is an allegation in the source report, not an established finding of an audit or investigation. However, it identifies a specific weakness: photographs can document presence at a location, but they do not by themselves prove the quantity, quality or uniqueness of the work performed.
For stormwater maintenance, the distinction between an engineering record and a payment record matters. A photograph may show an open chamber or a cleared drain, but the corporation also needs a contract reference, measurable length, chamber identification, before-and-after evidence and an inspection record. The supplied report does not state that such a unified verification system exists or that an independent audit has confirmed duplicate billing. It does, however, describe a procurement structure in which multiple departments and administrative levels may be responsible for related works.
That fragmentation is the institutional issue beneath the immediate tender dispute. The sewage department frames technical requirements. Regional offices issue or manage certain tenders. The disaster management department coordinates. Councillors identify works through the ‘S’ list. Contractors execute the work, while municipal officials certify it. When responsibilities are divided in this way, no single tender document necessarily shows the full history of a drain or chamber. A contractor may be assessed against one work order even though another department has recently paid for work at the same location.
The ‘S’ list also creates a separate planning question. The reported budget provision follows the return of municipal elections after a four-year gap. Under the arrangement described in the report, 165 councillors can suggest works according to their priorities in their wards. This can help direct spending towards local problems, but it can also make citywide maintenance harder to coordinate when technically similar works are split across ward-level proposals.
Drain cleaning is not an isolated ward amenity. It is part of a connected stormwater system. A chamber or drain cleaned in one ward may connect to a larger line, nullah or downstream outfall managed through another contract. Splitting the work by political or administrative boundary can therefore create gaps in continuity. It may also make it more difficult to determine whether a local tender is addressing a genuine new requirement or repeating a citywide maintenance activity already assigned to the sewage department.
The procurement condition on machine ownership raises a related competition issue. If a contractor must own a specified machine rather than have access to a compliant rented machine, the number of eligible bidders may fall. The report alleges that this condition was introduced to favour preferred contractors. That allegation has not been independently established in the supplied material. The observable administrative concern is narrower but consequential: a technical condition should be linked to the safety, capacity and performance required for the work, rather than becoming an avoidable barrier to participation.
The chief engineer’s statement provides the corporation’s stated policy position: machines may be owned or rented, as long as they are registered and comply with municipal specifications. If this is the applicable policy, deviations in ward-level tenders require a documented administrative reason. The supplied report does not say whether the corporation has cancelled, revised or formally reviewed the tenders in question. It also does not provide the names of the contractors, the affected wards, the tender numbers or the value of each disputed work.
Those missing details limit what can be concluded. The report establishes a conflict over tender conditions and a risk of overlapping expenditure, but it does not establish that duplicate bills have already been paid. Nor does it establish that every ‘S’ list drain-cleaning work duplicates the corporation’s earlier work. These questions can only be settled by comparing the work registers, tender schedules, measurement books, inspection certificates, geotagged records and payment files for each location.
The larger urban question is whether Pune’s routine infrastructure maintenance is being managed as a connected public system or as a collection of short-term work orders. Stormwater drains are often noticed only when they fail during heavy rain. Yet their reliability depends on decisions made months earlier: which department owns the asset record, who defines the technical specification, how contracts are divided, who verifies completion and whether the next tender can see what the previous one paid for.
For now, the evidence supplied points to a governance risk rather than a proven financial offence. The immediate developments to monitor are whether the municipal administration applies the same machinery rules to ‘S’ list tenders, whether it identifies overlaps with the Rs 40 crore to Rs 45 crore programme, and whether it publishes ward-wise records for the 2,72,891 metres of drains and 59,739 chambers cited in the report. Those steps would determine whether the tender controversy produces a documented correction or remains another dispute over the visibility of civic spending.
