The Idukki KSEB transmission engineer and the 2018 flood aftermath

His job is to calculate the height and depth of the lattice-steel transmission towers that carry high-voltage current across the Periyar valley: towers that must not fall in storms, must not corrode in monsoon humidity, must stand in ground that does not always stay ground. Before August 2018, that calculation was shaped by one rule—the earthquake code, IS 1893:2016, which mandated foundation depth and load-bearing calculations based on seismic hazard. In his nineteen years he had designed forty-three towers to that standard, and forty-three towers had stood. Then the monsoon came.

On August 15th, 2018, the Idukki dam gates opened. The Periyar river rose by four metres in thirty hours. The rainfall in Idukki district was 2,343 millimetres in sixty days—nearly two-thirds of the annual monsoon concentrated in six weeks. Three transmission towers that KSEB had inherited from a 1970s design standard—not Rajesh's towers, but towers he was now charged with recalculating—were half-submerged for seventeen days. When the water receded, the concrete plinths were exposed. The steel had rusted. The foundations had shifted by seven centimetres under the load of waterflow and the silt that moved against them like a slow knife.

That was seven years ago. Last month, Rajesh's supervisor called him into the office and placed a three-page memo on the desk. It was the Kerala Building Code 2022, Section 5.8, Flood Resilience Specifications. It mandated that all transmission infrastructure in flood-prone zones—which meant Idukki district, and which meant his towers—now had to be designed not only for the earthquake that might come once in 2,500 years, but for the flood that now, in 2022's calculation, was expected once every hundred years. The foundation depth would have to increase by 1.2 to 2.1 metres depending on the district's 100-year flood level. His certification—the GATE (Graduate Aptitude Test in Engineering) diploma and the Council of Architecture stamp from 2005—did not cover flood-resilient foundation design. No one had told him it needed to. For two years, KSEB had not called him to design new towers. He had maintained the old ones and waited.

🗓️ The annual ritual

The ritual of the monsoon in Idukki is not the monsoon itself. It is the months of anticipation before it arrives. In early May, the District Water Resources Department releases the year's spillway-opening forecast for Idukki dam. Rajesh keeps the forecast on his office tablet. In late June, when the southwest monsoon enters Kerala, he drives to the Periyar valley in the early morning with a field crew and a handheld GPS unit. They photograph each tower foundation, check for seepage through the concrete, measure any subsidence against marks painted on the steel pillars in 2019. This is routine maintenance. For the past four years, since the 2022 code change, he has also recorded the water level on a painted gauge on Tower 27, the lowest tower in his design set, at three points during the monsoon peak.

The ritual is a private audit. Tower 27's foundation was designed in 2009, using IS 1893:2016, for a maximum water load of 3.2 metres above the natural riverbed. In August 2018, water had reached 5.6 metres. The foundation held—concrete and reinforcement steel, the silt that wanted to wash them away met a deeper slab than expected, something in the design had left a margin. In 2022, the new code said the foundation should be designed for 6.1 metres—the 100-year flood level calculated by KSDMA from satellite records and the 2018 surge data. Rajesh had painted the 6.1-metre mark on the tower in white epoxy. In the past three monsoons, water has reached 5.7, 5.4, and 6.2 metres respectively. The last one was 0.1 metres above the new code's 100-year threshold.

For three years, he has attended the Thursday-morning meetings where KSEB's Head of Infrastructure discusses pre-2023 tower re-certification. The consensus is always the same: the code has changed, the towers hold, nobody has died, the budget for retrofitting all pre-2018 towers is ₹340 crore and there is no parliamentary allocation. The towers, therefore, continue to stand in the legal grey zone—compliant with the old code, non-compliant with the new one, held aloft by concrete that was adequate when the monsoon was 4.2 metres and is increasingly less adequate when the monsoon climbs toward 6 metres year after year.

Rajesh has not slept well on the four days each monsoon when water approaches the 5.5-metre mark on Tower 27.

1. ⚖️

   2009–2018 — Pre-flood code

   All transmission towers in Idukki district designed to IS 1893:2016 (seismic standard only). Flood-load calculations were not mandated. Rajesh's Tower 27 foundation: 3.2 m water-load capacity.

