Custody begins with what arrived, not what was expected

A dispatch list is an account of what someone intended or recorded as being sent. A receipt is an account of what another party actually accepted. The two should agree, but copying the first into the second does not establish that they do. In records work, that distinction can seem unnecessarily formal until a physical item cannot be located. At that point the company needs to explain where the source was last confirmed, who held it and which transfer is supported by evidence rather than expectation.

The principle became practical for us when a client list described sixty-eight boxes and our receiving team counted sixty-seven. The transport paperwork carried the expected quantity, so it did not independently resolve the difference. Production wanted to begin with the material present and deal with the discrepancy later. That response was understandable: the line had been scheduled and people were waiting. It also risked allowing subsequent handling records to rest on an opening assumption that nobody had yet verified. I chose to pause the affected intake while the parties reconciled it.

## Keep planned dispatch separate from confirmed receipt

The first discipline was to describe the problem without deciding its cause. We had received sixty-seven boxes against a list of sixty-eight. We did not yet know whether the difference arose before dispatch, in transit, during receipt or in the way the list had been prepared. Calling it a lost box would have asserted more than the evidence supported. Treating the receipt as complete would have done the same in another direction. The accurate statement was narrower, and it gave the investigation a clearer starting point than either reassuring or alarming language.

Available identifiers and records should be examined in relation to the actual transfer. A repeated quantity on several forms may look like corroboration while all the forms derive from the same planned list. Teams need to understand that possibility without becoming suspicious of every document. The purpose is to establish which observation each record supports. A receiving count, an identifiable handover and a client confirmation may answer different parts of the question. Their value depends on what was checked, not merely on how official the paperwork appears.

In this case, the remaining box was located in stock retained at the client's site. It had been included in the planned dispatch but had not accompanied the other sixty-seven. We corrected the records to show the actual transfer and retained the explanation with the job. That result mattered because it established that the box had not entered our custody. Describing the episode as material recovered by our operations would have been inaccurate, even if it sounded like a stronger account of service. A resolved discrepancy does not need an invented recovery story to justify the attention it received.

## Authorise the pause before people need it

Receiving colleagues should know when they can stop affected work and who will help resolve the issue. If a supervisor must choose between an explicit production schedule and a vague expectation to be careful, the schedule often wins. Authority to pause should be connected to a clear escalation route and an understanding of the cost. This does not mean every minor query should halt an entire operation. It means the scope of the hold should match the uncertainty, and somebody with the relevant authority should decide how unaffected work can proceed.

Our hold lasted five days and cost ₹7 lakh in standby expense. The figure belongs in the account. Capacity cannot always be reassigned immediately, especially when preparation, access or client-specific arrangements limit what a team can handle next. I do not present the pause as costless because the final explanation was straightforward. The company accepted a real consequence to avoid building further handling activity on an unresolved receipt. A better initial dispatch process might have prevented that consequence, which is why the review needed to examine preparation as well as the decision made after arrival.

Commercial colleagues should be part of this discussion early. A client may be frustrated by a hold when most material is visibly present, and an account manager needs an explanation that is both precise and proportionate. The message should state the discrepancy, the evidence needed and the work affected, rather than suggest misconduct or hide behind a generic policy. In our case, working with the client's records team was essential. The answer lay in material still at its site, so our own internal checks alone could not have resolved the question.

## Preserve the explanation after the total is corrected

Once the totals agree, there is a temptation to replace the old record and move on. That can leave a later reviewer unable to understand why work paused or why two versions of a list exist. The correction should carry its basis, with appropriate access and retention arrangements. A future manager should be able to distinguish a clerical correction from a transfer that occurred later. This is especially important when the source material will move through several teams or return to the client long after the original participants have changed roles.

The custody account also has limits. Knowing which box was received does not establish the authenticity, completeness or legal sufficiency of every document inside it. It does not authorise destruction of an original after conversion. Those are separate questions requiring the relevant client decisions and applicable advice. I want our operating teams to be confident about the facts they can support and equally clear about the authority they do not hold. Otherwise a well-maintained handling record can be mistaken for a broader assurance that the service was never designed to provide.

A board considering a material handling incident should ask what was confirmed at each stage and whether management has separated evidence from inference. Directors also need to know whether staff had practical authority to raise the issue and whether commercial pressure altered the record. They do not need to conduct the box reconciliation themselves. Their concern is whether the company can explain its custody claims and learn from the discrepancy. A report that moves too quickly from an alarming headline to a closed status may omit the most useful part: how the conclusion was established.

The next improvement I would make is to agree the dispatch confirmation point before mobilisation and use distinct fields for expected and confirmed quantities. That is a modest operating change, but it addresses the origin of our difficulty. I prefer such a correction to a broad assurance that staff will be more vigilant. People should not have to compensate indefinitely for records that combine different states. Custody becomes dependable when the business makes the transfer explicit, supports the person who questions a mismatch and preserves the reason for the eventual answer.