Most failed onsite visits are not caused by the engineer. They are caused by the field engineer work order: missing access details, a vague scope, the wrong part, or no one to call when the engineer reaches the comms room. Each of those turns a one-visit job into two, and the second visit is usually at your cost.
We already publish a field engineer work order template. This article takes a different angle: the mistakes we see most often in work orders from service providers and MSPs, and how to brief an engineer so the job gets done first time.
Mistake 1: Describing the problem, not the task
“User reports slow network” is a ticket, not a work order. The engineer needs to know what to do: replace switch port module, test link to desk 4.12, swap patch lead, confirm with remote team. If the task genuinely is diagnostic, say so, and say what the engineer is allowed to change.
Fix: write the scope as numbered steps with a clear end point, and state what is out of scope.
Mistake 2: Incomplete access details
Engineers lose more time at reception than anywhere else. A site in Canary Wharf, a colocation hall in Frankfurt or a mall in Riyadh may each need advance registration, photo ID, inductions or escorts.
Fix: include the full site address, the named contact with an email address and a backup contact, access hours, any pre-registration done, parking or loading arrangements and the exact room or rack location.
Mistake 3: Parts that do not match the job
The wrong part, a part that has not arrived, or a part sent to the wrong address all lead to revisits. So do missing rails, cables or optics that “everyone assumed” would be on site.
Fix: list every part with part number and quantity, the courier tracking reference and where it will be delivered. Confirm delivery before the engineer travels, and state who returns the faulty part and how.
Mistake 4: No remote support lined up
Many jobs need someone remote to configure a port, push a profile or confirm the device is online. If that person is in a meeting, the engineer waits, and the clock runs.
Fix: name the remote contact for the visit window, include how to reach them, and add a fallback. Our guide to onsite IT escalation paths covers this in more detail.
Mistake 5: Unclear sign-off and evidence
If the work order does not say what “done” looks like, the engineer will decide. That rarely matches what your end customer expects.
Fix: specify the evidence you need: photos before and after, serial numbers in and out, test results, and who signs on site. Use the same evidence standard on every job so reports are comparable.
Mistake 6: Missing skills or tools requirements
A fibre termination, a server firmware update and a ceiling-mounted access point install need different skills and tools. If the work order does not state them, you may get the wrong engineer.
Fix: state the required skills, certifications if any are essential, and special tools such as fibre test kits, laptops with console cables or ladders over a certain height.
Mistake 7: Too much information in the wrong place
The opposite problem is a work order that pastes in a long ticket history, email threads and three versions of the scope. The engineer reads it on a phone in a corridor.
Fix: put the essentials at the top: site, time, contact, task, parts, sign-off. Attach the history separately for reference.
Briefing engineers across countries, from Manchester to Dubai
When jobs run across the UK, Europe and the Middle East, consistency matters more than length. A few practical habits help:
- Use one format everywhere. An engineer in Manchester and one in Dubai should receive the same structure, so your dispatch team can check them quickly.
- Write in plain English. Avoid internal project codes and acronyms without explanation.
- Allow for local time and rules. State visit times in the site’s local time zone and flag local requirements, such as weekend working days in Riyadh and Dubai.
- Send it early. Give the engineer the work order the day before, so questions surface before travel rather than at the door.
- Close the loop. After each failed or extended visit, ask what was missing from the work order and update your template.
A pre-dispatch check that takes two minutes
- Can the engineer get into the building and to the equipment?
- Is the task written as steps with a clear end point?
- Are the parts confirmed on site or with the engineer?
- Is a remote contact available for the full visit window?
- Is the required evidence listed?
If any answer is no, fix it before dispatch. It is cheaper than a revisit.
At Simplify Networks our London service desk checks every incoming work order against these points before booking an engineer, and comes back to you with questions rather than sending someone to guess. See how we handle dispatch and SLAs, our IMAC and break-fix service, our coverage and how we support field service partners.
Where we deliver
We take work orders for engineers in the UK, Germany, the UAE, Saudi Arabia, the USA and Canada, among many other countries.
Frequently asked questions
What should a field engineer work order include?
At minimum: site address and access details, a named contact, the visit window in local time, the task as numbered steps, parts with tracking, remote support contact, skills and tools required, and the sign-off evidence needed.
Why do onsite IT visits fail first time?
The most common reasons are access problems, missing or wrong parts, a vague scope and no remote support available during the visit. Almost all of these can be fixed in the work order before dispatch.
How far in advance should a work order be sent?
Ideally the day before for planned work, so the engineer can raise questions before travelling. For urgent break-fix, send the essentials first and follow up with detail.
Do you have a work order template we can use?
Yes. Our field engineer work order template sets out the fields we recommend, and this article explains the common mistakes to avoid when filling it in.
Want fewer revisits?
Send us a sample work order and we will show you how our service desk would brief engineers for your jobs, UK and worldwide.