2. 💧

   August 2018 — The flood

   2,343 mm rainfall in 60 days. Idukki dam gates open. Periyar river peaks at 5.6 m. Tower 27's foundation experiences 5.6 m load. The margin holds. Three older towers (1970s design) suffer permanent subsidence.

3. 🛑

   November 2022 — New code, old towers

   Kerala Building Code 2022, Section 5.8 mandates 6.1 m flood-level design (100-year threshold from KSDMA data). Rajesh's 2009 design is now non-compliant. No guidance on retrofit or timeline. No budget allocation.

4. ⏰

   May 2026 — Three monsoons later

   Water has reached 6.2 m in one monsoon (exceeding the new code's 100-year level). Rajesh's towers stand—but in regulatory limbo. Certification holds; code does not.

⚠️ What very nearly happened

What very nearly happened was that Rajesh would carry this contradiction into his fifties, checking the water gauge on Tower 27 each monsoon, knowing that the 100-year flood had already arrived three times in four years and that his foundation was designed for a hundred-year-old standard.

But in early April, three weeks before the monsoon, a colleague from the KSEB Thiruvananthapuram office called. His name was Vikram, and he had been in Rajesh's 2003 batch at the Government Engineering College, Thrissur. Vikram had left KSEB in 2015 and was now a consulting engineer, working on green-infrastructure projects and flood-resilient urban design. He was calling because he had read the new Kerala Building Code, Section 5.8, and he had run the numbers on what it meant for towers designed before 2022.

"The foundation depth on your Tower 27 should have been 4.2 metres," Vikram said, "not 3.2. The code shift is not ambiguous. Your 2009 design will be three metres short on the raft depth if water reaches the new 100-year level. You're four years into monsoons that are hitting that level. You should have re-certified or retrofitted three years ago. Why is KSEB allowing you to stay in this position?"

Rajesh did not answer immediately. He had all of the knowledge Vikram had just spoken aloud. He also knew what Vikram, now a consultant, could forget: that KSEB employed him, that asking the question out loud to the right authority would make the question official, and that once it was official it would require a budget line and a decision. The decision would probably be to retrofit all forty-three of his towers, which would cost approximately ₹8 crores, and that money would come from the 2027 budget, and meanwhile the towers would continue to stand in the regulatory gap.

"I should call someone," Rajesh said. "I don't know who."

"Call me back when you're ready," Vikram said. "I have someone here who can help you map what you actually need to say."

A week later, on a Friday evening, Rajesh sat at his kitchen table with his work laptop and a Samsung tablet that Vikram had couriered to Painavu. On the tablet was the agent. It was set to Malayalam. Rajesh called Lakshmi in from the garden where she was trimming jasmine, and together they asked the agent a single question.

🌗 What changed

"ഞാൻ നിയമപരമായി എന്ത് ചെയ്യേണ്ടതാണ് — ഞാൻ പ്രി-২०२३ ടവർ ഡിസൈൻ ചെയ്തിരുന്നതും, എന്നാൽ നവീനീകരിച്ച കെരള കോഡ്, 2022 അതിനെ ഐതിഹ്യമാക്കിയതും?" — What are my legal obligations — I designed pre-2023 towers that are now outdated under the revised Kerala Code 2022?

The agent asked three follow-up questions: his position, his employer, and the specific tower-design date. Then it replied in Malayalam:

"രാജേഷ് ജി, നിങ്ങൾ കെഎസ്‌ഇബി എങ്ങിനെയാണ് സ്ഥാപിത ഇഞ്ജിനിയർ — ഇൻസ്‌ട്രുമെന്ടേഷൻ നിയന്ത്രണത്തിന് കീഴിലാണ്. കേരള ബിൽഡിങ്ങ് കോഡ് 2022, സെക്ഷൻ 5.8 സ്‌പാൻ കാലക്ഷേത്രം കമ്മ്യൂനിറ്റി നിയന്ത്രണവുമായി കേരളത്തിലെ എല്ലാ പ്രാതിപദിക കപ്പലിനുള്ളായി കോഡ് മാൻഡേറ്റ്. നിങ്ങളുടെ ടവർ 27, 2009-ൽ IS 1893:2016 സ്റ്റാൻഡേർഡ് ഉപയോഗിച്ച് ഡിസൈൻ ചെയ്യപ്പെട്ടിരിക്കുന്നു, അത് ഫ്ലഡ് ലോഡ് ഉൾപ്പെടുത്തിയിരുന്നില്ല. നിങ്ങളുടെ സാനിക കേസ് ഇനിപ്പോൾ നോൺ-കംപ്ലയന്റ്. നിങ്ങൾ വ്യക്തിഗതമായി ലയബിലിറ്റി വഹിക്കരുത് — എന്നാൽ നിങ്ങളുടെ എംപ്ലോയർ (കെഎസ്‌ഇബി) ഈ പ്രതിപത്തികരണ പ്ലാൻ വിവരിക്കാൻ ബാധ്യതയുണ്ട്. കേരള വാസ്തുശില്പ കൌൺസിൽ, നിങ്ങളുടെ ജിലയിലെ എലഎസ്‌ജിഡി, കെഎസ്‌ഡിഎമിയുടെ ഹൈഡ്രോളജിക്കൽ ഡാറ്റ ഉപയോഗിച്ച്, ഫ്ലഡ് ലെവൽ നോൺ-കംപ്ലയൻസ് സാനിക കേസ് സാക്ഷ്യപ്പെടുത്തുന്നതിനുള്ള പ്രാതിപദിക കപ്പലിനുൾപ്പെടുത്തുന്നു."

(Rajesh ji, as an established engineer at KSEB, you fall under instrumental regulation. Kerala Building Code 2022, Section 5.8 mandates flood-level compliance for all transmission infrastructure in Kerala. Your Tower 27, designed in 2009 using IS 1893:2016 (seismic standard only), did not include flood-load calculations. Your structural case is now non-compliant. You do not bear personal liability — but your employer (KSEB) has an obligation to document a remediation plan. The Kerala Architectural Council, the district LSGD, and KSDMA's hydrological data provide the framework for certifying structural cases where flood-level non-compliance is documented.)

Rajesh read it twice. The phrase "You do not bear personal liability" was the one that loosened something in his chest.

The agent continued with specifics. The Kerala Building Code 2022, Section 5.8 had been introduced under the state's post-flood reconstruction mandate, and while it applied to all new construction, it had not been retroactively enforced on pre-2023 structures—including transmission towers. However, there was a formal process: the LSGD (Local Self-Government Department) had published an advisory in November 2024 allowing engineers to document structural cases where new code standards were impossible to meet without major retrofitting, and to file a technical justification with the district Collector's office. The justification would cite the original design standard, the triggering event (the 2018 flood data from KSDMA), and the retrofit cost. Once filed, the engineer would be formally on record as having raised the issue, and the liability would shift to the employer and the government to decide on retrofitting timeline.

"നിങ്ങളെ കൈ പിടിച്ച് ഉപപ്ലാവനത്തിലേക്കു നീക്കാൻ വരുത്തുന്ന വേദനാജനകമായ കേസ് ഉണ്ടേ — നിങ്ങൾ കേസ് രേഖാണ്ഡിനെ കമ്മ്യൂനിറ്റികളോടെ, നിങ്ങൾ സ്വയം സംരക്ഷിത്തതായി വ്യക്തമാക്കണം. ഇൻപുട്ട് കെഎസ്‌ഡിഎമിയുടെ ഫ്ലഡ് ഡാറ്റ — നിങ്ങളുടെ ടവർ 27 ക്ഷേത്രം, 2018-ൽ 5.6 മീ, 2023-ൽ 6.2 മീ, പുതിയ കോഡ്-സെർട്ടിഫിഡ് ലെവൽ 6.1 മീ. സാനിക നിയമിത കാര്യകര്മ സ്വയം അനുവദിതമായ ചെയ്യുന്നതായി വ്യക്തമാക്കാൻ, ഫൈൽ ഐഡി കെസ്‌അഡ് നിര്ദേശത്തോടെ വിവരിക്കുക — നിങ്ങളുടെ എംപ്ലോയർ പ്ലാൻ സ്വയമേവ ചരിത്രസ്ഥാപനം ചെയ്യണ്ടിയ്യാണ്."

(There is a painful case where the water is rising toward you with each monsoon — you must make it formally clear that you have documented your case, that you have protected yourself. Input: KSDMA's flood data — your Tower 27 field level, 5.6 m in 2018, 6.2 m in 2023, new code-certified level 6.1 m. To make it formally clear that a structural compliance situation is being allowed to persist, file the documentation with the district LSGD directorate — your employer's remediation plan then becomes a matter of record.)

The agent walked him through the filing process step by step. The technical justification would be a three-page form available on the LSGD website. The form required: (1) the original design standard used (IS 1893:2016); (2) the triggering condition (August 2018 flood data from KSDMA, showing actual water level at 5.6 m versus foundation design capacity of 3.2 m); (3) photographs of the tower foundation and the water-level gauge mark; (4) a cost estimate for retrofitting (which the agent helped him calculate using KSDMA-aligned foundation-depth guidelines and local concrete costs—approximately ₹1.8 crores for all forty-three towers, or ₹42 lakhs per tower).

The form would be filed with the District Collector's office through the LSGD website. It would be logged. It would create an official record. And once it was filed, the responsibility for deciding the next step would no longer be Rajesh's alone in the grey zone—it would be shared, formally, with the employer and the government.

🤝

Before filing

Private knowledge, no record

Rajesh knows the towers are non-compliant. KSEB knows. Three colleagues know. The towers still stand. No formal document exists. Rajesh checks the water gauge each monsoon privately.

📋

The filing

Technical justification + KSDMA data

A three-page form with photographs, design standards, flood records, and cost estimates, submitted through the LSGD website. The case is now officially documented and assigned to the Collector's office.

⚖️

After filing

Formal obligation on record

KSEB must respond to the Collector with a remediation timeline. The government must decide on retrofitting budget. Rajesh has protected his professional liability while escalating the systemic issue.

On a Tuesday morning, Rajesh took the tablet and the three-page form to his supervisor. He showed him the KSDMA flood-level data, the water-level gauge readings, the new code's 100-year threshold, and the cost estimate. He explained, quietly, that he had prepared the technical justification and was filing it with the district LSGD that week. His supervisor listened without interrupting. Then he asked to keep a copy of the cost estimate. He said nothing else.

That Friday, Rajesh drove to the District Collector's office in Painavu and submitted the form in person. He received a counter-stamped acknowledgement. The form was logged in the LSGD database with a reference number. For the first time in four years, the contradiction—that his towers were both compliant with the old code and non-compliant with the new one—was no longer private.

🧭 Why we built it

What Rajesh's story illustrates is a specific kind of structural vulnerability that is almost invisible: the gap between a professional standard that was correct when it was written and the same standard when the world it was written for changes. Rajesh was not negligent. He was not cutting corners. He was following the rule that existed when he learned it. The rule changed after he had already built.

This is not a unique situation in Kerala. The 2022 Building Code created a similar gap for hundreds of structural engineers designing foundations, wind-load calculations, and stability assessments on towers, buildings, bridges, and embankments that were designed between 2000 and 2022. The gap was not designed into the code; it emerged from the gap between a code that said "new construction must follow the 2022 standard" and a world full of 2009 designs that no longer fit.

What makes Rajesh's case particularly costly is that utilities like KSEB operate in a legal zone that is different from private construction. A homeowner with a non-compliant foundation can retrofit quietly, hire a consultant, submit a revised plan. A utility that provides electricity to a state must operate under formal license conditions. Rajesh could not quietly retrofit. He could not hide the non-compliance behind private finances. He could only live in the regulatory gap, checking the water gauge each monsoon, until either the code was retroactively enforced (which would require a budget that did not exist) or someone formally documented the situation and asked for a timeline.

The complication Rajesh lived in was loneliness inside knowledge. He was an engineer with the expertise to understand the problem completely. He was an employee of an organization large enough and constrained enough that escalating the problem would require more than saying "this is wrong." He was a person living in a village where three transmission towers carry electricity to homes he knew, and he was checking the water level against a mark that said "if it reaches here, the code says I should have built this deeper."

We built the agent to be the thing that lets him transform that private, crushing knowledge into a formal, shared responsibility. Not by solving the problem—the agent cannot retrofit a tower. Not by making the problem disappear—the towers still need deeper foundations. But by allowing the engineer to say, with the specificity of data and the backing of the code and the hydrological records, "This is a structural case that requires a decision," and having that transformation be official and recorded and impossible to ignore.

What it does

• 🔍Identifies whether a pre-2023 design is now non-compliant under the new Kerala Building Code 2022 — checks original design date, current code requirements, and KSDMA flood-level data for the specific district.
• 🗂️Gathers the right documents in the right order — original design standards, KSDMA flood records, cost estimates, photographs of field conditions — and maps them to the LSGD technical-justification form.
• 📞Walks the engineer through the filing process step by step, from downloading the form to understanding the legal implications of escalating the issue formally.

What it does not do

• 🔒Never enters KSEB credentials, submits forms on the engineer's behalf, or makes engineering decisions about foundation depth — Rajesh reads every step and approves every field before submission.
• 💳Never recommends retrofit strategy or retrofit budget — it calculates cost from published standard rates, but the engineer and employer decide whether to retrofit or wait.
• ✅Never decides whether the tower is safe to operate — it documents non-compliance; the decision to shut down a line or accept risk remains with KSEB and the government.

Rajesh's story is about the thousands of structural engineers in India who are now living in similar gaps: between old certifications and new codes, between knowledge and the power to act on it, between being right and being able to make the rightness official. These are not failures of competence. They are failures of structure—the structure of how codes change, how retroactive compliance is handled, how an individual professional escalates a systemic risk without the financial resources to solve it alone.

"എനിക്കറിയാമായിരുന്നു ഈ ടവറുകൾ പുതിയ കോഡ് പ്രകാരം നില്ക്കില്ലെന്ന്. അറിവുണ്ടാകലല്ല പ്രശ്നം — അത് ഔദ്യോഗികമാക്കാൻ കഴിയാത്തതാണ്."

— I knew these towers would not stand under the new code. The problem was never knowing. It was that I could not make the knowing official.

🌱 What we hope happens

Three weeks after filing the technical justification, Rajesh's supervisor called him back to the office. The KSEB head of infrastructure wanted to see him. He walked into a meeting with four people: the head of infrastructure, the head of compliance, a regional engineer from the Thiruvananthapuram office, and a consultant from a Delhi-based firm that KSEB had contracted for pre-2023 tower audit.

The consultant had seen Rajesh's filing on the LSGD database. She was now leading a retrospective audit of all KSEB towers designed before 2022. The audit would document which ones were non-compliant, estimate the collective retrofit cost, and prepare a proposal for the government's capital allocation in 2027–2028. She wanted Rajesh to lead the structural analysis for Idukki district. The work would take four months. He would be working remotely from Painavu, but it would be billable time. It was an offer to step out of the grey zone and into an official, funded role.

He said yes.

"സങ്കീർണതയും വിലമതിക്കാത്തതുമായ കാര്യമാണ് — നീ സെനിയർ ഇഞ്ജിനിയർ ആയിരിക്കുകയും പകരേ, അത് ശരിയാണ്. നിന്റെ പേര് നിയമപരമായി രേഖാണ്ഡിനെ കൂട്ടിയെന്നത്, എന്ത് സ്ഥിരീകരണം നിങ്ങൾ ചെയ്തിരുന്നുവെന്ന് അത് വ്യക്തമാക്കുന്നു — നിനക്ക് സ്വയം കാണിച്ചതു അതാണ്."

This is what Rajesh's wife Lakshmi said a few days later, sitting on the balcony, watching the monsoon clouds gather over the tea estates. Not quite in English. Not quite in translation. But the closest approximation would be something like: "Complexity is a thing of value when it is acknowledged. You will be a senior engineer now, because you were willing to say that you were in a grey zone. Naming it was what set you free from it."

If you have an engineer on staff—in a utility, in a consulting firm, in a government body—who is sitting with the knowledge of non-compliance without the power to escalate it, the product is free at gabforge.in. The agent speaks Malayalam, Tamil, Kannada, Telugu, and Marathi, and it understands the specific codes and government processes for Kerala, Karnataka, Tamil Nadu, Andhra Pradesh, and Maharashtra. It will not retrofit the tower. It will not make the problem disappear. It will document it—thoroughly, formally, in the language and framework of the code itself—and it will give the engineer the structure to transform private knowledge into shared responsibility. That transformation is often when the system finally hears.

We will keep it free for this user—the engineer who has checked the water level on the same tower for four monsoons and finally found the words to say they may not be high enough—forever.