Purpose
Provide assurance that personnel understand and apply training and that identified competence gaps are mitigated and closed.
Objective
Ensure every module has a knowledge check, higher-risk subjects use appropriate scenarios or observation, annual competence review occurs and gaps are reassessed before closure.
Normative
Bitkaya shall assess competence proportionately, restrict higher-risk work where necessary and retain evidence that remediation was completed and effective.
Descriptive
Assessment uses training results together with file quality, escalation timeliness, control testing, incidents, findings, manager observation and annual HR and Compliance review. Competence should be assessed using one or more of: onboarding knowledge checks; annual refresher assessments; supervisor review and observation; practical case review; quality assurance sampling; control testing outcomes; incident or error analysis; and audit or compliance findings. Assessments should test whether employees understand their escalation obligations; when a matter must be referred to Compliance; key onboarding and screening controls; documentation expectations; sanctions stop rules; the difference between internal handling and external reporting; and how to operate within their delegated authority. Where recurring misunderstandings, poor escalation quality, weak documentation, or repeated control failures are identified, targeted remediation must be initiated.
Evidence
- Expected evidence: Module knowledge-check results
- Expected evidence: Scenario, observation and file-review results
- Expected evidence: Annual competence reviews
- Expected evidence: Gap classification and remediation plan
- Expected evidence: Restriction, retraining and reassessment evidence
- Evidence location: source evidence in SYS-ECM-002 Compliance Reporting and Evidence Repository; target Hermes assessment record in Odoo under ISS-HERMES-001.
- Retention: according to the applicable approved policy and Bitkaya record-retention requirements.
- Testing method: sample failed, weak or overdue outcomes and confirm risk mitigation, remediation, reassessment and authorized closure
- Testing frequency: quarterly
Assurance
Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.
- Design status: implemented
Assurance Assertions
- Every module has a recorded knowledge check.
- Higher-risk topics receive practical or scenario assessment.
- Annual competence review is completed.
- Material gaps remain open until reassessment demonstrates readiness.
Relationships
- Policy: POL-TRAIN-001 Training and Awareness Manual
- Process: PRC-RSA-001 Resilience Systems and Assurance
- Procedure: PROC-TRAIN-005 Assess Competence and Remediate Gaps
History
- 2026-07-26: Normalized evidence metadata and separated design status from runtime effectiveness.
- 2026-07-26: Created from the approved Training & Awareness Manual version 1.1.