TL;DR
Right to repair hardware arguments usually arrive as a sustainability point and get filed accordingly. The more interesting version is financial. If a device can be repaired economically, the refresh cycle you set three years ago may be retiring machines a year or two early, and that is a line in the budget rather than a line in a values statement.
- Repairability changes when a device should retire, not whether.
- The decision is repair cost against residual value, not age.
- Battery and screen are usually economic. Board level rarely is.
- Logistics, not parts, is what makes remote repair expensive.
- Downtime belongs in the sum and is usually left out.
- A spare pool makes repair viable. Without one, replacement wins.
What has actually changed
Two things, and only one of them is law.
Regulation has moved. the EU right to repair directive on EUR-Lex sets obligations around repair in the European Union, and comparable pressure exists in several other markets. The direction is settled even where the detail is not.
Manufacturers have moved further and faster than the regulation, largely in anticipation of it. Parts, manuals and tools are more available than they were, and more devices are designed with replaceable batteries again.
What has not changed is your refresh policy, which was probably written when none of that was true.
The question worth reopening
Not “should we repair things”, which everyone says yes to. The question is whether the retirement age in your policy still reflects the cost of keeping a machine working, because that cost has fallen.
The sum that actually decides it
Four numbers, and most teams only use two.
Repair cost. Parts plus labour. Usually known and usually quoted quickly.
Residual value. What the device is worth on the secondary market today, working.
Replacement cost. The new machine, configured and delivered.
Downtime cost. Days the person cannot work properly, which is the number nobody puts in.
| Repair type | Typically economic? | Main constraint |
|---|---|---|
| Battery replacement | Yes, comfortably | Turnaround |
| Screen | Usually | Part availability by model |
| Keyboard or trackpad | Often | Labour on glued assemblies |
| Storage upgrade | Depends on the model | Soldered components |
| Logic board | Rarely | Part cost approaches a new unit |
Run the sum per repair type rather than per device age. our note on device repairability covers how repairability varies by model, which is the input this table assumes.
Logistics is the real cost
For a distributed team, the part is rarely the expensive bit.
Getting a device from a home to a workshop and back involves two shipments, a window where the person has no machine, and a risk that something goes missing in transit. That is where the money and the frustration live.
Three arrangements, roughly in order of cost per incident. Local repair near the employee, which is fastest and hardest to control for quality. Mail-in to a central workshop, which is controllable and slow. On-site, which is expensive and rarely justified outside dense cities.
RemoAsset’s maintenance and repairs service handles the collection and return leg, which is the part that makes mail-in tolerable rather than the part that makes it possible.
The variable that changes everything
A spare pool. With one, repair turnaround stops mattering because the person gets a working machine the same week. Without one, every repair decision is really a decision about how long somebody sits idle, and replacement wins almost every time.
Sizing the spare pool
This is the intervention that makes everything else in this article possible, and it is usually underfunded because it looks like idle stock.
It is not idle stock. It is the thing that converts a four day outage into a one day one, and it is reused continuously.
The sizing question is how many simultaneous failures and new starters you need to cover in a typical month, plus a margin for the month that is not typical. Most teams land on a small number and are surprised how small it is.
Two mistakes to avoid. Holding spares in only one country, which means the spare is useless to half the team. And holding the newest machines as spares, which is expensive; last generation is usually fine for a two week loan.
RemoAsset’s device storage and redeployment service exists because holding that pool somewhere sensible is a logistics problem rather than an IT one.
Rewriting the refresh policy
If the policy says three years, the honest question is where that number came from. Usually a depreciation schedule, a warranty term, or a previous employer’s policy.
A better policy has a condition rather than a date. Retire when the device fails a performance or reliability threshold, or when the economic repair options are exhausted, or when a security requirement makes it unsupportable.
That is harder to administer and it is the reason age based policies persist. The compromise that works is a default age with a documented extension path, so the age is a prompt to assess rather than an instruction to replace.
What finance needs to accept it
- A stated assessment at the default age, not an automatic order.
- The repair cost against residual value sum, recorded.
- A cap, so one machine is not repaired indefinitely.
- Reporting on how many extensions were granted and what they cost.
Where this argument runs out
Three situations where replacing is simply right, and pretending otherwise wastes money.
The device cannot run current software securely. the NCSC device security guidance is clear that unsupported devices are a risk, and no repair fixes an end of support date.
The repair is board level on a machine past mid life. The cost curve is unforgiving and the next failure is usually close behind.
The person needs more performance than the machine ever had. A repaired slow laptop is still a slow laptop, and the cost of that shows up in work rather than in the budget.
There is also a quieter limit. Repair programmes need somebody to own them. If nobody does, the policy produces devices sitting in a queue, which is worse than either repairing or replacing promptly. RemoAsset’s laptop lifecycle management service is one way to put that ownership somewhere with capacity.
The number that tells you it is working
Not repairs completed, which rewards activity. Track average device age in service, and track it by team.
If the programme works, that number rises gently and nobody complains. If it rises and complaints rise with it, you have extended the fleet past the point where the machines are pleasant to use, which costs more than it saves in ways that never reach the budget.
Watch the spread as well as the average. One team on five year old hardware while another refreshes annually is a fairness problem before it is a cost one, and it usually tracks whoever had budget in a given year rather than any policy you wrote.
The fix for the spread is to hold the refresh budget centrally rather than per team. It is unpopular with whoever currently holds it, and it is the only arrangement where the policy you wrote is the policy that runs.
What to tell the team
Say that devices are kept longer because they are maintained, not because the budget was cut. Those are indistinguishable from a desk unless somebody explains, and people assume the second.
Pair it with something visible. A fast route to a battery replacement, or a spare that arrives next day, does more for how the policy is received than any amount of framing. People accept an older machine readily when a broken one gets fixed quickly, and resent a new machine that took three weeks to arrive.
[Two-CTA block: Case Studies | Talk to Expert]
Frequently asked questions
Does right to repair hardware legislation change what I must do?
It changes what is available to you more than what is required of you. The EU directive sets obligations around repair and comparable pressure exists in other markets, and manufacturers have moved faster than the regulation in anticipation of it. Parts, manuals and tools are more available than they were. The practical consequence for most companies is that a refresh policy written before those changes may now be retiring machines a year or two early.
How do I decide whether to repair or replace?
Four numbers, and most teams use only two. Repair cost as parts plus labour, residual value of the working device on the secondary market, replacement cost configured and delivered, and downtime cost for the days the person cannot work properly. That last one is almost always left out and it frequently decides the answer. Run the sum per repair type rather than per device age.
Which repairs are usually worth doing?
Battery replacement comfortably, screens usually, and keyboards or trackpads often, though labour on glued assemblies can change that. Storage upgrades depend entirely on whether components are soldered. Logic board work is rarely economic, because the part cost approaches a new unit and the next failure tends to follow closely. The model matters as much as the fault, so check repairability before assuming.
Why is remote repair so expensive?
The part is rarely the expensive element. Getting a device from a home to a workshop and back involves two shipments, a window where the person has no machine, and transit risk. Local repair near the employee is fastest and hardest to quality control, mail-in is controllable and slow, and on-site is expensive and rarely justified outside dense cities. Logistics is what makes or breaks the economics.
What makes repair viable at all?
A spare pool. With one, repair turnaround stops being the deciding factor because the person gets a working machine the same week. Without one, every repair decision is actually a decision about how long somebody sits idle, and replacement wins nearly every time. Two sizing mistakes to avoid are holding spares in only one country, and holding the newest machines as spares when last generation is fine for a two week loan.
Should I change our three year refresh policy?
Ask where the three came from first, because it is usually a depreciation schedule, a warranty term or a previous employer’s habit rather than an assessment. The better policy sets a condition rather than a date. The workable compromise is a default age with a documented extension path, so the age prompts an assessment instead of triggering an automatic order, with a cap so one machine is not repaired indefinitely.
When should I stop arguing for repair?
Three situations. When the device cannot run current software securely, because no repair fixes an end of support date and unsupported devices are a genuine risk. When the repair is board level on a machine past mid life. And when the person needs more performance than the machine ever had, since a repaired slow laptop is still slow and that cost shows up in their work rather than in your budget.
[Start for free]