Technician & Team Management
The right person, matched to the job
When a breakdown call comes in at 2 AM, the question isn't just "what broke" — it's "who on this shift actually knows how to fix a servo drive, and what will it cost to send them." Most plants answer that from memory or a WhatsApp group. AssetAI keeps the technician's skills, certifications, cost and past performance on record so the work order can answer that question in one click, without pretending to solve HR problems it was never built for.
The Staff Master: One Record Per Person
Every technician, contractor and vendor resource gets a profile with an auto-generated employee code, photo, date of birth, gender, national ID and PAN, employment type, joining date, branch, department, designation, grade, shift, base location, reporting manager and an active flag. This matters on Indian shop floors where the workforce is a mix of permanent staff, contract labour and vendor technicians who rotate in and out — you need one place that tells you who someone reports to and whether they're still active, regardless of which category they fall into.
Only a Company Admin can open the Staff screen, which keeps sensitive ID and salary data out of general access. A few guardrails exist by design: you can't deactivate your own account, editing your own profile always re-adds the Company Admin role so you don't accidentally lock yourself out, and Super Admin itself can never be assigned as a role to anyone. If your plan has a user limit, creating staff beyond it is blocked with the exact limit named in the message — no silent failures.
Skills and Certifications, Matched to the Asset
Skills come from a master list, and each technician's link to a skill carries a level — beginner, intermediate or expert. Assets carry their own required skills, so a hydraulic press and a PLC panel can demand different expertise without you having to remember it.
- Certifications are logged per person with issuing body, valid-until date and a supporting file up to 8 MB, with alerts before they expire — useful for boiler operators, crane operators or anyone working under a statutory certificate.
- Skill levels give you a quick read on bench strength — how many expert-level electricians you actually have versus how many are still beginners.
- This structure is what powers the technician suggestion on the work order (below) — it's the same data feeding two different screens.
We deliberately don't try to be a training or LMS-style tracker beyond this — it's skill and certificate data tied to the person and the asset, not a course catalogue.
Suggesting the Right Technician on a Work Order
Open a work order against an asset and AssetAI looks at active users whose skills intersect that asset's required skills, ranks them by number of matches, and shows each one with their hourly rate. One click adds the top match as a pre-costed labour line — no separate costing exercise after the job is done.
Be clear about what this ranking does and doesn't consider: it's purely a skills match. It does not check whether the technician is on leave, already loaded with three other breakdowns, whether their certification has lapsed, or what their rate does to the day's budget. If you run a 40-machine unit with two shifts and one competent instrument technician, the system will still suggest them for every instrumentation job on every shift — it won't tell you they're double-booked. Read that as the tool it is: a fast way to find who's qualified, not a scheduler. For plants that need capacity-aware assignment, that's a manual judgement call layered on top, not something AssetAI resolves for you — a distinction worth understanding before you rely on it, and one covered in more depth on Maintenance Scheduling & Planning.
Costing Labour Without a Payroll System
Every technician, whether on the payroll or on a vendor's, carries a costing basis — monthly or hourly. If only a monthly salary is entered, AssetAI derives the hourly rate by dividing by 208 standard monthly hours, a fixed divisor rather than a variable you configure per person. Overtime rate, vendor rate and a timesheet-required flag are also stored against the profile.
- The timesheet-required flag is a policy marker only — there's no timesheet entry screen behind it. Labour hours still get typed manually as work-order lines, the same way they would for any technician.
- Vendor rates let you cost external labour the same way as in-house staff, which matters when a shutdown job pulls in three vendor electricians alongside your own team.
- None of this replaces payroll. AssetAI has no attendance, leave or payroll processing — shift is a reference field on the profile, and nothing schedules or pays against it. If you're looking for an HR or payroll system, this isn't it; if you're looking for accurate labour cost on a work order, it is.
Performance, Availability and What They Don't Cover
Each technician carries a performance card built from the work orders they were responsible for: on-time percentage, average MTTR in hours, and a rework count derived from repeated breakdowns on the same asset. Over a few months this tells you, in plain numbers, whether your "best" technician is actually closing jobs on time or just getting assigned the easy ones. It's a useful companion to asset-level OEE tracking, since a technician's rework rate often explains why an asset's uptime isn't improving despite frequent attention.
Availability, working days, emergency availability, on-call status and maximum hours a day are all stored on the profile — defaults are Monday to Saturday and 8 hours a day, editable per person. But these are set by hand. Nothing recalculates availability from open work orders, and nothing stops you from assigning a technician who's marked busy or on leave. Treat these fields as information for a human planner, not as an automated roster — this product has no shift-roster engine, and if that's what you need, it's worth checking what your plant actually requires against the fuller list on /features.
When someone new is made responsible for a work order, they get an assignment notification — so a handover between shifts doesn't depend on someone remembering to make a phone call.
Access by Role, Not by Guesswork
Seven built-in roles cover the common structure of a maintenance team, with a per-company permission matrix you can edit — so what a technician sees can differ plant to plant. The Technician role, by default, gets asset view, breakdown reporting, work orders and raising requisitions, but no access to spares or vendor screens, which keeps procurement decisions with the people meant to make them.
There's no separate mobile app login for technicians, and no GPS or field check-in — access runs through the same web-based roles as the rest of the system. If your technicians are multi-lingual and split across mezzanine floors or a scattered layout, that's a real constraint worth weighing; some plants manage it with shared tablets logged in under a technician's role rather than individual devices. For a broader sense of how this fits into a maintenance function, What is a CMMS is a reasonable starting point, and our /industries and /use-cases pages cover how plants across different sectors structure their teams around it. If you'd rather talk through your specific staff structure than read about it, book a demo.
Rolling It Out Without Losing a Week to Data Entry
The biggest rollout mistake is trying to load every technician's full history on day one. Start narrower:
- Build the skill master list first — weld, hydraulics, PLC, servo drives, boiler operation — before you start tagging individual users. A messy skill list makes the technician suggester noisy for everyone downstream.
- Tag required skills on your most critical assets first, not all of them at once. If you haven't run a criticality assessment yet, that decides which machines need this rigour on day one and which can wait.
- Enter employment type honestly — internal, contract, vendor — from the start. It's a one-time field but it's what later tells you, at a glance, how much of your maintenance labour is actually on your own payroll versus borrowed.
- Upload certification files (up to 8 MB) as you onboard, not retroactively. A boiler operator's license or a vendor's electrical safety certificate is easier to scan once than to chase six months later when the expiry alert fires.
What to Watch Once the Data Is Live
Once work orders start closing against named technicians, three numbers on the performance card are worth a monthly look: on-time percentage, average MTTR in hours, and rework count. Used well, these flag training gaps and skill mismatches — not people to blame. A technician with a high rework count on the same asset usually means the skill level tagged against them (beginner, intermediate, expert) doesn't match what that machine actually needs, and MTTR trends feed the same repair-time thinking that sits behind OEE. Certification expiry alerts deserve equal attention — a lapsed license quietly sitting on a profile is the kind of gap that only surfaces during an audit or, worse, an incident.
Roles Are a Starting Point, Not a Lock
The seven built-in roles ship with sensible defaults — a Technician, for instance, gets asset view, breakdown reporting, work orders and requisition raising, but no spares or vendor access. Most plants leave it there and regret it later, either because a senior technician needs requisition approval or because a contract resource has more access than the plant head realised. The permission matrix is editable per company for exactly this reason — review it once during rollout rather than after someone's raised a purchase order they shouldn't have.
Where This Module Stops
Worth saying plainly: this is not attendance, leave or payroll software, and it doesn't try to be. Shift is stored as a reference field, not a roster — nothing schedules against it, and nothing here processes salaries beyond deriving an hourly rate. There's no timesheet capture screen either; if the timesheet-required flag is on, hours still get typed manually as work-order labour lines. There's no separate mobile app or GPS check-in for field technicians. And the technician suggester itself ranks purely on skill match — it doesn't know if someone is on leave, already loaded with six open work orders, or has a certification that expired last week. That judgement stays with the maintenance head, especially on plants running contract labour across shifts or coping with the kind of unplanned downtime a power cut brings. For everything else this connects to — work orders, scheduling, and the wider standards context — ISO's maintenance-related standards are a reasonable place to benchmark against once your staff data is clean.
Technician & Team Management FAQs
How do I check which technician has the right certification before assigning a breakdown?
AssetAI stores each technician's certifications as part of their Staff Master profile, so you can check qualification before assigning a breakdown instead of relying on memory or a shift WhatsApp group. The certification field sits alongside designation, grade, department and employment type, so a Company Admin can filter staff by these attributes when a work order needs a specific skill — for example, someone certified on servo drives rather than general electrical work. Because the profile also carries an active flag, technicians who have left or moved departments don't show up as available options. This keeps the qualification check part of the same record used for cost and performance, rather than a separate spreadsheet. For background on how this fits the wider system, see what a CMMS actually does.
How does AssetAI track the cost of sending a contractor versus a permanent technician?
AssetAI records technician cost as a field on the individual's profile, not a separate payroll module, so a work order can show the cost of sending a particular person regardless of whether they're permanent staff, contract labour or a vendor technician. Because employment type is recorded alongside cost, base location and shift, the same Staff Master entry works whether the person is on your rolls or rotates in from a vendor. This means the decision of who to send and what it costs pulls from one record rather than cross-checking a vendor invoice or HR sheet. It doesn't replace invoicing or contract management; it only surfaces the cost already on file at the point a work order is raised. See how this sits with other data points on the features page.
Can I see a technician's past work order performance before assigning a new job?
Yes, AssetAI keeps a technician's past work orders linked to their profile, so you can review their history rather than going on general reputation when deciding who to send. Because every completed work order ties back to the technician who did it, the record builds up over time within the same Staff Master entry that holds skills, certification and cost. This is useful when comparing two people with similar designation and grade but different track records on a particular asset type. It doesn't score or rank technicians automatically — it just keeps the history attached to the person so whoever is assigning work can look before making a call. For a broader view of how this fits maintenance workflows, see maintenance use cases.
How does AssetAI handle technician availability across different shifts in a 24/7 plant?
AssetAI records each technician's shift and base location as fields in their profile, so assigning work at any hour can account for who is actually on site rather than guessing. Because shift is stored alongside reporting manager and active flag, a supervisor can see which shift a person belongs to without pulling a separate roster. This matters on Indian shop floors where permanent staff, contract labour and vendor technicians may all follow different shift patterns at the same plant. The field doesn't build or rotate shift schedules automatically — it records what's already assigned so the information is available the moment a work order is raised and someone needs to know who's on duty. This sits within the broader set of technician management features.
Can I manage contractor and vendor technicians alongside permanent staff in the same system?
Yes, contract labour and vendor technicians are recorded through the same Staff Master screen as permanent staff, distinguished by an employment type field rather than handled in a separate system. Each still gets an employee code, designation, grade, shift, base location and reporting manager, so you know who they report to on-site even though they aren't on your payroll. When a vendor technician's assignment ends, a Company Admin can switch off their active flag rather than deleting the record, keeping history intact if they rotate back in later. This matters on Indian shop floors where the workforce genuinely mixes categories on a single line or shift. It's not a vendor contract or invoicing tool — it only keeps the people-side data consistent, which is part of how CMMS platforms are generally structured for mixed workforces.
What happens if I try to add more technicians than my AssetAI plan allows?
AssetAI blocks the creation of additional staff once you hit your plan's user limit and shows an error message rather than letting the record save quietly. This check happens the moment a Company Admin tries to add a new profile, so it's caught immediately rather than discovered later during a billing review. Deactivating staff who have left frees up room within the existing limit, since inactive profiles are kept for record purposes while only the active count is checked against the plan. To add more seats beyond that, the plan itself needs to be changed. Details on how user limits are structured by plan are on the pricing page.
How do I assign preventive maintenance tasks to technicians based on their skill tags in AssetAI?
Create skill tags (e.g., "CNC Operator," "Hydraulics Expert") in technician profiles. When scheduling PM tasks, filter technicians by required skills. AssetAI matches task complexity to certified personnel, reducing errors. You can also set skill expiry dates for recertification tracking across work orders.
See Technician & Team Management on your own machines
A 30-minute demo on your plant, not our slides.