IMAC stands for install, move, add and change — the four routine hardware tasks that keep an IT estate current. Install puts new equipment in and proves it works. Move relocates it. Add fits components to kit already in place. Change alters the configuration of a live device. Some providers extend it to IMACD, adding disposal.
The acronym appears in contracts, rate cards and vendor panels without ever being spelled out, which is how buyers end up paying skilled engineering rates for a cable move, or discovering that “change” did not include the thing they needed changed. This article sets out what each letter covers, how the work is scoped, where the boundaries sit against break-fix and project work, and what to confirm before signing.
Throne Solutions is a B2B on-site IT field engineering provider headquartered in Sheffield, UK, supporting businesses in 60+ countries.
Need engineers on site in the UK, Europe or further afield?
Throne Solutions provides on-site IT field engineers across 60+ countries. Tell us your sites and the kind of cover you need, and we will come back with options and a quote.
What IMAC means
IMAC is the standing name for routine hardware work on an installed estate. TechTarget defines the underlying term, moves, adds and changes, as “a set of tasks that IT teams regularly perform to keep computing equipment up to date”, and notes that it is “a general term for any routine or ongoing tasks performed on enterprise IT equipment” (TechTarget).
The same source confirms the two expansions you will see on rate cards: “MAC sometimes is referred to as IMAC (installs, moves, adds and changes)” and, where end-of-life handling is included, “IMACD (installs, moves, adds, changes and disposal)”. In those cases the work usually sits inside “a larger IT asset lifecycle management initiative” rather than standing alone.
The important word is routine. IMAC is planned, repeatable, scheduled work. It is not incident response, and treating it as such is the single most common scoping error in these contracts.
What each letter covers
Install, move, add and change are separate task types with different skill requirements and different durations. Park Place Technologies publishes the clearest operational breakdown, and its wording is worth borrowing when you write your own schedule.
| Task | What it covers | Typical trigger |
|---|---|---|
| Install | “New installation and verification of infrastructure devices into cabinets, racks or enclosures” — Park Place describes the scope as “from shipping box to green light power” | New kit arriving, refresh cycle, new site |
| Move | “Gracefully power down equipment, physical de-install, and move from one cabinet/rack/enclosure to another location” | Office relocation, rack consolidation, floor reorganisation |
| Add | “Addition of components such as drives, memory, or modules to existing devices” | Capacity upgrade, port expansion, storage growth |
| Change | “Access consoles and make configuration changes to existing devices at the customer’s direction” | Firmware, settings, re-cabling, re-addressing |
| De-install (the D in IMACD) | “Equipment de-installation and disposition, including optional data destruction and recycling” | End of life, decommission, lease return |
Source for the quoted scope descriptions: Park Place Technologies IMAC services. TechTarget’s own task list is broader still, covering “adding new devices to the network”, “changing the configuration of existing devices”, “moving equipment from one location to another”, “upgrading hardware or system software” and “consolidating or migrating a data center”.
Note the phrase “at the customer’s direction” against Change. That is the defining limit of the tier: the engineer executes a named instruction on a device you own, under your authority. IMAC is not a mandate to decide what the configuration should be.
Why IMAC work gets outsourced
Because the work is routine but the travel is not. Park Place frames its own offering as “designed to alleviate the high cost incurred by organizations when utilizing expensive IT staff members to perform routine tasks”, and adds a second argument: it “reduces the risk of inadvertent outages by only leveraging seasoned engineers/technicians”.
Both arguments land hardest on a dispersed estate. Fitting memory to a server is a thirty-minute job; sending a salaried engineer four hours each way to do it is not a thirty-minute cost. The economics flip the moment sites are spread across regions or countries, which is why IMAC is almost always bought as a dispatched service rather than staffed in-house.
The third reason is simply volume shape. IMAC demand is lumpy — quiet for weeks, then a refresh lands. Headcount sized for the peak idles; headcount sized for the average misses the peak. A dispatched model absorbs that without either problem.
Where IMAC ends and something else begins
IMAC vs break-fix
IMAC is planned work with a date on it. Hardware break-fix is unplanned work with a clock on it. They are priced differently and dispatched differently, and the response tiers that matter for a failed switch are irrelevant to a scheduled memory upgrade. Buying one out of the other’s allowance is how allowances disappear.
IMAC vs a rollout
Scale and sequencing. A single install at one site is an IMAC ticket. Two hundred installs across forty sites in eight weeks is a project, with a survey, a build standard, a pilot and a schedule — handled as rollouts and migrations rather than as a stack of tickets. The practical test is whether the work needs sequencing. If it does, it is a project.
IMAC vs smart hands
Location. Smart hands and remote hands are colocation products tied to one provider’s building. IMAC travels to your address list — branch offices, retail sites, factory floors, customer premises — and so does data centre support delivered by a field partner rather than by the facility.
IMAC vs asset disposal
The D in IMACD overlaps, but compliance does not come free with a de-install. Secure data destruction and WEEE handling are a separate evidence trail, covered under IT asset disposal. If you need certificates, say so in the schedule — a de-install alone does not produce them.
What to confirm before you sign an IMAC schedule
- The task list, by name. Not “IMAC services” but the specific tasks, with examples. Ambiguity here becomes a change request later.
- Who supplies the parts. An add needs the module in the engineer’s hand. Confirm whether the provider stocks, you ship, or the OEM drop-ships — and who owns the delay when it does not arrive.
- Lead time versus response time. Scheduled work is booked, not dispatched. Ask how much notice a booking needs, not how fast an incident is answered.
- Out-of-hours and weekend cover. Most moves and changes happen outside trading hours. Confirm that the window you need is in scope at every site, not just the main ones.
- Site access and escorts. Inductions, DBS or equivalent checks, badge lead times and escort requirements all sit on the critical path. They are the most common cause of a wasted visit.
- Evidence of completion. Photographs, asset tag updates, serial capture, a signed worksheet. Decide the format before the first visit, because retrofitting an audit trail across an estate is painful.
- What happens when the task is bigger than the ticket. Does the engineer escalate on site, or close the job and rebook? That single clause decides whether a second visit gets billed.
- Geographic reach. Confirm cover at every address, including the awkward ones. A schedule that works in the capital and not in the regions is not a schedule.
Planning cover for a new contract or region?
Send us the countries, sites and service level you need. It takes two minutes, and there is no obligation.
Key takeaways
- IMAC means install, move, add and change — routine, planned hardware work on an estate that already exists. IMACD adds disposal.
- It is scheduled work, not incident response. Keep it out of your break-fix allowance and judge it on lead time rather than response time.
- “Change” means configuration changes made at your direction. The engineer executes your instruction; they do not decide the target state.
- The economics favour outsourcing wherever sites are dispersed, because travel, not task time, is the real cost.
- Parts supply, site access and completion evidence cause more failed visits than the technical work does. Settle all three in the schedule.
Frequently asked questions
What does IMAC stand for in IT?
Install, move, add and change. TechTarget records it as an expansion of the older term moves, adds and changes: “MAC sometimes is referred to as IMAC (installs, moves, adds and changes)”. Where end-of-life handling is included it becomes IMACD, adding disposal.
What is included in IMAC services?
Installing and verifying new devices, powering down and relocating existing ones, fitting components such as drives, memory or modules, and making configuration changes to live devices at the customer’s direction. Park Place Technologies describes the install scope as “from shipping box to green light power”.
Is IMAC the same as break-fix support?
No. IMAC is planned, scheduled work on equipment that is functioning. Break-fix is unplanned repair of equipment that has failed, dispatched against a response target. They are scoped, booked and priced separately, and should not share an allowance.
What is the difference between IMAC and IMACD?
The D is disposal. TechTarget notes the variant “IMACD (installs, moves, adds, changes and disposal)”, typically used where the work forms part of “a larger IT asset lifecycle management initiative”. If you need data destruction certificates or WEEE evidence, specify them — a de-install on its own does not produce them.
Why do companies outsource IMAC work?
Cost and reach. Park Place frames IMAC as a way to “alleviate the high cost incurred by organizations when utilizing expensive IT staff members to perform routine tasks”, and argues it “reduces the risk of inadvertent outages by only leveraging seasoned engineers/technicians”. On a dispersed estate, travel time dominates task time, so dispatching locally is cheaper than sending your own staff.
How is IMAC work priced?
Models vary by provider. Common structures are per task, per visit, per engineer day, or a committed monthly volume with an overage rate. Throne Solutions publishes no rate card, because the right model depends on your site count, geography and task mix — ask for a quote against the real estate.
Does an IMAC visit cover more than one task?
Usually, if you schedule it that way. Batching an add, a change and an asset-tag update into one visit is far cheaper than three separate dispatches to the same address. Ask how your provider counts tasks against a visit before you assume it is free.
Who is responsible for parts on an IMAC job?
Whoever the contract says, which is why it needs saying. The component may be stocked by the provider, shipped by you, or drop-shipped by the OEM. Agree the model and agree who carries the cost of a visit that fails because the part was not there.
IMAC and field engineering from Throne Solutions
Throne Solutions delivers IMAC services as scheduled, dispatched work across a multi-site estate, with site surveys and installations in front of larger pieces of work and hardware maintenance or third-party maintenance behind the estate. Cross-border dispatch runs through global field services, response tiers are agreed under SLA-based IT support, and coverage by territory is set out on Our Presence.
Throne runs offices in the United Kingdom, the United States, Denmark, Canada, Saudi Arabia and Pakistan, so a booking can be raised in your working day rather than someone else’s.
Send your site addresses, the task types you expect and the booking windows you need, and you will get a quote against the real estate rather than a standard rate card.
Email: info@thronesolutions.com
Tell us what you need covered ·
Rollouts and migrations ·
IT consulting and field engineering
