Bharat has demonstrated that it can build infrastructure at national scale. Highways, airports, ports, metro systems, freight corridors, digital public infrastructure, logistics platforms and urban transit projects have become central to the country’s development imagination. The more difficult question is no longer whether large assets can be created. It is whether governments can reliably know what is happening to those assets, and to the land, water, utilities and settlements around them, after they are built.

The problem becomes clearest in Bengaluru. The city is often remembered for its technology economy, but its older ecological intelligence lay in a network of tanks, lakes, wetlands and rajakaluves that stored rainwater and moved excess flow through natural gradients. Historical accounts frequently describe Bengaluru as once having more than 1,400 interconnected water bodies. Today, only a fraction of that system remains intact, and many surviving lakes have been narrowed, encroached, polluted or cut off from their feeder channels.

Urban flooding in Bengaluru did not arise from one dramatic administrative failure. It emerged from cumulative, localised and often invisible changes: a stormwater drain covered here, a lakebed converted there, a road raised without hydrological modelling, a construction approval issued without checking downstream flow, a utility trench left poorly restored, and an institutional file closed without anyone updating the map. Each change may have appeared manageable in isolation. Together, they weakened the city’s capacity to absorb heavy rain.

This is the central infrastructure lesson. Bharat’s challenge is not merely construction capacity; it is situational awareness. A bridge, road, lake, drain, culvert, flyover or metro pier is not a static object. It exists inside a living system of land use, traffic, rainfall, groundwater, sewage, informal settlement, commercial pressure, legal title and political incentive. When agencies cannot see those changes in near real time, infrastructure begins to fail long before the public sees the failure.

Modern infrastructure governance therefore requires a shift from project completion to asset intelligence. Completion certificates, ribbon cuttings and budget utilisation reports are useful, but they cannot substitute for continuous monitoring. A city needs to know where every drain lies, whether its cross-section has narrowed, whether sewage is entering it, whether a new building has blocked a feeder channel, whether a culvert has lost carrying capacity, and whether road levels now redirect water into homes. Without this knowledge, even large capital expenditure produces fragile outcomes.

The technical foundation for such monitoring is not beyond India’s reach. The country has decades of experience in remote sensing through ISRO, a growing ecosystem of state remote sensing application centres, increasingly sophisticated GIS platforms, mobile governance applications, satellite imagery, drone surveys, IoT sensors, digital land records and platforms such as PM GatiShakti. The tools exist. The missing element is often institutional integration: who owns the data, who updates it, who audits it, who acts on it, and who is accountable when the map and the ground reality diverge.

PM GatiShakti has already shown the value of bringing infrastructure layers into a common geospatial platform for planning. Its logic is powerful: railways, roads, ports, airports, logistics corridors, industrial clusters and utility networks cannot be planned as separate administrative worlds. Yet the same logic must extend beyond planning into operations and maintenance. A national master plan is valuable, but a national culture of verified, frequently updated asset data would be transformative.

Karnataka’s recent lake geotagging efforts point in the right direction. By using satellite imagery, drones, ArcGIS mapping and ground verification, the state has attempted to create more accurate digital profiles of water bodies. Reports have described thousands of lakes being mapped, with boundaries, encroachments and ownership details made more visible. This kind of work matters because ecological assets are also infrastructure. A lake is not just scenery; it is storage, recharge, flood control, biodiversity, thermal regulation and public memory.

The deeper issue is that Bharat has historically treated maintenance as a secondary administrative task rather than a core development function. New construction attracts political attention, budgetary visibility and public symbolism. Maintenance is quieter. It requires inspection schedules, boring data standards, procurement discipline, repair budgets, trained municipal engineers, legal follow-through and interdepartmental coordination. Yet it is maintenance that determines whether infrastructure serves citizens for decades or deteriorates within years.

Reliable tracking begins with a complete asset registry. Every public asset should have a unique identifier, location coordinates, ownership record, design capacity, construction date, contractor history, inspection cycle, condition grade, maintenance log, risk score and linked documents. For roads, this includes pavement condition, drainage links, utility cuts, accident history and traffic loading. For bridges, it includes structural health, load limits, bearings, joints, scour risk and inspection photographs. For drains and lakes, it includes catchment boundaries, inflow points, outflow points, encroachments, silt levels and flood history.

