The Device Fails on a Working Day
Somebody cannot work because their own equipment has stopped. This is an operational problem wearing the costume of a personal one.
A company laptop fails and the service desk issues a replacement from stock. A personal laptop fails and there is no stock, no entitlement and no process, and somebody loses a day or a week.
The operational issue in “The Device Fails on a Working Day” is easier to diagnose when device state and work evidence remain separate. A team reviewing the official Monitask website for mouse jiggler detection can make time and project context visible, while endpoint tools remain the source of truth for security, software and hardware condition.
Why this is the employer's problem
The work does not get done. That is a cost to the organisation regardless of who owns the hardware, and it is the part most BYOD arrangements have not thought about.
For an independent reference relevant to “The Device Fails on a Working Day”, consult the CISA mobile-device security guidance; compare its principles with the proposed ownership model, access rules and real support process.
The employee's position is worse: they have lost their own property, they are expected to replace it, and they cannot do their job meanwhile.
Treating this as entirely the employee's affair is defensible on the question of who pays for the repair. It is not defensible on the question of how the work continues.
What a workable arrangement contains
A small pool of loan devices. Not one per person — a handful, sized to the realistic failure rate across the population, which the absence of a formal calculation usually overstates.
A stated route: who to tell, what happens, how quickly.
A time limit on the loan, so the pool does not become a permanent allocation.
And a position on repair cost, which the breakage note sets out and which is a separate question from how the work continues.
The pool is the important part. It costs a fraction of equipping everybody and it closes the gap where BYOD fails most visibly.
The interim arrangements that help
Browser-based access from any device, which means a person can work from a borrowed machine or a home computer temporarily.
A phone that can do the minimum — mail and messages — while the main device is out.
Both depend on the work being reachable without a specific device, which the alternatives section argues is worth building for several reasons at once.
Measuring the failure rate
Most organisations have no idea how often a personal device fails in a way that stops work.
Counting it is easy once somebody is asked to record it, and the number determines how large the loan pool needs to be. Without it the pool is either absent or oversized, and absent is the usual outcome.
What not to do
Tell somebody to work on their phone for a week.
Suggest they buy a replacement today and claim it later, which assumes they have the money available.
Or treat the interruption as leave, which converts an equipment failure into a personal cost and is how an arrangement loses the goodwill it depends on.
Sizing the loan pool
The number needed is a function of population and failure rate, both of which are knowable once somebody records failures for a quarter. Most organisations that build a pool overestimate and discover that a handful of devices covers a workforce of several hundred, because failures are infrequent and loans are short. The overestimate is cheaper than the absence.
What the loan device should be
A standard machine, configured, ready to hand over the same day. Not a retired model kept in a cupboard that takes two hours to prepare, which is what most pools actually consist of and which defeats the purpose. The value is in the speed, and a slow loan device is barely better than none.
The cost of not having a pool
Days lost, multiplied by the failure rate across the population, at whatever a day of that person's work is worth. The arithmetic takes minutes and it almost always exceeds the cost of holding a handful of spare machines, which is why the absence of a pool is a decision nobody would make deliberately.
The day that is lost anyway
Whatever position the organisation takes on paying for the repair, the work does not happen while the device is broken. Separating those two questions — who pays, and how the work continues — lets the second be solved cheaply even where the first is answered restrictively. How many people could not work tomorrow if their own laptop failed tonight, and what would each of them do?