The same cycle for every client
A recurring schedule opens each client’s refresh a few months before its budget year, assigned to the account manager and the lead technician.
Hardware Lifecycle Refresh Checklist Template
A replacement ordered the day a laptop dies is a repair, not a refresh. Pull the dates from the RMM once a year, price them in the client’s budget, and the new kit arrives before the old kit fails.
Most MSP clients replace hardware the same way: something breaks, a ticket goes in, a quote goes out and a user works on a borrowed machine for a week. It is the most expensive way to buy a laptop, and it leaves a mix of models and warranty dates nobody planned. This free hardware lifecycle refresh checklist gives vCIOs, account managers and technicians an annual cycle for each client instead. It pulls age, warranty, operating system support and Windows 11 eligibility from the RMM, applies the client’s refresh policy, and turns the result into a priced list in the client’s budget year. Nothing is ordered until the client’s written approval is attached. New devices are provisioned through Windows Autopilot and Intune or your standard image, users are migrated, and old devices are deregistered, sanitised and removed from billing. When servers or network equipment are in the refresh, a conditional phase adds the maintenance window, rollback plan and post-cutover checks.
A Refresh Cycle Decides What to Replace Before Users Decide for You
Four processes touch a client’s hardware, and this page covers only one of them. The IT Asset Management Checklist keeps the register accurate month by month. The IT Asset Disposal (ITAD) Checklist takes a batch of retired devices through sanitisation and certificates. The Operating System Upgrade Rollout Checklist moves devices that can stay to a new OS version. The refresh cycle is the decision in the middle: once a year, for one client, which devices are replaced, at what cost, in which budget period, and how the swap is done without losing anyone’s data.
It is also where the vCIO’s plan becomes a purchase order. The vCIO Technology Roadmap Review Checklist sets the multi-year budget line for hardware. This checklist fills that line with serial numbers, and its last phase updates the agreement’s device counts so the MSP Billing Reconciliation Checklist isn’t left to discover the change a quarter later.
Windows 10 makes the 2026 cycle unusual. Microsoft ended support on 14 October 2025, so every Windows 10 device still in a client’s estate this autumn needs an explicit choice: upgrade, replace, or pay for another year of Extended Security Updates (ESU).
Break-fix replacement
One device at a time, on failure
Trigger: a ticket from a user who can’t work.
Price: whatever is in stock this week, often at short notice.
Budget: a surprise invoice the client didn’t plan for.
Old device: left in a drawer, still in the RMM and still billed.
Annual refresh cycle
The whole estate, once a year
Trigger: age, warranty and OS support dates from the RMM.
Price: standard models, quoted and ordered in a batch.
Budget: agreed in advance and split across the client’s year.
Old device: deregistered, sanitised, certified and removed from billing.
What the Hardware Lifecycle Refresh Checklist Covers
Seven phases take one client from inventory export to updated billing. Phase 6 appears only when servers or network equipment are in the refresh.
Phase 1
Phase 1: Pull the Estate Data
Run it two or three months before the client sets its budget.
- Open the refresh for the client and budget year — record the start of the client’s financial year, its refresh policy and who signs off hardware spend
- Export the hardware inventory from the RMM — model, serial, first-seen or purchase date, processor, memory, storage, OS version and last check-in for every device
- Add warranty end dates — from the manufacturer’s warranty lookup or the documentation platform, and flag devices with no warranty record
- Check Windows 11 eligibility for every Windows 10 device — TPM 2.0, UEFI with Secure Boot, a supported processor, 4 GB of memory and 64 GB of storage
- Reconcile the RMM with the documentation platform — devices in one but not the other are found now, not after the order is placed
Phase 2
Phase 2: Apply the Refresh Policy
- Flag devices past their refresh age — by device class, using the client’s agreed cycle or your standard where it has none
- Flag devices losing OS support — Windows 10 devices not enrolled in ESU, servers on an operating system near its end date and network kit with no further firmware
- Flag devices with a poor repair history — repeat hardware tickets, disk health alerts and worn batteries, whatever their age
- Build the devices-due list — each device with its user, reason and priority: replace now, replace this year or review next year
- Confirm whether servers or network equipment are in this refresh — answer Yes or No; Yes adds the infrastructure phase
Phase 3
Phase 3: Quote, Budget & Approval
- Choose standard models for each role — from your standard device list, so builds, docks and spares stay consistent
- Build the quote — hardware, accessories, setup labour, data migration and disposal, split across the client’s budget periods
- Check the quote against the technology roadmap — explain any difference from the hardware line the client already approved
- Present the options to the client — replace now, defer with a warranty extension or ESU, or retire the device without replacement
- Approve the refresh order — the account manager records the client’s written approval as an attachment and answers Approved or Not approved before anything is ordered
Phase 4
Phase 4: Order, Receive & Provision
- Place the order against the approved quote — and ask the reseller to register the devices for Windows Autopilot where they can
- Check deliveries against the order — serials, condition and accessories, then tag each device and add it to the documentation platform
- Confirm Autopilot registration and profile assignment — or apply your standard image where devices are not cloud-managed
- Provision the standard build — compliance policies, disk encryption, RMM agent, EDR and backup, checked on each device before it leaves the bench
- Book a handover slot with each user — agreed with the client contact, so nobody is swapped in the middle of month-end
Phase 5
Phase 5: Deploy & Migrate Users
- Copy what the old device holds locally — files outside OneDrive or the file server, browser profiles, printers and application settings
- Hand over the new device — the user signs in, OneDrive syncs, and line-of-business applications, printers and peripherals are tested with them
- Record the user’s acceptance — after a working day on the new device, not at the desk during handover
- Collect and quarantine the old device — labelled with its asset tag, held for the agreed grace period and logged into custody
Phase 6 — Infrastructure Only
Phase 6: Servers & Network Equipment
Shown only when servers or network equipment are in the refresh. A laptop-only refresh goes straight to Phase 7.
- Book the maintenance window — under an approved change record, with the client told what will be unavailable and for how long
- Back up configurations and firmware versions — a verified server backup and exported switch, firewall and access point configurations
- Write the migration and rollback plan — cutover steps, the point where you decide to roll back and how long rollback takes
- Cut over in the window — follow the plan and record each step’s start and finish time
- Run the post-cutover checks — services, DNS and DHCP, VPN, Wi-Fi, backup jobs, monitoring and a user test at each site
- Hand the old server to decommissioning — dependencies, DNS records, firewall rules and backup jobs removed before the hardware leaves
Phase 7
Phase 7: Retire Devices & Update Records
- Deregister retired devices from Intune and Windows Autopilot — delete each device from Intune first, then remove its Autopilot registration
- Send retired devices to disposal — as one batch through your disposal process, with sanitisation and a certificate per device
- Remove retired devices from the RMM, EDR and backup — so no agent, seat or job keeps running for hardware that has gone
- Update the documentation platform and agreement device counts — so next month’s invoice matches the estate
- Set the next refresh review date — and record every device deferred this year and why
Refresh Cycles That Hold Up When the Client Asks Why
No standard sets how long a laptop should last. The cycles below are common practice among MSPs and in-house teams, and the right one for a client depends on how the devices are used, what the warranty covers and what the client can afford. Agree a policy once and write it into the client’s documentation.
| Device class | Common refresh cycle | What brings it forward |
|---|---|---|
| Laptops | 3 to 5 years | Warranty ending, battery wear, heavy travel, or a processor not supported by Windows 11 |
| Desktops | 4 to 6 years | Windows 11 ineligibility, repeated disk or power faults, a role that now needs more memory |
| Servers | 5 to 7 years | The operating system reaching end of extended support, warranty or parts no longer available, capacity |
| Switches, firewalls and access points | 5 to 7 years | No further firmware or security updates from the manufacturer, a licence that can’t be renewed, bandwidth |
| Phones and tablets | 2 to 4 years | The device no longer receiving operating system updates |
Warranty is usually the cleanest trigger, because out-of-warranty repairs are slow to source and hard to price into a fixed fee. For servers, check the operating system as well as the hardware: Windows Server 2016 reaches the end of extended support in January 2027, so any 2016 server still running in a client estate this autumn belongs on the devices-due list or in a migration plan.
Windows 10 devices in October 2026: three choices
Windows 10 support ended on 14 October 2025, and the first year of commercial ESU is now running out. Every Windows 10 device on the inventory should leave Phase 2 with one of these decisions recorded against it:
- Upgrade. The device passes the Windows 11 checks and has life left. It goes to the OS upgrade rollout, not the refresh order.
- Replace. The device fails the checks, is near the end of its cycle or would cost more to keep than to replace. It goes on the devices-due list.
- Extend for a year. The device runs a line-of-business application that can’t move yet. It stays on ESU, which needs version 22H2, with a named reason and a review date. Because ESU is cumulative and the price doubles each year, it rarely stays cheaper than a new device for long.
Microsoft has extended its consumer ESU programme to 12 October 2027, but that programme is aimed at individuals. Business devices are covered through Microsoft’s commercial ESU offer, for up to three years after end of support.
Why Run Hardware Refreshes in CheckFlow?
Nothing ordered without a signature
The approval task halts the order until the account manager has attached the client’s written approval and answered Approved. The quote, the approval and the delivery check sit on one record, so a disputed invoice is settled in minutes.
Infrastructure steps only when they apply
One answer in Phase 2 decides whether conditional logic adds the server and network phase. A laptop refresh stays short, and a firewall swap can’t skip its rollback plan.
Hardware refresh touches sales, service and billing at once, which is why the MSP process management guide recommends standardising it. CheckFlow for MSPs runs it alongside onboarding, QBRs and renewals for every client.
Server cutovers should go through your change process: the Server Decommissioning Checklist retires the old server once the new one is live, and the refresh feeds the hardware section of the MSP QBR Checklist. Retired devices leave through the ITAD checklist, which follows NIST SP 800-88 Rev. 2, published in September 2025 to replace Rev. 1.
Frequently Asked Questions
How often should an MSP refresh client hardware?
There is no fixed rule. Common practice is three to five years for laptops, four to six for desktops and five to seven for servers and network equipment, adjusted for how hard the devices are used and how long the warranty runs. Many MSPs tie the cycle to the warranty they sell with the device. Agree the policy with the client, write it down and review the whole estate against it once a year.
Is it cheaper to pay for Windows 10 ESU or replace the device?
For one year, ESU is usually cheaper than a new device: the commercial first-year price was $61 per device. It doubles each year, though, and it is cumulative, so a device joining in year two pays for year one as well. ESU also only delivers security updates, not fixes or support. Use it as a bridge for devices that genuinely can’t move yet, with a named reason and a replacement date in the next refresh.
How should an MSP charge for hardware refresh work?
Most agreements treat new-device setup and data migration as project work, quoted per device alongside the hardware, rather than as part of the monthly fee. Whichever model you use, put the labour in the refresh quote so the client approves it with the hardware, and log the time against the refresh project in the PSA.
Can staff buy or keep their old laptops?
They can, if the client agrees, but treat the device like any other disposal. Sanitise it, deregister it from Intune and Windows Autopilot so it doesn’t try to enrol back into the client’s tenant, remove the asset tag and record the sale or gift and its value. Remove company-licensed software first.
How do you stop billing for devices that were replaced?
Remove the old device from the RMM, EDR and backup as part of the refresh, not as a separate tidy-up task weeks later, then update the agreement’s device count in the PSA the same day. The monthly billing reconciliation should then find nothing to correct. Phase 7 does both before the checklist can close, so a replaced laptop never sits in the RMM for months.
Is CheckFlow free for this template?
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.