How we work
Scope, Plan, Deliver, Report.
Field work goes wrong when the plan lives in someone's head. The site rules are unknown, the scope is vague, or nobody can prove what was done. Our process exists to remove those gaps before an engineer reaches the door.
Last reviewed October 27, 2026.
Quick answer
How does an engagement work?
Deploris runs every IT field services job in four phases: Scope, Plan, Deliver and Report. We agree the work in writing first. One engagement manager then plans access and logistics, local engineers do the work, and you receive photos, test results and a closeout report. The same process applies to a single visit or a multi-city rollout.
The four phases below group the steps used across our service pages: audit and design, logistics and prep, onsite execution, test and certify, and handover and report. A small job moves through them quickly. A large rollout spends more time in Scope and Plan. The order never changes.
FOUR STEPS
The four phases.
PHASE 01
Scope
We agree what will be done, where, and what is out of bounds, in writing.
What happens
- Your engagement manager gathers requirements by call, walkthrough or video survey of each site.
- We list the sites, devices, racks or users involved and the tasks expected at each.
- We record what is out of scope, including any do-not-touch devices.
- We confirm who can request and approve work, and who to call when something goes wrong.
- We capture site rules such as visitor registration, escort requirements, freight lift bookings and photo policy.
What you receive
- A written scope that names tasks, sites, exclusions and dependencies
- A list of authorized requesters and escalation contacts
- A quote based on that scope, with the pricing structure explained
PHASE 02
Plan
We turn the scope into a schedule, a staffing plan and a clear brief for each engineer.
What happens
- We match local engineers to the work and the site, and register their names with each building or facility.
- We book access windows, loading docks and freight lifts, and handle certificate of insurance requests where a building asks for them.
- We plan equipment, spares and pre-staging so parts are on hand before the visit.
- We write a project-specific brief for each engineer covering the task list, tools, site rules and who to contact.
- Where the risk justifies it, we run a rehearsal or test request before the real work starts.
What you receive
- A schedule with dates, access windows and named engineers per site
- An access plan listing each site's entry rules
- A plan for equipment, spares and any pre-staging
PHASE 03
Deliver
Local engineers carry out the approved scope, capture evidence and test the result.
What happens
- The engineer arrives with the brief, confirms identity and authorization, and follows the site's rules.
- The work follows the written scope. Anything outside it goes back to the authorized requester first.
- The engineer photographs the before and after state of what was touched, including labels and indicators.
- Tests are run and recorded, for example link tests, cable certification, signal checks or device boot checks.
- The engineer posts status updates to your ticket or to the agreed contact as the job progresses.
What you receive
- Status updates during the job in your ticketing tool or the channel you choose
- Photos of the work, with labels legible
- Test results for the work that was tested
PHASE 04
Report
We close the job with a report you can file, audit or hand to your own customer.
What happens
- The engineer records what was done, what was found and any deviation from the plan.
- Photos, test results, parts used and asset details are collected in one place.
- Open items and follow-up recommendations are listed, not left implied.
- Your team confirms the result from its own tools before the request is closed.
- Your engagement manager reviews the job with you and updates the scope if something should change next time.
What you receive
- A closeout report with photos, test results and asset records
- Work notes in your ticket history
- A list of open items and recommendations
HOW WE DECIDE
Principles behind every job.
Written scope first
No work starts until the scope is written down and agreed. It states the tasks, the sites, the exclusions and the dependencies. Changes are agreed in writing before they are done.
One engagement manager
You have one named person who owns scheduling, escalation and reporting, even when several engineers in several cities are involved.
Access and authorization agreed before the day
Engineers are registered with each site in advance. You name who can request and approve work. Out-of-hours entry is tested before it is needed, not during the first incident.
Evidence for every job
Photos, test results and work notes are part of the job, not an extra. Your remote team can verify the result without traveling to the site.
Your tools and your rules
We work inside your ticketing tool, your runbooks and your data handling policy where you have them. Decisions about your systems stay with your team.
Local engineers, one standard
The engineer is local to the site. The process, the brief and the report format are the same in every city.
QUESTIONS
Common questions.
How does an IT field services engagement work from start to finish?
Who will I talk to during an engagement?
What happens if the work changes after the scope is agreed?
How do I know the work was done correctly?
Can you work in our ticketing system and follow our runbooks?
Get started
Need engineers on site? Tell us where.
Tell us the sites, the scope and the timeline. We reply with a written plan.