IMAC stands for Install, Move, Add, Change. IMACD adds Decommission. That single letter is the difference between a process that manages equipment while it is useful and a process that also accounts for it when it stops being useful. In practice, the D is where most of the risk sits, and it is the part organisations most often leave out of the contract.
What each letter means
Install. New equipment is delivered, staged, configured to your build standard, physically installed, tested and handed over to a user or a system owner. A proper install ends with an asset record, not with a box being opened.
Move. Existing equipment is relocated, whether that is a desk to desk change, a floor move, an office relocation or a migration between sites. The technical work is usually simple. The planning, sequencing and downtime management are not.
Add. Capability is added to something that already exists: memory, storage, a peripheral, a second screen, a network port, a licence. Small individually, significant in volume.
Change. Configuration is altered without new hardware arriving. Reimaging, reassignment between users, a change of role for a device, a firmware update rolled across an estate.
Decommission. Equipment is retired: removed from service, wiped, removed from the asset register and the licence count, and then reused, resold or recycled. This is the letter that turns an IMAC process into an IMACD one.
Every organisation has an install process. Far fewer have a decommission process, which is precisely why decommission is where the losses accumulate.
Why the D matters more than the other four
Data risk. A retired laptop or server that leaves the building without verified erasure is a data breach waiting to be discovered. Under the EU GDPR, Ghana's Data Protection Act 2012 (Act 843) and Nigeria's Data Protection Act 2023, the obligation does not end when the asset stops being useful to you. Certified data destruction with a per asset certificate is the evidence that it was handled properly. Our certified Green ITAD service exists for this reason.
Financial accuracy. Assets that are physically gone but still on the register distort depreciation, insurance and the licence count. Organisations routinely pay maintenance and software subscriptions on equipment that was thrown away years earlier.
Physical accumulation. Without a decommission route, dead equipment simply occupies space. Store rooms fill with hardware nobody is willing to authorise the disposal of, because nobody is certain what is on it.
Environmental exposure. Informal disposal of electronic waste is a recognised problem across West Africa. An organisation with a public reputation to protect needs a documented chain of custody showing where its equipment actually went.
How an IMACD engagement is normally structured
Most enterprise IMACD arrangements have four moving parts.
- A request channel. Requests arrive through your service desk or ticketing platform, categorised by type, with an approval step for anything that costs money or removes an asset.
- A staging capability. Equipment is configured to the standard build before it goes anywhere near a user. Staging centrally and shipping ready to use is faster and far more consistent than configuring at the desk.
- Field execution. Engineers carry out the work on site, within an agreed window, with the parts and the brief. This is where field engineering and dispatch meets the process.
- Asset reconciliation. Every action updates the asset register. At the end of a period, the register and the physical estate should agree. If they do not, the process is not working, whatever the ticket statistics say.
Where IMACD programmes go wrong
Volume is underestimated. Individual IMAC actions are small, so they are treated as noise. In an estate of a thousand devices, moves and changes alone can run to several hundred actions a year, and they consume real engineering time.
The asset register is treated as an afterthought. If updating the register is a separate manual step performed by someone other than the engineer, it will drift. It should be an output of the work, not a follow up task.
Decommission has no owner. Install has a requester and a budget. Decommission has neither, so it never gets scheduled. Naming an owner and a periodic sweep is the fix.
Sites are attended in ticket order. In a multi site estate, this wastes most of the working day in transit. Batching by location turns three days of driving into one day of work, which matters especially in Lagos and Accra.
Should you buy IMAC or IMACD?
If your equipment never leaves service, IMAC is enough. That describes almost no organisation. If you refresh hardware, close or move offices, or hold data on any device that will eventually be retired, you need the D, whether or not it is in the contract you signed.
The practical test is this: ask who currently authorises the disposal of a failed laptop, what evidence exists that its data was destroyed, and whether it is still on the asset register. If those three questions produce hesitation, the decommission process is missing rather than merely informal.
How Hankaka runs IMACD
We deliver IMACD across seven cities in four countries: Accra and Tema in Ghana, Lagos, Port Harcourt and Abuja in Nigeria, and Lome in Togo and Cotonou in Benin. Equipment is staged and configured before deployment, field work is scheduled by location rather than by ticket order, and every action reconciles against the asset register. Decommissioning runs through our certified disposal process, with per asset data destruction certificates and a reconciled register showing what was collected and what happened to it.
For the wider service, see our IT services, or read how the same discipline applies to ITIL aligned incident management.