74.1% of planned hires for general maintenance and industrial mechanics technicians are expected to be difficult to fill by the employers concerned. The figure is 52.9% for electrical maintenance and control systems. Across metalworking and maintenance occupations as a whole, the difficulty rate exceeds 70% nationally, according to 2026 shortage-occupation data published by the sector's training bodies (OPCO).
What comes next is familiar: review the pay scale, increase the referral bonus, polish the job ad, open apprenticeship positions, work on the employer brand. All of it works. The problem lies elsewhere: these levers don't create technicians, they move them around. Every successful hire in a tight labour market is a technician taken from a competitor, a client or a manufacturing site that will in turn replace them by bidding higher. You're playing a zero-sum game, with a payroll that climbs at every round.
Demographics won't turn around for another ten years
Today's tension is not a blip in the cycle. It comes from an imbalance between people leaving and people arriving: the cohorts retiring from technical trades are larger than those entering initial training, and that gap runs across the whole of the coming decade. No recruitment campaign fixes an age pyramid.
The real cost of these departures isn't the vacant position, it's what walks out with it. A technician with twenty years in the field knows which panel at which customer site has had an earthing fault since 2016, which compressor struggles to restart below five degrees, when to call the site operator rather than force the issue. None of this is written down anywhere. It leaves through the door on the day of the farewell drinks, and the replacement rebuilds it at your expense, in failed jobs and return visits.
Apprenticeship is the answer most often cited. It's a fair one, but it's slow and it carries a hidden cost: the mentor. Training an apprentice means tying up precisely the senior technician who is already overloaded, the one you need out on jobs. You fund tomorrow's capacity by cutting into today's.
Change the metric: how many jobs per technician per year?
Frame the question differently. You're not looking for technicians, you're looking for field capacity. Recruitment is one way to get it, it isn't the only one, and right now it's the most expensive and the least reliable.
Do the arithmetic on your own organisation. A branch with twelve technicians that gains 10% in usable capacity has 1.2 positions it doesn't need to open this year. Unlike a hire, nobody is competing with you for that gain, it doesn't depend on the local job market, and it isn't renegotiated six months later.
Three untapped sources exist in almost every maintenance business. They're rarely treated as operational priorities because they don't show up on any dashboard.
Cutting a junior's time to autonomy from eight months to eight weeks
A junior technician isn't slow because they lack technical skill. They're slow because they lack context. They arrive at a site they don't know, in front of a machine whose history they don't have, with no way of telling whether the displayed fault is recurring or new, and no idea who to call on the customer side. So they phone the senior, come back the next day with the right part, or treat the symptom.
That context can be supplied. A technician who opens a tablet in front of the asset and immediately finds:
- the last ten jobs on that specific machine, with reports and photos;
- the step-by-step task list, check points and expected values;
- the parts already replaced and their actual part numbers, not the catalogue ones;
- site specifics: access, lockout/tagout, contact person, permitted shutdown windows;
- the faults already encountered and how they were diagnosed;
…is working in conditions that bear little resemblance to the previous situation. They don't become an expert, but they do become self-sufficient on the 80% of jobs that don't call for expertise. The threshold at which you're willing to send them out alone moves forward by several months.
The benefit is twofold, and the second part matters more: every call they don't make to the senior is an interruption the senior doesn't take. In a team of ten where three people carry the knowledge, those interruptions add up to a considerable number of hours — invisible, because they aren't booked against any job.
The hours you pay for and never invoice
Take one technician's timesheet over a full week and break it down honestly: time on site, travel time, admin time. The result is almost always worse than management's back-of-the-envelope estimate.
Two of these lines shrink without asking anything of anyone. The first is travel: a route built in the order requests came in rather than by geography, an emergency call-out assigned to whoever is free rather than whoever is closest, a return trip to the depot for a part that could have been loaded that morning. The second is re-entering data. A report scribbled on site on Tuesday, typed up on Friday evening, re-keyed on Monday by the office to raise the invoice: the same information handled three times. At thirty minutes a day per technician, you're at roughly 2.5 hours a week, in the order of 5 to 6% of working time — across ten technicians, the equivalent of a half-time post.
These hours require no recruitment. They require the report to be entered once, on site, by the person who did the work, and to feed the quote and the invoice directly.
Capturing senior know-how while they're still here
If you know a technician is leaving in eighteen months, you have eighteen months to transfer what they know. Not by arranging a two-week handover at the end, which transfers nothing: by turning each of their jobs into written material.
In practice, that means giving them responsibility for writing the task lists on the assets they own, and building that time into their planned workload — a few hours a month, recorded, not unpaid goodwill on a Friday afternoon. It also means asking them, for every non-trivial fault, to write down not the repair but the diagnostic path: what they suspected, what they measured, why they ruled out a given hypothesis. That's the part with real value, and it's the part nobody ever writes down.
A task list written by a senior technician is worth more than the manufacturer's documentation, because it reflects the site as it actually is: the valve that isn't where it should be, the workaround approved by the site operator, the tolerance the machine has been out of since 2019. A manual describes new equipment under ideal conditions. Your technicians are working on something else.
The trade-off to make this year
These three levers rest on the same foundation: an up-to-date asset register, accessible in the field, where history builds itself because reports are entered there. That's the core function of a CMMS like Yuman, but the tool produces nothing if nobody decides that filling in a task list is part of the job.
Keep recruiting, obviously. But set the full cost of a hire — direct sourcing or agency fees, ramp-up period, mentor time, the risk of losing them within a year — against what it costs to structure your knowledge base. The second budget is smaller, and above all it doesn't evaporate when a technician resigns.
In five years' time, the maintenance companies still standing won't be the ones that recruited best. They'll be the ones that need fewer people to look after the same asset base.