Why this matters
How to plan a laptop refresh cycle is a budgeting and operations exercise, not a shopping spree. A laptop that still boots can still be a bad machine: battery runtime falls, hinges crack, firmware updates stop, and the model drops off the vendor support list. When support ends, you lose easy repairs and sometimes OS updates.
A written cycle gives finance a predictable line item and gives IT a repeatable build. It also reduces the number of models on the floor, which cuts spare parts, dock types, charger types and help desk guesses.
The goal is not to replace every machine on the same day. It is to move each role to a standard device, on a schedule, with a spare pool and a disposal path that protects data.
Before you start
Before you pick models, collect facts. Export your device list from your management tool, such as Intune, Jamf or a spreadsheet if you have no tool. For each laptop record asset tag, serial, owner, department, role, purchase date, warranty end, model, CPU, RAM, storage, OS version, encryption status and battery health.
Group users by role instead of job title. A sales rep who lives in a browser, a developer who runs containers and a finance user who runs heavy spreadsheets need different minimums. Write one standard specification for each group: screen size, weight, RAM, SSD, ports, docking, camera and security features like TPM 2.0 and a fingerprint reader.
Check support dates yourself. Look up the model on the vendor support site and note the end of warranty and the end of OS support. For Windows, check the Windows 11 hardware requirements and the support timeline for the installed release. For macOS, check which Mac models the next release supports.
Get a budget range approved before you ask suppliers for quotes. Decide whether you will buy, lease or mix the two, and who signs off. Set a rule for exceptions, such as a user who needs a larger screen or more RAM.
How to do it
Run the work in waves. Start with the oldest and least supported machines, then move to growth teams and heavy users. Keep a small buffer of ready devices so a failed laptop does not wait for a factory order.
Build a standard image or enrollment profile before the first box arrives. Test docking, printing, VPN, Wi-Fi, certificate renewal and the line of business apps on one device per role. Fix the build once, then repeat it.
Set a retirement rule. A laptop leaves service when it loses OS support, when repair cost and downtime pass the value of a replacement, or when battery health and performance fail your own threshold. Do not use age alone.
- Export and clean the inventory. Pull the raw list from your management tool, warranty portal and finance records. Reconcile duplicates, missing owners and devices marked lost. You cannot schedule what you cannot identify.
- Define role standards. Create two or three laptop standards, not one per person. State the minimum CPU class, RAM, SSD size, screen, ports and warranty. Publish the exception process.
- Set a three year schedule. Assign each device to a refresh year based on support end, battery health and role. Put the oldest and unsupported models in year one. Leave room to pull a device forward when it fails.
- Price the plan and get approval. Collect quotes for the devices, docks, monitors, licenses and spares. Add the disposal and data wipe steps. Ask finance to approve a range, not a single number.
- Pilot one device per role. Give a test laptop to one user in each role group. Run their real work for a week, including meetings, printing and travel. Record every failure and fix the build before the bulk order.
- Prepare enrollment and security. Enroll devices with Autopilot, Intune, Jamf or your tool of choice. Turn on disk encryption, screen lock, firewall and endpoint protection. Confirm that the asset tag and serial match the inventory.
- Deploy in waves with a spare pool. Schedule swaps by team and set a fixed handover window. Move data, sign in to key apps and test the dock before the user leaves. Keep a small spare pool sized to your failure rate.
- Retire and wipe old devices. Remove the device from management, back up user data and wipe the drive. Record the wipe and disposal in the asset log. Never pass a laptop to a new user without a clean install.
How to check it worked
After each wave, compare the deployed list to the plan. Count devices by role, model and warranty end. Check that every new laptop is enrolled, encrypted, backed up and assigned to a named user.
Ask the help desk for ticket themes. A rise in dock or printer tickets after a model change points to a build problem, not user error. Fix the build before the next wave.
Review the spare pool monthly. If you use more spares than you planned, adjust the buffer or the standard. If spares sit untouched, reduce the pool.
At the end of the cycle, update the inventory and the next schedule. The output is a living list, not a one time report.
Mistakes to avoid
Do not replace every laptop on one date. A big bang refresh ties up cash, strains the help desk and hides build defects until the warranty window is half gone.
Do not forget the accessories and licenses. Docks, monitors, chargers, cables, Windows Pro upgrades, security agents and backup tools all belong in the plan. A cheap laptop with the wrong dock is a support ticket.
Do not let users keep old laptops without a rule. An old machine that stays in service still needs patches, encryption and support. If it is out of support, take it back and wipe it.
Do not skip the disposal trail. A missing wipe record is a data breach waiting to happen. If you want outside help, the Hardware and endpoint review from Cloudverg is a fixed price $4,500 package that runs for two weeks and starts within 10 business days. It includes an inventory, a standard device specification per role and a three year refresh plan with quantities and prices.
Frequently asked questions
How often should you refresh laptops?
Use a three to four year planning window, but let support dates and condition drive the actual swap. A laptop that loses OS support, has a failing battery or needs repeated repairs should leave earlier. Do not replace every device on one date.
Is leasing better than buying laptops?
Leasing spreads the payment and can include disposal, but it locks you into a term and may charge for damage. Buying gives you control and a longer service tail, but you carry resale and disposal. Choose based on cash flow and admin capacity, not habit.
What should a laptop standard include?
Set role based minimums for CPU class, RAM, SSD, screen size, ports, docking, camera, Wi-Fi, TPM 2.0 and warranty. Add accidental damage cover if users travel. Keep two or three standards so support and spares stay simple.