Staff management in a CMMS: what it covers

It’s worth starting with the scope, because it’s the most common wrong expectation: a CMMS isn’t HR software. There’s no payroll, no contracts, no performance reviews, no recruitment.

What’s there is the part of staff management that maintenance needs in order to plan work against reality. And that part matters more than it seems, because without it the plan is built against an ideal calendar and is unfulfilled from day one.

Why planning needs this

A plan that schedules a review on a public holiday, or under the name of someone on vacation, isn’t a plan: it’s a delay scheduled in advance.

In GMAO Cloud, before generating a preventive order, the system checks whether that day is a holiday and whether the technician is available. That check is only possible if the system knows the work calendar and absences.

That’s the underlying reason this information lives here and not in the HR system: it’s not there to manage people, it’s there so the work gets generated on a day that actually exists.

What’s there

Shifts, with their assigned technicians. In operations that work shifts or on-call rotations, this is what lets you know who’s on at each time slot.

Working hours, with their totals, and their history. Plus warnings on working-hour totals, which help catch deviations before they become a labor agreement or cost problem.

Vacations, with their types, and holidays. This is what feeds the availability check.

Work teams, with their supervisor. This lets you assign work to a team instead of a person, and lets each supervisor see just their own without having the whole company’s orders in front of them.

Personal protective equipment, with its assignment per person, its request, its delivery, and its notified expiry.

PPE, the part that stings the most when it fails

It deserves its own section because it’s not a logistics matter: it’s a matter of liability.

PPE is assigned to a person, requested, delivered, and it expires. There’s a check that warns before it lapses, just like with documentation.

Discovering that a piece of protective equipment had expired after an incident is the kind of problem money doesn’t fix.

Seeing the workload before assigning it

The pattern that repeats in almost every department: half the crew swamped and the other half waiting, and nobody finds out until something’s late.

With a list of orders sorted by date, you don’t see it, because the list has no people axis. In the calendar and in the Gantt-style planning view, you do: who has the week full, who has gaps, and — most useful — what work has no owner yet, which is exactly what’s going to slip.

And when something needs moving, which happens every day, it gets dragged to another day. If updating the plan costs more than ignoring it, it gets ignored.

Letting the technician take on work

The other direction, and the one that lightens the planner’s load the most: the technician can see unassigned work orders from the app and take them on themselves, because they know if it’s on their way and whether they have the material.

Watch for a side effect: with an open queue, people tend to grab the easy ones, leaving a residue of hard orders nobody takes. It’s fixed with real priorities and deadlines on incidents, not by closing the queue.

Hours, measured

Without real time tracking you can’t size a team, only supervise it. Hours jotted down from memory at the end of the day always come in low.

The stopwatch built into the order itself fixes that, and from there the reports on hours per technician, non-effective hours, time allocations, working days, absences, and per-supervisor summaries describe reality.

The warning that has to come with using this data

It’s for sizing teams, budgeting, and distributing workload. Not for surveillance.

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

It’s worth saying this openly during rollout, because the suspicion shows up on its own and it’s easier to defuse it early than later.

A licensing detail that shapes this

If the software is billed per user, registering a seasonal temp or a subcontractor is a financial decision, and the temptation to share accounts shows up. As soon as two people log in with the same account, per-technician reports stop meaning anything.

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

Subcontractors are capacity too

A point that gets forgotten when planning: in many operations, half the work is done by people who aren’t on payroll. If those companies aren’t in the system, whoever’s planning sees half the picture — the in-house side in detail and the outside side as an invoice at month end — and sizes things wrong.

Suppliers are registered and receive the orders that belong to them, logging time, materials, and signature just like in-house staff. From there, the workload you see on the calendar is the real workload.

And there’s a connector between GMAO Cloud installations, working both ways, for when the subcontractor also uses it: work moves from one system to the other without an intermediate file and keeping its traceability.

Where to start

With the minimum that makes a plan credible: teams with their supervisor, working days, and holidays. With that, the system can already check availability before generating an order, which is 80% of the value.

Shifts, detailed vacations, and PPE get added later, once work distribution is already running.

What stays out, again

Payroll, contracts, performance reviews, recruitment, formal training. If you need that, you need an HR system, and the sensible thing is for both to coexist: the HR system rules on labor data, the CMMS rules on work planning.

Saying this in the demo itself avoids the meeting where someone asks about payroll.

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