Refresh policy by role
| Role band | Device type | Refresh cycle | Rationale | Devices in band |
|---|---|---|---|---|
| Engineering | High-spec laptop | 3 years | Build performance; heavy workload | 28 |
| General staff | Standard laptop | 4 years | Balance of cost and reliability | 96 |
Hardware refresh gets deferred because the cost is visible and the consequence is not. Showing the support-ticket cost of ageing devices alongside the replacement cost turns deferral into a decision rather than a default.
Set refresh policy by role, not uniformly. Engineering workstations and reception kiosks do not need the same cycle. Define bands by role so the budget reflects actual need rather than an averaged assumption.
Measure the ticket cost of old devices. Pull ticket volume by device age. The difference between a two-year-old and a five-year-old fleet is usually substantial, and it is the number that justifies the budget line.
Smooth the replacement curve. If a large cohort was bought at once, it will all expire at once. Deliberately stagger replacements across years to avoid a capital spike that gets refused.
Here's a preview. Unlock the free download to get all 4 sections (3 more below).
| Role band | Device type | Refresh cycle | Rationale | Devices in band |
|---|---|---|---|---|
| Engineering | High-spec laptop | 3 years | Build performance; heavy workload | 28 |
| General staff | Standard laptop | 4 years | Balance of cost and reliability | 96 |
More free templates IT teams use alongside this one.
Most asset registers die of one disease: nothing in the organisation forces them to be updated. This one is built around the three events that actually change an asset's state (assignment, repair, and disposal), so the register is maintained by the work rather than by an annual audit.
Most provisioning delay is not procurement, it is the three days spent asking the hiring manager for information that should have arrived with the request. Standard bundles by role remove most of the questions entirely.
An IT budget presented as a list of line items invites line-by-line cuts. Split into run, grow, and transform, it becomes a conversation about what the business is choosing to fund, which is a far better conversation to be in.
Three years for high-demand roles such as engineering, four for general staff, and up to five for light-use devices and servers aligned to support contracts. Setting one cycle across the whole estate either overspends or underserves.
By measuring support cost against device age. Ticket volume per device typically rises sharply beyond three or four years, and expressing that as an annual cost per device makes the comparison with replacement cost direct.
Support cost rises, devices fall out of warranty and then out of OS support, and the deferred cohort eventually needs replacing all at once. Recording deferrals explicitly keeps that accumulating liability visible.