Managing maintenance teams with a CMMS

Planning people is harder than planning machines, because people have shifts, vacations, different schedules, and the occasional bad day. And because maintenance work isn’t distributed evenly: some weeks have three preventive jobs and others have twenty breakdowns.

What a CMMS brings here isn’t HR software — worth saying early, because it’s the most common wrong expectation — but the workforce piece you need in order to plan work against reality.

Teams, and who’s accountable for each one

The first thing is that the structure has to exist in the system. Technicians are grouped into teams with a supervisor, and that enables two things: assigning work to a team instead of to one specific person, and letting each team lead see their own work without staring at the whole company’s workload.

It’s a detail you notice a lot once headcount passes ten people: a list of three hundred open work orders isn’t information, it’s noise.

Seeing the workload before you distribute it

The pattern that repeats across almost every department is the same: half the team overloaded, the other half waiting, and nobody finds out until someone complains.

The calendar shows what’s happening each day and whose it is, and the diagram-based planning view lets you see each technician’s workload across the weeks. The most useful part of that screen isn’t what’s assigned: it’s what isn’t, because whatever has no owner is what’s going to fall through. You can color-code unassigned work for exactly that reason.

When something needs to move — and something always needs to move — you drag it to another day.

Letting the technician pick up work

One of the functions that does the most to lighten a planner’s load, and one of the least talked about: self-assignment. The technician can see the work orders that have no one assigned and take them on themselves.

It sounds minor and it changes the day-to-day quite a bit. The person on the ground knows better than anyone whether it’s on their way, whether they’ve got the material in the van, and whether it fits with what they’re already carrying. And it avoids the bottleneck of having one person handing out work all day.

Along the same lines, from the app the technician can sort their work orders by route using GPS, so they don’t cross the city twice. Travel is the single biggest cost item in almost any maintenance operation, and that’s the direct lever on it.

Shifts, schedules, vacations, and public holidays

Planning without this information produces plans that can’t actually be carried out. In GMAO Cloud there are shifts with their assigned technicians, schedules with their hours, vacations with their types, and public holidays.

That has one concrete, very useful consequence: before generating a preventive work order, the system checks whether that day is a public holiday and whether the technician is available. Scheduling a check for August 15th, or for someone who’s on vacation, stops being possible.

There are also schedule-hour alerts, useful for catching deviations before they turn into a labor-agreement or cost problem.

Real hours, by technician and by client

You can’t manage a team without measured time, only supervise it. Hours jotted down from memory at the end of the day always come out low, and with them the cost of a job is a guess.

The stopwatch built into the work order itself fixes that. From there, the reports on hours by technician, hours by client, time entries, schedules, absences, and a summary by team lead let you see reality: who’s overloaded, where the time is going, and which jobs cost twice what they bill.

A warning about using those reports: they’re for sizing and quoting, not for watching people. A team that senses the system exists to monitor them stops feeding it accurately, and then the reports stop being worth anything.

Licenses, which condition everything above

There’s a pricing-model detail that directly affects team management. If the software is charged per user, onboarding a new technician, an intern, or a subcontractor becomes an economic decision, and the temptation to share accounts shows up.

The moment two people sign in under the same user, per-technician reports stop meaning anything and the history stops holding up as proof. In GMAO Cloud, licenses are unlimited across all three plans, which is what lets every job stay recorded under the name of the person who actually did it.

The gear, not just the people

A work team needs tools and protective equipment, and both have their own tracking: assignment per person, requesting, issuing, and expiration of PPE, with its alert before it expires.

It’s the part of workforce management that gets forgotten most often and hurts most when it fails, because it isn’t a logistics problem: it’s a liability problem.

Subcontractors: part of the team even off the payroll

In many operations, half the work is done by people who aren’t in-house. If those companies operate outside the system, the planner only sees half the picture: their own work in detail, and the outside work as an invoice at the end of the month.

Vendors get set up with their associated warehouses and receive the work orders that correspond to them, so what they do gets recorded exactly like in-house work: time, materials, documentation, and signature. There’s also a connector between GMAO Cloud sites for when the subcontractor also uses it, working both ways, so the work passes from one system to the other with no intermediate file and no manual reconciliation.

The real advantage isn’t the administrative savings: it’s that the workload you see on the calendar is the actual workload, not just the share your own staff carries out.

Where to start

With the minimum structure: teams, supervisors, schedules, and public holidays. That alone lets you plan against reality. Shifts, vacations, and PPE get added later, once the work distribution is already running.

If you want to see it with your own structure, you can request a demo.