It makes sense to stop planning technicians in Excel the moment the spreadsheet stops answering operational questions faster than a person would. That is, when orders overlap, appointments change during the day, and the question of who is free and has the required qualification only gets answered after a phone call. Until then, Excel is a legitimate tool. The operation decides, not the size of the company.
- The limit is not set by the number of technicians, but by how often the plan changes during the day and how many orders run in parallel.
- A spreadsheet does not flag a clash by itself. A technician assigned twice is usually found only when the customer calls.
- Excel does not tie a specific order, a technician's qualification or a job history to an appointment.
- The switch can start with one team and one week, without migrating the whole history.
- ServisBook costs EUR 20 per user per month, the first 30 days free and without a payment card.
Excel is not a bad tool, but it has a clear limit
Excel only fails where the spreadsheet is expected to check, not just record. As long as it is an overview of who has a shift on which day and who is on holiday, the spreadsheet does its job and costs nothing. But as soon as the plan contains specific orders, times and sites, Excel starts asking you to keep all the rules in your head. A cell accepts any text. It does not know that the same technician is already somewhere else that day, or that they are not qualified for the job.
The second limit is sharing. A spreadsheet has one author and several readers who have downloaded a copy. The moment two people change the plan at the same time, or a technician in the field needs to look at it, the question arises of which version is valid. That question has no good answer in Excel.
Five signs the spreadsheet has hit its ceiling
The signs are operational, not technical. None of them means the spreadsheet is broken; they mean you want something from it that it cannot do.
- The customer reports the clash, not the plan. Two technicians turn up at one site, or nobody turns up. The error arose in the spreadsheet, but only came to light in the field.
- An appointment takes three e-mails and two phone calls to arrange. You offer two days, the customer turns both down, in the meantime one of them is taken and the round starts again.
- You cannot answer "who is free next week and qualified for it" during the call. You have to open the spreadsheet, the holiday calendar next to it, and add in your head who holds which qualification.
- Technicians call the office to find out where to go. The plan exists, but it is on a screen in the office and nobody sees it in the field.
- The order history is scattered. What was dealt with at the customer last year is known to one specific person and their e-mail inbox.
One sign on its own does not call for a solution. Three or more at once mean that coordination is consuming more time than the actual work on the orders.
What a spreadsheet cannot verify
The difference is not in what the plan looks like, but in who enforces the rules. In a spreadsheet it is you. In a planning tool it is the app.
| Operational question | Excel | Planning tool |
|---|---|---|
| Is the technician already assigned that day? | you spot it by eye, across sheets | the app flags a clash on save |
| Does the technician have the required qualification? | kept in someone's head or in another file | a recorded skill on the technician |
| Who is absent next week? | a separate column or a second file | part of the capacity overview |
| Which appointment to offer the customer? | manually picked days in an e-mail | a link with free days to choose from |
| Can the technician see their day in the field? | no, unless someone sends it to them | a browser on their phone |
| What has happened on the order so far? | e-mails, notes, memory | a change log on the order |
| Who last changed the plan? | untraceable | part of the history |
Three of these rows are handled by the planning board, where technicians are in rows and days in columns and assignments are entered by dragging across cells. The rest is covered by capacity and skills and orders and history.
When switching does not make sense yet
Stay with the spreadsheet if you mostly plan recurring shifts with no link to a specific order. A shift grid with daily resolution is exactly the case where Excel does the job cheaply and reliably.
Likewise, postpone the switch if you already have an ERP in which orders and the plan are actually kept and people work in it. Two parallel plans are worse than one imperfect one. And if what you plan over time is not people but production or stock, a planning board for technicians is not the right tool.
How to verify the moment on your own numbers
Instead of guessing, write down four figures for one month. A sheet of paper next to the phone is enough.
- How many times you called or wrote to the customer while arranging a single appointment.
- How many times a month a technician called the office asking where to go.
- How many times a clash or a wasted site visit occurred and how it was resolved.
- How many times you searched e-mails for what had happened on a given order before.
After a month you have your own data, not someone else's estimate. If all four numbers are low and stable, the spreadsheet is serving you. If they grow with every additional parallel order, so does the time that will go on coordination next month.
How to switch without stopping operations
Switching does not mean transferring the whole history. It means moving decisions about appointments to one place.
- Pick one team and one week. The rest of the company carries on unchanged for now.
- Name the statuses and appointment types according to your own habits. Customisation is done at the start and without a programmer; changing the terminology halfway through the rollout causes the most confusion.
- Enter next week's plan into the board, not a year's worth retrospectively. Add historical data only for orders that are actually continuing.
- Give the technicians a link to their day. Mobile for technicians is a browser, not an installation, so there is no handing out of apps.
- After a week, compare the four numbers from the previous section. If they have dropped, extend to the next team. If they have not, look for the reason before adding people.
Expect the team to work more slowly for the first two weeks. The plan is being entered, the terminology fine-tuned, and some people are still checking the old procedure alongside the new one. That is a cost that belongs on the other side of the balance sheet.
What changes in the weekly rhythm
What changes most is who waits for whom. With a spreadsheet, the customer waits for you to find them a free appointment, and the technician waits for the office to confirm the address. After the switch, the customer picks from the appointment offer themselves and you just confirm their choice.
The second change is in looking things up. Attachments, internal notes and a record of every change sit on the order, so the question "what did we do there last time" is answered by the system, not by one specific person's memory. That is a difference that only shows when that person is on holiday.
Excel does not end there. It remains a good tool for source data, calculations and one-off overviews. It stops being the place where it is decided who goes where tomorrow.
Frequently asked questions
Does switching from Excel mean we have to transfer the whole order history?
No. Transfer the plan for the coming weeks and add history only for orders that are actually continuing. Bulk migration of old data slows the rollout down and brings little benefit. Closed orders can stay in the original files as an archive.
Is it worth it even for a small company of two people?
The operation decides, not the size. If with two people orders run in parallel, appointments change during the day and customers call for confirmation, the limit of Excel shows just as it does for a larger team. If you mostly plan regular shifts, a spreadsheet is enough.
What if part of the company wants to stay with the spreadsheet?
Let them, but not on the same plan. Two parallel plans for the same technicians are worse than one imperfect one. Split the rollout by teams, not by functions, so that each team has only one binding source of appointments at any given time.
How long does it take for the team to get used to the new plan?
ServisBook has no published measurement from which a specific period could honestly be promised. Expect a period when the team works more slowly, because the plan is being entered and the terminology fine-tuned. The free trial lasts 30 days and needs no payment card.
Will a planning tool replace accounting or an ERP as well?
No. It handles planning technicians over time, orders and their history. If you already have an ERP in which orders are actually kept and people work in it, it is better to stay with it than to run two parallel plans.
When Excel is enough for planning technicians, where it stops being enough and what changes when you switch.
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.
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.
A shared calendar, a spreadsheet or a chat can plan installations for free. Where that stops being enough and what to replace it with.
How to spot the limits of Excel for planning techniciansA practical audit of a spreadsheet for planning technicians: clashes, absences, qualifications, change history and the rules that have to be maintained.
How to stop two technicians going out to the same orderA 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.
Plan more simply
ServisBook free for 30 days, no credit card.
Free trial →