Repairs, Warranty and Spares

Devices break. Whether that costs you anything depends on a field in the register that takes seconds to check and is routinely skipped.

Check warranty first

Before authorising any repair, look up the warranty status.

Organisations pay for repairs covered by warranty regularly, for the same reason they pay for software they already own: nobody checked.

Record warranty expiry at receipt, not when you need it.

Report on expiries, monthly, ninety days ahead. A device approaching warranty expiry is a candidate for a final inspection and for a refresh decision.

What warranties actually cover

Parts and labour, for a defined period, usually excluding accidental damage.

Accidental damage protection as a separate purchase, which is worth modelling against your actual breakage rate rather than buying by default.

On-site versus return-to-base, which matters enormously for a distributed workforce and is frequently the cheaper option overlooked at purchase.

Battery coverage, which is commonly shorter than the main warranty and is the most frequent failure in a laptop fleet.

Read the terms once per supplier and record the summary, rather than reading them at the point of each failure.

The repair decision

Under warranty: claim.

Out of warranty: compare repair cost against replacement cost and remaining useful life.

A common threshold: repair if the cost is below a third of replacement and the device has more than a year of planned life. Set the numbers to suit and write them down, so the decision is not made case by case under time pressure.

Batteries are the exception. A battery replacement on an otherwise sound machine is almost always worth it.

Screens and boards on older devices usually are not.

Turnaround and loans

The user needs a machine while theirs is away.

Hold loan stock, sized to your failure rate.

Record the loan with an expected return date, and chase overdue ones.

Image loans in advance so a handover takes minutes.

Track repair turnaround by supplier. A cheaper repair contract with a three-week turnaround is not cheaper once you count the loan fleet it requires.

Spares

Hold spares for the failure modes you actually see: chargers, docks, cables, and complete devices.

Chargers are the most-lost item in any fleet and holding them centrally is cheaper than individual purchases.

Do not hold parts unless you repair in-house, which most organisations should not.

Standardisation reduces the spares requirement more than any stock policy.

Recording it

Per repair: asset, date, fault, action, cost, supplier, warranty claimed or not.

This history feeds two decisions: whether to replace a device with repeated faults, and whether a model is worth buying again.

A model generating disproportionate repairs is a procurement finding, and it is only visible if the repair history is attached to the asset rather than living in a supplier's system.

The pattern worth watching

Repeated failures on one asset: replace it.

Repeated failures on one model: stop buying it.

Repeated failures for one user: a conversation about handling, or a more robust device, rather than another repair.

Repairs clustering after a specific date: a batch problem, and possibly a warranty claim across the batch.

The battery exception

Batteries are the most common failure in a laptop fleet and the one where the standard repair-versus-replace threshold gives the wrong answer.

A battery replacement is cheap relative to a device.

It restores most of the practical complaint people have about an ageing machine.

It extends useful life by a year or more, which defers a much larger cost.

Battery warranty is frequently shorter than the main warranty, so check separately.

Batch them. Devices of the same age fail together, and a planned batch replacement is cheaper and less disruptive than twelve individual repairs over six months.

Track battery health where your endpoint platform reports it, and replace on the forecast rather than on the failure.

The repair threshold, written down

Deciding case by case under time pressure produces inconsistency and, on average, overspending.

Write the rule: repair if cost is below a stated fraction of replacement and the device has more than a stated remaining life.

State the battery exception, which almost always favours repair.

State the out-of-warranty screen position, which on older devices usually favours replacement.

State who can approve an exception.

Review the numbers annually against actual repair costs and residual values.

A written threshold also protects the person making the decision, which is why it gets followed rather than argued about each time.