Training and competence tracking in one traceable flow.
Most organisations know roughly who needs training. Far fewer can say, on any given day, whose certificate has lapsed, which planned session never ran, or whether last quarter's training budget was actually spent on the right people. Tenderely BPM connects the competence requirement, the training plan, the session, the attendance record and the approval into one flow — attached to the person records you already have — without code.
What does a training and competence process repeat?
01
Defining what is required
Every role or job has competences attached to it. Without a catalogue of those requirements, training becomes reactive — something is learned after the gap is felt.
02
Planning sessions
A course has dates, a trainer, a venue and a maximum number of seats. Coordinating those four variables for each session is its own small project.
03
Recording attendance
Who was invited, who actually attended, who left early. When attendance is not logged per session, certificates are issued on assumption.
04
Tracking validity per person
A first-aid certificate is good for two years. A forklift licence must be renewed annually. When those expiry dates live in a spreadsheet, lapses go unnoticed.
05
Managing the certificate archive
Issued certificates need to be stored, retrievable during an audit and linked to the person who holds them, not buried in a folder nobody maintains.
06
Requesting and approving new training
An employee identifies a training need, a manager approves it, a budget line is checked. Without a structured flow, those three steps happen over e-mail and leave no record.
Where does this break down today?
Validity lapses are discovered late
A certificate expires on a Tuesday. Nobody notices until a client audit or a regulatory inspection asks for it. The gap was always there — it just was not visible.
Attendance is recorded inconsistently
Some trainers use a sign-in sheet, some use a chat message, some use nothing. Certificates are issued based on who thinks they remember who attended.
Training requests disappear into e-mail
A request is sent, a manager replies, a budget owner is CC'd. Three weeks later nobody can say whether it was approved, rejected or simply forgotten.
The competence picture never exists in real time
How many people currently hold the required competence for a given role? The answer requires someone to open a spreadsheet, cross-reference a certificate folder and do arithmetic. By the time they finish, it is already out of date.
What changes with Tenderely BPM
01
Requirements are structured, not remembered
The competence catalogue sits inside the platform alongside the person records. What each role requires is defined once and consulted every time, so gaps appear automatically.
02
Sessions carry their own attendance grid
Each planned session holds its own list of who was invited and who confirmed attendance. The attendance record is part of the session, not a separate document filed somewhere else.
03
Validity reminds itself
Give a competence an expiry period and the platform warns the person, their manager or an HR contact before the deadline passes. The lapse does not wait to be discovered.
04
Certificates are attached to the right record
A scanned or issued certificate lives on the person record it belongs to. During an audit, finding it is a search, not an excavation.
05
Training requests follow a real approval flow
With Tenderely, a training request is a structured record. It moves through manager and budget-owner approval steps with SLA reminders, without any of it happening over e-mail.
06
The competence picture is a dashboard, not a project
Who is qualified, who is expiring soon, which sessions are planned and which never ran — these become numbers that are simply there, not a report someone has to compile.
FAQ
Does this module connect to our existing employee records?
+
Yes. The training module is designed to bind to the person form you already have in your Tenderely workspace. Competences, session attendance, certificates and validity records all attach to the same person record rather than creating a parallel set of data.
Can we track different validity periods for different competences?
+
Yes. Each competence in the catalogue carries its own validity period. The platform tracks expiry per person per competence and triggers reminders before the deadline, so a first-aid certificate and an equipment licence can have entirely different renewal cycles without any extra configuration.
Can an employee request training themselves, or is it only managed top-down?
+
Either way. An employee can raise a training request that then travels through a configured approval flow — manager, budget owner, or both in sequence or in parallel. Alternatively, HR or a manager can plan sessions and assign participants directly. Both paths produce a traceable record.
Can external trainers or participants submit anything without a system account?
+
Yes. A public form can be shared as a link with an external trainer or a participant who is not an internal user. What they submit lands on the correct record inside the platform. They do not need an account to contribute.
Who can see training and competence data?
+
Role- and unit-based permissions decide who sees what. An employee can be limited to their own records and upcoming sessions. A line manager can see their team. An HR administrator can see the whole organisation. Sensitive fields, such as assessment scores, can be restricted to specific roles.