A technician's time is the scarce resource

Almost every conversation about maintenance talks about budget. And in almost every real operation, the resource that actually limits you isn’t money: it’s the available hours of people who know how to do the work.

Hiring someone takes months, and training them takes longer. Buying a part takes days. That’s why it’s worth looking at where that time actually goes, which is almost never where it looks like it goes.

The hours that show up nowhere

Productive time —the time a technician actually spends with hands on the equipment— tends to be a lot smaller than everyone assumes. The rest is spread across four places, and none of them get billed as such.

Traveling. In field-service operations this is the biggest chunk of all, and the one that shows up least in the analysis.

Waiting. For a site to open, for a machine to stop, for a part to arrive, for someone to answer a question.

Searching. For equipment information, a diagram, a manual, an old work order. It’s lost in five-minute pieces, which is exactly why nobody counts it.

Repeating. Going back to a site because materials were missing, because the model wasn’t known, or because nobody had the key. That hour gets paid for twice.

How to cut down each one

Travel is cut by sorting work orders by route using GPS from the app, and letting the technician pick up unassigned work that’s along the way. Bundling three minor jobs into one trip instead of three is, in scattered sites, the biggest lever there is.

Waiting is cut by planning against reality: shifts, working days, vacations and public holidays in staff management, so the system checks availability before generating a preventive work order. And by notifying the customer of upcoming preventive visits through their portal access, so the site is open when the technician arrives.

Searching is cut by attaching documentation to the asset in the document manager, not to a folder. And by storing it on the device, so it’s still there in a basement with no signal.

Repeating is cut with minimum stock on the parts that hold up work, with the van registered as its own warehouse, and with the equipment’s history in front of you before you leave.

The time spent on admin

Besides the technician’s own time, there are office hours that disappear entirely —not just get faster— once logging happens in the field:

Writing up paper reports afterward. Chasing receipts. Answering calls that only ask how something’s going. Typing into the ERP what was already written down that morning.

All four are eliminated with the same thing: a stopwatch inside the work order, materials consumed against the warehouse, an on-screen signature, a customer portal, and a connection to the ERP —whose scope is worth checking in integrations, because not every connector does the same thing.

The time investment that pays off the most

There’s one that returns hours permanently and is always the first thing to get postponed: writing down what needs to be checked on each piece of equipment.

Checklists defined by family —with cascading resolution by asset, model, subfamily and family— get written once and serve two hundred pieces of equipment. They stop each inspection from depending on who happened to do it that day, and stop knowledge from walking out the door with people.

One afternoon of work that pays off for years.

The time you lose in the future

The least visible line item: the urgent corrective job caused by the preventive visit that never happened.

A breakdown costs quite a bit more than the check that would have prevented it: immediate travel, downtime, a spare part with no lead time, and work done under pressure. If scheduled checks are the first thing to get bumped when an emergency comes in, the time that looked saved today gets paid back with interest a few months later.

What sustains this is that preventive maintenance is a work order with an owner and a date, generated automatically — not an intention on a calendar.

The cost of not having anyone to ask

There’s a time drain that isn’t the technician’s, and it’s worth counting: the person everyone consults.

In almost every department there’s someone who knows how each piece of equipment is handled, where the documentation is, and what was done last time. That person spends a good part of the day answering other people’s questions, and their time is the most expensive on the team.

It doesn’t get fixed by asking them to delegate: it gets fixed by writing down what they know. Checklists by family, the history attached to the asset and documentation accessible from a phone are the practical way to do it.

The side effect is the one that really matters: when that person goes on vacation —or leaves the company— the operation doesn’t leave with them.

How to find out where the time goes in your case

With reports, and without making up percentages:

Non-effective hours, which capture travel and waiting.

Deviation between estimated and actual time, which reveals which jobs are quoted below what they actually cost.

Orders marked as pending material or needing a return visit, which directly measure repeat trips.

Ratio of preventive to corrective hours, which tells you whether time is being recovered or just reshuffled.

A word of caution about this data

It’s useful for sizing the team, budgeting and distributing workload. Not for monitoring anyone.

A team that senses the system exists to watch them logs things late, rounds off times and stops noting anomalies. And once that happens, the reports stop being worth anything, and the time you wanted to measure becomes unmeasurable.

The honest pitch to make to the team is the one that actually affects them: fewer kilometers, fewer repeat visits, fewer calls to the office, and no more writing up paper reports in the evening.

And one final idea that ties it all together: the goal isn’t for people to work faster, but for them to spend more time with their hands on the equipment and less traveling, waiting, searching and repeating. Those four are the ones that can be cut, and none of them require asking anyone for anything.

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