
Repair, Retain, Replace, or Repurpose? A Hardware Decision Framework
asitplan Strategy Team
Author
Rob Lloyd
Technical Reviewer
06 August 2026
Last Reviewed
IT managers, network administrators, and business leaders
Target Audience
The Context
When an IT device fails or reaches a certain age, IT teams often fall into binary habits: they either repair everything indefinitely (wasting labor hours on obsolete tech) or replace everything automatically (wasting capital on functional tech). Neither approach is financially sustainable.
Who This Guide is For
IT managers, network administrators, and school business leaders.
Why This Matters
Poor hardware lifecycle decisions directly impact the school's bottom line. Spending £150 on labor and parts to repair a 6-year-old laptop that is unsupported by the vendor is a net loss. Conversely, throwing away a 4-year-old laptop that simply needs a new £40 battery is a waste of capital expenditure.
What Good Looks Like
A documented, objective framework (often called the 4Rs: Repair, Retain, Replace, Repurpose) that guides the IT team's decision-making process for every device, removing emotion and guesswork.
Approach and Methodology
- Define the 'Replace' Threshold: Establish clear rules for when a device MUST be replaced. Example: "Any device that can no longer receive vendor security updates, or where the repair cost exceeds 40% of a new equivalent device, must be replaced."
- Define the 'Repair' Rules: When is a repair viable? Example: "In-warranty repairs are always executed. Out-of-warranty repairs are only approved if the device has at least 2 years of vendor support remaining."
- The 'Repurpose' (Cascade) Strategy: Identify high-performance devices (e.g., a 3-year-old Media Studies PC) that are no longer fast enough for their primary role, but are perfectly adequate for a secondary role (e.g., a library catalog terminal).
- The 'Retain' Decision: Sometimes the best action is no action. If a device is out of warranty but still receiving security updates and performing adequately, retain it, but flag it for replacement in the next financial year.
- Standardize the Fleet: The 4R framework is infinitely easier to manage if you only have 3 models of laptops across the school, rather than 15 different models, as you can cannibalize broken units for spare parts.
Evidence to Retain
- A documented Hardware Lifecycle Policy outlining the 4R rules.
- Helpdesk ticket categories that track whether an incident resulted in a repair, replacement, or repurpose.
- An asset register that reflects the new location/user of a repurposed device.
Questions Leadership Should Ask
- "What is our financial threshold for repairing an out-of-warranty device versus buying a new one?"
- "Do we actively cascade 'power user' devices down to lighter roles, or do we just throw them away?"
Common Pitfalls
- The Sunk Cost Fallacy: Continuing to repair a failing device simply because you've already spent money repairing it previously.
- Hoarding: "Repurposing" a device by putting it in a cupboard "just in case," where it sits for three years until it is completely worthless.
- Ignoring the Labor Cost: Factoring in the £30 cost of a replacement screen, but ignoring the £50 cost of the technician's time to fit it.
How asitplan Can Help
asitplan allows you to track the exact age, warranty status, and vendor support lifecycle of every device. By having this data instantly available, IT teams can quickly apply the 4R framework and make financially sound decisions the moment a hardware ticket is raised.