For technicians

On-site professionalism: what gets you called back

By the Techwhere editorial team Last updated 7 min read

In short

Dispatch coordinators reuse the technicians who make their day easier. That means answering quickly, arriving inside the window, checking in and out in the app every time, photographing the work, and writing closing notes a stranger could act on. Consistency over months, not heroics on one ticket, is what moves you up a region's call list.

Why does the coordinator care about paperwork more than skill?

Because their job is not to fix the equipment — it is to prove to the end client that the service level was met. Your check-in time, your photos and your closing notes are the evidence they report with. A technician who does excellent work and documents none of it creates a problem for the coordinator, who then has to go and ask for it.

This is the single most useful thing to understand about field service. Competence is assumed. What distinguishes technicians, from the dispatcher's seat, is whether the ticket closes cleanly without anyone having to chase.

Before the visit

  • Answer fast. Accepting or declining within the hour is worth more than accepting everything slowly. A quick decline genuinely helps — it lets them move on.
  • Read the work order properly. Scope, site address, arrival window, site contact, deliverables, NTE if there is one.
  • Decline work you are not equipped for. Far better than failing it on site. Nobody remembers a decline; everyone remembers a wasted visit.
  • Confirm the day before, in writing, with the site contact if you have one.
  • Check you have the parts and tools the scope implies, not just the ones it lists.

Arriving

Arrival windows exist because they are contractual. If traffic turns against you, call before the window closes — not after. A technician who warns the coordinator at 09:40 that they will be twenty minutes late is managing a problem; one who arrives at 10:20 without a word has created one.

  • Park sensibly and carry in what you need in one trip where you can.
  • Sign in at reception as the site requires, and have ID ready.
  • Introduce yourself to the site contact and say roughly how long you expect to be.
  • Check in through the app before you start work, not at the end from the car.

While you work

Photograph everything

Before, during and after — even when nobody asked. Before shots protect you from being blamed for pre-existing damage. During shots evidence what you found inside. After shots prove the state you left the site in. This habit resolves more disputes than any amount of arguing.

Record serials as you go

Anything installed, removed or swapped. Reading a serial off a photo later is slow and error-prone; writing it down at the time takes seconds.

Leave the site tidy

Cable offcuts, packaging, old equipment, ceiling tiles put back. The end client's impression of the dispatch company is formed almost entirely by what the room looks like after you leave.

Call from site when you are blocked

If the equipment is not there, access is refused, or the scope turns out to be wrong, call while you are still standing in the building. A coordinator can often resolve it in five minutes or authorise a return visit. Discovering it from your closing notes that evening is far too late to re-dispatch.

Closing out

This is where tickets are won or lost. The test for closing notes is simple: could a stranger who has never seen the site act on them?

  1. What you found. The actual condition on arrival, not just the reported fault.
  2. What you did. Specific actions, in order.
  3. What you changed. Parts fitted or removed, with serials.
  4. What is outstanding. Anything the next person needs to know, including anything you could not complete and why.
  5. Signature or documented exception. Never leave without one or the other.
  6. Check out in the app before you drive away.

“Completed as per scope” is not closing notes. It tells the coordinator nothing, and when the end client queries the visit in three weeks it will come straight back to you.

Communication that builds a relationship

  • Use the coordinator's name, and keep the same thread for the same ticket.
  • Flag problems early and with a proposed solution, not just a complaint.
  • If you make a mistake, say so first. It is almost always recoverable; being found out is not.
  • Ask, after a few tickets, what would make them send you more work. Almost nobody asks, and the answer is usually specific and easy.

None of this is complicated. It is simply reliable, and reliability is scarce enough in field service that it is a genuine competitive advantage. See also how to get steady work.

Checklist

  • Dispatch offers answered within the hour
  • Work order read in full before accepting
  • Appointment confirmed the day before in writing
  • Called ahead if running late, before the window closed
  • Checked in through the app on arrival
  • Photos before, during and after
  • Serial numbers recorded at the time
  • Site left tidy
  • Called from site the moment you were blocked
  • Closing notes a stranger could act on
  • Signature captured, or exception documented with a name and time
  • Checked out in the app before leaving

Get the Work Directory

130+ companies that dispatch or hire contract IT techs, with how to apply, who to contact, what each one requires and how they pay. One payment, no commission, no subscription.

See the Work Directory Join free

Placeholder — real policy text still needed.

This is where the Techwhere privacy policy goes: what personal data is collected from technicians and buyers, how it is stored, how long it is kept, who it is sold or disclosed to, and how someone exercises their rights to access or delete it.

Placeholder — real terms text still needed.

This is where the terms of sale and acceptable use go: what a buyer may and may not do with a purchased list, resale and redistribution limits, accuracy disclaimers and limitation of liability.

Orders are placed by email. We send an invoice; you pay by bank transfer or a payment link we send you, and we email you the file once payment arrives.

All sales are final. If you have a problem with your download, email us.

Email us your email address, your phone number or both. They are taken out of every Techwhere list, including any file a company downloads from then on.

Email techwhere.sales@proton.me