A carrier count cannot promise a uniform week of work

The simple count behind an unsupported date

The number was 480 carriers. It seemed a workable basis for estimating the programme against routine transfer capacity, and I accepted an eight-week delivery assumption too readily. The subsequent condition account identified 360 ready for routine transfer, 84 needing specialist preparation and 36 with incomplete identification. The total had not changed. The work represented by it had become much clearer, and the earlier timetable no longer described that work adequately.

A count is necessary for planning, but its usefulness depends on what the counted items have in common. In this case they shared a place in the incoming collection, not a uniform state of readiness. Some could proceed through the routine path. Others required qualified examination and preparation. Another group needed clarification about identity. Treating them as equivalent units would not make those differences disappear; it would simply move the resulting disagreement into the delivery period.

The account manager had a serious objection to revising the date. The customer had planned an internal access project around the original expectation. A later programme would affect people outside our own organisation and could weaken confidence in the service. I did not think the operating team could answer that concern with a list of technical reasons and leave the customer to manage the consequences. We had accepted the earlier assumption. We needed to help produce a usable alternative and acknowledge the cost of changing it.

Ravi and the relevant specialists examined what could proceed, what needed preparation and what required owner clarification. Their role was not to endorse the eight-week plan retrospectively. They had to make the appropriate judgement about the material and the work. My responsibility was to connect that account with staffing, expense and an authorised customer discussion. If the specialist finding could never change the programme, asking for it would have been an exercise in reassurance rather than a real part of planning.

The thirty-six incompletely identified carriers required particular care in the management account. We did not invent titles or assume that a familiar-looking label settled every relevant question. We also did not describe the group as lost or unusable. The status concerned identification at that review point. Preserving that limited meaning helped the team ask the right next question instead of allowing an administrative category to become a conclusion about the value or recoverability of the material.

Give uncertainty an owner before it becomes a missed promise

We agreed a twelve-week programme with the customer and incurred ₹48 lakh additional preparation and coordination expense. Routine-ready work could proceed while the other groups followed their appropriate paths. The revised account did not report 480 completed transfers or 84 successful recoveries. It described the conditions from which the programme was being organised. Actual completion and acceptance needed their own evidence as the work progressed.

The customer had to alter part of the access plan. Our operating teams had to carry a longer programme beside other commitments. I wanted those consequences recorded rather than present the revision as a free improvement in planning discipline. A more accurate account can still arrive too late to prevent inconvenience. Owning the original assumption means acknowledging that cost, not merely showing that the corrected plan is now more technically defensible.

The extension also did not remove every uncertainty. A condition-dependent service can reveal further questions as qualified work proceeds. The answer is not to promise an outcome for every item before the relevant evidence exists. It is to establish who decides, how the customer will be informed and what a change means under the actual agreement. Those arrangements must remain proportionate to the work rather than become a general disclaimer that leaves the customer unable to plan anything.

I would resist two opposite responses. One is to preserve the original date regardless of the material, placing the burden of an unsupported promise on the people doing the work. The other is to refuse any useful schedule until all uncertainty has disappeared. Neither serves the customer well. The practical task is to distinguish the work sufficiently, explain the basis of the commitment and retain a process for the conditions that cannot yet be settled.

That approach requires commercial participation early. The account team understands the customer's intended use and the consequences of delay. Specialists understand the material and its treatment. Operations understands programme capacity and the effect on other commitments. A timetable becomes more credible when those accounts meet before the date is announced. It becomes less credible when one team chooses a reassuring interval and asks the others to justify it afterwards.

The schedule should describe the work entrusted to us

The lesson is not that equipment throughput is irrelevant. It remains part of the programme where its assumptions apply. The mistake is treating it as a complete description of the service before condition, identity and preparation have been examined. A fast routine step can coexist with a slower overall programme because the work includes responsibilities on either side of that step. A COO should make those responsibilities visible instead of allowing the most easily measured activity to define completion.

For directors, the question is whether management's delivery account rests on an adequate description of its commitments. The board should not determine handling methods or assign individual carriers to a technical path. It can ask how the company forms a date, what evidence supports it and how changes are authorised and communicated. It should also understand the expense of specialist preparation and coordination where these are necessary to provide the service being sold.

A useful performance review would examine the quality of those decisions as well as the final interval. A programme that meets a date by narrowing the claim silently is not the same as one that fulfils the agreed work. Conversely, an authorised revision based on a material condition should not automatically be treated as evidence that the operating team failed to work hard enough. The account needs to explain what changed and what the enterprise actually undertook.

I now ask what the item count conceals before I approve a headline schedule. In this case, the answer was a combination of routine readiness, specialist preparation and unfinished identification. The correction cost money and changed the customer's plan. It also made our commitment more faithful to the work entrusted to us. The durable responsibility is to establish that account early enough for a real decision, and to keep the customer informed through an authorised process when the material requires the enterprise to reconsider its first promise.