From field handover to the whole operating commitment

Mandate

Keep the physical and environmental dependencies inside the operating commitment

Outcomes

• Retained unresolved release periods in the performance account
• Qualified recovery assumptions against the actual access route
• Preserved engineering and environmental decision ownership

Decisions in context

The COO remit spans four station heads and 172 operating employees within ₹32 crore annual non-capital expense. I report to the CEO without holding a statutory seat. Civil-engineering head Devang Vezqralni helps coordinate the qualified examination of works and access conditions. The release-record review required us to distinguish an aggregate volume from evidence of a continuing condition, retaining five unresolved days after the reconstruction. The component review then required transportability to sit beside stock availability. In each case my role was to fund the relevant work, change the management recommendation and keep the unresolved scope visible. Technical methods, water-related permissions and safety decisions remained with the appropriate owners. I want the organisation to know what its operating commitment rests on before it asks someone else to rely on that commitment, including when the most convenient account is the one we must withdraw.

Reason for the move

Current appointment; considering regional hydro operations leadership and a prepared first board contribution

Concurrent appointment

Executive employment without a statutory directorship

Mandate

Connect station maintenance quantities with the arrangements needed to deliver them

Outcomes

• Withdrew support for an incomplete sediment programme
• Held unsupported receiving volume outside authorised work
• Changed review practice to include the destination and its conditions

Decisions in context

Three station heads and 126 colleagues formed my regional remit within ₹23 crore annual non-capital expense. The wider view was supposed to help me recognise dependencies beyond an individual works package. Yet in 2017 I supported a sediment programme whose receiving arrangement did not cover the full proposed quantity. I had focused on the removal volume and contractor schedule more than the destination. We held the unsupported part outside authorised work and funded a redesign with qualified owners. No unsupported disposal is represented as having occurred. The correction changed how I reviewed a programme: a physical chain could not be called complete merely because our own site activity had been planned. Moving into the COO role extended that lesson to the company’s reporting and recovery commitments, where aggregate evidence or available stock could create similarly premature confidence.

Reason for the move

Promoted to company-wide operating leadership

Concurrent appointment

No statutory appointment

Mandate

Maintain a continuing operating account beyond completion of individual works

Outcomes

• Connected maintenance access with station planning
• Distinguished activity records from evidence of operating conditions
• Kept water-related and technical responsibilities identifiable

Decisions in context

I joined the owner’s operating organisation with fifty-one station employees and ₹7.8 crore annual non-capital expense. The change from delivery management was the continuing obligation after a works package ended. I needed to understand access arrangements, maintenance dependencies and water-related conditions while preserving qualified technical authority. An activity could be recorded as complete without establishing every condition required for the wider operating claim. I learned to ask what the record proved and which question still needed a different source of evidence. That experience later informed the release-record exercise, where daily aggregates did not establish the condition throughout each day. At the time, it also helped me work across civil, electrical and environmental responsibilities without assuming that station management could certify them all. Regional promotion followed because the organisation needed those connected questions to travel across more than one station.

Reason for the move

Promoted to regional multi-station operations

Mandate

Coordinate design, access and receiving dependencies before treating the schedule as deliverable

Outcomes

• Brought off-site dependencies into delivery discussions
• Distinguished coordination from engineering certification
• Documented conditions needed before subsequent work could proceed

Decisions in context

Nineteen colleagues worked within a ₹2.6 crore annual delivery envelope. Client capital decisions and professional certification remained elsewhere, and I learned to make that separation explicit when a schedule became urgent. The team saw how access, receiving arrangements and permissions could determine whether apparently straightforward work was possible. Bringing those matters into one conversation did not make me the technical owner of each answer. My responsibility was to coordinate the evidence and identify the consequence for the programme when an answer was missing. I wanted to understand the operator’s continuing perspective, because the client inherited the practical consequences after our defined assignment ended. The move into station management offered that wider responsibility and required me to think beyond the contractor’s completion date, including the evidence needed to describe the condition left behind.

Reason for the move

Joined a hydro owner to manage continuing station operations

Mandate

Record work conditions and outstanding dependencies accurately under professional supervision

Outcomes

• Prepared field records for qualified review
• Learned the limits of an activity-completion statement
• Carried unresolved conditions into the next-stage handover

Decisions in context

I joined a six-person field group after graduating in May 1993. My work concerned records and coordination under a supervising civil engineer, without independent authority over methods, structures or work around water. The early assignments showed that a completed activity was not always permission for the next one to start. Access might change, a receiving arrangement might remain unfinished or the relevant professional review might still be pending. I learned to keep those conditions in the account rather than leave them to an informal conversation after handover. The experience also taught me to ask when a question was outside my competence. That boundary remained important as my management responsibility grew. Promotion to delivery manager required me to help others see the dependencies I had once recorded, while retaining the qualified ownership of the decisions themselves.

Reason for the move

Promoted to civil-works delivery management