Short answer
Treat computers as a planned service. Match each device to the work, keep a record of its identity and condition, maintain it, review upgrade options, and decide early whether to repair, redeploy, replace or retire it. Four years is a review rhythm, not an automatic expiry date.
An office computer rarely fails at a convenient time. It stops during payroll, a client presentation, a month-end close or a field report that has not yet been backed up.
The response is usually an urgent purchase: whatever is available, at whatever price, with little time to check whether it suits the work. That is a poor way to manage an important business asset.
A small organisation in Kampala can run a simple four-year device plan for desktops, laptops and shared machines. The plan is not a promise that every computer will last exactly four years. It is a rhythm for making decisions before a failure makes them for you.
Start with the work, not the price
Before comparing models, write down what each device must do. A receptionist working in a browser and an accounting officer running large workbooks do not need the same specification. A designer, developer or analyst may need more memory, faster storage or a better display. A shared machine in a reception area may need a different balance of durability, security and ease of reset.
Record the real workload for each role:
- the applications used every week;
- the number and size of documents handled;
- whether the user works mostly online or needs local files;
- whether the device travels between offices or stays at a desk;
- which peripherals are essential, such as a printer, scanner, projector or external display; and
- what the organisation expects to add during the next two years.
The 2026 edition of Building Your Own PC Complete Manual makes the same planning point for a build: decide what the computer is for before selecting components, then check that the parts work together. For an office purchase, the equivalent is a written workload and compatibility check. Confirm memory, storage, ports, operating-system support, charger or power-supply requirements, and the availability of replacement parts with the supplier. Component specifications change; do not reuse an old shopping list without checking it against today’s workload and the supplier’s current stock.
The cheapest device becomes expensive when staff wait for it, replace it early, or cannot find a compatible charger, battery, memory module or storage drive. Price is one input. Suitability, supportability and the cost of interruption matter as well.
Keep a record that survives staff changes
An asset register does not need to be a complicated IT-management platform. A shared, access-controlled spreadsheet is enough to begin if somebody owns it and updates it.
For every computer, record:
- asset tag and serial number;
- device type and make/model;
- processor, memory and storage as supplied;
- assigned user, department and physical location;
- purchase date, supplier, invoice reference and warranty end date;
- operating-system version and important licences;
- condition at the last review;
- repairs, upgrades and parts replaced;
- backup responsibility and last restore test; and
- the current decision: in service, under repair, ready for redeployment, or retired.
Keep a photograph of the serial-number label where practical. Store the invoice and warranty terms with the record. When a staff member leaves, the device should be easy to identify, secure, inspect and reassign; it should not depend on that person’s memory.
Year 1: commission it properly
The first year is when you establish a baseline. Before handing over a device, install approved updates, encryption and security controls, name the device consistently, and confirm that the user can access the applications and shared services required for the role. Record the initial condition, battery health for laptops, charger condition, and available storage.
Test the backup arrangement before the device becomes part of a critical process. A laptop synchronised to a cloud service is not automatically a complete backup, and a desktop with files on its local drive is not protected merely because it is in an office. Decide which data is backed up, who checks it, where a second copy is held, and when a sample restore will be tested. The test matters: a backup that cannot be restored is an assumption, not an operating control.
Power deserves a place in the commissioning checklist. Use a suitable surge-protection or UPS arrangement for the device and its essential peripherals, and label the correct charger or power supply. A UPS can provide continuity for a short period and help with orderly shutdown; it does not replace backups and it does not correct every power-quality problem. Match the equipment to the office’s electrical setup and have a qualified person investigate unsafe wiring or repeated power faults.
Year 2: maintain the baseline
Routine maintenance is mostly unglamorous, which is why it is often skipped. Keep operating-system and application updates on a managed schedule. Remove accounts and software that are no longer needed. Check that endpoint protection, disk encryption and screen-lock policies still work. Ask users to report unusual heat, fan noise, repeated crashes, swollen batteries, damaged chargers and intermittent ports before the problem becomes a failure.
Kampala offices also need a sensible dust and heat routine. Keep air vents clear, do not push a desktop hard against a wall, and do not use a laptop on a surface that blocks its intake. At an agreed interval, inspect and clean equipment safely according to the manufacturer’s guidance. A technician should handle internal cleaning or component work where opening the case could cause damage or affect the warranty. The manual’s cooling guidance is practical here: airflow, a suitable cooler and clean internal paths help a computer manage heat; cable clutter and blocked vents make that harder.

