When should a business replace a computer?

Age is a review trigger, not the whole decision

Replace a computer when keeping it creates an unacceptable support, reliability, compatibility or productivity problem relative to a suitable replacement. Some older devices remain adequate for modest tasks; some newer purchases are unsuitable from day one. Use a consistent review process so replacement is neither an annual shopping exercise nor a crisis response after every failure.

Start with the role and the consequence of interruption. A shared spare might cover an office administrator while a specialist workstation needs a different continuity plan. Do not assume a device can stay in service merely because it starts. Supported software, secure configuration and recoverable information matter as well as visible performance.

Check support and compatibility first

Review operating-system support, application support, firmware availability and hardware requirements. Consult current vendor guidance for the exact device and software. Microsoft's Windows 11 requirements are an example of why a machine's hardware and supported operating-system path should be checked rather than guessed.

Avoid unsupported bypasses as an ordinary business lifecycle strategy. Ask the IT provider to explain the options and risk if the existing hardware cannot run a supported required system. A replacement may be justified even when the old device is fast enough for documents. Conversely, a supported upgrade can sometimes extend useful life without a full hardware purchase.

Measure the actual problem

Record failures, repair bills, lost working time, battery condition, storage capacity and user complaints. Distinguish hardware limitations from slow internet, a misconfigured application or insufficient training. Replacing the laptop will not necessarily fix a poor cloud connection or a broken workflow.

Use representative tasks to assess performance: opening the working file, joining a meeting, searching records or compiling a project. Note the duration and frequency of delays. A computer that is ten seconds slower once a day creates a different business case from one that crashes during every customer call. Where an inexpensive supported repair is proposed, include its warranty and expected remaining service life.

Compare keep, repair and replace

Calculate the purchase and setup cost of replacement against repair, expected support effort and the consequences of failure. Avoid claiming a precise future failure probability without evidence. Use scenarios instead: no major failure, one repair and a substantial interruption. A spare device can reduce the downside without immediately replacing every machine.

For example, an illustrative A$1,800 replacement plus A$250 setup can be compared with a A$400 repair and uncertain later work. If the repaired machine meets the role and remains supported, keeping it may be economical. If it still cannot run the required application, the repair does not solve the problem. These figures are assumptions excluding GST, not current market quotes.

Plan a staggered fleet budget

Use an asset register to see purchase dates, support status and role criticality. Spread planned replacements where practical, allowing for common standards and bulk setup efficiencies. Keep an allowance for unexpected failures rather than using the entire budget on cosmetic improvements. Replacing devices in batches also requires care to avoid every warranty expiring together.

Set a review date for each device instead of an automatic disposal date. Reassign a still-supported machine to a lighter role only after checking suitability and wiping or configuring it appropriately. A hand-me-down that creates more support work can be a false saving. Document changes in assigned user and location so accountability is maintained.

Keep a practical decision record

Keep a decision note for machines retained after review: current role, supported software, known limitations, repair history and the next trigger for reassessment. This avoids treating a postponed replacement as a forgotten issue. If a device is moved into spare stock, prepare it so it can actually be deployed, with supported software and a documented setup path. A cupboard full of untested machines is not a reliable continuity plan. Review the spare alongside the active fleet, because batteries, updates and recovery arrangements still age while equipment is unused.

Retire devices carefully

Confirm the required records are backed up and usable before erasing the old device. Follow current vendor instructions and the business's data-handling requirements. Apple publishes model-dependent erase guidance; other systems need their appropriate supported process. Obtain specialist advice for sensitive storage or devices that cannot be securely prepared through ordinary methods.

Remove business management and recovery links as appropriate, record disposal or resale and use suitable recycling channels. Use the IT budget planner to include replacement and setup allowances, then update the asset register. The objective is dependable supported tools at a sensible lifetime cost, with replacement decided before avoidable disruption forces a rushed purchase.