Decide when an item has moved and who is responsible.

A scan identifies an event only when the team agrees what it means. Use the questions and worked example below to define a movement before choosing screens or scanning equipment. Keep the answers in your own planning notes.

Identify what is being tracked

Distinguish a quantity of interchangeable stock from an individual asset with its own history. Choose the identifier that stays with the item when its description or location changes. Decide what staff do with an unreadable label, an unknown item or a unit that differs from the expected pack size.

For each event, record the item or quantity, origin, destination, responsible person and expected change. Decide whether the event changes physical location, available quantity, custody or several of these. They need not all change at the same instant.

Keep dispatch and confirmed receipt distinct

Choose the point at which a transfer leaves the sender and the evidence the receiver must supply. Decide who owns an item while it is in transit, when it becomes available at the destination and who investigates an unconfirmed delivery.

Include a partial receipt, a wrong destination and a canceled movement. Name the person who can resolve each exception and what history is retained. Avoid a status that says “transferred” while staff cannot tell whether it was sent or actually received.

Explain differences rather than overwriting them

Choose who performs a physical count, who reviews a difference and which reasons accompany an approved correction. Keep the original event and the correction understandable to someone investigating later. Decide how the system records an unknown count while the team checks it.

Separate damaged, quarantined or otherwise unavailable stock from missing stock. An item can remain in the building and in someone's custody while being unavailable for use. Ask how those distinctions affect the available quantity and the work needed to return the item to service.

Work through a fictional tool transfer

1. Dispatch: record an illustrative tool, T-12, leaving store A for crew B. Confirm the sender, time and in-transit responsibility.
2. Repeat: scan the same dispatch again. Agree and check the expected response so a repeated attempt does not create a second movement.
3. Receive: have an authorized receiver confirm T-12. Verify that dispatch and receipt remain separate events and that current custody changes at the agreed point.
4. Interrupt: simulate an uncertain or failed save in an approved test environment. Check the actual stored movement before retrying and show staff how to tell a completed event from one awaiting attention.
5. Find: ask an authorized colleague to locate the tool's current custody and explain its journey from the history. Check that a role without permission cannot alter the event.

Write the observed result and any unresolved difference beside each check. Include a partial or damaged receipt if it is part of your ordinary work.

Set a boundary for work without a connection

Name the specific events staff may record offline, which device holds pending work and how a person sees that it has not reached the shared record. Decide how repeated events or conflicting changes are reviewed after reconnection. A previously loaded screen is not evidence that a new movement has been stored.

If offline movement is outside the first release, give staff an agreed temporary process and reconciliation owner. Review inventory identifiers, explore inventory and field-service software or describe the movement you need to track.