Calendar per technician and per team
Who has what and when, with filters by client, site, work type or status. This is the day-to-day view.
Feature
The maintenance calendar isn't an agenda: it's where you decide what isn't going to happen this week. And that decision is made better when you can see each person's real workload.
Three things that compete with each other. Recurring work, which has a fixed date and shouldn't move. Corrective work, which shows up unannounced and is almost always urgent. And whatever carries over from the previous week. Scheduling means fitting all three into the available hours of a team that has shifts, time off, travel and days when someone doesn't show up. Doing it on a whiteboard works with four technicians; beyond that the problem isn't drawing it, it's finding out about the changes.
Not for lack of a plan. For lack of reality in the plan.
The same information in whatever form each decision needs.
Who has what and when, with filters by client, site, work type or status. This is the day-to-day view.
Workload spread out over time, to see at a glance where work is piling up and which week is empty.
Planned preventive orders show up on the calendar before they're generated, with their date and estimated time. That's what lets you reserve hours.
Sites grouped by route and linked to their technicians, so assignment takes geography into account, not just availability.
The team's real availability inside the same calendar. Scheduling without that is scheduling against a workforce that doesn't exist.
For teams that still want the paper route sheet at the start of the day.
No maintenance day ends the way it started. That's why the calendar lets you move a job by dragging it to another date or another technician, and the change reaches the phone of whoever it's assigned to without anyone having to notify them. The practical difference isn't the convenience of dragging: it's that when rescheduling is easy, it happens; and when rescheduling means calling three people, what happens is the plan gets abandoned and everyone improvises. A calendar that doesn't reflect what's actually going to happen is worse than no calendar at all, because it also gives a false sense of security.
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
The question almost no one can answer is how much work fits. With estimated times on preventive plans and work types, the calendar stops being just a schedule and starts being a measurement: how many preventive hours next month demands, how many are left free for corrective work, and at what point you need to subcontract or say no. It's the information you negotiate a contract expansion with, without committing to something the team can't sustain.
Deciding who does what looks like load balancing, but it's actually three decisions at once. There's competence, because not everyone can handle every piece of equipment or holds the certification some jobs require. There's geography, because sending someone to the far end of the area when a colleague is right nearby costs a whole morning. And there's accumulated knowledge: whoever was at that machine last time will solve it faster than someone arriving fresh, even if both know how to do the job. A calendar that only shows gaps lets you make the first decision; one that also shows where everyone is and who serviced that equipment before lets you make all three, which is the difference between distributing work and organizing it.
There's a useful asymmetry worth taking advantage of. The manager needs to see the whole week, every technician at once, and the gaps, because their job is deciding. The technician needs exactly the opposite: just theirs, in order, starting with today, without the noise of what everyone else is doing. Showing both the same screen forces one of them to mentally filter it every time they open it, and in practice what happens is the technician stops opening it and calls instead. Each role seeing the version it needs isn't a matter of convenience: it's what determines whether the calendar gets used or turns into an office tool nobody looks at in the field.
The technician sees their work in the app, which is the view they need: just theirs, starting with today. Planning the full week, with the whole team at once, is a desktop task for a practical reason: it requires seeing a lot of things together and dragging between them, and that doesn't work well on a phone screen no matter how well it's adapted.
Yes. Shifts, holidays and absences are part of the same calendar, and automatic preventive order generation checks availability before creating the order when the HR module is active.
Yes, and the change reaches the technician's phone without a separate notification. That's what makes rescheduling actually happen instead of the plan being abandoned.
Yes. Planned preventive orders can be seen with their date, their assets and their estimated time before they exist as an order, which is what lets you reserve hours and negotiate shutdowns.
Yes. Sites are grouped into routes and linked to their technicians, so assignment takes geography into account. The app also lets you order the day's orders by proximity using GPS.
With the estimated times from the plans and work types, you can see how many preventive hours fall in each period and how many are left free for the unexpected.
In the demo we set it up with your technicians, your shifts and your routes, and see how much capacity you really have left.
Accessibility
Saved in this browser. Light or dark theme is set from the footer.