The type of work
Corrective, preventive, capital work or a reading. It changes the urgency and who can do it.
Guide
Scheduling is mostly about seeing
A calendar where everything looks the same forces you to read every entry to decide. One where status and type stand out at a glance lets you decide by looking, which is what happens twenty times a day.
Why color isn’t decoration
In a week with a hundred and twenty interventions spread across eight technicians, the difference between a readable calendar and one that isn’t shows up as coordination time. Whoever schedules doesn’t need to read: they need to spot. That an urgent corrective job stands out from a routine preventive one, that an unassigned work order jumps out, that an overloaded day looks overloaded without counting entries. Color, icon and position do that work in a fraction of the time reading takes, which is why a well-designed view saves more than it seems to.
What you should be able to tell apart without reading
Five things that should stand out at a glance.
The status
Unassigned, in progress, waiting on material, closed. Unassigned is what needs to be seen first.
Who has it
The workload per person, to see at a glance who has spare capacity and who’s overloaded.
Where it is
Grouped by site or by route, because two jobs at the same location get done in one visit.
How long it takes
A half-hour entry and a full-day one can’t look the same.
One view doesn’t serve every purpose
The daily calendar answers today’s question: who goes where. The weekly view is for distributing work and spotting gaps. And the timeline view, read like a per-technician or per-equipment timeline, is the one that serves what neither of the other two does: seeing the load for the coming weeks and deciding whether something should move before committing to it. Using the wrong view for the question at hand is a silent source of bad scheduling: with the daily view nothing gets anticipated, and with the monthly view a Tuesday doesn’t get organized.
What makes a calendar get abandoned
Always the same thing: that it stops reflecting reality. As soon as changes get communicated by phone and the calendar falls out of date, people stop checking it, and from then on everyone improvises. That’s why what matters isn’t the color but making rescheduling trivial — drag and drop — and having the change reach only the phone of whoever it’s assigned to. A pretty calendar that has to be maintained by hand lasts three weeks. One that updates as a side effect of the work lasts for years.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
The calendar as a measure of capacity
A maintenance calendar serves two different purposes, and the second one is rarely used well. The first is knowing what needs doing this week. The second is knowing whether it fits, which is a much more important question. When every scheduled job carries a duration estimate and an owner, the calendar stops being a list of intentions and starts showing load: this week there are a hundred and twenty planned hours against seventy available, and that’s a decision that has to be made now, not on Thursday. Most maintenance plans that don’t get met fail not for lack of discipline but for lack of arithmetic, and the problem is that the arithmetic isn’t visible until the month is over. Seeing it ahead of time turns non-compliance into a conscious decision about what gets moved, instead of a result discovered at the end.
Moving isn’t the same as deleting
When an emergency comes up and something has to come off the calendar, how you do it determines whether the plan survives the year. If the job simply disappears, nothing visible has happened: nobody misses it, and the plan erodes without leaving a trace. If it gets rescheduled to a new date, it’s still there and someone will see it show up again. The difference is one click, and it’s the difference between a plan that’s met seventy percent of the time and one that’s quietly emptied out without anyone deciding that. And there’s a second effect, even more useful: when postponements get logged, at the end of the quarter you can see how many there were and why. If the same thing always gets moved, that’s not an emergencies problem: it’s a sign that job is sized wrong, or that nobody actually thinks it’s necessary.
Frequently asked questions
What should I color-code: status, type, or technician?
Only one of the three at a time, and that’s the hard discipline. Color is a calendar’s fastest reading channel and also the easiest to saturate: as soon as it’s used for two different things it stops communicating and becomes decoration. The usual approach is to code by status, since that’s checked most often, and leave type and person for filters or the detail view.
Why do we keep going back to the spreadsheet?
Almost always for the same reason: the calendar stopped reflecting reality. It only takes a few weeks of changes being agreed by phone and not reflected for nobody to trust what they see anymore, and from there everyone builds their own version. A shared calendar only works if it’s the one place decisions get made, not one more place where what was already decided elsewhere gets jotted down.
Can you see the workload per technician?
Yes, per technician and per team, with their shifts and absences in the same view. It’s what lets you distribute work by looking instead of counting.
Can you reschedule by dragging?
Yes, and the change reaches the technician’s phone without a separate notice needed. It’s what keeps the calendar reflecting reality, which is what everything else depends on.
Which view should I use?
The daily view to resolve today, the weekly view to distribute work, and the timeline view to anticipate. Using the wrong one for the question at hand is a silent source of bad scheduling.
Can you see what doesn’t exist yet?
Yes. Scheduled preventive work orders appear before they’re generated, with their date and estimated duration, which lets you reserve hours ahead of time.
Show us your week
In the demo we build a real week with your technicians and see what shows up and what doesn’t.