The next requirement is change detection. Infrastructure failure often begins as change outside the asset: a new layout in a catchment, a blocked culvert upstream, a missing manhole cover, a private compound wall crossing a drain alignment, a wetland filled with debris, or a road shoulder converted into informal parking. Satellite imagery can identify land-use change. Drones can document encroachment and surface damage. Mobile inspection apps can give field engineers geo-tagged evidence. Citizen reporting can add early warnings. But these inputs must flow into a system that triggers action rather than merely creating another dashboard.

Data quality is the most underappreciated part of the problem. A map that is not updated is worse than no map, because it creates false confidence. A drain shown as open on a GIS layer may have been narrowed in practice. A road marked as completed may lack functioning shoulders or side drains. A lake boundary may exist in revenue records while the ground has been altered. Therefore, infrastructure tracking must combine satellite data, cadastral records, engineering drawings, field verification and public grievance data, with timestamps and clear responsibility for updates.

The governance challenge is also jurisdictional. One agency may own a road, another the drain below it, another the water pipeline, another the sewage line, another the land record, another the building permission, and another the disaster response plan. When flooding occurs, each department may possess one part of the truth. The citizen, however, experiences the failure as one event. A serious infrastructure monitoring system must therefore be built around places and assets, not merely around departmental boundaries.

This is especially important for rapidly urbanising India. Cities such as Bengaluru, Hyderabad, Pune, Gurugram, Chennai, Mumbai, Ahmedabad and the National Capital Region are not only expanding outward; they are becoming denser, taller and more infrastructure-dependent. The margin for poor records is shrinking. A blocked drain in a low-density settlement is a local inconvenience. The same blockage in a dense technology corridor, hospital zone, metro catchment or logistics hub can disrupt livelihoods, emergency access and economic activity across the city.

Climate variability raises the stakes. Extreme rainfall events, heat stress, water scarcity and urban flooding are no longer rare planning footnotes. Infrastructure designed for older rainfall assumptions may not perform under new hydrological realities. This does not mean every asset must be rebuilt. It means assets must be monitored against changing risk. Drain capacity, lake storage, road elevation, slope stability, coastal exposure, bridge scour and heat vulnerability should become part of routine infrastructure intelligence.

There is also an economic argument. Poor tracking increases lifecycle costs. When damage is detected late, repairs become expensive and disruptive. When encroachments are allowed to mature, legal recovery becomes harder. When utilities dig roads repeatedly without integrated records, public money is wasted on reconstruction. When maintenance is deferred, citizens pay through traffic delays, vehicle damage, business losses, health risks and insurance costs. Infrastructure that is not tracked becomes a hidden tax on the public.

A more mature system would use risk-based maintenance rather than complaint-based maintenance. Assets with high public consequence, high exposure and declining condition would receive priority attention. A culvert near a hospital, a bridge on a freight route, a drain serving a flood-prone ward, or a road carrying school traffic should not wait for collapse or public outrage. The data system should identify vulnerability before it becomes a crisis.

Public participation can strengthen this model, but it must be structured carefully. Citizens can report flooding, broken pavements, illegal dumping, encroachment, missing covers and blocked drains. Resident welfare associations, lake groups, temple committees, gurdwaras, Jain sanghs, Buddhist organisations, local businesses and civic volunteers often possess granular knowledge of neighbourhood change. In a Bharatiya civic imagination, this is not separate from dharma; stewardship of shared spaces is part of responsible public life. Yet citizen reporting must be verified, integrated and acted upon, otherwise it becomes performative consultation.

The legal dimension is equally important. A digital record should not merely describe encroachment; it should support enforcement. If a lake boundary, drain alignment or public road edge is legally defined and geo-referenced, approvals can be screened before construction begins. Building permissions, environmental clearances, utility permissions and road-cutting approvals should be automatically checked against protected infrastructure layers. Prevention is cheaper than demolition, litigation and disaster response.

