Last updated
Most failed field visits are not caused by bad technicians. They are caused by work orders that leave out something the technician needed: the suite number, the name of the person who can unlock the closet, where the replacement switch was delivered, or what "done" is supposed to look like. Every one of those gaps costs a return visit, an unhappy site, and a week of schedule.
A work order is a set of instructions for someone who has never been to the site and cannot ask you questions once the window starts. Write it for that reader. The sections below are the ones we look for when a work order arrives, and the questions we ask when they are missing.
1. Site details that get the technician through the door
The address alone is rarely enough. Include everything needed to arrive at the right door at the right time and be let in.
- Full address with suite, floor, store number, or building name
- Site contact name and phone number, plus a backup contact
- Business hours, and whether the site will be open during the visit
- Access instructions: parking, loading dock, badge desk, escort requirements, or key holder
- Site rules the technician must follow, such as dress code, PPE, photo restrictions, or quiet hours
If the site has to be told the technician is coming, say who is responsible for telling them. A visit announced by nobody often ends at a locked door.
2. A schedule window that matches the work
State the arrival window, not just a date, and an honest estimate of how long the work takes. If the job must happen after hours, before opening, or inside a change window, say so and say why. Technicians plan travel and other commitments around the window, and a two-hour job written as a thirty-minute job will run into the next appointment.
3. Scope written as steps
Paragraphs of background are useful, but the scope itself should be a numbered list of tasks in the order they happen. Each step should be something a technician can do and confirm.
- Check in with the site contact and the help desk.
- Locate the delivered equipment and confirm it against the packing list.
- Photograph the existing equipment and the network closet.
- Remove the old device and label it for return.
- Install and connect the new device to the port map provided.
- Run the test steps with the help desk and record the result.
- Photograph the finished work, obtain a signature, and check out.
Then say what complete means. "Device installed and online, confirmed by the help desk, with photos and a signed work order" is a definition of done. "Install the device" is not. It is just as useful to state what the technician must not do, such as changing configurations, moving other equipment, or opening a ceiling without approval.
4. Equipment, materials, and who supplies what
List every item that has been shipped, with tracking numbers and where it will be at the site. Say who supplies consumables such as patch cords, mounting hardware, anchors, labels, and cable. If old equipment must be returned, include the return method, labels, and the address.
A surprising number of return visits happen because a part arrived but nobody on site knew where it was put. Name the person who received it, or ask the site to hold it in a specific place.
5. Tools and skills required
Name the tools that are not obvious: a cable certifier at a specific test level, a lift above a certain ceiling height, a console cable for a specific device, or a laptop with particular software. If the job requires a certification or license, say so. This lets the dispatcher match the right technician instead of finding out on site.
6. Deliverables and closeout requirements
Tell the technician exactly what you need back. Vague requests such as "send photos" produce whatever photos were convenient. Specific requests produce what you can actually use.
- Required photos, for example: closet before and after, each device with its label visible, and the serial number plate
- Test results and the format you need them in
- Serial numbers or asset tags for installed and removed equipment
- Who signs the work order, and what happens if that person is not available
- The deadline for the closeout package
Our guide on closeout documentation covers what a complete package should contain.
7. Check-in, check-out, and communication
Describe the check-in procedure step by step: who the technician calls or messages on arrival, whether a help desk ticket must be referenced, and how to check out. Include any mid-visit updates you expect, such as a photo when the old equipment is removed.
8. Escalation and out-of-scope work
Something will eventually not match the plan: the wrong part, a blocked cable path, or a site that is closed. Give a named escalation contact who can make decisions during the window, with a phone number that will be answered. Then explain how out-of-scope work is approved. Technicians should never have to choose between leaving a job unfinished and doing unapproved work.
Common mistakes to avoid
- Copying the previous site's work order without updating the address, contacts, or equipment
- Leaving the escalation contact as a general mailbox that nobody monitors during the window
- Assuming the site knows the visit is happening
- Asking for test results without saying what test or what format
- Listing equipment as "shipped" without tracking or a delivery location
A short checklist before you send it
- Could someone who has never seen this site find the right door and get in?
- Is the scope a list of steps with a clear definition of done?
- Is every shipped item listed with its location?
- Are the deliverables specific enough to check?
- Will the escalation contact answer during the window?
When we receive a work order, we review it against these questions before dispatch and come back to you with anything missing. That is the cheapest point to find a gap, and it is the single biggest factor in completing work on the first visit.