Time management in maintenance

When people talk about efficiency in maintenance, they usually think the goal is to make people work faster. That’s almost never where the problem is. Time is lost between jobs, and in amounts nobody measures because it leaks away in ten-minute chunks.

This is a walk through the five usual drains, and what reduces each one. No invented percentages: you’ll need to pull the numbers from your own data, and at the end I explain which ones to look at.

1. Travel time

In any operation with field technicians, this is the biggest line item, and the one that shows up least in analysis because it isn’t billed as such.

Order the day by route. From the app, the technician can order their work orders using GPS, instead of handling them in the order they were assigned. Crossing the city twice is a cost nobody sees.

Let them pick up work. They can see unassigned orders and take them on themselves, because they know whether it’s on their way and whether they’re carrying the material. That also removes the bottleneck of having one person dispatching work all morning.

Group by zone. If assets have their location recorded in asset management, three minor interventions in the same zone can be handled in a single trip instead of three.

2. The visit that has to be repeated

Going back because a part was missing, because the model wasn’t known, or because nobody had the key. It’s paid for twice: the trip and the hour.

The material. Items carry their minimum stock, which warns before running out of what a job needs. And registering each technician’s van as its own warehouse is what stops the material that travels from being invisible.

Equipment information. In the app, when opening the order, the technician has the asset’s history, its documentation, and the anomalies that were left open. Many breakdowns are repeats of something already seen.

What was left pending. The order can be flagged as pending material and as needing a return visit. Without those states, that work lives in a notebook, and the client remembers before we do.

3. Searching for information

The hardest drain to see, because it’s lost in fractions. A technician calling to ask for a pump’s model. Someone searching for a drawing across three folders. Last year’s report that a client is now asking for.

What fixes this isn’t more folders: it’s that the document hangs off the thing it belongs to. In the document manager, documents are attached to the asset, the client, the site, the order, or the incident, and they appear when you open that entity. With their visibility decided in advance — who can see it — so nobody has to filter by hand every time.

And they’re stored on the device, so they stay available in a basement with no signal.

4. Administrative work

Here there are whole tasks that disappear, not just tasks that get faster.

Writing up the report afterward. If the record happens on site — a timer inside the order, material consumed against the warehouse, checklist, photos and signature on screen — there’s nothing left to type up later.

Tracking where each thing stands. The statuses of an incident can have an associated email, so the status change notifies on its own. And with their own access, the client checks the status of their orders and downloads their reports without calling.

Typing everything twice to invoice. Closed orders with their hours and material are what the ERP needs. Integrations lists the scope of each connector.

5. Waiting and overlap

The universal pattern: half the team overloaded and the other half waiting. Nobody notices until something is late.

With a list sorted by date, you can’t see it, because the list has no people axis. In the calendar and in the diagram-based scheduling, you can: who has a full week, who has gaps and — most useful of all — what work doesn’t have an owner yet, which is exactly what’s going to fall through the cracks.

And planning against reality: shifts, working hours, vacations, and holidays exist in staff management for exactly that. Before generating a preventive order, the system checks whether the day is a holiday and whether that person is available.

The drain that doesn’t look like one: preventive maintenance that doesn’t happen

The five above are minutes. This one is hours, and it’s paid for later.

A breakdown costs considerably more than the check that would have prevented it: emergency travel, downtime, a part with no lead time, and rushed work. If scheduled checks are the first thing to give way when an emergency comes in, the time that seems saved today gets paid back with interest.

What sustains this is having preventive maintenance be an order with an owner and a date, generated automatically from its periodicity, and not an intention on a calendar.

What to measure to know if it’s improving

No promises: use your data. Four reports answer this.

Non-effective hours, which include travel and waiting. The direct indicator of drains 1 and 5.

Deviation between estimated and actual time. The one that surprises people most the first time: it almost always reveals a type of job that’s budgeted below what it actually costs.

Orders closed per technician per day, which only makes sense alongside the previous one.

Ratio of preventive to corrective hours. The one that tells you whether time is really being recovered or just being reorganized.

A warning about using this data

It’s meant to size teams, budget better, and distribute workload. Not to monitor anyone.

A team that senses the system exists to watch them stops feeding it accurately: they log late, round off times, and stop noting anomalies. And once that happens, the reports stop being useful and the efficiency you wanted to measure becomes unmeasurable.

The honest argument to make to the team is the one that actually affects them: fewer kilometers, fewer back-and-forths, fewer calls to the office, and not having to write up reports in the evening.

If you want to see where time is going in your operation, you can request a demo.