TL;DR
Equipment for deskless workers does not work like equipment for office staff. There is often no personal device, no fixed address to deliver to, and no individual to hold accountable, because the hardware belongs to a site or a shift rather than a person. Policies written for laptops fail immediately.
- Assign to a location or a shift, not to an individual who moves between them.
- Shared devices need a handover step. Personal ones do not.
- Loss and damage rates are higher and that is a design input, not a failure.
- Delivery goes to a site, which is far easier than a home address.
- Ruggedised hardware costs more up front and often less across its life.
The moment this becomes real
Say a company adds a field operations team of forty to a workforce that was previously all office and remote. The existing equipment policy is applied, because it exists and nobody wants to write a second one.
Within a month the problems arrive. The policy assigns a device to a named individual, and these devices are used by whoever is on shift. It requires a signed agreement per person, which nobody can maintain across a rota. It specifies return on the last day, and the device never left the site.
Best tools for Device Management
The policy is not being ignored out of carelessness. It is being ignored because it describes a situation that does not exist here. The real issue is not compliance. It is that one policy was asked to cover two completely different ways of working.
When this is lighter than you think
Four stages where the existing approach is fine.
- Deskless staff with personal devices. Some field roles do have an assigned phone or tablet. Then your normal process applies.
- Very small teams. Under about ten people a manager knows who has what without any system.
- Single site operations. Everything is in one building, which removes most of the tracking difficulty.
- Bring your own device with an allowance. Common in some sectors and it moves the question to access and reimbursement.
It gets difficult across multiple sites, with rotating shifts, and anywhere devices are shared between people who never meet.
The five questions teams actually ask
Who is the device assigned to? For shared equipment, a location or a shift rather than a person. That single change makes the register work, because it stops describing an ownership that does not exist. Most asset systems allow a non person holder, and most teams have never used that field.
How do we handle handover between shifts? A short check at start and end of shift, recorded somewhere simple. It catches damage while you still know which shift it happened on, which is the thing you lose entirely without it.
What about loss and damage? Rates are higher than office equipment and that is a fact to budget for rather than a problem to solve with policy. Deductions and liability for shared devices are also much harder to apply fairly, since you often cannot establish who was responsible.
Where do we deliver? To a site, which is far easier than the home addresses that make office equipment logistics hard. This is the one area where deskless is simpler, and it is worth taking advantage of.
Should we buy ruggedised hardware? Often yes. The higher purchase price frequently beats the replacement rate on standard devices in demanding environments. Work it out from your actual failure rate rather than from the vendor’s claims.
Three ways teams handle it, and where each breaks
Apply the office policy anyway. The default, and it fails quietly. The policy is not followed, nobody says so, and the register fills with devices assigned to people who left. It breaks the first time anyone audits it.
Assign to individuals properly. Give every deskless worker their own device. Clean accountability and it genuinely works. It breaks on cost and utilisation, since a device used for one shift in three sits idle most of the time.
Assign to sites and shifts. Devices belong to a location, with a handover check between shifts. Best utilisation and it matches how the work actually happens. It breaks on accountability, because when something is everybody’s it can become nobody’s unless the handover step is real.
Five questions to size the difference
Working out your approach to equipment for deskless workers takes five answers.
Is any device genuinely personal? If not, stop assigning them to people.
Can your register hold a non person holder? Most can, and almost nobody uses it.
What is your actual loss and damage rate? Measure it rather than reacting to incidents.
Who does the shift handover? If nobody, damage is untraceable by design.
What does the office policy say that cannot apply here? That list is your second policy.
What is actually available
Five honest options, including ours.
Personal assignment. Best where the role genuinely needs a consistent device, such as field engineers with specialist configurations. Clearest accountability. Struggles on cost and idle time.
Site based pools. Best general answer for shift work. High utilisation, simple delivery. Struggles on accountability without a handover step, and on devices wandering between sites.
Lockers or managed charging stations. Best for larger sites. Devices are checked in and out automatically, which solves the handover problem mechanically. Struggles on upfront cost and on needing physical space.
Bring your own device with an allowance. Best in sectors where it is already normal. No hardware to manage. Struggles on security and on what happens to company data on a personal phone.
RemoAsset. Best where sites are spread across countries and replacing a broken device currently means somebody improvising locally, since maintenance and repairs plus device management cover the higher failure rate these environments produce. Where it struggles: shared device handover and shift accountability are process problems inside your operation that no external service touches, and they are the hard part here. Its published pricing starts with a pay as you go plan and a yearly subscription above it.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Personal devices per worker | Any | Assigned hardware | Normal | Use your existing equipment policy |
| Single site, shared devices | Under 50 | One location | Register says the wrong thing | Assign devices to the site, not to people |
| Multiple sites, rotating shifts | 50 plus | No handover step | Damage untraceable | Add a start and end of shift check |
| High loss or damage rate | Any | Standard hardware | Replacement cost | Price ruggedised options against your real failure rate |
| Sites across several countries | Any | No local IT | Replacements improvised | A service such as RemoAsset for repair and replacement |
What the gap actually costs
Applying an office policy to deskless work costs very little directly and produces a register that is wrong in a specific way: it names individuals for devices nobody individually holds. That matters at audit and it matters when something breaks.
The real money is in utilisation. Buying a device per person for a workforce where only a third are on shift at once means paying three times for one requirement. Teams that assign by site rather than by person often find they need far fewer devices than headcount, which is the opposite of the office assumption.
The third cost falls on the people. Shared devices with no handover step and no clear ownership get treated accordingly: nobody reports a cracked screen because nobody is sure whether they will be blamed. So the question is not how to make the office policy fit. It is whether anybody has written down how this actually works.
When one policy cannot cover two workforces
The instinct to have a single equipment policy is reasonable and it is the thing causing the problem. Office and remote staff hold personal devices at fixed addresses for years. Deskless staff share devices at sites across shifts. Those are different enough that one document cannot describe both honestly.
The practical answer is a short second section rather than a second policy: who the device is assigned to, what the handover looks like, how damage is reported without blame, and where replacements come from. Four paragraphs usually covers it.
Where it becomes an external question is replacement speed. Higher failure rates across multiple sites means a steady flow of repairs and swaps, and in several countries that is a supply chain rather than a ticket. A laptop lifecycle management service handles that half. The handover and accountability half stays firmly with you.
See how repairs and replacements are handled across sites
Read our guide to writing an employee equipment policy
Related reading
- Writing an employee equipment policy
- Device damage liability
- Writing an asset management policy
- Equipment for part time and job share staff
- Shift and working time arrangements are regulated. Acas publishes UK guidance on working time and rest, and the UK government sets out maximum weekly working hours.
Frequently Asked Questions
How is equipment for deskless workers different?
The device usually belongs to a site or a shift rather than to a person, there is no home address to deliver to, and several people use the same hardware. Policies written around a named individual holding a laptop for years do not describe any part of that.
Who should a shared device be assigned to in the register?
A location or a shift rather than an individual. Most asset systems support a non person holder and almost no team uses it. Making that change stops the register describing an ownership that does not exist and makes audits straightforward.
How do we handle damage on shared devices?
With a short handover check at the start and end of each shift, recorded simply. Without it you cannot establish when damage occurred, which makes any liability approach unfair and means people stop reporting problems rather than risk being blamed.
Should we charge people for damage to shared equipment?
It is much harder to do fairly than with personal devices, because you usually cannot establish who was responsible. Most teams find a no blame reporting culture recovers more value than a deduction policy, since the alternative is damage going unreported until failure.
Is ruggedised hardware worth the extra cost?
Frequently, in demanding environments. The higher purchase price often beats the replacement rate on standard devices. Work it out from your own measured failure rate rather than from a vendor’s durability claims, since the answer depends entirely on your conditions.
How many devices do we actually need?
Usually fewer than headcount, which surprises teams used to office assumptions. If only a third of staff are on shift at once, a site based pool serves everyone with far fewer machines. Size it against concurrent users rather than total employees.
Do we need a separate equipment policy?
A short additional section is usually enough rather than a second document. Cover who the device is assigned to, what handover looks like, how damage is reported and where replacements come from. Four paragraphs typically does it.
