How to Manage Service Jobs and Site Visits

Managing service jobs comes down to four steps that never change: log the request in one place, with the fault, the site address and the contact on site; turn it into a visit with a date, a time slot and a named technician; give the technician everything they need before they get in the van; then record hours, parts and any extra work against the customer record. What makes this repeatable is not the software, it is having decided once who takes the request, who sets the priority and who closes the job. Extra work found on site never appears as a surprise on the invoice: it becomes an agreed line or a separate quote before anyone does it.

If calls currently reach you through three different channels and next week's schedule lives on a whiteboard, by the end of this guide you will have one path from request to invoice, and you will know what has to be written down at each step.

One distinction first: this guide is about the individual visit to a customer site. The commercial container that groups several visits together, with a budget and a margin, is the job or project, and how you open and close one is covered in the guide on managing client jobs.

What you need before you start

• One place where requests land. Phone, email, WhatsApp and the website form can all stay open, but they have to feed a single list. As long as each request lives in the inbox of whoever received it, priority is decided by chance.
• Customer records with the site address, not the registered office. They are often different, and that is the most common reason a technician knocks on the wrong door.
• A list of the equipment installed per customer, even just model, serial number and installation date: it tells you whether the visit is under warranty before you send anyone out.
• A three level urgency scale: production stopped, degraded service, plannable request. Three is enough, nobody ever uses five.
• The response times you have promised in maintenance contracts, read when you plan the week rather than after the angry phone call.
• One person who does the scheduling, because when four people decide who goes where, two technicians end up in the same area on the same day.

Then agree on what has to be written down at each stage.

Stage	Who does it	What has to be recorded
Request	whoever answers	customer, contact, symptom, urgency, address
Check	scheduler	warranty or contract, history, likely spare part
Scheduling	scheduler	date, time slot, technician, estimated duration
Visit	technician	arrival time, finish time, what was done
Parts	technician	codes and quantities taken from stock
Closing	coordinator	outcome, extra work found, what gets invoiced

How to manage a service job, step by step

1. Log the request as an activity linked to the customer, not as a note on a scrap of paper. On the customer record create the activity with four fields: the symptom in the customer's own words, the contact on site with a direct number, the site address, and the urgency level. The expected result is that tomorrow morning anyone opening that record sees the request without asking the person who took the call.

2. Ask the three questions on the phone that save a second visit: model and serial number, how long it has been happening, and what changed just before it started. Thirty seconds of questions is worth a round trip, because without the model the technician leaves without the right part.

3. Check warranty and contract before you assign the visit, using the history and the installation date. Knowing now whether the work is covered, chargeable or included in the contract is what the technician will have to say on site, and improvising that answer is the fastest way to end up arguing over the invoice.

4. Assign a date, a time slot, a technician and an estimated duration. Not an exact time: a slot, for instance Tuesday between 9 and 12. The duration stops you stacking four two hour visits into an eight hour day. Group customers who are geographically close on the same day, because that choice changes how many visits fit into a week more than anything else.

5. Confirm the appointment and send a reminder the day before. A wasted trip because nobody was there to open the door is avoided with one message: how to set up a reminder that goes out on its own is covered in the guide on appointment reminders and no shows. If the channel your customers actually use is WhatsApp, it pays to run it from a shared business number rather than the technician's personal phone, as described in the guide on messaging several customers on WhatsApp.

6. Brief the technician before departure with the five pieces of information listed further down. The expected result is no calls to the office between eight and nine in the morning.

7. Have the outcome recorded the same day: arrival time, finish time, what was done, parts used, and one line on any extra work found. An outcome reconstructed on Friday is always rounded down, and that rounding comes straight out of your margin.

8. Close the job yourself, not the technician. The coordinator reads the outcome, decides whether a second visit is needed, and turns extra work into either a quote or a line to invoice. That way no job sits in an intermediate state for weeks, which is how billable hours quietly disappear.

Emergency callouts: fitting them into a full day

A real emergency is one that stops the customer working. Everything else is high priority, which is a different thing and can wait until tomorrow.

Keep one slot a day free, usually the first one after lunch, and schedule nothing in it. If no emergency comes in you use it to catch up; if one does, you cancel on nobody. When you are forced to move an appointment anyway, call the customer before they notice and offer an alternative date in the same conversation.

Planned maintenance and contract customers

Planned maintenance is the opposite of an emergency: you know about it months ahead, so not scheduling it is a decision rather than bad luck.

The method is to generate the whole year's appointments in one go. If a machine needs checking every six months and the last check was in March, the September date already exists today and belongs in the calendar today. What you get is a predictable base that emergencies slot into instead of wiping out.

On contract customers there is one useful question: how many visits has this customer used compared with what the contract covers. It is the kind of loss you never see, because the invoice goes out unchanged while the visits pile up.

