Skip to content

1 de noviembre de 2026 • Centoffer Editorial • 18 min de lectura

IMAC Services Explained: Managing Install, Move, Add and Change Requests at Scale

IMAC Services Explained: Managing Install, Move, Add and Change Requests at Scale

IMAC Services Explained: Managing Install, Move, Add and Change Requests at Scale

Ask most IT operations leaders where their field budget goes and they will point at outages: the failed switch, the dead point-of-sale terminal, the laptop that will not boot. Yet a large share of on-site IT work is not emergency work at all. It is the steady flow of new starters who need a desk set up, teams that move floors, printers that need adding, and docking stations that need changing. That flow has a name — IMAC services, short for Install, Move, Add and Change — and at one office it is a minor nuisance. Across fifty or five hundred sites, it becomes one of the hardest things in IT operations to run well.

The difficulty is not technical. Plugging in a monitor is easy. The difficulty is consistency: making sure that the same request is scoped the same way, priced the same way, delivered by someone with the right skills, completed on the first visit, and recorded properly in every location you operate. This guide explains what IMAC services include, how they differ from break-fix and project work, how to build a request catalogue, what an IMAC service level agreement should measure, and how to prove that every job was actually done.

What are IMAC services?

IMAC services are the planned, repeatable field tasks that keep end-user and site IT aligned with how a business is changing: installing new equipment, moving existing equipment, adding devices or capacity, and changing configurations. Unlike incident work, IMAC is requested in advance and can be scheduled, which makes it ideal for standardisation.

Centoffer’s own IMAC glossary entry describes it as the high-volume deployment tasks of IT operations, each typically closed with proof of delivery on-site. That last clause matters more than it first appears, and we will come back to it.

In practice, IMAC work covers end-user devices (laptops, desktops, monitors, docks, phones, headsets), shared devices (printers, meeting-room equipment, kiosks, label printers, scanners), and light site infrastructure (patching, access points, small switches, cabling moves). Some organisations put server and core network changes under the same heading; most mature operations keep those under a separate, more tightly controlled change process.

Many contracts now use the extended acronym IMACD, where D stands for Dispose or Decommission: the final step in which retired equipment is removed, wiped, written off and recycled. Treating disposal as part of the same service closes the loop on the asset lifecycle rather than leaving old devices to pile up in a storeroom.

Why does IMAC get harder as you add sites?

IMAC gets harder with scale because variation multiplies: every additional site, country and supplier introduces its own way of scoping, scheduling, pricing and recording the same request. The individual tasks stay simple; the coordination cost grows.

Consider a single request type, “set up a new starter’s desk.” At headquarters, the internal team knows the standard build, has spare docks in the cupboard, and updates the asset register out of habit. At a regional branch served by a local contractor, the same request may arrive as an email, be quoted by the hour, be completed without a dock because nobody shipped one, and never reach the asset register at all. Multiply that by dozens of request types and hundreds of locations and three predictable problems emerge:

  • Cost becomes opaque. When each site prices the same task differently, nobody can tell whether a branch is expensive because the work is harder or because the scope was never defined.
  • First-visit completion drops. Engineers arrive without the right parts, access or information, so a fifteen-minute job becomes two visits and a week’s delay for the user.
  • Records decay. Every move that is not recorded makes the next move harder, because the next engineer is sent to the wrong desk to collect the wrong serial number.

The fix is not to hire more coordinators. It is to make the request itself carry everything the engineer needs, and to make closure impossible without the evidence and the record update.

What counts as an install, a move, an add and a change?

An install puts new equipment into service; a move relocates existing equipment or users; an add extends what is already there; a change alters the configuration of something that stays in place. The boundaries are worth writing down, because ambiguous categories are where scope disputes start.

TypeWhat it meansTypical examplesCommon hidden scope
InstallNew equipment placed into service for a user or siteNew-starter desk build, new printer, meeting-room display, branch kioskUnboxing and packaging removal, cable management, user orientation
MoveExisting equipment or a user relocatedDesk-to-desk move, floor move, office relocation, device transfer between sitesData and peripheral reconnection, re-labelling, network port patching
AddExtra capacity or a peripheral added to an existing setupSecond monitor, docking station, extra access point, additional network dropPower and port availability, mounting hardware
ChangeConfiguration altered on equipment that stays putRe-patching, firmware update on site, printer queue change, hardware component swapPre- and post-change testing, rollback if it fails
Dispose (IMACD)Equipment retired and removedCollection of old laptops, decommissioning a branch printerData sanitisation, certificate of destruction, asset write-off

