A capture count is not an acceptance account

A conversion line can produce thousands of images while leaving the service obligation partly unfinished. That is not a criticism of measuring output. Operators need to know what they have processed, supervisors need to plan capacity and commercial colleagues need a view of progress. The difficulty begins when a capture count is asked to prove something different: that the customer has received a record meeting the agreed conditions. An image can exist, carry the right identifier and still require work before that claim is justified.

I learned the distinction on the production line and have had to relearn it in larger operating roles. A daily number is reassuring because it is available quickly and appears easy to compare. It can also combine new captures, repeats and items whose quality has not yet been reviewed. If those categories are not kept separate, additional activity may make the report look stronger while increasing the amount of work still required. The organisation can then discover the problem only when the client asks why a supposedly complete delivery is not ready to use.

## Define the obligation behind the count

The starting point is the agreed record standard and the intended use, not a preference for a more elaborate dashboard. A source may contain faint annotations, folded material or an unclear identifier. Some issues can be addressed through preparation and capture settings; others reflect limitations of the original. The service needs to distinguish those cases. Otherwise the team may either accept a correctable defect as unavoidable or promise a result that the source cannot support. Both errors make the final acceptance discussion more difficult than it needs to be.

In one programme at Thervani, the planned total reached 740,000 images. Review identified 86,000 requiring reprocessing because faint annotations had not remained consistently legible. The issue was not whether files had been produced. It was whether a defined part of the source had survived capture sufficiently for the agreed standard. The population needing correction had to be identified and discussed on that basis. Describing it as a small percentage of a large successful delivery would not change the obligation attached to those particular records.

The delivery team suggested dispatching the full set while corrections followed. That might be a legitimate arrangement in some circumstances if the customer understands and agrees to it. It should not happen by allowing an unqualified completion claim to precede a more complicated explanation. We agreed a three-week extension and accepted ₹29 lakh in additional operating cost. The revised plan made the affected work explicit. It also separated our capture problem from imperfections already present in the originals, which could not be resolved simply by repeating the same process more carefully.

## Show correction as work still owed

Rework should remain visible in both capacity and commercial discussions. A line that recaptures an item has performed more activity, but it has not created another unique accepted record. If repeat work is added to the output total without explanation, management may reward the very pattern it needs to understand. I want the operating account to show the original population, the work requiring correction and the stage at which the corrected item meets the agreed conditions. The categories should reconcile, so that a reader does not need to guess which numbers overlap.

There is a temptation to soften the financial account as well. Additional expense can be described as investment in quality, which may be true in a broad sense but can obscure the immediate result. In this case the company spent money correcting a defined delivery problem. We should show that cost before arguing that the experience will improve future performance. Any later benefit needs its own evidence. A responsible decision can reduce the current margin without needing to be presented as a saving that has merely not arrived yet.

Correction also requires an explanation of how the problem was identified. If reviewers found a recurring issue in a particular source type, the company should ask whether the preparation sample adequately represented that material. That is more useful than treating the episode only as an operator's failure. The question may concern settings, instructions, equipment condition or the way difficult material was routed. I do not want a report that jumps immediately to a familiar cause. We should establish what the evidence supports and which changes follow from it, including matters that remain uncertain.

## Give exceptions a place in the delivery decision

An exception needs an owner, a proposed action and a clear effect on the commitment. Some can be resolved within operations; others require a source decision from the client or a revised commercial agreement. The operating system should help colleagues identify that difference early. If every unresolved item is placed in a general pending category, important distinctions disappear. A missing customer instruction is not the same as an avoidable capture defect, even though both may prevent acceptance. Management needs to know which action can actually move the work forward.

The client conversation matters as much as the internal classification. A customer should understand what has been corrected, what remains limited by the source and what the conversion company is not certifying. We do not become the engineering authority for a drawing because its annotations are now readable. Nor does a successful capture determine the legal status or retention requirement of the original. Those boundaries should be stated in the service account, rather than introduced only when someone asks a question the provider cannot answer. Clear limits make the result more useful, not less professional.

For directors, a completion measure deserves scrutiny when it carries a material commercial or risk consequence. They should ask what the number includes, how known exceptions are treated and whether acceptance conditions have changed during the programme. This is not an invitation to inspect individual records from the boardroom. It is a way to test whether management's report supports the decision being requested. A high production total may be relevant to capacity; a qualified acceptance account may be necessary to understand revenue timing, remediation expense or a customer dispute.

After the reprocessing, our delivery addressed the identified legibility issue. I would not extend that result into a claim that every possible future defect had been excluded. What changed was specific and supported. That is the standard I want for operating communication: enough detail to understand the obligation and enough restraint to preserve its limits. A useful count helps people decide what to do next. When it is made to stand for an acceptance judgement it cannot support, it becomes a source of confusion precisely because it looks so clear.