Technician management: what a field worker sees and does

A CMMS is fed by whoever is out in the field. That sentence sounds obvious, and it has a consequence that gets overlooked when buying one: if the tool makes the technician’s day harder, logging gets pushed to the end of the shift and stops being a record to become a reconstruction from memory. And a reconstruction from memory always has fewer hours than the job actually took.

So the useful question isn’t what features the system has, but what exactly the technician sees and does. This is that walkthrough.

The first thing they see: their day

The list of their work orders, with whatever time window you decide —today, this week, overdue—.

Two things that save time from day one. They can sort by route using GPS, so they don’t cross the city twice, and they can see unassigned work and take it themselves, because they know better than anyone whether it’s on their way and whether they’re carrying the material. That also removes the bottleneck of having one person handing out work all day.

In the work order: context before starting

Opening the order, they have the equipment’s history, its documentation and the anomalies left open from the last visit right in front of them.

It’s the detail that prevents the most callbacks. Many breakdowns are repeats of something already seen, and knowing that before starting is the difference between fixing it and patching it again. If the asset has a QR code, they scan it and land on the right record without depending on a numbering scheme everyone interprets their own way.

What gets logged while working

Stopwatch time tracking, inside the order itself. Start and stop. The hours booked are measured, not remembered, and that difference shows up directly in the real cost of the job and in what gets invoiced.

Materials from the warehouse, with batch number when applicable. Consumption isn’t a later entry: it’s a consequence of closing the order, so stock and cost update with what was actually used. If you set up their van as its own warehouse, the material that travels stops being invisible.

Equipment checklists, with anomaly logging. On preventive orders, the app won’t let you close until they’re filled in. And fields support a minimum and maximum value, so a reading out of range gets logged as an anomaly on the spot instead of as a side comment. More detail in checklists.

Photos, before and after. They stop staying stuck on the phone’s camera roll.

Client signature on screen, when finishing, with geolocation if enabled. The technician can also sign themselves when the workflow requires it.

Work goes on without coverage

This is the part that decides whether everything above actually happens, because maintenance takes place in basements, warehouses, plant rooms and elevators — exactly where there’s no signal.

The technician app isn’t a wrapped website: it stores orders, assets and documents on the device itself, and every action taken offline —changing a status, logging hours, consuming material, filling in a checklist, collecting a signature— goes into a queue that empties itself once coverage returns.

And if an action fails to sync, it doesn’t disappear: it gets flagged with the reason and stays visible. Silently losing a morning’s work would be worse than not having an app.

One clarification worth keeping, because it’s the most common confusion: that full offline mode belongs to the technician app. Client access installs on the device but doesn’t work offline.

What they receive without asking

The notification system alerts them by push and email about work assigned to them, and there are scheduled alerts for the following week’s work.

Worth tuning: you can mark which statuses should not notify, and that matters as much as the opposite. Notifying on every internal move turns notifications into noise and people stop reading them, which is worse than not having them.

What’s behind it, in the office

For their day to add up, planning needs to know reality: shifts, working days, vacations and holidays, which exist in staff management so you can plan around them. In fact, before generating a preventive order the system checks whether the day is a holiday and whether that person is available.

Technicians are grouped into teams with their supervisor, so each manager sees their own and work can be assigned to the team instead of to one person.

And their personal protective equipment is managed with its assignment, request and an expiry alert, which is the part that stings the most when it fails, because it’s not a logistics problem — it’s a liability one.

What not to do to them

Three things that guarantee the system gets abandoned:

Asking for fields that serve no purpose. Every useless field multiplies across every order in the year.

Forcing them to re-enter data the system already has.

Doing nothing with what they log. If they detect an anomaly and it doesn’t turn into an issue with an owner and a date, by the third time they’ll stop logging it. And they’ll be right.

How to roll it out without pushback

Resistance to a new system is almost never about the technology: it’s about someone watching what you do. Worth taking seriously, because the quality of all the data depends on it.

What works is starting with what saves the technician work, not with what the office needs. Having the team’s history and documentation on the phone without calling anyone, not having to go back to a site because a part was missing, not having to write up reports neatly in the afternoon. Once that’s felt, the rest falls into place on its own.

And it helps a lot to start with a small group of technicians for a few weeks. That trial always produces two things: configuration adjustments no one had anticipated, and the arguments to convince everyone else. One technician telling another that they no longer call the office convinces more than any training session.

A pricing model detail

This affects the above directly. If the software is priced per user, adding a new technician, a seasonal temp or a subcontractor becomes a financial decision, and the temptation to share accounts shows up. As soon as two people sign in with the same user, per-technician reports stop meaning anything and the history stops holding up as evidence.

In GMAO Cloud, licenses are unlimited on all three plans.

If you want one of your own technicians to see it before deciding —which is the test that best predicts whether the project will work—, you can request a demo.