What Does IMACD Mean in IT Asset Management?
Every server, laptop, and network switch moves through a series of changes during its working life, and IMACD gives those changes a standard name.
IMACD stands for Install, Move, Add, Change, Dispose. It organizes asset lifecycle work into a governed workflow, so records stay accurate. IMACD also groups all five request types under one process with clear owners in IT Asset Management and IT Service Management. This approach enables real-time visibility across asset operations and helps streamline related business processes.
Each letter covers one action:
- Install: bring new equipment or software into service.
- Move: relocate assets between offices, racks, or data centers.
- Add: expand an asset with components or capacity.
- Change: modify configurations, settings, or upgrades.
- Dispose: retire assets securely, often through recycling.
Documenting each step keeps your inventory aligned with physical reality. Without a defined workflow, these activities are handled inconsistently across siloed teams, and skipped steps leave out-of-sync records that produce an inventory nobody trusts.
How Does the IMACD Process Work Step by Step?
How does an IMACD request move from a simple ticket to a verified asset record? The process follows five steps.
- Intake: The service desk captures the action, user or device, location, justification, and target date, then classifies the request as install, move, add, change, or dispose. IMACD requests commonly arise from new hires and terminations that affect IT assets. Integrated ITSM systems enable real-time data sharing to reduce manual entry and errors, improving workflow efficiency with API-driven connectivity.
- Review: Approvers check completeness, policy fit, and impact. Incomplete requests return for clarification.
- Planning: Teams schedule work and confirm resources, such as compatibility for a laptop upgrade.
- Execution: The technician works within the approved scope, and you verify completion.
- Closure: The asset record updates, and the ticket closes. In one large US city program, automated ServiceNow workflows kept the asset database at 97% accuracy across roughly 40,000 managed IT assets.
What Causes Most IMACD Request Problems?
Most IMACD request problems come from five causes: unclear scope, slow approvals, limited resources, logistics failures, and site access issues. Each cause delays work in a specific way.
- Unclear scope: missing purpose, location, or timing causes rework and scheduling errors.
- Slow approvals: delayed sign-off pushes completion past the agreed timeline.
- Limited resources: engineer shortages and short booking notice cause missed milestones.
- Logistics and access: late parts, missing hardware, badge lead times, and power problems block visits.
Teams reduce risk by confirming details, approvals, parts, and access before scheduling. Early checks prevent wasted visits, stalled requests, and missed SLA targets. When the same kind of delay keeps recurring, teams can log it as a problem record linked to the triggering incidents, so the underlying cause is analysed and removed through a change. Organizations that adopt ITSM best practices often see measurable reductions in recurring incidents and improved process efficiency.
How Do You Fix a Stalled or Incorrect IMACD Request?
Where does a stalled or incorrect IMACD request go wrong? Start by finding the break point. Then fix it in order.
Most stalled IMACD requests fail at one identifiable point. Find that break point first, then fix each issue in sequence.
- Recheck the request for missing requester, asset, location, or start date, and return it for clarification.
- Confirm the correct owner, manager, or CAB approved the work.
- Compare the date against lead-time rules and confirm technician, site access, and hardware are ready.
- Inspect the queue assignment and reassign misrouted tasks.
Before closing, verify:
- The work is completed and tested.
- The asset record shows the new location, user, or disposal status.
- Data wipe evidence exists for disposals.
Inform the requester. For ticket handling, align the lifecycle to ITIL by ticket logging, categorisation, and resolution tracking so each request stays visible until it is finished. Remember that IMACD is planned work, so it runs on a lead time rather than an incident response clock, and it should never be logged as an incident. Standardized processes will help maintain consistency and improve service quality.
Why Do Incomplete IMACD Closures Create Audit Risk?
Incomplete IMACD closures create audit risk because a closed ticket does not prove that the required control happened.
Auditors treat missing evidence as a control failure, not a documentation gap. Tickets track work but do not govern access, so a closed ticket cannot show that approval and provisioning were treated as one event at the exact specified level. Organizations that consolidate data from multiple sources can better detect these gaps by improving data integration across systems.
Four gaps matter most:
- Missing approval proof breaks traceability from request to execution.
- Absent provisioning or deprovisioning evidence leaves former users or contractors with lingering access.
- Outdated asset location, assignment, or status data creates inventory errors.
- Disposal without sanitization evidence leaves data-bearing devices untracked.
Each gap lets a ticket show “closed” while work remains incomplete. An IMAC ticket is not finished until proof of delivery is captured and the asset record, including serial, user, location, and status, is updated.
Frameworks such as SOC 2 and ISO 27001 expect demonstrable governance, not closed tickets.


