Home · Solutions · HR & people
Solution · HR & peopleNobody starts a shift on a permit that ran out last week
Qualifications and training tracked before they expire
Every mandatory training, permit and health clearance sits in one register that reconciles itself nightly and warns the employee and the manager in Teams before the date.
Executive summary
Your training register is only as current as the last time someone remembered to update it.
We build one register and point everything else at it.
Expiries surface weeks ahead instead of on the day, so refreshers are booked in groups, at normal notice and normal prices.
the qualification register in Microsoft Lists; SharePoint evidence library; Power BI compliance model
Business problem
Compliance training
Mandatory qualifications are not one kind of thing. Some are internal courses in the learning system. Some are permits from an external body, printed on a card in someone's wallet. Some are clearances that arrive from a clinic on paper. Some are read-and-understand confirmations against a procedure version. Each has its own source, its own renewal path and its own consequence when it lapses, and no single system was ever asked to hold all of them.
What holds them instead is a workbook. It is accurate on the day it is updated and drifts every day afterwards, and nothing in the daily routine reads it, so the drift goes unnoticed. Meanwhile people change roles, sites borrow operators, new equipment brings new permit requirements, and leavers' rows stay in the file for a year.
The consequence lands on people who did not create the problem. A supervisor learns on Monday that the only crane operator on the roster may not legally use the crane, so the shift is replanned and someone works overtime. Quality opens a deviation because a batch record was signed on a lapsed qualification. HR is asked why nobody was warned, and the honest answer is that the warning depended on somebody remembering.
How it works today
Most companies we meet run some version of this, whatever their industry.
- PersonThe coordinator keeps a workbook per site: one tab for safety training, one for equipment permits, one for medical examinations
- SystemThe learning system records e‑learning completions; nobody exports them into the workbook until an audit is announced
- PersonProviders email certificates to a shared mailbox; the PDFs land in a personal folder and the row is updated if there is time
- WaitingExpiry dates are reviewed when somebody thinks of it, usually quarterly or before a client visit
- PersonReminders go out as individual emails; the employee books a course by replying to the coordinator
- Risk of errorShift planners schedule by name and availability, with no reliable way to see whether a permit is still valid
- Risk of errorThe gap is found by an auditor, by a client's quality team, or after something goes wrong
Why the current process costs more than it appears
The budget shows headcount, not what it is spent on.
- Rushed renewals cost more than planned ones. A course booked at three days' notice is bought at the provider's price and in the provider's slot, for one person rather than twelve.
- Lost production time never lands in the training budget. When a permit lapses, the roster is rebuilt, a colleague is pulled off another task, or the line waits for someone allowed to run the machine.
- Deviations cost out of all proportion to their cause. Work done on a lapsed qualification means an investigation, an impact assessment on the batches concerned, a corrective action and a paragraph in the next audit report.
- Reconstructing evidence consumes senior time when it is scarcest: proving who was trained on what occupies the coordinator, HR and quality for as long as the auditor is on site.
- Everything rests on one person's diligence. If the coordinator leaves or falls ill in an audit window, maintenance stops and nobody can say what is missing.
Cost of inaction
Administration is the smaller cost here, and the only one that is easy to count. What grows quietly is the gap between what the register says and what is true. Every month it widens by the moves, hires and new equipment nobody entered, and the only things that close it are an audit or an incident, each dearer than the maintenance would have been.
There is also a capability question. A company that cannot say who is qualified to do what cannot plan a new shift pattern, take on a customer with stricter requirements, or open a third site without another coordinator and another workbook. The register is not only a compliance artefact; it is the data operational planning has been missing.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
A pharmaceutical contract manufacturer, 1,500 employees across two production sites and a warehouse, running Microsoft 365 E3, an HR system for employment and position data, and a separate learning system.
4,800 tracked qualifications: procedure and GMP training, cleanroom and gowning qualifications, forklift and crane permits, periodic safety training, first aid, electrical permits and occupational-health clearances. Around 380 reach their expiry date every month.
Three workbooks kept by a training coordinator, a learning system that knows only its own courses, certificates from six providers arriving by email, and clinic results delivered on paper.
About twenty minutes of administration per expiring qualification: noticing it, finding the certificate, agreeing a date, booking, chasing, updating the workbook. None of it is visible to the people building next week's roster.
One register reconciled nightly by robots against the learning system, the HR system and the provider mailbox; expiry rules per role; reminders in Microsoft Teams at 30, 14 and 7 days; a booking request from the card; a daily list of assignments the planner should not make; a dashboard and an audit pack that already exists.
In the modelled case the twenty minutes per expiry becomes a confirmation for the routine majority, expiries close before the date rather than after it, and the audit answer is an export rather than a reconstruction. The figures are a model, not a measurement.
Proposed solution
We build one register and point everything else at it. It holds a row per employee and qualification: type, issuing body, certificate reference, valid from, valid to, evidence link and status. Beside it sits the rule set that makes it work: a matrix of role to required qualifications, validity period, renewal lead time and whether a lapse blocks work. Safety and quality own the matrix, and it is versioned, so changes carry a name and a date.
Robots do the collection. Every night they read completions from the learning system, position changes from the HR system and new certificates from the provider mailbox, and match each record to an employee and a qualification type. A new hire or an internal move creates the rows the new role requires; a leaver's rows close. Each status is then recalculated: valid, expiring in 30, 14 or 7 days, expired, or required and never obtained. That last category is the one a spreadsheet never shows.
People meet the register in Microsoft Teams. The employee gets a card at each threshold with the qualification, the date and a button that starts the renewal; the manager sees the same for the team, plus an escalation when a date passes. Planners get a daily list of who cannot be assigned to what, and the evidence library holds the certificate behind every row, which turns an audit request into an export.
Microsoft Lists with version history and item rules; Power Automate scheduled flows and Adaptive Cards in Microsoft Teams; UiPath Orchestrator time triggers, queues and audit; UiPath Integration Service connectors for Microsoft Outlook 365, Teams and OneDrive & SharePoint; Microsoft Purview retention labels
The register model and role matrix, the nightly reconciliation, the status rules, the 30/14/7 reminders and escalation, the booking request, the blocked-assignment list, the Power BI model and the audit export pack
Read access to the learning and HR systems through their APIs, or UI automation where none exist; the qualification feed into shift planning, via Microsoft Graph Shifts APIs where Teams Shifts is used
How the automated process works
- AutomationOvernight, robots collect completions from the learning system, position changes from the HR system and certificates from the provider mailbox
- SystemEach record is matched to an employee and a qualification type; new hires and role changes generate the rows the matrix requires
- AutomationEvery status is recalculated: valid, expiring in 30, 14 or 7 days, expired, or required and missing
- AutomationEmployees get a card in Microsoft Teams at each threshold: the qualification, the date, and a button to request the renewal
- SystemA request enrols the employee in the internal course, or reaches the coordinator with the provider, dates and cost centre
- PersonThe coordinator confirms external bookings and settles what rules cannot: providers without slots, long absences, disputed requirements
- AutomationA daily blocked-assignment list reaches shift planners, and a weekly compliance digest each manager's Teams channel
- AutomationCertificates, status history and the rule applied go to the evidence library, ready to export as an audit pack
Human-in-the-loop model
Automation handles
- Nightly collection and reconciliation of completions, certificates, positions and leavers
- Recalculation of every status against the role matrix, including new hires and internal moves
- Reminders at 30, 14 and 7 days, escalation to the manager, and the weekly compliance digest
- Evidence filing and the audit pack: certificate, dates, rule applied and full status history
People decide
- Which qualifications a role actually requires, and the lead time each renewal needs, owned by safety and quality
- Which provider and which date, when an internal course is full or the permit is issued externally
- Exceptions: long absences, secondments, employees on notice, disputed clearance results
- Whether someone may work while a renewal is pending, recorded with a reason and an approver
Before and after
Systems and integrations
Where a rule suffices we do not use a model. Where judgement is needed, a person decides.
Inputs
- learning system completions
- HR system positions and employment changes
- provider certificates in a shared mailbox
- occupational-health clearance dates
- scanned permits on SharePoint
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- Power Automate
Target systems
- the qualification register in Microsoft Lists
- SharePoint evidence library
- Power BI compliance model
- the shift-planning system
Human touchpoints: employee reminder cards in Microsoft Teams; manager digest and escalation in Teams; the training coordinator's booking queue
Technologies used
holds the qualification register and the role matrix, with version history and item rules
Anightly collection on a time trigger, with queues, retries and audit
Areads provider mail, writes register rows, files evidence, posts to Teams
Areminder and escalation flows, the booking request, and the weekly manager digest
Awhere employees see their dates and start a renewal, and managers see their team
Aevidence library for certificates and audit packs, with retention labels and logging
Acompliance by site, department, qualification type and month, embedded in Teams
Asources of completions, positions, moves and leavers
CIllustrative economic model
Start by questioning the assumptions.
One expiring qualification costs twenty minutes to chase: noticing it, contacting the employee and the manager, agreeing a date, booking, chasing and updating the record. That figure is a model built from typical ranges, not a client result. €26 is a fully loaded hourly cost for HR administration in Central Europe. Replanning, rushed course prices and deviation handling are left out on purpose.
Run the numbers on your data
An illustrative estimate from your own inputs. It models released capacity; it is not a promise of savings.
Business benefits
- Expiries surface weeks ahead instead of on the day, so refreshers are booked in groups, at normal notice and normal prices
- Rosters are built on qualifications that are actually valid, so shifts are not rebuilt on Monday and lines do not wait for a permitted operator
- The register shows what is missing as well as what is expiring, and missing is where most findings come from
- Audit evidence is exported with the certificates attached, instead of reassembled from mailboxes and personal folders
- Next year's training budget is built from a list of dates rather than last year's invoices
The management view
- Compliance becomes a number per site and qualification type, refreshed nightly, rather than an assurance given days before an audit
- Headcount growth stops multiplying the coordinator's workload: the matrix grows, the tracking does not
- Every reminder, booking and override carries a name, a timestamp and a reason
- The process outlives whoever built the spreadsheet, and can be handed over in a morning
Board-level KPIs
Security and governance
Trust in automation is built on the audit trail, not on a promise.
- Service accounts read the learning and HR systems with rights limited to the fields the register needs; the only write-back is course enrolment, and every run is logged
- Register, evidence and reminders stay in your Microsoft 365 tenant; orchestration runs in the UiPath Automation Cloud EU region
- Occupational-health rows carry the examination type, the validity date and the clearance status only; medical content stays with the clinic and access is limited to HR
- Editing the role matrix is a different permission from reading the register; changes are versioned, attributed and signed off by safety or quality
- Certificates carry Microsoft Purview retention labels, and the audit log records who exported which pack and when
Why now
An audit arrives with weeks of notice, not months, and the register shown then has to have been correct all along; it cannot be rebuilt inside the notice period, when the coordinator has least time
EU health and safety law makes training an employer duty that must be evidenced, including on transfer to a new job and on the arrival of new equipment; in regulated manufacturing the record is part of the quality system, not an HR convenience
Nothing here needs a new platform: the register sits in Microsoft Lists, the reminders in Teams, the collection in robots you may already run. The modelled €3,300 a month of administration is the smallest argument on the list
Relevant executive roles
Rosters stop resting on assumptions, and a lapsed permit stops being something a supervisor discovers mid-shift
One register replaces several workbooks, administration falls to exceptions, and the answer to "who is compliant" survives holidays and turnover
Training evidence is complete, versioned and exportable, and lapsed-qualification findings stop repeating from audit to audit
Common questions and objections
It reminds people about the courses it knows. It does not know the forklift permit from an external body, the clearance from the clinic or the procedure training signed on paper, and it does not know that somebody moved into a role needing three more qualifications. It covers one source; the register covers the obligation.
Then keep it there. The register can live in your HR system or in Dataverse as easily as in Microsoft Lists; the robots, the rules and the Teams reminders do not change. We propose Lists when the HR system's change process would turn weeks of work into quarters.
Not to start with. A certificate arrives against a booking the register already made, so the course and dates are known and the scan is filed as evidence. For a backlog of old scans with no matching record, UiPath Document Understanding can read them once, as an add-on rather than a prerequisite.
When this is not the right solution
- A single site with a few dozen tracked qualifications, where a shared calendar and a disciplined coordinator cover it
- Nobody will own the role-to-qualification matrix. The matrix is the substance of this solution and it cannot be automated into existence
- Employees cannot be matched reliably across the HR system, the learning system and provider lists; that link has to be fixed before any register can be trusted
A question for the next management meeting
If an inspector asked this afternoon for everyone working today without a valid qualification, how long would the list take, and would we sign it?
Implementation approach
We start with one slice of the process and extend only once it is proven.
We deliver
- A working session with safety, quality and HR that turns today's requirements into an explicit role matrix with validity periods
- Nightly collection from the learning system, the HR system and the provider mailbox
- Status rules, the 30/14/7 reminder cadence, escalation and the weekly digest in Teams
- The booking request flow, the blocked-assignment list and the Power BI compliance model
- A one-off load of the existing workbooks and certificates, with a report of what does not match
We need from you
- The current registers, however they look, and certificates from the last cycle
- Owners for the matrix in safety and quality, plus one person from HR
- Read access for service accounts to the learning system and the HR system
- The rule to apply when a qualification lapses: warn, block, or block with a documented override
Stages
Discovery
Qualification types, sources, registers, volumes and the owner of each requirement
Matrix and design
Role matrix, status rules, reminder cadence, permissions and the blocking rule
Build
Register, collection robots, Teams reminders, booking flow, dashboard and audit export
Migration and validation
Load existing records, reconcile differences, test the rules on historical expiries
Go-live
One site first, then the rest, with the coordinator watching the first reminder cycles
Quick win. Effort is driven by the number of qualification types, how cleanly employees match across the HR and learning systems, and whether the role matrix exists in writing.
Name everyone who worked on last month's batch and prove each was trained.
Send us the qualification requirements you have today, even as a spreadsheet, with the number of tracked employees and the systems the records sit in. We come back with a written assessment of what can be reconciled automatically and where the register should live.
Find what expires this quarterThe neighbouring process usually has the same problem
Stop retyping site inspections into a register and chasing corrective actions from an inbox.
View solution Legal & complianceAudit-ready for every brand, without the week of panicStop rebuilding the standards file the week before each importer audit and fixing the same finding twice.
View solution Operations & qualityNo driver dispatched on an expired documentDriver and vehicle documents expire on fourteen calendars. Dispatch checks them by asking whoever keeps the file.
View solutionIndustries we deliver this in most oftenManufacturing & industryTransport & logisticsServices & IT