Is planning software suitable for a company with eight technicians?

For a company with eight technicians, planning software is suitable, and it is the size where its benefit shows most clearly. What matters is not the number of people in itself, but the number of combinations that come with it: free days, qualifications, absences and appointments the customer has not yet confirmed. With eight people, a plan held in someone's head works until the first absence of the person holding it.

• With eight people the problem does not come from the number of people, but from the number of combinations.
• The hardest things to remember are appointments still being negotiated and not yet confirmed.
• Absences stop being a detail and start determining what can be promised.
• Introduce one shared plan first, and only then records of qualifications.
• The threshold where it starts to hurt is lower: at roughly three people.

What counts differently with eight technicians

Eight people means roughly forty days of capacity in one week. That in itself is not much; if it were just about filling forty cells, a spreadsheet would handle it.

But work does not arrive by the day. It arrives as orders of varying length, some of which take one person a whole week, others an hour, and some need two people at once. Tied to that is who is allowed on a given job, who is on holiday right now and which appointments have been offered to the customer but not yet confirmed.

It is the last group that breaks a plan kept in someone's head. An offered, unconfirmed appointment effectively takes up a slot in the plan, but it is not written down anywhere. In a company of three, the planner remembers them. With eight, there are so many under negotiation at any one time that nobody remembers them all, and one day gets promised twice.

Where exactly the dispatcher stops coping

Not in the overview, but in three specific places.

The morning reshuffle. When something changes in the morning, you need to find a person who is free, has the qualification and can make the journey in time. With eight people that means going through more variants than fit into one phone call with the customer.

Answering during the call. The customer calls and wants an appointment. Either you answer straight away, or you promise to call back. The second option costs one extra call and a share of the orders, because the customer calls elsewhere in the meantime.

Handing over the plan. When the planner falls ill, someone else has to take over not just the list of orders, but also what was promised to whom and why Thursday is deliberately empty for one technician. That part does not get handed over, because it is not anywhere.

The first two places are unpleasant daily, the third is unpleasant once a year and costs the most.

Absences stop being a detail

With three people, holidays are remembered. With eight, someone is almost always away and absence stops being an exception accounted for separately. It becomes a routine part of calculating free capacity.

The practical difference is in when you find out about it. A planner who keeps holidays in a different file from the plan offers an appointment and only then finds out the technician is off that week. The customer has to be called again, this time with an apology.

In capacity and skills, free capacity, qualification and absence are in one place, so the filter returns only people who are actually usable. That difference shows precisely at this company size: with three people it is a convenience, with eight it determines what can be promised to the customer.

Who plans when there is more than one planner

A company with eight technicians often ends up in a state where several people plan: the owner in the morning, the service manager in the afternoon, occasionally the workshop foreman too. This is where a second type of clash arises, one that is not caused by size but grows with it.

The solution is not to split the technicians into two groups and plan each separately. That does remove the overwriting, but introduces a worse problem: free capacity in one group is not visible from the other, so an order gets turned down for which there would have been people.

The solution is one plan both can see. In the planning board, technicians are in rows and days in columns, assignments are entered by dragging across cells, and the app flags a clash on save. This does not restrict who changes the plan; it just stops happening that the other planner does not know about a change.

What to introduce first

The order decides whether the rollout succeeds or gets abandoned after a month. This sequence has proven itself:

1. One plan that both the office and the technicians can see. As long as there are two, you are adding work, not removing it.
2. Absences in the same plan. Without them, free capacity is untrue and nobody will trust the plan.
3. Qualifications on technicians. Only once the plan is live does it make sense to filter who is allowed on what.
4. Distinguishing offered and confirmed appointments. That removes most double promises.
5. Logging the job on the order. The history starts filling itself and the calls to the office stop.
6. Reports and invoicing documents last. They only bring benefit once the input is reliable.

The most common mistake is to start from point six, because it looks best on paper. It adds work for the technicians before it takes any away, and the rollout stalls on their resistance. The procedure for companies just starting out is covered in technician dispatching for beginners.

Why the threshold is not at eight, but at three

Eight technicians is the size where the cost of coordination is visible daily. But it does not arise there, it arises earlier.

From three people, technicians start taking turns at the same customer and the question of qualification is added to free time. Combinations grow faster than people, so between three and eight it is not twice the work, but many times the variants.

The difference between three and eight is therefore in how often it hurts, not in whether it hurts. A company of three pays for coordination once a week, a company of eight several times a day. With eight people the decision is therefore usually easier: the cost is visible and nobody questions it.

What will not change

You will not gain capacity. Eight technicians remain eight technicians and the plan will not turn them into ten. What changes is the share of their time that goes on travel and waiting instead of work.

Nor will the decision-making disappear. How much time to allow for a job, whom to send to a difficult customer and when to say it will not get done this week remain with whoever plans. The plan makes those decisions visible and flags clashes, but it does not make them.

What goes away is finding things out and repeating the same information. The answer to the question of who is free on Thursday and allowed on the job exists in one place, not in one person's head and three phone calls.

Frequently asked questions