Two practical rules help. First, classify by what happens to the asset, not by who asked. A “move” requested by facilities and a “move” requested by HR are the same job. Second, if one request mixes types — for example, a desk move that also adds a monitor — log it as one ticket with two line items, so that each component is scoped, priced and evidenced separately.

How is IMAC different from break-fix and project work?

IMAC differs from break-fix because it is planned rather than reactive, and from project work because each request is small, repeatable and independent. Each of the three needs a different commercial and service model, and mixing them is one of the most common causes of poor IMAC performance.

DimensionBreak-fixIMACProject / rollout
TriggerSomething has failedA business change (starter, move, new kit)A programme decision (refresh, new site, migration)
TimingUnplanned; clock starts at loggingPlanned; booked into a windowPlanned in waves over weeks or months
Volume per requestOne incidentOne to a few tasksHundreds or thousands of tasks
Main SLA measureResponse and restoration timeOn-time arrival and first-visit completionMilestones, wave completion, defect rate
Best pricing modelPer incident or retainerFixed price per catalogue itemFixed price per unit plus project management
ApprovalIncident processPre-approved standard changeProgramme governance and change board

The practical consequence: do not let IMAC tickets sit in the same queue and SLA as incidents. If a desk move is measured against a four-hour response clock, either it will be rushed and done badly, or the vendor will routinely breach a target that never made sense. Equally, do not run a thousand-device refresh as a thousand separate IMAC tickets; that is a project and needs wave planning. (We cover that case in our companion guide on end-user device deployment and deskside laptop refreshes.)

How do you turn IMAC requests into standard changes?

You turn IMAC requests into standard changes by defining each common request type once — its scope, risk, steps, skills, parts and evidence — and pre-approving it so that individual requests can be scheduled without further review. This is the single biggest lever for running IMAC at scale.

The idea comes from ITIL, the widely used IT service management framework maintained by AXELOS/PeopleCert. ITIL distinguishes “standard changes” — low-risk, well-understood, pre-authorised changes that follow a known procedure — from normal changes that need assessment and authorisation each time, and emergency changes that must be implemented quickly. Most IMAC tasks fit the standard-change pattern exactly: a desk install done for the five-hundredth time carries little new risk, so it should not wait for a weekly change advisory board.

To convert a request type into a standard change, write a one-page template that answers:

  1. Scope. What is included and, just as importantly, what is not (for example, “includes connecting up to two monitors and one dock; excludes wall mounting”).
  2. Preconditions. What must be true before the engineer is dispatched: equipment on site, user account created, network port live, access arranged.
  3. Steps. The procedure in order, including any configuration or test.
  4. Skills profile. The minimum competence required, so the job can be matched to a suitably qualified engineer rather than whoever is nearest.
  5. Duration estimate. A realistic on-site time, which drives scheduling and the fixed price.
  6. Evidence required. The proof-of-delivery items that must be captured before closure.
  7. Escalation trigger. The conditions under which the job stops being standard — for instance, finding that the work would affect a whole floor’s network — and must go to the normal change process.

Review the templates periodically. If a standard IMAC type regularly needs a second visit or regularly breaches its duration estimate, the template is wrong, not the engineers.

What should an IMAC service catalogue and request form contain?

An IMAC service catalogue should list every pre-scoped request type with its price, lead time and inclusions, and the request form should collect everything an engineer needs to complete the job on the first visit. If information is missing at the point of request, it will be missing at the desk.

A good catalogue entry is short and unambiguous. A typical starter catalogue for an office estate might include: new-starter desk build; leaver desk recovery; single-user desk move; team move (priced per user); additional monitor; docking station add or swap; printer install; printer move; meeting-room display install; network port patch; access point install; device collection for disposal.

The request form for each entry should require, not merely allow:

  • Site, floor, room and desk identifier, ideally from a maintained location list rather than free text.
  • End user name and contact, plus an alternative site contact for access.
  • Requested date and acceptable appointment windows, with the catalogue lead time enforced.
  • Equipment details: what is being installed or moved, with serial numbers or asset tags where known, and where the equipment will be on the day.
  • Access requirements: building passes, escort needs, permitted working hours, loading-bay booking for larger moves.
  • Dependencies: account creation, port activation, or software licensing that must be done beforehand.
  • Approver, where your policy requires budget or line-manager approval.

The form is where IMAC programmes are won or lost. Each extra required field feels like friction to the requester, but each missing field costs an engineer visit.

How should an IMAC SLA be written?

