Make the conditions part of the operating promise

In 2018 I approved thirty-six daily plans containing two site examinations of four hours each. The calendar allocated eight hours before travel, access arrangements or other practical needs. Twenty-three routes required more than three hours of travel, and thirteen required no more than three. The latter group was not therefore adequately planned. I had accepted a schedule that looked complete because each examination had a time allocation, while the work of moving between appointments was effectively absent.

Field colleagues challenged the plans before we treated the calendar as an instruction to compress the visits. We reviewed all thirty-six with the relevant site and technical owners. Twenty-three were split across separate days. Thirteen were resequenced with appropriate visit windows. The revised arrangements did not establish a universal rule about the number of visits an engineer can make in a day. They responded to the actual routes and assignments, while keeping the examination scope subject to its proper technical owner.

Extra travel, lodging and coordination cost ₹46 lakh. I retained the expense against the correction rather than describe it as an efficiency improvement. Commercial colleagues had to explain changed appointments, and the operating plan could no longer display the original compact sequence. The case does not claim that every revised visit was completed or that the original plans produced a measured health or safety incident. More than three hours added to eight is more than eleven, but that calculation alone does not describe anyone's actual working day.

The mistake changed the evidence I require before approving a field programme. A visit is not an isolated block that can be placed beside another block without accounting for the journey and the conditions at each end. Central planning needs the knowledge of people who understand the route and site. My responsibility was to correct the plan and its consequences, not ask the field team to make my original arithmetic true by doing less work on the ground.

In 2022 a review of nineteen field kits found eight thermal cameras beyond the company's scheduled calibration date. Eleven were current under that schedule. I arranged withdrawal of the eight and worked with the technical team on suitable replacement equipment. Six qualified replacements were rented, while two equipment-dependent visit windows were deferred. The company schedule is a fictional operating requirement; it is not presented as a regulatory interval or a universal technical prescription.

The equipment finding also raised a question about earlier work. Technical director Arvind Vezqerni led qualified review of thirty-six reports. Twenty-one required additional measurement. In fifteen, other material was adequate for the stated limited purpose of the report. Those outcomes did not mean all thirty-six reports were invalid, nor that fifteen properties had been certified safe. My role was to provide resources, preserve the review status and ensure that the operating account did not conceal the work still needed.

Rental and review expense was ₹38 lakh. The cost did not settle all possible consequences for a client or an insurer, and the case contains no invented claim payment or premium effect. Technical owners and authorised recipients had to consider the implications of the available evidence. We did not substitute a procurement receipt for confirmation that equipment was suitable, or treat possession of a replacement as completion of a deferred examination. The two visit windows remained a scheduling responsibility to resolve.

The decision required urgency without overstatement. Operations needed to stop relying on the affected equipment and enable the next appropriate work. It also needed to avoid declaring a technical verdict merely because a calendar condition had been missed. A senior operating leader can take responsibility for resources and communication while admitting that the evidential consequence requires another discipline. That distinction protected both action and accuracy: we did not wait passively for a complete retrospective answer, and we did not invent that answer to make the management update appear decisive.

A 2023 review covered fifty-five property assessments. Seventeen included intended areas the team had not been able to access, yet the operating status had moved too quickly to complete. A document could be issued with an explicit limitation, but the completion label did not distinguish that from an examination whose agreed scope had been observed. I asked the operating and technical teams to retain the unobserved areas and the reason for restricted access in the account presented to authorised recipients.

The response was not to force access or assume a site owner had acted improperly. Permissions and physical conditions had to be understood in each case. Technical owners determined how the limitation affected the assessment and what additional work was needed. Ten of the seventeen later received permitted visits. Seven still awaited access. We kept those seven open in the account rather than treating a scheduled follow-up or a named contact as equivalent to an observation already made.

Revisit expense was ₹31 lakh. That cost belonged to obtaining evidence the original operating status had obscured. It was not a claim that a plant became safe after another visit or that an insurance decision had been corrected. The other thirty-eight assessments were not declared defect-free merely because they were outside the reported access issue. Neither a document's delivery nor entry to a property establishes legal compliance, coverage or the absence of a hazard. Those conclusions require their own authorised basis.

My contribution was to make scope and status usable together. A client or insurer needs to know what was examined, what was not and what remains necessary before relying on the account for a particular purpose. Operations can help obtain permission and arrange another visit, but it cannot fill an unobserved area with an assumption in order to complete a programme. I would now require the limitation account before a completion summary is prepared, so the physical boundary of the work remains visible when the report becomes a short management update.

In 2024 an operating list of sixty-four risk-improvement recommendations was sorted by estimated implementation cost. The sequence made budgeting convenient, but some sponsors were reading the order as a statement of engineering priority. The cheapest action appeared first, and the presentation did not adequately distinguish that ordering from a judgement about urgency. I asked technical director Arvind Vezqerni to lead the qualified review needed to establish the intended priority account for the defined circumstances.

The technical review placed fourteen recommendations in an urgent group, twenty-two in a planned group and twenty-eight in a monitoring or further-review group. Those categories totalled sixty-four, but they did not mean every action within a group had identical requirements. I did not assign severity as COO. My responsibility was to fund and organise the review, then ensure the operating plan reflected the technical account rather than quietly restoring the convenient cost order when work was scheduled.

Company technical-review expense was ₹46 lakh. A separate ₹2.4 crore estimate described possible client implementation work. It was not our expenditure, an approved client budget or evidence that the recommendations had been implemented. The account therefore makes no claim of realised risk reduction, improved insurability or a lower premium. Authorised clients and other relevant parties retained their decisions, informed by the technical explanation and any professional assessment required in the actual circumstances.

The practical correction was to label the purpose of an ordering before people relied on it. Cost can be relevant to an implementation discussion without determining which hazard deserves attention first. A presentation that collapses those questions may lead management to believe it has received a technical recommendation when it has only seen a budget list. I want operations to support informed sequencing, with unfinished actions still unfinished. The case shows a funded clarification of judgement, not a claim that rearranging sixty-four rows changed the condition of sixty-four risks.

Weather and road restrictions affected sixteen of forty-four planned field assignments in 2025. Twenty-eight were not affected by the reported restriction; that did not itself establish their completion or outcome. The immediate commercial pressure was to maintain progress across the programme. I asked the technical owners to distinguish what limited work could proceed remotely from what required safe, authorised physical access. The original visit plan could not decide that question simply because the appointments had been booked.

Nine of the sixteen affected assignments could support limited remote information work. Seven were deferred entirely until suitable access became possible. The nine retained explicit unvisited areas and limits on what the available material could support. They were not reported as completed physical assessments. Technical owners determined the scope of the remote work, while clients and insurers retained their decisions about how to use the evidence. Operations arranged the revised programme without asserting a universal equivalence between a conversation and a site examination.

Extra coordination and replanning expense was ₹57 lakh. That amount remained separate from any later site work, insurance value or claim settlement. The account does not say that all forty-four assignments were completed, that every road restriction ended on one date or that a later physical visit confirmed the remote material. It records a differentiated response to the work that could and could not proceed under the stated conditions. No colleague was instructed to enter a hazardous or unauthorised location to preserve a progress figure.

The judgement was to accept different operating states inside one programme. A single completion percentage would have been easier to present but would have hidden the difference between limited information gathering and an examination postponed for access. The nine assignments offered useful work within a boundary; the seven deferred assignments preserved the need for a different condition. My responsibility was to resource both honestly. Continuity should mean doing the work that can be justified now while keeping the missing work visible, rather than changing its name until the original schedule appears to have survived.