IT Staffing & Engineer Dispatch · Case study
Nationwide Equipment Refresh Across Five US Metros With On-Demand Dispatch.
A scenario showing how a project field team and on-demand dispatch can cover a five-metro hardware refresh.
Representative scenario. Last reviewed October 2026.
Engagement profile
- Customer
- Distributed professional services firm with regional offices in eight US metros
- Scale
- 28 sites, about 1,400 endpoints, five listed metros
- Where
- United States
Representative scenario. This case study shows how Deploris scopes and delivers this kind of work. It does not describe a real client, and no results are claimed. Want a plan like this for your own sites? Request a quote.
Quick answer
What does this engagement look like?
A nationwide equipment refresh staffed through Deploris involves a project team of vetted local field engineers installing, imaging, and retiring hardware across several US metros, with on-demand dispatch kept available for exceptions. Deploris scopes the work in writing, assigns one engagement manager, matches engineers by metro and skill, and gives the customer a closeout report with photos, test results, and asset reconciliation per site.
THE CHALLENGE
The challenge.
The customer's laptops, docking stations, and branch network switches had reached the end of their lifecycle at roughly the same time, and the refresh had to touch every regional office in a single program. The internal IT team was small and centralized, with no staff in most of the metros. Sending the same two or three people around the country would have stretched the program across many months, while hiring a separate local contractor in each metro would have produced five different ways of doing the same job.
The program also could not be treated as a one-time rollout. Even after the refresh waves were complete, new hires, failed docks, and returned devices would keep generating small tasks in every metro. The customer wanted one staffing model that could carry a planned project team through the refresh and then step down to a lighter on-demand arrangement, without renegotiating a new contract or re-explaining the environment to a new vendor.
Constraints the plan had to respect
- Most offices were occupied floors in multi-tenant buildings, so freight elevator reservations, loading dock windows, and certificate of insurance requirements set the calendar before any engineer's availability did.
- Staff devices could only be swapped outside core hours at several offices, which meant evening and early morning shifts with reduced building services and no on-site IT contact.
- Old laptops held company data, so every retired device needed an unbroken custody trail from desk to certified recycler, with no engineer expected to wipe or decide disposal on the spot.
- Metros span three time zones, and working-time rules on overtime and breaks vary by state, so shift lengths and start times had to be set in the written scope, not improvised on the day.
- The customer wanted engagement-based pricing with no lock-in, so the team size had to be adjustable between waves instead of fixed for the whole program.
HOW THE WORK RUNS
How the work is run.
- 1
Scope the program from a site manifest
The engagement manager started from the customer's asset export: one row per device with serial number, asset tag, user, desk location, and model. From it Deploris built a site manifest listing device counts, floor and suite, building management contact, and access rules for each office. A short pre-visit survey form, completed by a local engineer or the office manager, captured freight elevator booking lead time, dock hours, whether carts are allowed, and Wi-Fi or port availability for imaging. The written scope fixed a per-site task list, shift windows, and the rule for when a site counts as ready to start.
- 2
Size the project team and the on-demand bench separately
Deploris split the demand into two lanes. The project lane was a planned team of local engineers per metro, sized by endpoints per site and the number of shift windows the buildings allowed, with a team lead named for the busiest metros. The on-demand lane was a bench of pre-vetted engineers in each covered metro, held for the exceptions a planned wave always produces, such as a no-show device, a failed dock, or a user who was out on the scheduled day. Both lanes drew from the same vetted, background-checked pool, so the customer saw one standard of work.
- 3
Prepare the buildings, the kits, and the engineers
Before any shift, the engagement manager obtained certificates of insurance that meet each building manager's requirements, submitted engineer names for badge or visitor registration, and booked freight elevators and dock slots. Devices were imaged and enrolled in the customer's MDM tool, such as Intune or Jamf, at a staging location, then packed in labeled kits per user with the asset tag on the box and a tracking number in the manifest. Each engineer received a visit brief covering building rules, escalation contacts, the swap checklist, and photo requirements, and acknowledged it before the first shift.
- 4
Run waves with a daily dispatch rhythm
Work ran in waves of one to three sites per metro. On each shift the engineer scanned the incoming kit, confirmed user sign-in and data sync with the customer's remote support team, swapped the device and dock, tested network, display, and printing, then packed the old device into a sealed, tagged return container. Arrival, progress, and exceptions were reported against the customer's ticket reference in the ITSM tool, such as ServiceNow or Jira Service Management. Exceptions went to the on-demand lane, with the 4-hour response target for priority dispatch applying in covered metros during business hours. Because Houston and Seattle sit in different time zones, the engagement manager held one handover note per day instead of per metro.
- 5
Close out by site and step down to on-demand
Each site closed with a structured report: photos of the work area and any cabling changes, test results per device, the asset reconciliation showing which serials were installed and which were collected, and the custody receipt for the recycler hand-off. Open items, such as a spare dock or a device still in transit, were listed with an owner. Once the final wave closed, the engagement moved from the project team to on-demand dispatch under the same engagement manager, with the customer's building access details, site briefs, and preferred engineers already on file for each metro.
WHAT WAS PRODUCED
What the engagement delivers.
Each item links to a full guide with its scope, process and FAQs.
WHAT THE CUSTOMER ENDS UP WITH
What the customer ends up with.
- 01A written scope per site, covering task list, shift windows, access rules, and the definition of ready, agreed before any engineer traveled or badged in.
- 02A reconciled asset record showing, device by device, what was installed, what was collected, and where each retired unit went, built from the customer's own serial numbers.
- 03A closeout report for every site with photos, test results, and open items assigned to named owners, stored in a format the customer's audit and finance teams can reuse.
- 04A reusable set of site briefs and building access notes for each metro, so later dispatch requests start from known conditions instead of a blank page.
- 05A staffing model that moves from a planned project team to on-demand dispatch under one engagement manager, with no lock-in contract to unwind.
WHAT APPLIES TO YOUR PROJECT
Decisions that apply to similar projects.
Treat building access as a scheduling constraint, not an admin task. In New York and Chicago office towers, a missing certificate of insurance or an unbooked freight elevator can cancel a shift, so access paperwork should be requested during scoping, with names submitted well before the first visit.
Separate the planned team from the on-demand bench. A project team is sized to a manifest and moves in waves, while exceptions arrive at random and need engineers who are free to go. Mixing the two means exceptions either wait for the wave or pull project engineers off their shifts.
Stage and label devices before the engineer arrives. Imaging in a controlled location and shipping kits with asset tags matched to the manifest turns the on-site visit into a swap and test, and makes it much easier to reconcile serial numbers afterward, especially in hotter metros like Houston and Phoenix where equipment should not sit in a vehicle.
WHERE IT APPLIES
Metros in this scenario.
Local engineers in each metro, coordinated by one engagement manager. Open a metro to see local details.
QUESTIONS
Frequently asked questions.
How many field engineers does a multi-city equipment refresh need?
Can one provider cover project work and on-demand dispatch under the same engagement?
How are retired laptops handled during a field refresh?
More case studies
Other scenarios we have planned.
QUOTE
Plan a project like this.
Share a few details and we will come back with the next steps.
Get started
Need engineers on site? Tell us where.
Tell us the sites, the scope and the timeline. We reply with a written plan.