How Delivery Companies Keep Driver Phones Secure and on Task

Driver phones have one job and a hostile environment. They run a delivery app all day, get handled with one hand, lose signal in car parks and stairwells, and go home in someone’s pocket whether you intended that or not. The configuration that works is narrow, tolerant of being offline, and clear about what happens at the end of a shift.

Here is how delivery operations usually set them up, and the one line you should not cross.

Decide first: assigned or pooled

This decision drives everything else.

Assigned phones belong to a named driver. They can be fully managed with a normal app list, and the driver signs into the delivery app as themselves. Handover is rare.

Pooled phones live in a charging rack and go out with whoever is on shift. These want a kiosk configuration: locked to the delivery app, no launcher, no settings, identical every morning. Nobody personalises them because nobody keeps them.

Pooled devices are far easier to manage and far easier to lose track of. Assigned devices are the opposite. Most operations end up with both, which is fine, but they need different groups and different policies.

The configuration that survives a shift

Screen lock, with the practical caveat. Enforced, always. But drivers use phones one-handed in the rain, and a long complex password on a pooled device gets written on the charging rack. A PIN is the realistic answer for shared handsets.

Screen stays awake while charging. A phone in a dashboard cradle that sleeps every thirty seconds is the single most common complaint. For kiosk devices, set it to stay on while powered.

Camera allowed. Proof of delivery photos are the whole audit trail for a delivery business. Do not block it.

Location permission for the delivery app. Worth separating from device management, and we come back to this below.

Required apps installed on enrollment. The delivery app, maps, and a messaging tool if drivers use one. A phone out of the rack should be ready to work without anyone configuring it.

An approved catalogue, not a blocklist. Pooled phones attract games with remarkable speed. If the store only contains what you approved, there is nothing to remove later.

Where device management stops and dispatch begins

This is the line that matters, and getting it wrong costs you your drivers’ trust.

Your delivery or dispatch app tracks routes and deliveries. Drivers know it does, it is visible in the app, and it is the normal expectation of the job. That is where operational tracking belongs.

Device management is not a second, hidden tracking layer. NounDesk reports a device’s location only while it is in lost mode, and while that is active the phone is locked and the screen says so. There is no background location history to look through.

Keep those separate deliberately. The moment device management gets used to check where somebody went on their break, you have a different relationship with your drivers and a worse one. Our post on explaining device management to staff has wording that works.

Build for going offline

Delivery phones lose signal constantly: underground car parks, lifts, rural gaps, tall buildings.

Commands queue and run at the next check-in, so a lock issued while a driver is in a basement takes effect when they surface. That is normal and not a fault.

Set alert thresholds to match. If a device offline for thirty minutes triggers an alert, you will have alerts all day and will stop reading them. For delivery work, a device unseen since yesterday is worth knowing about; a device quiet for an hour is a stairwell.

End of shift is your biggest risk

More delivery phones go missing between the last drop and the rack than anywhere else in the process.

Have a return routine and make it boring. Phones go back in the rack, on charge, counted. Somebody looks at the count.

For pooled devices, a daily check of which handsets have not reported in is faster than counting by hand, and it catches the phone that went home in a jacket pocket. That is the moment to call the driver, not three days later.

If a device does go missing, lock it first and put a callback number on the screen before doing anything else. The sequence is in what to do in the first hour.

Battery, briefly

Drivers will tell you device management drains the battery. It does not; there is no background agent app on a modern Android deployment. What drains the battery is a mapping app with the screen on for nine hours.

Worth knowing: NounDesk does not report battery level outside lost mode, so you cannot use the console to find out which handsets are dying mid-shift. The practical answer is cradles with chargers in every vehicle, which is cheaper than the alternative anyway.

What to do this week

1. Split your phones into assigned and pooled and give each a group. Most operations have never made this explicit, and it is the root of a lot of configuration mess.
2. Fix the screen timeout on cradle devices. It is the complaint you are already getting.
3. Count the rack tonight. Whatever the discrepancy is, that is your baseline.

FAQ

Can I see where a driver is using device management?

Not with NounDesk, outside lost mode. Route visibility belongs in your dispatch app, where drivers expect it. Device management here is for securing and recovering the hardware.

Should pooled phones be kiosk mode?

Usually yes. A pooled device exists to run one app, and kiosk removes the launcher, blocks settings and keeps the screen awake. See the kiosk guide.

What if a driver takes a phone home?

Common, and not always a problem if the device is assigned. For pooled devices it breaks the next shift. A rack count and a policy line handle it better than a rule nobody checks.

Do drivers need their own Google accounts?

Not for the device to be managed. Enrollment does not involve typing a personal Google password into the handset, and apps come from your organisation’s approved catalogue.

Delivery phones reward a narrow configuration and a boring end-of-shift routine. Most losses are process, not security.

See the delivery and logistics setup, or start a free trial.