An employee finishes a course somewhere else — a TVTC or IPA programme, an HRDF-funded track, Doroob, a vendor certification like PMP or CFA, a university short course, a MOOC. External credentials are how that learning enters Jadiroon: as a verified record and as evidence, without silently inflating anyone's assessed competency level.
Who records what
The employee records the completion themselves, from My credentials (/{slug}/me/credentials). They either pick a course from the workspace catalog or type in an external one, set the completion date, optionally add training hours, choose an evidence type, and upload the certificate.
HR reviews every submission before it counts for anything. Until an HR admin verifies it, a credential sits at Awaiting review and contributes nothing.
The three evidence types
The evidence type is the single most important field on the form, because it decides what the credential is allowed to do. The employee picks one; the HR admin can correct it at verification time.
- Attendance certificate — an attendance record, a MOOC audit, most Doroob modules. Recorded as evidence and nothing more. It never proposes a competency-level change.
- Course with a graded check — the course ended in a real assessment or gated quiz. After HR verification this may propose a small level change.
- Third-party proctored exam — PMP, CFA, an AWS or Microsoft certification exam. After HR verification this may propose a larger level change.
The line is drawn around whether a validated performance check actually happened, not around how prestigious the provider is. A PMP certificate carries weight because PMI proctors and grades an exam — the bootcamp that preceded it does not.
What happens when HR verifies
Verifying a credential does several things at once:
- The credential moves to
Verifiedand becomes part of the training-participation ledger. - If the completion matches an open formal learning (10%) action on the employee's development plan, that action is marked done. This is plan progress, not a capability signal.
- The certificate becomes visible as evidence next to the competencies the course was mapped to.
- For assessed and proctored tiers only, a competency-level proposal is created for HR review.
Verifying does not move a competency level. Not for any tier.
Competency-level proposals need a second approval
A proposal is a suggestion sitting in a queue at Develop → External credentials, showing the employee, the competency, the proposed level, the evidence behind it, and a link to the certificate. Nothing happens until an HR admin presses Apply.
When applied, the proposed level is merged into the current level at a low weight — it does not replace it. Every other source of competency data in Jadiroon carries more weight than an external credential does, so an applied credential nudges a level rather than redefining it. The change is recorded in the competency's history, tagged as coming from a credential, so it is always auditable.
An HR admin can also Reject a proposal, which leaves the level untouched and keeps the credential as evidence.
Why completion alone does not raise a level
This is deliberate, and it is the most common thing people expect to work differently.
A completion certificate proves exposure — that someone attended, and sometimes that they passed a knowledge check. It does not prove demonstrated capability on the job. In the 70:20:10 model, formal learning is the 10%; the capability that shows up in real work comes from the 70 and the 20. A competency level in Jadiroon is a claim about what someone can actually do, and it is what feeds gap analysis, succession readiness, and internal-mobility fit.
If a two-day exam-prep course could move a level on its own, the cheapest and most procurable signal in the system would quietly inflate the numbers that promotion and succession decisions rest on. So the credential is kept as evidence, the competency is flagged as a candidate for reassessment, and the level moves when an assessment measures it — or when an HR admin explicitly decides the exam result justifies a nudge.
Where competencies for a credential come from
When a credential is submitted, Jadiroon maps it to the competencies it plausibly builds:
- If the course is in the workspace catalog and is already linked to competencies through a learning path, those links are reused directly.
- Otherwise the course title and page are read and mapped to the workspace's own competency catalog, with a contribution strength from 0 to 100 for each competency.
The strength describes how central the competency is to the course content — not how good the learner is at it. It scales how much of the tier's allowance a proposal may use.
Training participation reporting
Develop → External credentials → Training participation report rolls up every verified credential: total credentials, training hours, employees, Saudi employees, and the HRDF-eligible subset, broken down by provider and exportable as CSV.
This is a participation ledger for HRDF and Human Capability Development Program reporting, kept deliberately separate from proficiency data. "How many Saudi employees received HRDF-funded training this quarter" is a question competency levels cannot answer, and should not be asked to.
Not covered yet
Professional licensure — SCFHS registration, SOCPA membership, a TVTC NQF-placed diploma — can be recorded as a credential, but Jadiroon does not yet track expiry, renewal, or CPD hours for it, and never uses it to gate who is legally allowed to practise. Licensure answers a different question from capability, and gets its own treatment in a later release.