Hardware refresh cycle for company phones and tablets: when to replace devices
A hardware refresh cycle is the planned interval at which an organization replaces its devices, set by policy and budget rather than by individual breakdowns. For laptops and desktops, the cycle has traditionally followed performance and warranty terms. For company phones and tablets, the deciding factors differ: the vendor’s security support window, battery health, and repair costs usually end a device’s working life before its processor does.
This guide explains how to set a refresh cycle for mobile fleets, what each major vendor commits to, and how to use device data to replace phones and tablets based on evidence rather than the calendar.
When should IT replace phones and tablets?
Replace a company phone or tablet when the first of these four triggers applies:
- Security support ends. Once the vendor stops shipping security patches, the device carries known, unpatched vulnerabilities. Plan the replacement at least a budget cycle before that date.
- The battery can no longer cover a working day. Many phone batteries are rated to keep about 80 percent of their capacity for a set number of charge cycles. Below that, the battery needs service or replacement.
- Repair costs more than your threshold. Set a policy threshold, such as a share of the new-device price, and replace above it.
- It cannot run what the job needs. When a required app or OS version can no longer install, the device is functionally retired, regardless of its condition.
The calendar still matters, but as a budgeting tool. A fixed cycle tells finance when to expect spend; the triggers tell IT which devices to replace first.
What is a hardware refresh cycle?
A hardware refresh cycle defines when devices leave service and how companies fund and roll out replacements. Organizations use one of three models:
| Model | How it works | Works well for | Watch out for |
|---|---|---|---|
| Fixed calendar | Every device is replaced after a set number of years | Predictable budgets, uniform fleets | Replacing healthy devices early, or keeping unsupported ones because the date has not arrived |
| Condition-based | Devices are replaced when a trigger fires: support end, battery, repair cost | Mixed fleets, cost control | Lumpy spending and surprise peaks without forecasting |
| Hybrid | A calendar sets the budget; triggers decide which devices go first | Most mobile fleets | Needs reliable device data to work |
The hybrid model fits phones and tablets best, because support windows differ widely by vendor and model. Two phones bought on the same day can reach end-of-support years apart.
Vendor support windows set the outer limit
The security support window is the hard ceiling on a device’s service life. Check it before you buy, not when it is about to run out. Vendors publish three separate commitments that often end on different dates: OS upgrades (new major versions), security updates (patches for the installed version, which can continue after the last OS upgrade), and hardware service (repairs and spare parts). Read each one separately: a final OS version or the end of repair service is not the security deadline. Published commitments vary:
| Platform or rule | Published commitment | Source |
|---|---|---|
| Apple iPhone and iPad | Minimum five years of security updates from the first supply date, stated in UK product security (PSTI) compliance statements | iPhone 15 Pro Max statement; iPad model A2926 |
| Google Pixel 8 and later | Seven years of OS and security updates from first US Google Store availability | Google Pixel help |
| Samsung Galaxy Tab Active5 Pro | Security updates until May 31, 2033, on Samsung’s monthly update tier | Samsung product page; Samsung update tiers |
| Zebra ET40-HC and ET45-HC | OS upgrades: Android 14 is the final supported version. Security updates: no published end date for these models; Zebra’s LifeGuard FAQ commits to at least 24 months from a product’s launch on each Android version, so confirm the date with Zebra. Hardware: sold for three years from first sale, with repair service for six | Zebra OS list; Zebra spec sheet; Zebra LifeGuard FAQ |
| Android Enterprise Recommended | For Android 13 and later devices, the maker must publish a security support end date and support at least one major OS upgrade | Android Enterprise requirements |
| EU ecodesign rules | Since June 20, 2025: OS updates for at least five years after the last unit of a model is sold, spare parts for seven years, batteries rated for 800 cycles at 80 percent capacity | European Commission |
| Windows 10 laptops (for comparison) | Support ended October 14, 2025. Paid Extended Security Updates run up to three years, from $61 per device in year one, doubling each year | Microsoft Learn |
Two practical rules follow. First, record each model’s security-update end date at purchase and treat it as the device’s retirement date unless a trigger fires sooner. Second, compare windows when choosing hardware: a cheaper device with a short support window can cost more per year of service. The mobile device procurement checklist covers what to verify before buying, and the business smartphone guide and business tablet guide compare current models.
Battery health is the trigger most fleets hit first
Batteries wear out on charge cycles, not years. Apple rates iPhone 15 and later batteries to keep 80 percent of original capacity at 1,000 complete charge cycles, and iPhone 14 and earlier at 500 cycles, under ideal conditions (Apple). EU ecodesign rules now require phones and tablets placed on the EU market to reach 800 cycles at 80 percent.
The arithmetic matters for planning. A phone that runs one full cycle per working day reaches 500 cycles in about two years. A shared device charged after every shift gets there faster. That is why battery health, not processor speed, retires many frontline devices.
- Phones and tablets with sealed batteries: a battery service is often cheaper than a new device if the model still has years of security support left.
- Rugged devices with swappable batteries: replace the battery pack on its own schedule and keep the device until its support window closes.
- Devices near end of support: skip the battery service and bring the replacement forward.
Repair or replace: setting the threshold
A written threshold stops case-by-case debate at the help desk. Many organizations express it as a share of the replacement price, adjusted by remaining support life:
| Situation | Recommended action |
|---|---|
| More than two years of security support left, repair below threshold | Repair and keep |
| More than two years of support left, repair above threshold | Replace |
| Less than 12 months of support left, any significant repair | Replace and retire the old device |
| Battery below 80 percent, sealed battery, long support window | Battery service |
| Battery below 80 percent, swappable battery | Replace the battery pack |
| Required app or OS version no longer installs | Replace |
Hypothetical example: Replacement costs $600; repair costs $150; three years of security support remain → repair. The same repair with six months of support remaining → replace.
These cut-offs are starting points. Tune them to your device prices, your repair partner’s rates, and the downtime cost of a broken device on the front line. Spare parts are easier to plan for in the EU, where key parts must stay available for seven years after a model leaves the market.
Refresh triggers by device type
| Device type | Usual first trigger | What to track |
|---|---|---|
| Knowledge-worker phones | Battery wear, then end of security support | OS version, patch level, battery health, enrollment date |
| Shared frontline phones and handhelds | Battery wear from multi-shift charging; drop damage | Battery health, repair history, last check-in |
| Rugged tablets and scanners | End of security updates | Security-update end date, final supported OS, battery pack age |
| Kiosk and fixed-mount tablets | App or OS compatibility, since batteries see little use | OS version, app version, uptime |
| Laptops (for comparison) | OS support and hardware requirements, such as Windows 11 eligibility | OS build, hardware model, warranty date |
Rugged fleets deserve separate planning. Their batteries and housings often outlast the vendor’s OS upgrades, so the security-update end date is usually the real retirement date. The guide to rugged device management mistakes covers the operational side.
How MDM data turns refresh into a forecast
A refresh plan is only as good as the device data behind it. Mobile device management (MDM) is where that data already lives:
- Inventory: model, serial number, OS version, and enrollment date for every device, so you can group the fleet by support end date.
- Health signals: battery, storage, and last check-in. The battery data available to MDM varies by platform and OS version, so confirm which fields your devices report before you build a policy on them.
- Patch status: devices that stopped receiving security patches show up as stuck on an old patch level, an early sign that support has ended.
- Reports: a scheduled export by model and support date becomes next year’s refresh budget.
Bento MDM’s device inventory, monitoring, and reporting features record OS version, battery, storage, and app data for each device and can send scheduled reports in PDF or CSV. Automated OS updates keep devices on the latest supported release until their window closes.
“The fleets that overspend on hardware are rarely the ones replacing too often. They are the ones replacing blind. When you can sort every device by support end date and battery health, the refresh budget writes itself.”
Vlad Bodea, Bento MDM
Retiring devices at the end of the cycle
A refresh is not finished until the old device is wiped, removed from management, and disposed of with evidence. NIST published SP 800-88 Rev. 2, Guidelines for Media Sanitization, on September 26, 2025, and it is the usual reference for proving data was removed. The device lifecycle management guide covers sanitization, disposal, and leasing options in full. For iPhones and iPads that move to a new user instead of retiring, Apple Return to Service resets and re-enrolls a device without manual setup, and Windows Autopilot does the same job for Windows laptops.
Frequently asked questions
Replace a phone when its security support ends, its battery can no longer last a working day, or repairs cost more than your threshold, whichever comes first. With current support commitments, that is usually several years for flagship phones and sooner for budget models with shorter windows.
Tablets often last longer than phones because users charge them less often or keep them mounted in place. Use the vendor’s published security-update end date as the outer limit. For example, Samsung lists security updates for the Galaxy Tab Active5 Pro until May 2033.
Quis nostrud exerci
It can work as a budget assumption, but it ignores support windows that now range from short to seven years. A hybrid model, with a budgeting calendar and triggers to decide which devices go first, fits mixed mobile fleets better.
tation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Device lifecycle management covers every stage from planning and procurement to retirement. The hardware refresh cycle is one decision inside it: when a device leaves service and gets replaced.
Replace on evidence, not on habit
A good refresh cycle is quiet. Finance knows next year’s number, help desks follow a written threshold, and no device keeps running past the date its vendor stopped patching it. Record each model’s security-update end date at purchase, track battery health and repair history in your MDM, and review the forecast every quarter.
Related Articles