For laptops, review battery health rather than waiting for a calendar date. A shorter runtime may be an inconvenience; swelling, excessive heat or physical damage is a safety issue and requires prompt isolation and qualified assessment. Do not keep a damaged battery in service because the laptop is still usable on mains power.
Year 3: upgrade only where the numbers support it
An upgrade should answer a specific work problem. “The computer feels old” is not enough. Identify whether the constraint is memory pressure, slow storage, lack of free space, a failing battery, insufficient ports, poor cooling or an application that now requires a different platform.
Desktops often offer more repair and upgrade options than thin laptops, but do not assume that an upgrade will fit. Check the motherboard, available slots, storage interface, power supply, cooling, operating system and warranty. The PC manual’s storage guidance is a useful reminder: even a seemingly straightforward SSD change depends on the computer’s supported interface, physical mounting and available power or data connections. Back up first, record the change, and use a competent technician when the work involves internal components or sensitive business data.
For laptops, the sensible upgrade may be a battery, charger, dock or external storage rather than a new internal component. If the only viable repair is a costly proprietary part with no dependable supplier, that is evidence for replacement or redeployment, not a reason to keep spending.
Year 4: decide before the emergency
At the fourth-year review, classify each device as repair, redeploy, replace or retire.
Repair when the fault is understood, the part is available, the repair is safe, and the resulting device can still meet the user’s workload. Redeploy when the computer remains reliable for a lighter role: a previous accounts workstation may be suitable for reception, training or a controlled shared task after secure reconfiguration. Replace when performance, reliability, compatibility or support no longer matches the work, or when the repair cost and delay are disproportionate. Retire when the device is unsafe, unrepairable, unsupported for the organisation’s required software, or cannot be securely wiped and transferred.
Retirement is a process, not a trip to the rubbish pile. Confirm the data has been backed up or transferred, remove the device from user accounts and management tools, record the disposal decision, and use a secure data-erasure or destruction process appropriate to the storage media. Keep the asset record and disposal evidence. If a device is donated or sold, treat it as a data-protection decision as well as an environmental one.
The one-page annual review
Once a year, an office manager can complete this review with the asset register and a short conversation with each user.
Annual device review
Device: ____________________ User/location: ____________________ Reviewer/date: ____________________
- Identity: serial number, asset tag, model and assigned user match the register. Yes / No
- Workload: the device still runs the user’s required applications and documents without unacceptable delay. Yes / No
- Condition: screen, keyboard, ports, charger, casing, fans and battery show no unresolved damage or warning signs. Yes / No
- Updates: operating system, applications and security controls are current under the organisation’s normal update process. Yes / No / Escalate
- Heat and dust: vents are clear, the device has safe airflow, and cleaning or technician inspection is recorded where needed. Yes / No
- Power: the correct charger or power supply is labelled; surge protection or UPS arrangements are known; repeated power faults are logged. Yes / No
- Data: important files have a named backup owner, and the last restore test date is recorded. Yes / No
- Support: warranty status and a realistic source for parts, chargers or batteries are known. Yes / No
- Decision: keep / maintain / upgrade / repair / redeploy / replace / retire.
- Action owner and date: ____________________
Do this review before the annual budget is finalised. It turns a surprise purchase into a visible pipeline of maintenance, upgrades and replacements. It also gives management a better question than “Which computer is cheapest?”: “Which device will reliably do this job, for how long, and what will we do when it no longer should?”
This is practical guidance, not a substitute for the manufacturer’s instructions, a qualified technician’s assessment or your organisation’s data-protection policy. For current purchases, check current component specifications, operating-system requirements, warranty terms and supplier availability rather than relying on this article or an older specification sheet.
Frequently asked questions
Should every office computer be replaced after four years?
No. Four years is a review point, not an automatic expiry date. A reliable device that still meets its workload, has supportable parts and passes its security and data checks can remain in service. The review exists so that replacement is planned when the evidence says it is needed.
What should a small organisation record for each device?
Record the asset tag, serial number, model, specifications, user, location, purchase and warranty details, condition, repairs, upgrades, backup owner, last restore test and current decision. Keep the invoice and warranty terms with the record where possible.
Is a UPS enough to protect our computers and data?
No. A suitable UPS may provide short continuity and allow an orderly shutdown, but it does not replace backups or solve every power-quality issue. Combine appropriate power protection with tested backups and a clear shutdown procedure.
When is an upgrade better than buying a new computer?
Upgrade when you can name the constraint, confirm compatibility, obtain the part reliably and keep the resulting device fit for its role. If the component is proprietary, unavailable or nearly as costly as a suitable replacement, replacement or redeployment may be the better decision.
Sources & the researchers worth crediting
Primary working reference: Building Your Own PC Complete Manual - 15th Edition, 2026, used for its planning, compatibility, power, cooling, maintenance and upgrade principles. This article applies those principles to office asset management; it does not reproduce the manual’s build instructions. Current component specifications, software requirements, warranty terms and supplier availability must be checked before purchase.
Read next
The Security Basics Every Growing Business Ignores Until It’s Too Late
Build the practical controls that protect devices, accounts, payments and backups.
Why Your Business Must Go Digital Today
Connect device decisions to the systems and records your organisation actually uses.
Review your office technology plan
Start a conversation about a manageable, documented IT operating plan.
About the author
Peter Bamuhigire
Software architect and ICT consultant — business management systems across Africa
Peter Bamuhigire helps owners and managers turn technology decisions into workable operating systems. His approach connects practical infrastructure choices with the people, data, controls and processes that keep a small organisation moving.

