A branch clerk opens a shipping carton and sees twenty sealed envelopes. The packing slip also says twenty. It is tempting to put the carton away and mark the order finished. The better question is whether tomorrow’s custodian could show what’s left, what was moved, and what should never have been touched without asking that clerk to reconstruct the morning from memory.

Count the approved unit, not the contents

The program owner should say which item is a countable custody unit: a sealed individual packet, an unopened vendor bundle, or another approved unit. Do not open an individual envelope to manufacture evidence. If the agreement requires keeping an outer package sealed until a specific handoff, preserve that requirement and record the unit you can observe. Use an approved opaque inventory reference, not card numbers. A photo can reveal names, markings or addresses that an inventory record never needed.

Establish a practical handoff point with defined access, one accountable custodian per shift, and another authorized person available to review exceptions. The FTC guide to protecting personal information recommends taking stock of where information comes from, where it goes and who can access it. Its advice on limiting access and disposing securely is a sound starting point, not a provider shipping instruction or a requirement that every branch sign the same form.

Use a check that balances without explaining away a gap

Start with the opening count. Add receipts and approved transfers-in. Subtract recorded handoffs, transfers-out, and items moved to a documented separate hold area. Compare the result to the physical count of available units. Keep hold stock out of the available count. A separate hold list with its own count helps catch an obvious error: moving a packet to hold and then treating it both as available and removed. Do not make the actual count match by replacing the opening total or treating an undocumented handoff as fact.

For example, fictional Site C begins with 18 verified packets. It receives a batch of 10. Five approved handoffs are recorded, and three packets go to a separately counted hold. The expected available count is 20, the hold count is three. If staff count 19 available and three on hold, they have an unexplained difference of one. Mark it, restrict further movement of the affected group if the procedure calls for that, and report it to the designated owner. A rerun after a shift change should preserve the original count and the reason for any correction.

Skip the impulse to search someone’s desk or open a suspect envelope. The question is not who looks responsible. It’s what was last confirmed, who was allowed to move the item, and what evidence can be reviewed without spreading employee information. The exception can require both a physical-security response and a wage-delivery review. The first-pay dispatch guide explains how to keep the delivery problem from becoming the payroll calendar.

Give returns and leftovers their own shelf and decision

A returned packet is not unsent stock. Neither is an unclaimed packet whose assignment is no longer clear. Separate the items under the approved procedure and keep them sealed. A status like “held for review” is more useful than putting them back with available packets and hoping the next day’s count will make sense. For mail returns, follow the returned-mail pass. For packets no longer required, route them through authorized disposition, not a cleanup decision by the floor team.

During a busy season, look for benign reasons the arithmetic keeps breaking. A morning receipt may be counted by one team in units and later by another in cartons. A designated custodian might change halfway through a double shift with no time for a joint count. Fix the unit mismatch and the changeover window before adding a policy that requires staff to send more photographs. A lower-friction custody design gives good employees fewer opportunities to make routine errors.

Write one exception a future reader could audit

A useful entry says that Site C counted 19 against an expected 20 at 2:10 p.m., identifies which approved reference group was reviewed, notes that group movement was paused under the local procedure, and names the function responsible for the next review. It does not speculate about theft or make unsupported claims about card use. If the follow-up finds a tray moved during housekeeping, record the observed correction rather than claiming that the 2:10 count was never wrong.

The branch coordinator should be able to repeat the count with synthetic packets first. Use unmatched counts, a staged hold move, and a shift handoff to see whether two reviewers arrive at the same answer without needing private data. If the workflow only balances because the same person explains each line, it is not ready to hand over.