How to stop two technicians going out to the same order

There is only one way to stop two technicians going out to the same order: assignments must be created in one place that reports the clash at the moment of entry, not in the morning at the customer. That comes with a rule that outside this plan nobody sends anyone anywhere, neither by phone nor by a note on the desk. A double call-out almost never arises in the plan, but alongside it.

• A double assignment is born outside the plan, most often in a phone call that was never written down.
• What helps is a single place where the assignments of all technicians for all days can be seen.
• The clash must be reported by the tool at the moment of entry, not by a person during the morning check.
• The other half of the solution is an operating rule: if it is not in the plan, nobody goes.
• As long as site visits do not overlap, a shared calendar is enough.

Where a double call-out comes from

Almost always from two people deciding on an assignment, each at a different moment, with neither seeing what the other had done. It is not negligence, but a consequence of the plan existing in several places at once, or partly only in memory.

A typical sequence: on Tuesday afternoon the owner takes a call, promises the customer Thursday and calls the technician to make a note of the appointment. He does not enter it in the spreadsheet, because he is on the road. On Wednesday morning the service manager plans Thursday from the spreadsheet, sees the technician as free and assigns him another order. On Thursday the technician drives where the owner told him to, and a colleague assigned by the manager arrives at the second site. Two technicians, one order, and nobody broke any rule.

The second variant is more common and harder to detect. A customer reports a fault by e-mail and the next day calls to be on the safe side. Two records of the same thing are created, each with a different person. Two orders are then planned. That it is one fault on one unit only comes out on site.

The four places where it most often arises

All four have one thing in common: the pieces of information about the assignment do not meet before the technicians meet at the customer.

The procedure that stops it

1. Set one place where the plan is created. Not two, and not a spreadsheet next to a calendar.
2. Introduce the rule that an appointment counts only once it is entered in the plan. Until it is there, it is not arranged, even if someone promised it over the phone.
3. Write it down during the call, not after it. Most double call-outs arise in the gap when an appointment has been promised and is not written down anywhere.
4. Before assigning a technician, look at what they already have that day. The tool should show you that by itself, not only after your check.
5. Before you create a new order, check whether one is already running at that address. That catches double reports.
6. Go through the day once in the morning. Not to hunt for mistakes, but for the changes since the previous day.

The sixth point is the only one that can be dropped once the first four work reliably.

One place where the whole week can be seen

The change that shows fastest is the one where the plan stops being a list and becomes a grid. Technicians in rows, days in columns. When an assignment is entered in a specific technician's row, both the empty and the occupied cells are visible before anything is confirmed to the customer.

In the planning board you enter assignments by dragging across cells and it warns you about a clash before it happens. That is the moment a spreadsheet lacks: Excel will not highlight an empty cell, because it has no information that the technician is assigned elsewhere in the file that day. A grid with clash checking highlights the problem at the moment of entry, when the correction still has no consequences for the customer.

Who is free and who has the qualification

The other half of the question of who will go out to the order is not about time but about qualification. A double call-out also arises like this: the first technician arrives and finds that he does not hold a valid qualification for the job, so the next day someone else goes. Formally it is not a clash; in practice it is the same loss.

Capacity and skills keeps on the technicians the information of who is free, who holds the qualification for the given work and who has an absence recorded. So you have the answer while still on the phone with the customer. If holidays are kept in one file, qualifications in a second and the plan in a third, there is no quick answer and planning is done from memory.

Two orders that are really one

This case is not handled in the plan but on the order. If every order has one place holding the technicians' logs, internal notes, attachments and a record of every change, the duplicate is recognised when it is created, not on site.

Orders and history keeps everything on one order, so there is no searching through e-mails. The practical effect: if on Friday you create a job for an address where something has been running since Wednesday, you will see it. And if the customer asks a month later why two technicians from the same company were there on two days, you can trace where the second entry came from and who made it.

Appointments still being arranged

The riskiest state of a plan is neither full nor empty, but uncertain. An appointment that someone has offered a customer and that is awaiting confirmation is usually not entered in the spreadsheet, because it does not count yet. But as long as it is not there, the slot looks free and someone else takes it.

The appointment calendar distinguishes what is certain from what is still being arranged, so an appointment in progress takes up the slot visibly, but unmistakably apart from a confirmed one. A three-day installation is one bar, not three separate entries in which the middle day is easily lost.

The technician as the last safeguard

The last place where a double call-out can be caught is in the van in the morning. A technician who copied the plan onto paper last week drives by the paper. A technician who looks at the current day in the morning drives by the plan, including the change from the previous evening.

Mobile for technicians works in the browser; the technician opens their day and sees where they are going. They start the work and, on finishing, log the tasks done and any note for the office. They do not have to call to ask where to go next, and they are not driving by information several days old.

When you do not need to deal with it

Where site visits do not overlap, a double call-out happens rarely and the planner catches it through daily contact. A shared calendar is enough there, and a new tool would bring more work than benefit. The same applies to companies that do not plan people over time. The turning point comes with concurrent orders and changes of appointments, when the planner stops being sure they remember everything correctly.

When it happens anyway

What matters is not who caused the mistake, but where the second entry arose. In most cases it will be one of the four points in the table above, and the answer is always the same: at that moment the information did not reach the place where the others could see it. If every change has a record of who made it and when, finding out takes a few minutes. Without it, the matter is settled by guesswork at a meeting and repeats next month.

Frequently asked questions