An IMAC SLA should measure what a planned job promises: that the engineer arrives in the booked window, completes the job on the first visit, and leaves accurate evidence and records — not how fast someone responds to an emergency. Response-time clauses borrowed from break-fix contracts are the wrong tool. (For the wider principles of measurable, penalty-backed SLAs, see our guide to IT SLA management across many sites in India.)

MetricDefinitionWhy it mattersHow to verify
Lead-time complianceShare of catalogue requests scheduled within the published lead timeTells you whether capacity matches demandRequest and booking timestamps
On-time arrivalShare of visits where check-in falls inside the booked windowUsers and sites plan around the appointmentGeo-stamped check-in
First-visit completionShare of jobs completed without a return visitThe best single indicator of preparation qualityTicket history and visit count
Evidence completenessShare of closed jobs with every required POD itemWithout evidence, nothing else can be auditedPOD audit sample
Record accuracyShare of sampled assets whose register entry matches realityBad records make every future job harderPeriodic physical spot checks
User satisfactionPost-visit rating from the end user or site contactCaptures professionalism and communicationShort survey on closure

Set targets per metric rather than relying on one blended score, and attach consequences to the ones that matter most to you. For most organisations, first-visit completion and record accuracy are worth more than shaving a day off lead time. Also be explicit about who owns a failure: if a visit fails because the equipment was not delivered to site or the user’s account did not exist, that is a precondition failure on the client side and should not count against the provider — which is exactly why the request form must capture those preconditions.

What should close an IMAC ticket? Proof of delivery and the asset record

An IMAC ticket should close only when proof of delivery (POD) has been captured and the asset record has been updated in the same step. POD — a verifiable record that the work was done, by whom, where and when — turns a vendor’s claim into evidence. (See the POD glossary entry for the definition we use.)

A practical POD checklist for IMAC work:

  • Engineer identity and verified check-in and check-out times at the correct location.
  • Serial numbers or asset tags of every device installed, moved or removed.
  • Photos of the finished installation where layout matters (desk, rack, meeting room, access point).
  • The functional test performed and its result — for example, “user logged in, both displays active, dock charging, test print successful.”
  • Sign-off from the end user or site contact, or a recorded reason when sign-off was not possible.
  • Notes on anything left outstanding, which should automatically raise a follow-up rather than disappear.

The asset record is the half that is most often skipped. Each IMAC event changes at least one of four facts about a device: who has it, where it is, what state it is in, and what it is connected to. If the engineer’s closure step writes those changes back to the asset register — or produces a structured file that does — then the register stays accurate as a by-product of normal work. If it does not, the organisation will eventually fund a separate, expensive audit to rebuild the data, and the decay starts again the following week.

What about the “D” in IMACD — disposal and data sanitisation?

Disposal is the IMAC step with the highest data risk, so it should follow a documented sanitisation standard and produce a per-device certificate, rather than ending with a box of old laptops in a storeroom. Adding D to IMAC simply makes this step part of the same governed service.

The most widely referenced standard is the US National Institute of Standards and Technology’s Guidelines for Media Sanitization. NIST published SP 800-88 Revision 2 on 26 September 2025; it is intended to help organisations build a media sanitisation programme and select appropriate techniques for making data on storage media inaccessible at a level of effort suited to the sensitivity of the information. Your own legal and regulatory requirements may specify other standards, but having a named reference in the contract is far better than “the vendor will wipe the drive.”

For field IMAC, the disposal flow usually looks like this: the engineer collects the device against a ticket, records the serial number and the condition, seals it for transport or sanitises it on site where policy requires, and hands it to a disposal partner who returns a per-serial sanitisation and recycling record. The asset is then written off in the register. If any device cannot be accounted for at any step, that is a security incident, not an administrative gap.

Not every retired device should be destroyed. Redeployment is often the better outcome for machines with remaining life. For Windows estates, Microsoft notes that Windows Autopilot can also be used to reset, repurpose and recover devices, including quickly preparing an existing device for a new user — which turns a “leaver recovery plus new-starter install” pair into a cheaper reuse cycle.

How much do IMAC services cost? Comparing pricing models

IMAC cost depends far more on the pricing model and scope definition than on the hourly rate, because poorly scoped work generates repeat visits and disputes. There is no meaningful global “average price per IMAC,” since tasks range from a five-minute peripheral swap to a half-day team move; what you can control is how the work is priced.

