With five technicians, planning software is worth it, because for a service company with repeat jobs the threshold lies lower, at three people: from three onwards, technicians regularly alternate at one customer. Five is therefore above it. Exactly how much it does for your company depends on how often the plan changes, and you can check that within one week.
- For a service company with repeat jobs the threshold is at three people, not five.
- What decides is the number of plan changes per week, not the number of employees.
- The most expensive thing is not the jobs, but pending appointments that are recorded nowhere.
- A week of noting down acts of coordination answers more precisely than any general calculation.
- Without a single shared plan it does not pay off even with twenty people.
Why the threshold lies at three, not five
This applies to companies that visit repeat customers and plan people over time. A project company, where one crew works for months on one site, follows different rules and this text is not for it.
Up to two people, coordination costs little. One person holds the plan and the answer to who is free tomorrow is a single sentence they have in their head.
From three onwards it changes, because combinations grow faster than people. Every free day carries a question of qualification, travel distance and whether the customer has already confirmed the appointment. At the same time, technicians start to alternate at one customer, so whoever arrives for a repeat fault was not there for the last one.
Five technicians is therefore the size at which a company pays this cost every day, it just does not book it as a line item, because it breaks down into pieces of a few minutes each.
Pushing in the same direction as headcount is seasonality, because at peak the plan changes more often, and staff turnover, because a new technician has neither the qualifications nor the knowledge of customers yet, so they cannot be assigned to just anything.
What happens every day with five people
Four situations that cost the most and occur most frequently at this size.
A customer calls and wants an appointment. If at that moment you do not know who is free and allowed to do it, you promise to call back. That is one extra call and a share of the orders, because the customer calls elsewhere in the meantime.
Something changes in the morning. A breakdown or a cancelled job means finding who can be moved and with what impact on the rest of the week. With five people there are enough variants that it cannot be done from memory during the call.
An appointment is offered but not confirmed. This is the most underestimated item. An offered day effectively takes up capacity, but it is not in the spreadsheet. When there are three of these, the planner remembers them. When there are eight, they promise one day twice.
Someone is new or missing. A new technician does not have all the qualifications and does not know the customers, so they cannot be assigned to just anything. The same applies in reverse with holidays: a specific qualification drops out, not just one pair of hands.
The third point tends to be the reason a repeat visit or a double promise appears even in companies where the plan is otherwise in order. It is examined in how to prevent repeat visits by technicians.
A one-week test that answers for you
You need no tool for it, just a sheet of paper by the phone. Five working days are enough.
- For every call that was needed to arrange one appointment, make a tally mark.
- For every morning reshuffle in the plan, make a mark and note how many people it affected.
- For every technician's query to the office along the lines of where am I going or what was done there, make a mark.
- For every check of who is on holiday or who has a qualification, make a mark.
- For every promise to call a customer back, make a mark.
- On Friday, count how many of those marks would disappear if the answer were visible in one place.
Precision is not needed, the size of the result is enough. Companies that come out at up to ten marks a week have cheap coordination and the decision is not urgent. Companies that come out at several dozen pay for coordination every day and simply have it written down nowhere.
How five differs from two and from eight
| Two technicians | Five technicians | Eight technicians | |
|---|---|---|---|
| Where the plan is | In one person's head | In a head and a spreadsheet | In two heads and a spreadsheet |
| Pending appointments | A handful | Ten or more at once | So many they cannot be remembered |
| Morning reshuffle | One phone call | Several variants | Cannot be done from memory |
| Absences | Known about | Kept somewhere other than the plan | Almost always someone is missing |
| When the planner is away | The other one stands in | Improvisation | The week falls apart |
The table is a model of typical development, not the result of measurement. It is there so you can recognise your company in one of the columns, not as a basis for calculation.
The last row is the one that usually makes companies of five decide. The daily cost can be endured, because they get used to it. A week's holiday for the person who holds the plan in their head cannot.
Where exactly the time is saved
In three places, and it is worth telling them apart, because they show at different speeds.
An answer during the call. When you can see who is free and who has the required qualification, an appointment can be offered immediately. Capacity and skills show both at once, absences included, so calling back becomes the exception.
The customer chooses the appointment. Through the appointment offer, the customer receives a link with free days and chooses themselves. That removes the whole exchange of messages, not just part of it.
Unnecessary site visits that never happen. When assignments are visible and a conflict is reported on saving, there are fewer cases of two people driving to one place. This shows fastest and is easiest to count.
A comparison with what most companies use today is described in the comparison of ServisBook with Excel.
What has to hold for it to pay off
That one plan arises, not a second one alongside the existing one. Two plans side by side bring the cost of both and the benefit of neither, and it is the most common reason roll-outs fail at small companies.
That the technicians really do enter data into it. A history filled in every other day and haphazardly saves no queries to the office, because it cannot be relied on.
And that you do not start with work logs and invoicing. It is the most measurable part and the worst place to start, because it adds work for the technicians before it takes any away.
You can tell whether it worked by repeating the one-week test after two months of use and comparing the number of marks. When these three conditions do not hold, neither a tool nor a bigger company will help.
What to do this week, even if you buy nothing
Three adjustments that cost nothing and remove most double promises. They make sense on their own and at the same time prepare the ground should the company later move elsewhere.
- Record pending appointments in the same place as confirmed ones, just distinguish them by colour or a note. Until then they take up capacity nobody knows about.
- Move holidays and sick leave into the plan, not into a separate file. Free capacity calculated without absences is untrue and people stop trusting it.
- Introduce one place where the technician writes what they did at the customer, even if it is one sentence on the order. It removes most queries along the lines of what was done there last time.
When you introduce these three things and repeat the one-week test after two months, you get two pieces of information at once: how many marks disappeared through discipline alone and how many are left for a tool. A company left with a few marks a week after these adjustments does not need software right away. A company left with dozens knows what to ask a vendor.
The most common objection
That an experienced person can manage it from memory even with five people. That is true and it is not a counter-argument.
The question is not whether they manage it, but what happens in the week they are not there. In such a company the cost is not paid in drops every day, but all at once: nobody knows the pending appointments, customers get in touch about promises nobody knows of, and the plan is put together again from scratch.
The other side of the same objection is that the company closes off its path to growth. A sixth technician still fits in the planner's head. A seventh only fits if something else starts falling out.
Frequently asked questions
Is planning software worth it with five technicians?
Yes. The threshold at which coordination stops fitting in one person's head lies at roughly three people, so five is clearly above it. What decides, though, is the way of working: a company with fixed pairs and a set schedule hits it later than a company with daily dispatching.
How do I check it without committing straight away?
With a one-week test. Note down every act of coordination: a call about an appointment, a morning reshuffle, a technician's query, checking a holiday. After five days you will see how much time coordination costs, and that is the amount at stake.
Isn't a well-made spreadsheet enough for five people?
For the schedule itself, yes. It fails elsewhere: in concurrent entry, in absences kept somewhere other than the plan and above all in pending appointments that take up space but are recorded nowhere. That is exactly where double promises arise.
What if one experienced person holds the plan and it works?
It works as long as they are at work. In such a company the cost is not paid daily, but all at once in the week of their holiday or illness. So the question is not whether they manage it, but what happens in the week they are not there.
What has to hold for it to really pay off?
That a single plan arises, not a second one alongside the existing one, that the technicians actually enter data into it and that you do not start with work logs. Two plans side by side bring the cost of both and the benefit of neither.
EUR 20 per user per month, all features included. First 30 days free, no credit card.
Capacity and skillsWho is free, who has the required qualification and who is away. You get the answer while still on the phone.
Appointment offers to customersA link with available days. The customer picks a date, you confirm it.
Technician planTechnicians in rows, days in columns across a continuous 35-day strip. Create a new appointment by dragging; the app warns you about conflicts.
A double call-out does not start in the plan but alongside it. The four places it comes from and how to stop two technicians going to one job.
Proposed and confirmed appointments: a difference that costs moneyProposed vs confirmed appointment. Why a coloured cell in a spreadsheet is not enough, what it costs and how a schedule can show certainty.
How to replan the day when an emergency comes inAn emergency is never added to the plan, it replaces something. A step-by-step procedure, which job to move and what to tell the customer.
Plan more simply
ServisBook free for 30 days, no credit card.
Free trial →