InnerWeb
Skip to main content

Device return after a shift: implementation notes

A device not returned after a shift is worse than a broken one: nobody knows where it is, and the next shift works without it. These implementation notes describe the stages of setting up issue and return in a locker room or tool store, and the pitfalls that only show up after a few weeks.

4
stages of the issue and return rollout
Source: procedure described in the text

Why the return is the main risk

For plant-owned devices issued to workers, the largest loss does not come from theft but from a missing return: the device ends up in a pocket, a locker or at home. A tracker issued to a driver at the gate requires a multi-charger and a return procedure, and a missing return at the gate can trigger an alarm. The same logic applies to issuing in the locker room.

Four stages of the rollout

Below is a breakdown by case, in the order in which they most often appear in real rollouts.

Stage 1: set the issue point

Choose one place: the locker room or the tool store. One place means one source of truth about who holds a device. Issuing spread over several points leads to discrepancies.

Stage 2: build the assignment list

Each device has a number and is assigned to a person for the duration of the shift. The assignment list is an audit document and the starting point for an alarm about an unreturned device.

Stage 3: make the return a condition of ending the shift

The return must be a visible step: putting the device into a multi-charger slot and registering it in the system. A missing return becomes information before the next shift, not after a week.

Stage 4: set up alerting

Decide who receives information about an unreturned device: reception, the foreman or the IT department. Set the time after which the information goes further, and define what the recipient does then.

Example: devices invisible before the next shift

Example: devices invisible before the next shiftChart before and after introducing the return procedure, illustrative values.0246810devicesWithout procedure: Not returned after shift: 10 devices10Without procedureWith procedure: Not returned after shift: 2 devices2With procedure
Source: Example calculation: assumption of 100 devices, illustrative values

Where the rollout most often stumbles

The first pitfall is an overly complicated procedure. If issuing takes more than a minute, with three shifts in the queue dozens of people stand waiting. Shorten the steps to taking the device from the slot and confirming. The second pitfall is no reserve: a broken or lost device must not stop a worker, so a spare is needed.

The third pitfall is a mismatch between the charger data and the issue register. A full slot without the device in the register means an entry error. The fourth is the absence of the responsible person at night: make sure each shift has someone authorised to close discrepancies.

Integrations and data from the system

The system knows the battery state of a device and its last position, because the device periodically sends the beacons it hears, signal strength, battery level and status. Thanks to this, an unreturned device is visible on the map, most often outside the issue zone. We stress that a position does not prove that a person is present, and a device left in a locker may still report the locker room's position.

That is why a return as a physical placing into a slot is a stronger signal than position alone. It is worth making the station visible in the system's data as the place where the device should be after the shift.

Evidence and the report for audit

After the rollout, prepare a monthly report: number of issues, number of returns on time, number of unreturned devices and the average time from the end of the shift to clarifying the missing device. The report shows whether the procedure works and is material for the OHS auditor and the purchasing department. If unreturned devices keep appearing in one group, fix the procedure for that group instead of tightening the rules for everyone.

Order of steps before the start

Before the start, check whether the number of slots matches the number of devices, whether the assignment list is complete and whether each shift has a responsible person. Plan a trial week with a paper list running in parallel with the system, and after it switch to the register in the system. Only after stabilisation add alerting about an unreturned device, so as not to flood the team with false messages.

Video

Frequently asked questions

Where is it best to issue devices to our own workers?

In the locker room or the tool store, because every worker passes it and the point already has access control.

What if a worker forgets to return the device?

The system shows the last known position with a time stamp, and the procedure states who calls and after what time.

Do we have to set up alerting from the first day?

No. Start with visibility and turn on alerting after a trial week.

Does the issue register have to be in the system?

It should be, because then it matches the map and the state of the charger.

Let's talk about devices at your plant

We will show how to match devices to roles and how the system connects them on one map. Book a conversation with the InnerWeb team.

Let's talk