Colour theme
Book a consultation

Planning a business equipment refresh

Turn agreed equipment replacements into a staged rollout. Check dependencies, full deployment costs, staff acceptance and retirement before closing the work.

A laptop and a mechanical typewriter beside each other on a wooden desk.

Replacing several computers, a switch or a shared printer is a small project. The order, configuration and handover can affect people who aren’t receiving new equipment themselves.

Use the computer replacement guide to decide what needs replacing. Then turn those decisions into a rollout with owners, dependencies, acceptance checks and a retirement record. An older device is a reason to review it. There’s no universal replacement date.

Confirm the inventory

For each item, record its serial number, location, user or business purpose, operating system, firmware support and warranty. Include equipment in storage, at home and attached to specialist systems.

The Cyber Centre’s IT asset management guidance describes tracking assets through their lifecycle. Use your inventory to identify what will remain in service, what will move to another role and what will leave the business.

Check the dependencies before ordering. A new computer may need a different dock, a printer may depend on an older driver, and a network change may affect phones or building equipment. Confirm specialist-vendor restrictions and who can sign off on changes.

Set the rollout order

Prioritize confirmed support deadlines, repeated failures and the work affected by an outage. Group similar roles for testing, while allowing for exceptions such as design software or clinic equipment.

Schedule around business deadlines and staff availability. Shared equipment needs a change window and a way to continue essential work. Keep supported spares configured and tested where they can provide that fallback.

Don’t defer urgent security fixes until the refresh date. The Cyber Centre’s patching guidance advises against unsupported software and calls for documented justification and approval if it remains in use. Any temporary exception needs an owner, controls that limit the risk and an exit plan.

Budget for delivery

Include hardware, accessories, licences, configuration, installation, data transfer, staff handover and retirement in the estimate. Check warranty service and replacement lead times for the exact model being purchased.

If you’re comparing purchase and lease offers, record the total contractual cost, term, return conditions, damage obligations and end-of-term options. Confirm how business data will be removed before leased equipment is returned. A lower first payment can still cost more over the term.

Use the hardware-offer checklist to confirm configuration and support terms. Avoid ordering a whole batch before a representative unit has passed the required workload tests.

Pilot the complete setup

Prepare the test device with the updates, security settings, device management and applications staff will get. Test with a representative staff member using their normal permissions.

Check sign-in, MFA, shared files, calls, printing and specialist tools. Include accessibility settings and peripherals the person relies on. Confirm that required files are available and that the backup or recovery route works. An install can finish without errors and still leave the employee unable to do the job.

Record failures and adjust the setup before the next batch. Agree on a fallback and rollback decision with the owner of any shared system. Keep the old equipment secured until the transition is finished.

Close out each batch

Have staff confirm the agreed tasks work, and assign unresolved issues to someone who can finish them. Update the register with the new device, support dates, user and next review date.

Follow the device-retirement guide for required records, sanitization and disposal. Keep a handover or disposal record for the outgoing asset; don’t leave a cupboard of untracked devices as the last step of the project.

After the rollout, review what it cost and which support issues came up. Put the next planned batch into the IT roadmap with the dependencies and staff time you learned from this one.


Featured Image Credit