Installations and first commissioning

An installation is not a repair, it is a delivery: a date agreed by whoever sold it, material that has to arrive beforehand, and often more than one technician on site. The three checks to run the day before are that the material is there and has been inspected, that the customer has prepared what they were asked to (space, power, access), and that the person receiving the delivery will be present. Then the warranty clock starts: if that date is not written down anywhere, in a year's time nobody will be able to say whether the first fault is covered.

What the technician needs to know before leaving

The test is that they should never have to call the office for anything foreseeable. Five pieces of information, no more, because nobody reads a fifteen field form at seven in the morning.

1. Where they are going and who is expecting them: full site address, contact name with a direct number, and access instructions such as reception, badges or department opening hours.
2. What happened: the symptom in the customer's words. "It makes a noise and cuts out after ten minutes" is useful, "broken" is not.
3. What has already been tried: the last two visits to that machine, with dates and outcomes, so they do not repeat a diagnosis a colleague has ruled out.
4. Whether it is chargeable: warranty, contract or paid work, and in the last case the callout charge and hourly rate to quote.
5. What to load in the van: the likely spare part, based on symptom and history. Even a reasoned guess beats leaving empty handed.

Whatever tools you use, this has to be written down before the technician leaves: preparation cannot happen in the van.

How to close the job and invoice extra work

Closing has three parts, and mixing them up is the most common cause of invoice disputes.

The first is the record of what was planned: actual hours, parts taken from stock, travel. That gets logged and invoiced under the existing agreement.

The second is the extra work found on site. The rule is blunt: it either becomes a line agreed with the customer before anyone does it, or a separate quote sent the next day. There is no third option where you do it and put it on the invoice hoping nobody asks. If the extra work is substantial, treat it as a sale in its own right, using the structure in the guide on how to write a quote.

The third is what stays open: a part on order, a second visit, a check in a month. If it does not immediately become a new activity with a date, it does not exist.

On paperwork and tax treatment these are general organisational pointers only: for your own situation follow the guidance of your national tax authority and check with your accountant.

Alternative method: starting without changing tools

If you cannot change anything right now, there is a reduced version you can set up in an afternoon: a shared sheet with one row per request and eight columns (request date, customer, address, symptom, urgency, visit date, technician, outcome), a fixed ten minute scheduling meeting on the same day every week, and a confirmation message to the customer the day before.

It holds up while you have two or three technicians and fewer than ten requests a week. Beyond that, keeping the sheet aligned costs more than it saves. When the repetitive steps become the bottleneck, the part worth automating is always the same one, namely confirmation, reminder and status change: how that chain is built is covered in the guide on automatic workflows, and what a shared system costs is set out on the pricing page.

Common mistakes

• Scheduling without an estimated duration. If every job counts as "one visit", a day looks full at four entries when it actually holds six or two.
• Going on site without reading the history. The history is not there for the good technician, it is there for the second technician sent to the same customer, who would otherwise repeat checks already ruled out.
• Leaving job sheets in the van. An outcome written four days later loses the parts and half the hours.
• Treating extra work as a favour. "While I was there I fixed that too" is revenue that disappears and becomes an expectation next time.

How long it takes and what comes next

Defining the urgency levels, cleaning up site addresses and moving open requests into a single list usually takes a day if you have fewer than two hundred active customers. The long part is the two or three weeks it takes for recording the outcome the same day to become a habit rather than something someone remembers.

After the first month, watch one figure: the share of jobs closed with hours and parts recorded by the next day. Below half, any margin calculation you make is unreliable.

The next step is reading visits by customer and by machine rather than one at a time, so you can see which contracts consume more visits than they cover. That is the same commercial reading you apply to jobs.

Frequently asked questions

What is the difference between a service visit and a job? The visit is the single trip to the customer, with a date, a technician and an outcome. The job is the commercial container grouping several visits, with a sold value, a budget and a margin. A one off repair stays a visit; an installation with a survey, a fit and a commissioning is a job containing three visits.

How do you avoid wasted trips? The two main causes are the customer not being there and the technician arriving without the right part. The first is reduced by confirming the appointment and sending a reminder the day before, the second by three extra questions on the phone (model, serial number, exact symptom) and by reading the history first.

Who should set the priority of service jobs? One person, using a written rule: first the faults that stop the customer working, then commitments made for a specific date, then everything else in order of arrival. If whoever answers the phone decides, in practice the most insistent caller decides.

Do you need software to manage service jobs? Below a certain size a tidy sheet and a fixed meeting are enough. A shared system pays off when several people need to write to the same record, when requests arrive on different channels and nobody has the full picture, or when you notice you are copying the same details from the request to the schedule and from the schedule to the invoice.