Pricing modelHow it worksBest forWatch out for
Fixed price per catalogue itemEach request type has a published price with defined inclusionsRecurring, well-defined requests across many sitesNeeds a clear catalogue and an agreed process for out-of-scope extras
Bundled blockA set number of IMAC units per month or quarter, drawn down per requestPredictable volumes; budgeting simplicityUnused units expiring; disagreement on unit values per task
Per-seat subscriptionA monthly fee per user covering a defined IMAC allowanceStable headcount with steady churnOverage terms during a reorganisation or office move
Time and materialsHourly labour plus travel and partsGenuinely unusual work outside the catalogueRewards slow work; impossible to compare across sites

Whatever model you choose, define the commercial treatment of three edge cases in advance: aborted visits (who pays when the site was not ready), return visits (who pays when the first visit failed), and travel to remote sites (included, banded or charged at cost). These three items cause most IMAC billing disputes.

Worked example: standardising IMAC across a 40-site office network

The following is an illustrative scenario we have constructed to show the method, not a client case study.

A regional services firm runs 40 offices across several countries. Each country manager has historically arranged IT field work locally, so the same new-starter setup is handled by an internal technician in two countries, by different local contractors in the rest, and by the headquarters team for head office. Head office sees three symptoms: invoices for “IT support, 3 hours” with no detail; new starters waiting days for docking stations; and an asset register that nobody trusts.

The firm takes five steps:

  1. Catalogue. It defines twelve IMAC request types, each with a one-page standard-change template, a lead time and a skills profile.
  2. Single intake. All requests go through one service-desk form with mandatory fields, regardless of country.
  3. Fixed prices. Each catalogue item is priced per country, so differences in labour cost are visible and explainable rather than hidden in hours.
  4. POD and records. Closure requires the POD checklist and writes serial, user, location and status back to the asset register.
  5. Monthly review. Every month, the firm reviews first-visit completion by site and by request type, and rewrites any template that keeps failing.

The results the firm would look for are not a headline percentage but a set of observable changes: invoices that map line by line to catalogue items, a falling count of return visits, and an asset register that passes physical spot checks. Those are the signals that IMAC has moved from a collection of local habits to a managed service.

What are the most common IMAC failure modes?

Most IMAC failures trace back to missing preconditions, vague scope or skipped closure steps, not to engineer skill. The fixes are procedural and cheap compared with the cost of repeat visits.

  • Equipment not on site. The engineer arrives; the laptop is still in a courier depot. Fix: make equipment location a required field and confirm delivery before dispatch.
  • Accounts or ports not ready. The desk is built but the user cannot log in or the port is dead. Fix: list dependencies in the standard-change template and check them the day before.
  • Wrong skills. A cabling change is sent to a desktop technician. Fix: attach a skills profile to each request type and dispatch against it.
  • Scope creep on the day. “While you are here, could you…” turns a 30-minute job into an afternoon. Fix: capture extras as new line items with their own approval, rather than absorbing them silently.
  • Closure without evidence. The ticket closes on a phone call. Fix: make POD items mandatory in the closure workflow.
  • Records never updated. The register drifts until an audit is commissioned. Fix: write record changes as part of closure, not as a separate admin task.

Who should deliver IMAC: in-house, a single vendor, or a platform?

In-house teams deliver IMAC best where volume is concentrated in a few large sites; a single outsourced vendor suits a compact regional footprint; and a field services platform suits organisations with many dispersed sites across several countries that need one catalogue, one SLA and one evidence standard.

In-house technicians know the environment and the people, which is valuable at head office. But keeping full-time staff at every branch for intermittent IMAC demand is rarely economical, and travelling from head office to remote sites is slow. A single regional vendor can work well if its coverage genuinely matches your footprint; the risk is that “coverage” outside its home market means subcontracting, which reintroduces the inconsistency you were trying to remove.

A platform model, such as Centoffer’s global IT field services, approaches the problem differently: the catalogue, SLA and proof-of-delivery standard are set once, and vetted local engineers are dispatched against them in each location, with every job tracked and evidenced the same way. That consistency — the same request scoped, delivered and recorded identically everywhere — is what IMAC at scale actually requires.

The bottom line

IMAC services are unglamorous, but they shape how employees experience IT every week: the first day at a new desk, the office move, the extra monitor that finally arrives. Running them well across many sites does not depend on heroic engineers. It depends on a clear catalogue of standard changes, a request form that captures every precondition, an SLA that measures planned work properly, and a closure step that insists on proof of delivery and an accurate asset record.

If you are consolidating install, move, add and change work across multiple sites or countries, start by writing down your top ten request types as standard-change templates — then talk to Centoffer about delivering them under one SLA with proof of delivery on every job. Contact our team to discuss your IMAC catalogue and footprint.