How many spare laptops should a company keep?

Why this matters

A spare laptop is a buffer, not inventory. It exists so a broken machine or a new hire does not cost someone a working day. Sized well, the pool sits quietly in a cupboard and nobody thinks about it. Sized badly, you either run dry during a bad week or you watch hardware age out of warranty in a drawer.

The count depends on things you already know: how many laptops you run, how fast a supplier delivers, what your warranty covers, how often people travel, and how many new hires start each month. Two companies with 80 laptops can need very different pools. A studio in one office with next business day onsite support needs less than a sales team spread across four countries with mail in repairs.

Spare capacity also costs more than the purchase price. Every spare needs a license, an image, security patching and a slot in your refresh plan. A pool that is too large pulls budget forward and leaves you with machines that are halfway through their useful life before anyone opens the box. How many spare laptops should a company keep is really a question about tolerance for downtime, priced honestly.

Before you start

Pull your ticket history for the last 6 to 12 months. Count how many laptops went out of service, how long each person waited, and how many of those waits came from a missing machine rather than a slow repair. That tells you which problem you are actually solving.

List the facts that shape the pool: headcount, sites, device ages, warranty end dates and the type of cover you hold. Next business day onsite is a different world from depot return with a week of shipping. Note the lead time your supplier has actually delivered, not the one printed on the quote, and add your hiring plan for the next two quarters.

Decide what counts as a spare. It should be a machine you can hand over the same day: imaged, enrolled in your device management, licensed, asset tagged, with a charger and a dock if the role needs one. A laptop in a box with no build on it is a project, not a spare.

Agree the service target with whoever owns the work. For most small and mid sized companies that means a same day swap for a failed device and a ready machine on day one for a new hire. Write it down. The pool size falls out of that target.

How to do it

Split the pool into two jobs, because they behave differently. The repair pool covers failures, which arrive unevenly, so size it from your ticket history plus a margin. The onboarding pool covers the gap between a signed offer and a delivered machine, so size it from hires per month multiplied by supplier lead time.

Then adjust for what is specific to you. A second site needs at least one machine of its own, because shipping a spare across the country eats the day you were trying to save. Roles that travel or present to clients usually need a small loaner set that sits apart from the pool and comes back after each trip.

Keep the pool on the same build as the rest of the fleet: same image, same management enrollment, same disk encryption settings. Check that on a schedule rather than the morning someone needs a machine.

1. Set the service target. Write down how fast a failed machine must be replaced and how early a new hire's laptop must be ready. Every later decision uses those two numbers.
2. Measure failures from tickets. Average your hardware tickets over 6 to 12 months, then note the worst month as well. That bad week is what empties the cupboard.
3. Size the repair pool. Start with one spare for every 20 to 30 laptops in a single site fleet, then raise or lower it using your own failure count and warranty turnaround. Depot return with slow shipping pushes the number up.
4. Size the onboarding pool. Multiply expected hires per month by the weeks between order and delivery, then round up. If you hire in bursts, size to the burst rather than the yearly average.
5. Add for sites and travel. Give every site with more than a handful of people one local spare, and keep one or two loaners that travel and come back. Label loaners differently so they do not drift into the pool.
6. Stage every spare properly. Image it, enroll it in device management, apply the license, tag it with an asset number and the date it was staged, and store the charger with it. Run a check on each unit every quarter.
7. Write the hand out and hand back process. Record who has which machine, when it went out and when it returns. Wipe and rebuild a returned loaner before it goes back on the shelf.
8. Reset the count each quarter. Compare the pool against fresh ticket history and the hiring plan. Move machines that sat untouched for two quarters into the next refresh or disposal.

How to check it worked

Watch the waits, not the stock level. Two numbers tell you most of it: how many working days people lost waiting for a replacement, and how many times the pool hit zero. If both stay near zero through a normal quarter, the size is about right.

Check the health of the pool itself. Every spare should still be inside warranty, still receive updates and still match your current build. A spare that fails its own check is worse than no spare, because you plan around it.

Test it once for real. Take a machine out of the pool on a random morning, hand it to someone as if their laptop had died, and time how long until they are productive. Anything that trips you up, a missing license, a forgotten dock, an account that needs manual setup, is a fix to make before the real failure.

Mistakes to avoid

Counting broken machines as spares. A laptop waiting on a repair is not available. Keep the repair queue and the pool on separate lists, or the number you report to finance will be wrong.

Letting the pool become the place old machines go. Devices returned by leavers often land there. Some are fine, but they need the same staging and warranty check as anything else, and most should go to wiping and disposal instead.

Losing track of who holds what. Unrecorded spares turn into permanent assignments, and then you are short again with no explanation. A simple log tied to your asset tags prevents it. Forgetting accessories does the same damage: chargers, docks and adapters run out before laptops do.

Skipping the review. A pool sized two years ago was sized for a different fleet. Put the review on the calendar next to the refresh plan. If you want an outside read on the whole picture, the Hardware and endpoint review from Cloudverg is a fixed price $4,500 over two weeks and covers inventory, a standard device specification per role, a three year refresh plan and spare and warranty recommendations. It is one option among others, and the steps above work on their own if you would rather size the pool in house.

Frequently asked questions