India’s Digital Public Infrastructure experience offers a useful analogy. Aadhaar, UPI, DigiLocker and related systems succeeded because they created shared rails on which multiple services could operate. Infrastructure tracking needs similar shared rails: common asset IDs, interoperable GIS layers, standard inspection formats, open APIs for authorised agencies, audit trails, and public-facing transparency where security and privacy allow. The goal is not another isolated portal, but a public infrastructure data architecture.

Transparency must be calibrated but real. Citizens need not see sensitive engineering details of every strategic asset. But they should be able to see whether a neighbourhood lake is officially recognised, whether a stormwater drain exists under a road, whether a road has been recently repaired, whether a complaint has been closed after field verification, and whether flood-prone points have pending works. Public visibility creates pressure for accuracy, and accuracy creates trust.

Procurement reform is another pillar. Many government contracts reward construction output but underweight long-term performance. Infrastructure contracts should increasingly include digital handover requirements: as-built drawings, geo-referenced asset records, material specifications, photographs, sensor baselines, warranty terms and maintenance manuals. Contractors should not simply hand over a road or building; they should hand over a verified digital twin of the asset that future engineers can maintain.

Capacity at the municipal level will determine success. National platforms can provide architecture, funding and standards, but local bodies must inspect, update and enforce. This requires trained surveyors, engineers, GIS analysts, data managers and legal officers. It also requires political respect for maintenance staff, whose work rarely appears glamorous but prevents the failures that dominate headlines later. A city that values only new projects will repeatedly rebuild what it failed to maintain.

Bengaluru’s story therefore should not be treated as a local embarrassment alone. It is a national warning. The city’s lost water bodies, fragmented drains and recurring floods reveal what happens when urban growth outruns institutional memory. The same pattern can appear in hillsides where roads are widened without slope monitoring, in coastal towns where drainage is ignored, in industrial zones where utilities are not mapped, and in expanding suburbs where real estate growth precedes civic capacity.

The solution is not anti-development. Bharat needs infrastructure, and it needs it at scale. Roads reduce isolation, railways strengthen markets, ports improve trade, airports connect regions, power lines support industry, and digital networks expand opportunity. The argument is that infrastructure development must become more intelligent after construction. Building is the beginning of responsibility, not the end of it.

A practical national framework would include five priorities. First, create verified asset registries for roads, bridges, drains, lakes, public buildings and utilities. Second, integrate land records, building permissions, environmental layers and infrastructure maps. Third, use satellite imagery, drones, IoT sensors and mobile inspections for periodic change detection. Fourth, establish legal and financial accountability for delayed maintenance. Fifth, publish citizen-relevant dashboards that show condition, risk and action status in plain language.

Such a framework would also improve federal coordination. States differ in capacity, geography and urban pressure, but standards can be shared. A hill state needs landslide and road-slope monitoring. A coastal state needs flood, erosion and drainage intelligence. A dryland state needs tank, watershed and groundwater recharge tracking. A megacity needs underground utility mapping, traffic asset management and stormwater modelling. The national architecture should enable state-specific intelligence rather than impose a single template.

In the long term, infrastructure tracking should become part of public finance discipline. Budgets should not only ask how much has been built, but how much remains serviceable, how much is at risk, and how much maintenance liability has been created. Every new project creates a future obligation. If that obligation is not recorded, funded and monitored, development becomes visually impressive but structurally brittle.

Bharat’s infrastructure moment is real, and it deserves serious confidence. But confidence must be matched by institutional humility. Cities flood, roads crack, bridges weaken and lakes disappear when governments lose sight of gradual change. The next stage of Indian infrastructure development must therefore be defined not only by speed, scale and ambition, but by memory, monitoring and maintenance.

The measure of a developed society is not only how much it can build, but how carefully it can preserve what serves the public. For Bharat, the opportunity is clear: convert construction strength into lifecycle governance, convert scattered records into live intelligence, and convert infrastructure from a collection of projects into a continuously understood public system. That is how cities become resilient, citizens regain trust, and development becomes durable.

Inspired by this post on Hindu Post.