The HR manager of a garment manufacturer in the Vale do Ave with 120 female employees knows by heart who has their first-aid training up to date — because it is she who keeps the certificates in a blue folder. When the auditor from the buying brand asks for evidence of competencies, the panic is proportional to the number of folders. The issue is not digitising that paper. It is changing who decides what, on what basis — and blocking the assignment of an operator to a production line when their safety certification expired three days ago.
The framing error that costs dearly
Most companies assessing HR software for training ask the wrong question: "where does the system store the certificates?" The right question is another: "can the system prevent an operator without a valid certification from being assigned to a production line?"
The difference is not cosmetic. It is the difference between a digital repository and an HRIS with operational logic. Repositories have existed for 20 years. What has changed is the external pressure — auditors from international brands, sustainability compliance requirements, and a talent shortage that makes every trained employee an asset the company cannot afford to lose through internal disorganisation.
In 2024, 65% of employers in Portugal had difficulty finding professionals with the profile they need — one of the highest talent-shortage figures in the world (ManpowerGroup, 2024). Losing a qualified operator because a certification was not renewed in time is a cost that appears in no budget line, but it appears in line efficiency.
The argument of this article is straightforward: training and competency management on the factory floor only has operational value when it is linked to production planning, performance appraisal and shift scheduling. Everything else is a filing cabinet with a search engine.
What pplPortal records — and why the data structure matters
Competencies and training are not the same thing
The most common error in the initial configuration is treating competencies and training as synonyms. A training session is an event with a date, duration, training provider and certificate. A competency is a state — it can be acquired through training, through accumulated experience, through internal assessment, or through a combination of the three. Confusing the two objects is what produces systems where an operator with 15 years of practice on a hydraulic press appears as "not qualified" because they never attended the formal training, while a newly hired employee with the certificate on paper appears as "fit" without anyone having verified whether they know how to operate the machine.
pplPortal, through the pplAdvanced module, keeps the two objects separate and related. An employee may have competency in "hydraulic press operation" without having attended any formal training — because they were assessed internally. And they may have attended 40 hours of training in "machine safety" without that automatically translating into a certified competency, if the subsequent performance appraisal does not confirm it. This distinction is what ISO 9001 audits and international clients require — evidence of competency, not of attendance in a classroom.
The competency catalogue: building and maintaining it
Before recording anything, the catalogue needs to be defined. In the Portuguese industrial context, the typical error occurs at the two extremes: the overly generic catalogue ("can operate machines") is of no use because it does not distinguish between workstations. The overly granular catalogue ("can operate the Stoll CMS 530 E with program v2.3.1") is impossible to maintain — every firmware update requires a revision of the catalogue, and after 18 months it is out of date and abandoned.
pplAdvanced allows competencies to be structured into families — safety, process techniques, quality, cross-functional — with configurable proficiency levels, typically from 1 to 4 or 1 to 5. Each workstation has a required-competency profile with a minimum level per competency. The system automatically calculates the gap between the required profile and the actual profile of each employee. This gap is the data the production manager needs — not the training history.
Validity periods, renewals and automatic alerts
Certain certifications have legal or contractual validity: health and safety at work training, forklift operation, work at height, first aid. pplPortal records the expiry date and configures alerts with a parameterisable lead time — 30, 60 or 90 days before expiry. The alert does not go only to HR. It goes to the direct supervisor and, if configured, blocks the assignment of the employee to workstations that require that certification. This preventive block is the mechanism that turns HR software into an operational tool — and that justifies integration with production planning.
Attendance recording and post-training evaluation
pplPortal records attendance at training activities — internal or external — hours completed versus hours planned, and supports reaction evaluation (Kirkpatrick level 1) and transfer evaluation (level 3), the latter through a questionnaire to the direct supervisor, 30 to 90 days after the training. The result feeds the employee's competency profile and the decision on whether or not to renew the training provider. Without this feedback loop, the annual training plan is a list of expenses with no evidence of return.
Technical implementation options
| Approach | What it covers | Integration with production | Setup complexity | Typical suitability |
|---|---|---|---|---|
| pplCore + pplAdvanced | Competency catalogue, workstation profiles, gaps, validity periods, alerts | Via REST API with ERP/MES | Medium (4–8 weeks of configuration) | Factories with 50–500 employees running an industrial ERP |
| pplAdvanced + pplTalent | Competencies + gap-driven recruitment | Partial — gap data feeds the vacancy profile | Medium-high | Companies with high turnover and frequent recruitment |
| pplAdvanced + pplEvolution | Competencies + performance appraisal + individual development plan | Indirect — via the employee profile | High (requires a defined appraisal model) | Companies with a dedicated HR structure and more than 150 employees |
| Full pplPortal (Core + Advanced + Talent + Evolution) | Complete cycle: attendance, competencies, recruitment, appraisal, development | Full — all modules share the same data model | High (12–20 weeks) | Industrial groups with multiple units or more than 300 employees |
Decision matrix: what to implement first
| Criterion | Priority: Validity periods and alerts | Priority: Competency catalogue | Priority: Appraisal and development |
|---|---|---|---|
| External audit pressure (client, ISO, OSH) | High — implement first | Medium — required for evidence | Low — not an immediate requirement |
| Turnover above 15% per year | Medium | High — onboarding by workstation profile | High — retention through development |
| Product or line expansion (new workstations) | Low | High — define profiles before recruiting | Medium |
| Application to PT2030/COMPETE (HR digitalisation) | Medium | High — evidence of workforce qualification | High — the development plan is an eligible criterion |
| Integration with an existing production ERP | High — the assignment block requires this integration | High | Low — can come later |
Integration with the factory floor: where most companies fail
The problem of assignment without competency validation
Production planning assigns operators to workstations. Without integration with the competency system, that assignment is blind — the shift supervisor decides based on memory or immediate availability. When the operator does not have the required competency, the problem only shows up in product quality or in the accident. In both cases, the root cause does not appear in the non-conformity report as "operator without certification" — it appears as "human error", and the cycle repeats.
The integration between pplPortal and KORA Productivity — which manages production capture and operational efficiency in real time — allows the assignment of an operator to a work order to be validated against their competency profile. If the competency is missing or expired, the system alerts before the assignment is confirmed. This flow requires a REST API between the two systems, with pplPortal's competency data model exposing the profiles by employee and by workstation. Configuring this integration is the most demanding technical step — and the one most frequently postponed "to phase 2" and never carried out.
Industrial terminals and the employee without email
In a footwear factory in Felgueiras or a garment manufacturer in Guimarães, most operators have neither a corporate email address nor access to a computer. Training and competency assessment have to reach them by another channel. pplPortal supports browser access on a tablet or shared terminal — the employee authenticates with a PIN or card, sees their pending training, confirms attendance and answers evaluation questionnaires. The line supervisor manages their team's profiles from the same interface, without needing to access the HR back office.
This operational detail — email-free authentication, a simplified interface for the occasional user — is frequently underestimated in demos. Ask to see the complete operator flow, not just the manager's dashboard.
GDPR and the competency record
An employee's competency profile is personal data under GDPR and Law 58/2019. pplPortal maintains an audit log of all accesses and changes to the competency profile, with identification of the user who made the change and a timestamp. The employee has the right to access their own profile — the self-service portal covers this requirement without HR intervention. Where the company is required to have a whistleblowing channel (Law 93/2021, for organisations with 50 or more employees), the same principle of access separation applies: the line supervisor cannot see appraisal data that does not concern them, and HR cannot alter training records without leaving a trace.
What works in practice
Pattern 1: start with critical validity periods, not with the complete catalogue
The temptation is to build the complete competency catalogue before switching the system on. It is the slowest route and the one that most frequently results in abandonment halfway through — because the exercise of mapping all the competencies of all workstations takes months, exhausts the HR team, and in the end the catalogue is already out of date before it goes into production. The pattern that works is the reverse: identify the 5 to 8 competencies with legal or contractual validity — OSH, forklifts, work at height, first aid, operation of certified equipment — load only those, switch on the alerts, and let the catalogue grow organically as performance appraisals take place.
A typical textile factory of 80 to 120 employees can, in this model, have the system operational in 6 to 8 weeks — with immediate impact on audit preparation — without needing a 6-month competency-mapping project.
Pattern 2: link the competency gap to the annual training plan
The annual training plan — mandatory for the single report (relatório único) and for eligibility for PT2030 support — ceases to be a bureaucratic exercise when it is generated from the system's real gaps. pplPortal exports the list of employees with a gap per competency, HR groups them by competency family, and the plan results from data rather than from the training manager's intuition. For applications to PT2030 and COMPETE, evidence of a competency management system with an individual development plan is a qualification criterion that can make a difference to the technical score.
Pattern 3: use pplTalent to close the loop with recruitment
In Portugal, the average voluntary turnover in organisations was 10.6% in 2023, with 52% of companies admitting difficulty in retaining talent (Mercer, 2023). When turnover is this high, replacement recruitment is frequent and urgent — and urgency is the enemy of hiring quality. The most efficient pattern is to use the workstation's competency profile to automatically generate the vacancy profile in pplTalent, instead of rewriting the job description each time. The candidate is assessed against the same catalogue, and the gap at the point of entry is recorded as the starting point of the development plan.
This closes the loop: the employee joins with a known gap, is trained on the basis of that gap, is assessed against the workstation profile, and their departure — if it happens — automatically generates a vacancy with the correct profile. See how pplPortal detects departure signals before they happen — the unresolved competency gap is one of those signals.
Trade-offs by operational dimension
Configuration cost versus maintenance cost
A detailed competency catalogue costs more to configure and more to maintain. Every time a production process changes — a new machine, a new product, a new line — the catalogue needs to be updated. If there is no person designated for this maintenance, the catalogue degrades within 12 to 18 months and becomes useless again. The rule of thumb: the catalogue should have the minimum number of competencies that allows assignment and training decisions to be made. It is not an inventory of everything employees know — it is a decision model. Every competency that enters the catalogue should answer the question: "which operational decision is improved by this data?"
Integration versus standalone
pplPortal in standalone mode — without integration with the production ERP — has limited value in an industrial context. The KPI that justifies the investment is the reduction of non-conformities caused by incorrect operator assignment, and that KPI is only measurable when the competency system is linked to the production system. Without integration, the value is confined to HR — useful for audits, but with no impact on the line. For companies that already use the MULTI ERP, integration with pplPortal is the natural path. For companies with other ERPs, integration via API is possible but requires prior mapping of the data model for workstations and work orders.
HR autonomy versus IT dependence
pplPortal was designed so that HR can configure and maintain the competency catalogue without IT intervention. Creating competencies, defining workstation profiles and managing validity periods are back-office operations accessible to the HR user. Integration with external systems — ERP, MES, access control — requires IT in the initial phase, but not in routine operation. This balance is relevant to the Portuguese reality: the IT manager in an industrial SME is frequently a person with multiple roles, and a system that requires technical intervention for routine operations is a system that will be abandoned.
How to measure success after implementation
Adoption metrics
- Percentage of employees with a complete competency profile — target: above 90% in 6 months
- Percentage of workstations with a defined competency profile — target: 100% of critical workstations in 3 months
- Number of validity alerts processed versus number of certifications expired without an alert — target: zero unalerted expirations
- Average time between validity alert and certification renewal — target: less than 30 days
Operational impact metrics
Monitor the number of assignments blocked due to a missing competency. This number should exist and be visible — if it is zero, the system is not integrated with production or the workstation profiles are empty. Reducing non-conformities attributable to an unqualified operator requires a pre-implementation baseline: collect this data before switching the system on, or the before/after comparison will not be possible. The time to prepare for a competency audit — how long HR takes to gather evidence when the auditor arrives — is the easiest metric to measure and the one that most impresses top management. A downward trend in the average competency gap per department over time is the indicator that the training plan is having an effect.
HR metrics
Cross-reference competency gap data with absenteeism data and performance appraisal data. Employees with a high gap and a low appraisal have an above-average probability of leaving — this cross-reference is what pplTalent's predictive machine learning module calculates automatically when it has sufficient data, typically 12 to 18 months of history.
Implementation procedure: the steps that cannot be skipped
- Mapping of critical workstations — before opening the system, identify the 10 to 20 workstations where a missing competency has a direct consequence for quality, safety or compliance. These are the workstations that justify the investment and where the impact will be visible most quickly.
- Definition of the minimum viable catalogue — for each critical workstation, list the mandatory competencies with legal or contractual validity. Do not build the complete catalogue at this stage.
- Initial data load — load the history of existing training and certifications (paper, email, Excel). This step takes longer than expected — set aside double the estimated time. Historical data is rarely in a consistent format, and cleaning it is manual.
- Configuration of alerts and workflows — define who receives each type of alert (HR, direct supervisor, production manager) and with what lead time. Test with real data before switching it on for everyone.
- Integration with the production system — configure competency validation in operator assignment. This step requires the involvement of IT and the production manager. Do not delegate it to IT alone — the production manager must validate the blocking logic, because they are the one who will deal with the alerts day to day.
- Training of key users — the HR staff who will maintain the catalogue, the line supervisor who will manage their team's profiles, and the operator who will use the terminal. These are three profiles with completely different training needs that should not be mixed in the same session.
- Catalogue review at 90 days — after 3 months of operation, review the catalogue based on actual use. Competencies that are never consulted are candidates for removal. Situations not covered by the catalogue are candidates for addition.
The detail the manuals do not mention
The greatest risk in a competency management project is not technical. It is political. The line supervisor who has always decided who goes where will resist a system that validates — and eventually blocks — their decisions. If this alignment is not achieved before implementation, the system will be bypassed within weeks.
We see this pattern repeat itself in factories across every sector. The line supervisor is not ill-intentioned — they are someone who built their authority on the tacit knowledge of who knows what, and who interprets the competency system as a threat to that authority. The solution is not technical. It is a matter of process: the line supervisor has to be part of defining the workstation profiles, not a passive recipient of a catalogue built by HR in isolation. When the line supervisor recognises their own knowledge in the catalogue, resistance to automatic validation disappears — because the system has become the formalisation of what they already knew, not an external imposition.
This alignment is also what distinguishes a successful 6-month project from an 18-month project that ends with the system used only for audit reports. The difference between the two is not in the software — it is in who was in the room when the workstation profiles were defined.
For those assessing the performance appraisal component in parallel, the article Performance appraisal in the factory: from the form to the real decision details how pplEvolution structures this process without making it bureaucratic. And for those who want to understand how schedules and shift management tie in with competency profiles, Rotating schedules and shifts: what pplPortal solves that Excel cannot is the next step.
A competency management system that lives only in HR is an expensive filing cabinet. A system that blocks a production assignment because the certification expired three days ago is operational infrastructure. The difference lies in the integration — and in the decision to actually switch it on, not merely to plan it.
Sources
- ManpowerGroup, Talent Shortage Survey 2024 — talent shortage in Portugal (65% of employers with recruitment difficulty).
- Mercer, Total Remuneration Survey Portugal 2023 — average voluntary turnover of 10.6% and retention difficulty in 52% of companies.
- Regulation (EU) 2016/679 (GDPR) and Law No. 58/2019 — protection of personal data, including employees' professional profile and competency data.
- Law No. 93/2021 — general regime for the protection of whistleblowers, with the obligation of an internal channel for organisations with 50 or more workers.
Frequently asked questions
What is the difference between competency and training that pplPortal distinguishes?
A training session is an event with a date, duration and certificate. A competency is a state that can be acquired through training, accumulated experience or internal assessment. pplPortal keeps these two objects separate and related, allowing an operator to be recorded as competent without formal training, or with training but no competency confirmed by the performance appraisal.
How does pplPortal prevent an operator without a valid certification from being assigned to production?
The system records certification expiry dates and configures alerts with a parameterisable lead time (30, 60 or 90 days). If configured, it automatically blocks the assignment of the employee to workstations that require that expired certification. This preventive block integrates with production planning, turning the HR software into an operational tool.
What is the most common error in building a competency catalogue?
Both extremes are harmful: an overly generic catalogue ("can operate machines") does not distinguish between workstations; an overly granular catalogue (with specific firmware versions) is impossible to maintain and quickly becomes out of date. pplAdvanced structures competencies into families with configurable proficiency levels, avoiding both problems.
What is the "competency gap" that pplPortal calculates?
The system automatically compares the profile of competencies required for each workstation (with a minimum level per competency) with the actual profile of each employee. This gap — the difference between what is required and what is current — is the data the production manager needs to make operational and training decisions.
How does post-training evaluation work in pplPortal?
The system records attendance, hours completed versus planned, and supports immediate reaction evaluation and transfer evaluation (30 to 90 days afterwards) through a questionnaire to the direct supervisor. This feedback feeds the employee's competency profile and the decision on renewing the training provider.
For what company size is the pplCore + pplAdvanced approach suitable?
This combination is suitable for factories with 50 to 500 employees that have an industrial ERP. It covers the competency catalogue, workstation profiles, gaps, validity periods and alerts, with integration via REST API with the ERP/MES. Setup complexity is medium, requiring 4 to 8 weeks of configuration.
Why does training management linked to production planning have more value?
When training and competency management is linked to production planning, performance appraisal and shift scheduling, it becomes operational. Without this integration, the system is just a filing cabinet with a search engine. The link allows improper assignments to be blocked, gaps to be calculated and decisions to be made that affect line efficiency.