A full schedule is not always an efficient one. When each technician goes from one visit to the next with no leeway between them, a difficult site access, a repair that takes longer than expected or an emergency is enough to delay the entire day. The result is usually familiar: calls to apologise, rescheduled jobs, overtime and a team that ends up exhausted.
Technician planning means assigning a workload that can actually be completed, not filling every visible gap in the calendar. Doing it well requires combining capacity, travel, specialisms, priorities and variability. The goal is not for everyone to have every minute occupied, but to meet commitments at a sustainable pace with room to respond.
A full schedule and an efficient schedule are not the same
A full schedule measures theoretical utilisation. An efficient schedule reflects the work that fits into the day after accounting for everything else that also takes time: journeys, breaks, preparation, loading materials, calls, completing job sheets and minor incidents.
Imagine an eight-hour day with four visits estimated at two hours each. It fits on paper. In practice, there is no time left to travel, park, speak to the customer, put tools away or document the work. The plan is behind schedule from the outset, even if all the technical estimates are correct.
It is useful to distinguish between three concepts:
- Working hours: the contractual time available.
- Operational capacity: the part of the working day that can be devoted to visits and travel.
- Committed workload: the time already reserved for specific jobs.
Workload management begins by comparing operational capacity and committed workload, not by counting appointments.
Calculate each technician's real capacity
Not every day or every technician has the same capacity. To arrive at a useful figure, start with the working day and subtract the blocks you know will be needed:
Real capacity = available working day − breaks − administrative tasks − preparation − operational margin
Travel can be deducted in advance if you know the journeys, or included in the duration of each block. The important thing is not to forget it or treat it as free time.
For example, in a 480-minute working day, a technician may need a 30-minute break, 30 minutes for preparation and completion, and a 40-minute margin for small deviations. That leaves 380 minutes for visits and travel. This is the reasonable benchmark for loading their day, not the full eight hours.
The calculation must be adapted to the type of service. A routine inspection is generally more predictable than an undiagnosed fault. An installation on a construction site may require access, unloading and coordination with other trades. If you use the same standard duration for every case, the schedule will conceal the risk instead of helping you manage it.
Start with simple estimates for each type of work and correct them using the team's actual experience. Perfect accuracy is not necessary: a forecast reviewed every week is much more useful than a very detailed figure that nobody updates.
Include travel, breaks and administration
Gaps between visits are not wasted time. They are the invisible infrastructure that makes it possible to arrive on time and complete every service properly.
Allow time to:
- travel and find parking;
- access sites, unload materials and prepare the work area;
- take breaks during the working day;
- complete the job sheet, attach evidence and update the job status;
- call the office, suppliers or customers when necessary.
In densely populated areas, a short margin between nearby visits may be enough. In rural areas, industrial estates or city centres with difficult access, the journey must be planned explicitly. If you want to explore geographical sequencing in more detail, read this guide to route planning for technicians.
It is also best to avoid letting all administration build up until the end of the day. A short block after each visit helps to complete the information while it is fresh and avoids turning the last half-hour into a race.
Reserve capacity for emergencies and unforeseen events
If your company responds to breakdowns, a schedule at one hundred per cent capacity stops being viable as soon as the first emergency comes in. The solution is not to predict what will happen, but to reserve capacity before it happens.
You can do this in several ways. In small teams, leave a flexible block each day and decide who will cover it at the start of the working day. In larger teams, rotate the on-call technician or distribute some leeway across several routes. If emergency demand is very irregular, review the history by day of the week, time slot and season to choose a sensible buffer.
That margin does not have to remain empty if no incident arises. It can be used for flexible preventive maintenance, follow-up calls, warehouse tasks or internal jobs that can be interrupted without affecting a customer. This allows you to maintain productivity without selling the same hour twice.
Also define what is genuinely urgent. A critical shutdown, a safety risk or a contractual commitment should not compete on equal terms with an enquiry that can be resolved tomorrow. Shared criteria prevent every call from becoming an exception.
Assign by area, skills and duration
Availability is only one of the assignment criteria. A visit fits into a technician's schedule only if it also suits their location, capabilities and the time required.
Area. Group nearby jobs to reduce travel and switching between areas. There is no point making use of a 45-minute gap if getting there takes half an hour. Routes based on geographical areas help to keep working days compact.
Skills. Take account of the necessary specialisms, certifications, experience and tools. Sending the technician who is available but not suitable increases the risk of a second visit and ultimately fills two schedules rather than one.
Duration. Protect long blocks for installations or complex diagnostics and use short gaps for predictable inspections or nearby tasks. Avoid fragmenting the day in a way that leaves many unusable gaps.
Continuity. Where useful, assign the follow-up to the person who already knows the customer or equipment. The context time saved may outweigh a small difference in travel time.
In enrutar, routes allow you to group visits by area, nature of the work or necessary resource, while technicians are assigned separately. The calendar and timeline allow you to review visits by person responsible or route, move them, reassign them and adjust their duration. These features make manual planning easier by providing visible information, but they do not replace calculating the team's real capacity in advance.
How to identify overload and unproductive gaps
Overload does not always appear as an obvious overlap. It also shows up as chains of visits with no transition, journeys that cross several areas, jobs of uncertain duration at the end of the day or technicians who systematically finish outside working hours.
Look for these signs:
- committed workload very close to the full working day before accounting for travel;
- repeated delays in the same time slots or types of work;
- frequent rescheduling and job sheets completed the following day;
- overtime consistently concentrated among the same people;
- emergencies that force you to cancel visits that have already been confirmed.
At the other extreme, unproductive gaps usually appear between appointments that are too far apart, as a result of poor geographical grouping or because short time slots remain that no job can use. A technician with six hours assigned may be less productive than another with five if they spend much of the day crossing the city.
Look at the week as a whole, not just each day. Sometimes it is better to move a flexible visit to Tuesday to free up a continuous block on Thursday. A weekly view helps to identify this type of adjustment; the daily timeline is more useful for checking transitions, duration and gaps by person responsible.
Holidays, absences and seasonal peaks
Team capacity changes before demand does. Holidays, training, sick leave, local public holidays or vehicle maintenance reduce the available hours. Record these constraints as soon as they are known and recalculate the affected week; hiding them until the last minute simply transfers the problem to customers.
Prepare for holiday periods well in advance. Identify which skills will have less cover, which contracts have committed dates and which jobs can be brought forward or postponed. If a specialism depends on a single person, agree in advance how incidents will be handled during their absence.
Seasonal peaks deserve a separate forecast. Compare demand from previous years by type of work, not just by revenue. This will allow you to distinguish whether you will need more hours for air conditioning, preventive inspections or emergencies. For quieter periods, this guide on how to manage the low season suggests using capacity for maintenance, training and internal tasks.
Do not fill all the additional capacity of a peak season in advance. When the volume and duration of jobs are more variable, the operational margin should grow, not disappear.
A weekly adjustment routine
Planning improves when it becomes a short, consistent habit. Set aside a fixed time each week with the coordination team and, where possible, also gather the technicians' perspective.
- Review what happened. Compare planned and actual duration, delays, emergencies, overtime and rescheduling from the previous week.
- Update capacity. Include holidays, absences, training, on-call shifts and any known constraints.
- Classify demand. Separate fixed commitments, flexible jobs and capacity reserved for emergencies.
- Balance the week. Distribute work by area, skills and duration; correct overly busy days and group journeys.
- Check the edges. Pay particular attention to the first and last visit, long journeys and uncertain jobs.
- Adjust your benchmarks. If a type of work repeatedly takes longer than planned, change its standard duration.
During the day, change the plan only when you have enough information. Before inserting an emergency, confirm its priority, location, required skill and likely duration. Then decide which flexible block to use or which visit can be moved with the least impact.
Measure to improve without putting pressure on the team
Metrics should be used to improve the system, not to reward impossible schedules. Combine workload, execution and quality indicators: percentage of capacity committed, punctuality, planned versus actual duration, travel between visits, rescheduling, overtime and first-time resolution.
Analyse trends by type of service, area and week. Avoid comparing technicians without context: complex installations, dispersed customers and on-call duties create different workloads. The useful conversation is not ‘who made the most visits’, but ‘what conditions caused the plan to succeed or fail’.
Route optimisation in field services completes this analysis when a significant part of the working day is lost to travel.
From an overloaded schedule to a manageable one
A good field service schedule combines committed work, transition times and response capacity. First calculate the actual hours, reserve a margin, assign work using operational criteria and review deviations every week. With this discipline, gaps stop looking like a failure and become a tool for protecting punctuality, quality and the team itself.
If you need to centralise visits and review the workload by person responsible or route, you can try enrutar and adapt the calendar to your operations. The tool helps you visualise, reassign and adjust visits; the capacity you want to reserve and the planning rules remain under your control.