Define the requirement
Start by deciding which competencies apply to which roles or staff groups.
Define the task, the expected standard and the conditions in which it must be demonstrated. A broad label such as ‘manual handling competent’ is hard to assess consistently without observable criteria.
Clear rules for Training by role make reporting easier and reduce inconsistent sign-off decisions. Treat training completion and demonstrated competence as separate records where the work requires both.
Record the assessment outcome
Capture the assessor, outcome, date, evidence status and any follow-up action.
Also record the assessment method: observed practice, questioning, work sample or another agreed method. The assessor should know what would count as competent, needs development or not yet assessed before the review starts.
SkillProof supports activity records for forms, checklists and sign-offs that can be connected to staff profiles.
Review gaps
Managers need a gap view, not just a collection of completed forms.
Use reports to review missing competency records and evidence across teams. Review requirements after role, equipment or process changes rather than assuming an old sign-off is still sufficient.
Where a reassessment is needed, give it an owner and due date. Do not silently convert an expired or superseded assessment into a current pass.
How to implement a competency management system
Implement the system around one defined role or team before expanding it. Start with the organisation's own standards and decide how each requirement will be assessed, evidenced, reviewed and reassessed.
Use the pilot to test whether managers understand the outcomes, whether evidence can be reviewed consistently and whether gaps lead to owned actions. Expand only after the records and responsibilities are reliable.
- Define role standards and observable criteria
- Choose the assessment methods and acceptable evidence
- Identify the current records and evidence that can be migrated
- Configure roles, permissions, reviewers and reporting access
- Pilot the workflow with one role or team
- Review gaps and assign development actions
- Set reassessment or review dates
- Expand after the pilot produces reliable records
Official guidance used for this guide
Checked
The HSE describes competence as a combination of training, skills, experience and knowledge, plus the ability to apply them safely. A certificate alone may therefore be insufficient for a hands-on task.
Questions this guide answers
What is the difference between training and competence?
Training records that learning took place. Competence also considers whether the person has the skills, knowledge, experience and ability to apply them to the expected standard in the relevant setting.
What should a competency record include?
Record the requirement, observable standard, assessment method, assessor, outcome, date, supporting evidence, review or reassessment date and any development action.
Is competency management the same as a skills matrix?
Not exactly. A skills or competency matrix can summarise gaps across people and roles. Competency management also covers the underlying standards, assessments, evidence, sign-offs and reassessment actions that explain each status.
How do I implement a competency management system?
Define the standards for one role, choose assessment and evidence rules, configure reviewers and permissions, then pilot the workflow with one team. Review the gaps, assign actions and set reassessment dates before expanding it across the organisation.