Device refresh cycles: planning, funding, and secure disposal

Reference article · 5 min read

Every agency replaces computers. Fewer replace them on a plan. Without one, replacement becomes a reaction: a department escalates, a machine fails during a busy season, or a vendor ends support for an operating system and forces a purchase nobody budgeted.

A refresh program answers three questions before that pressure arrives. Which devices get replaced on what interval, where the money comes from each year, and what happens to the equipment coming out of service. Keeping those answers written down, funded, and current through staff turnover is the harder part.

Set the cadence by device role

A single interval for the whole fleet is easy to write and hard to defend. A desktop in a climate controlled office and a ruggedized tablet in a patrol vehicle do not wear at the same rate. Group devices by role and set an interval for each.

Stationary office machines. Light duty in a controlled environment, and usually the longest interval in the fleet.
Standard laptops. Carried and dropped, and batteries often need replacement partway through the life of the machine.
Field, vehicle, and public safety devices. Vibration, temperature swings, and constant power cycling shorten life. Plan the shortest interval here and keep a spares pool.
Shared and public access machines. Lobby, library, and training room devices see heavy but low stakes use. Cadence follows the software they run.
Specialized workstations. GIS, video, dispatch, and design machines get replaced when the application's requirements move, not on a calendar.

Cascading old machines to another department spreads support cost across two budgets and keeps unsupported devices in service.

Fund it so the cost repeats instead of spiking

The goal is a level annual cost. Agencies often combine mechanisms.

A replacement reserve or internal service fund. Departments pay an annual amount per device into a fund that buys the replacements. Durable, provided the contribution is part of the budget process and the balance is protected from sweeps in lean years.
Leasing or device as a service. Level payments with refresh built into the term. Predictability costs something, and the end of term provisions matter as much as the monthly figure.
A level capital schedule. Divide the fleet into cohorts so a similar number of devices comes due each year, rather than all at once.
Chargeback to departments. Ties cost to the program that owns the device and makes growth visible. It requires an accurate inventory.
Grants. One time funding can buy a wave of devices but rarely sustains a cycle, and federally funded equipment carries disposition conditions. Treat it as a supplement, not the basis for the cadence.

Settle accounting treatment with your finance office early. Most endpoints fall below the capital asset threshold, while leases and subscription arrangements follow governmental accounting standards that have changed in recent years.

Track the dates that force replacement

Hardware failure is rarely what ends a device's useful life. Support deadlines are. Carry these fields in the asset record.

In service date and the interval assigned to that role.
Warranty end and extended support end, and whether service is on site or depot.
Vendor end of service life: the last date parts, drivers, and firmware updates are available.
Operating system support end for that model. Hardware often stops qualifying for new operating system versions before the version it runs goes out of support.
Security update window for phones and tablets, published per model.
Lease end and return deadline, where applicable.

A device that runs fine but no longer receives security updates is a compliance problem, not only a performance problem. Frameworks covering criminal justice, health, cardholder, and tax data generally expect supported, patchable systems, so unsupported endpoints surface in audits and insurance applications.

Each year, before the budget is built, list every device whose earliest support date falls inside the next two budget years. That list is the draft replacement plan.

Put the policy in writing

A short policy prevents the annual argument. Name the device classes and their intervals, the standard configurations the agency buys, who approves an early or deferred replacement, the funding source, who maintains the inventory of record, and who retires equipment.

What to ask vendors and what to require in the contract

What is the published end of service life for this model, and how long will parts, drivers, and firmware updates be available?
Which operating system versions are supported on this model, and for mobile devices, how long will it receive security updates?
What does the warranty cover: response time, on site or depot service, shipping, battery, and accidental damage.
Can we keep failed drives rather than returning them, so media never leaves our control?
For a lease: total cost across the term, return condition standards, charges for missing or damaged units, and end of term options.

In the contract, hold pricing for a defined period, allow added units at that pricing, require an asset report at delivery with serial numbers matched to locations or users, state trade in credit terms, and rule out automatic renewal without written notice.

Retire on the schedule you set

The program only works if devices actually leave. Set a firm return deadline when a replacement is deployed, and budget for the exit: sanitization labor, recycling fees, and logistics arrive with every wave.

Nothing leaves until the data is gone, following your media sanitization policy. Then close the record: retire the asset, reclaim the licenses, and remove the device from endpoint management, patching, backup, monitoring, and network access. Federally funded equipment may carry added disposition requirements, so check the award terms.

HQT is a technology and software company working in enterprise IT and technology advisory services for state and local government agencies.

Frequently asked questions

How often should a local government replace computers?

There is no single correct interval, and a good policy sets several. Office desktops in a controlled environment tolerate the longest cycle, laptops a shorter one, and rugged field or vehicle devices the shortest. The constraint that usually decides the date is vendor and operating system support rather than failure, so check the support end dates published for the models you buy before fixing an interval.

How do agencies fund a replacement cycle without a budget spike?

The common approaches are a replacement reserve or internal service fund charged annually per device, leasing with refresh built into the term, and a level capital schedule that divides the fleet into cohorts so a similar number comes due each year. What they share is a recurring annual cost rather than a large appropriation every few years. Grant money can buy a wave of devices but rarely sustains a cycle, so it is better used as a supplement.

Is leasing computers better than buying for a public agency?

Leasing gives predictable payments and a built-in refresh, which helps agencies that cannot hold or protect a reserve fund. Buying is often cheaper in total when the agency can fund a reserve and manage retirement reliably. Compare total cost across the full term, read the return condition standards and damage charges closely, and confirm with your finance office how leases and subscription arrangements are reported under current governmental accounting standards.

What should a device refresh policy include?

Name the device classes and the interval for each, the standard configurations the agency buys, who approves an early or deferred replacement, the funding source and how rates are set, who maintains the inventory of record, and who is responsible for retiring equipment and on what timeline. Keep it short enough that staff will actually read it, and adopt it at whatever level your agency uses for administrative policy.

Can we keep using a computer after its operating system loses support?

An unsupported operating system stops receiving security updates, which generally conflicts with security requirements attached to criminal justice, health, cardholder, and tax data, and it can raise questions during audits and cyber insurance underwriting. If a device cannot be replaced immediately, document the risk, limit what the device can reach on the network, and set a dated remediation plan. Requirements vary by program and change over time, so confirm the specifics with the governing authority or your counsel.