Dispatch & route planning
Scheduling for your technicians: the plan holds
Monday morning, open faults, maintenance falling due, four technicians. Where a whiteboard, a spreadsheet and a round of phone calls used to be, you plan the week in Vecodesk in minutes — every stop with a reason, every route on the technician's phone.
- Week and day view
- Route proposal without AI
- Route straight in the technician app
The plan holds
One plan the office and the technicians work from
The week is planned in minutes
“Propose plan” spreads the open tickets across your technicians and fills each day up to their working hours. One click takes the proposal over as a draft.
Every stop says why it is there
“Deadline tomorrow · knows the site · on the way.” Every day shows its load, and whatever was not planned is listed with the reason.
The route is on the phone
Once published, each technician gets one message and finds their route in the app: stops in order, navigation via Apple or Google Maps.
As technicians and sites are added, planning the week stays a matter of minutes — without extra hands in dispatch.
How the week runs
From open ticket to finished route
Tickets on the left, the plan on the right: technicians as rows, days as columns, each cell one technician's route for one day.
- 1
Propose: one day or the whole week
Only technicians with the required skills who do not avoid the customer are proposed. Then the resolution deadline counts, who knows the machine, site or customer from the last 180 days, preferred regions, and the distance from the start point or the previous stop.
- Each day is filled up to the working hours, job duration estimated from recorded times on similar tickets
- Load per day, e.g. “5.5 of 8 h”
- Whatever was not planned is listed separately, with the reason
Screenshot to followThe route proposal dialog: proposed routes for several technicians, the reason at every stop, the load for each day - 2
Adjust: drag and drop
Drag one or several tickets onto a technician and a day. If the route already stops at that address, the ticket joins that stop; otherwise it becomes a new one. Every change can be undone.
- Preset view “Unplanned”, with “Overdue” always on top
- Public holidays by German state, Austria and Swiss canton, plus company days off, are hatched and named
- “Plan…” schedules ticked tickets without dragging, for tablet and phone
- 3
Publish: every technician gets their route
Planned routes stay drafts until you publish them. Then each technician gets one message — “Your route 27 Oct: 6 stops” — and sees the route in the app under “Today”.
- Red lines flag what needs attention: rejected, planned after the deadline, closed since
- A rejection shows “Re-plan” right at the stop
Screenshot to follow“My route” in the technician app: the day's stops in order, with navigation - 4
Morning meeting: the day view
Each route as a column with its stops. Reorder by dragging or “Sort by distance”; “Search at these stops” finds open tickets at the route's addresses and within 2, 5 or 10 km.
- Maintenance falling due at a stop within 14 days shows there with “Take along” — one click creates the maintenance tickets and plans them
- “Like last week…” re-plans the open tickets of an earlier route
Screenshot to followDay view of the planning: routes as columns, one stop showing due maintenance with “Take along”
In detail
What the planning takes into account
A planning profile per technician
Skills such as “refrigeration” or “card terminal”, preferred regions and customers, avoided customers, start point at home or at the depot, maximum stops a day, own working days and hours for part-time.
Instructions in one sentence
“Jannik tomorrow in Eschwege, all open faults there.” With the separately booked AI add-on, the AI re-weighs the plan accordingly. Skills, avoided customers and capacity are still checked by Vecodesk; the AI sees no customer names and no ticket texts.
What the route achieved
For today and past days: done and overdue, work and travel time, kilometres from the recorded times. The route's service reports as one ZIP in route order.
FAQ
Questions about scheduling
Do I need the AI add-on for route proposals?
No. “Propose plan” is part of the planning and works without AI. The separately booked AI add-on comes in when you want to give the plan instructions in a sentence.
What does the technician see before I publish?
Nothing. Planned routes are drafts. Only on publishing does the technician get their message and the route in the app.
Can several people plan at the same time?
Yes. Every change appears immediately for everyone who has the planning open.
Related
Let Vecodesk propose a week.
In the demo we plan a week, publish the routes and open one of them in the technician app.