IMAC Work Orders With Defined Scope

Quick answer

What is IMAC Work Orders With Completion Criteria?

An IMAC work order is a single written instruction to install, move, add, change, or dispose of one IT asset or a small group of assets, with a defined scope and testable completion criteria. Deploris dispatches a vetted field engineer against that order and returns a closed ticket with test results, sign-off, and evidence.

WHAT THE WORK COVERS

What IMAC Work Orders With Completion Criteria includes.

01Scope statement per ticket: task type, asset serial or asset tag, exact location (building, floor, desk or rack unit), and the agreed access window

02Completion criteria written as testable conditions, for example link up on the correct VLAN, user logged in, and every peripheral detected

03Complexity tiering so a monitor swap and a rack install are scoped and priced as different kinds of work

04Pre-stage requirements listed on the order: imaging, BIOS settings, cables, mounting hardware, and consumables

05A defined escalation path for blocked tasks such as missing access, wrong part, locked device, or a network port that is not live

06Closure data captured on every order: time on site, parts used, test results, photos, and the name of the signing contact

HOW WE DELIVER IT

How it is delivered.

1
Intake and validation
The request arrives through your ticket tool or a shared mailbox. Your engagement manager checks the asset, location, access rights, and completion criteria, and resolves gaps before any engineer is dispatched.
2
Scheduling and preparation
A vetted engineer is assigned in the covered metro. Equipment, cables, and configuration items are staged, and the site contact confirms the window and who will sign off.
3
Execution to procedure
The engineer carries out the task as written, records exceptions as they occur, and raises blockers to the engagement manager immediately instead of improvising outside the scope.
4
Verification and closure
Each completion criterion is tested and recorded, the site contact signs, and the order is closed with photos, parts used, and any open items listed for follow-up.

INPUTS AND OUTPUTS

What you provide and what you receive.

You provide

The request details: asset identifiers, source and destination location, and the task type
Site access instructions and a named on-site contact who can sign
Hardware, software, and licenses needed, or approval for Deploris to source them
Target configuration standards such as image name, naming convention, and VLAN or port mapping

You receive

A closed work order with timestamps, engineer name, and the completion criteria marked pass or fail
Completion evidence attached to the ticket: test results, sign-off, and photos where agreed
An exception list stating what blocked any task and who owns the next action
Status updates written back to your ticket tool or shared mailbox as agreed in the written scope

WHEN IT FITS

When this is the right deliverable.

Scenario 01

Your service desk needs a second monitor and a docking station installed for a new hire on Friday, and wants proof of completion on the same ticket.

Scenario 02

A facilities team is rearranging one department and needs each desk move defined by asset, destination, and acceptance test rather than a vague request.

Scenario 03

An IT manager is replacing a decommissioned branch printer and needs the install, driver deployment, and test page documented as one auditable order.

WHERE WE DELIVER

Delivered in 75+ metros across 11 countries.

Local, vetted engineers deliver this work on site across the United States and Western Europe, coordinated by one engagement manager.

United States Germany Austria Switzerland France Italy Spain Netherlands United Kingdom Ireland Portugal

View full coverage

QUESTIONS

Frequently asked questions.

What should an IMAC work order include?

An IMAC work order should include the task type, asset identifiers, exact location, access window, site contact, required configuration, and testable completion criteria. Without all of these, the engineer cannot prove the job is done. Deploris validates every field at intake and holds dispatch until the gaps are closed.

How are IMAC work orders priced?

IMAC work is typically priced per task by complexity tier, or on a retainer when volumes are predictable. Pricing depends on scope, location, and timing, and is set out in the written scope before work starts. Pricing is engagement-based, with no lock-in contract.

What happens if the engineer cannot complete an IMAC task on site?

The engineer stops, records the blocker with photos, and tells your engagement manager at once. Common blockers are missing access, a wrong part, a locked device, or a network port that is not live. The order stays open with a clear owner and a rebooking plan instead of being closed as done.

Can we raise IMAC work orders through our own ticketing system?

Usually yes. Orders can typically be raised through your existing ticket tool or a shared mailbox, and status is written back the same way. The exact route, fields, and update frequency depend on your environment and are agreed in the written scope before the first order is dispatched.

MORE DELIVERABLES

More from IMAC & Projects.

02

IMAC Asset Register and CMDB Updates

Keep your asset register and CMDB accurate after every install, move, add, change or disposal, with serials, locations and status captured at the device.

Learn more

03