01What a competency policy is for, and who it covers
The aim is that every employee knows what the job expects and what the next one will ask, and that every manager bases a judgement on described behaviour instead of an impression. It applies to the jobs for which the company adopts a competency card. Most companies begin with supervisory jobs and the largest job families, and widen the scope once the first cards have been used for a full cycle.
It does not replace measured goals: a goal says what was achieved, a competency says how. It does not change basic pay or the terms of a contract. It links to the appraisal policy, because competencies are one of the appraisal criteria, and to the training and development policy, because the gap between the required level and the actual one is what a training need is built on.
02The competency framework policy text
[Company name] Competency Framework Policy Version: [number] Effective date: [date] 1. Components 1.1 Core competencies are required of every employee: [names of core competencies]. 1.2 Functional competencies belong to one job family: [names of competencies per family]. 1.3 Leadership competencies are required of anyone with a team: [names of leadership competencies]. 1.4 Each competency has a one-sentence definition and at least three behavioural indicators for each level. 2. Proficiency levels 2.1 Level 1, beginner: performs with direct guidance. 2.2 Level 2, developing: performs independently in routine tasks. 2.3 Level 3, proficient: performs in changing situations and corrects his own work. 2.4 Level 4, advanced: guides others and improves the method. 2.5 Level 5, reference: sets the standard and is consulted outside his team. 3. The level required for each job 3.1 HR agrees with the head of the job family the level required of each competency for each job, and records it on the job competency card. 3.2 One card carries no more than [__] competencies, so that assessment stays manageable. 3.3 The requirement is shown to the employee on hiring or transfer. 4. Assessment 4.1 The direct manager rates each competency with behavioural examples from the assessment period, and the employee rates himself on the same form. 4.2 Examples are recorded with their dates, and no rating is accepted without an example. 4.3 A senior manager reviews ratings that are more than [__] points from the department average before they are approved. 5. Gaps and development 5.1 Gap = required level minus actual level. 5.2 A gap of one level is closed by learning on the job and the manager's coaching. A gap of two levels or more becomes a written development plan with deadlines. 5.3 The plan is recorded and reviewed with the employee every [__] months. 6. Using the framework 6.1 The job advertisement, the interview questions and the candidate scorecard are built on it. 6.2 It is consulted for promotion and for moves to a higher job, together with measured performance. 6.3 It is not used on its own as the ground for a disciplinary penalty. 7. Review and record 7.1 HR reviews the framework every [__] months and adds or removes a competency by written decision. 7.2 Competency cards, assessment results and development plans are kept in the employee file. Approval of the policy [Approver's name and title] Signature: ________ Date: [date] -------------------------------------------------- Job competency card Job: [title] Job family: [name] Approval date: [date] Competency | Type | Required level (1-5) | Behaviour that shows it [__] | core | [__] | [__] [__] | functional | [__] | [__] [__] | leadership | [__] | [__] Employee: [name] Assessment period: [from] to [to] Competency | Actual level | Gap | Behavioural example and its date [__] | [__] | [__] | [__] Development plan: [__] Manager's signature: ________ Employee's signature: ________
03Notes on the clauses of the policy
Clause 1: fewer competencies, stated clearly
A framework with forty competencies is read by nobody. Small companies start with five to seven core competencies and three or four for each job family, and add only when the need appears. Write each one as something that can be seen: "assigns tasks and follows them up" is clearer than "has managerial ability".
Clause 2: a level is a description, not praise
Level 3 is not "very good". It describes what the employee does when the situation changes. A new employee who is proficient in the tasks of his job may sit at level 2 in a competency he has not yet been trained on, and there is no shame in that. Write the indicators so that two different people reading them reach the same judgement.
Clause 3: the requirement differs with the job
The level required in "communication" from a cashier is not the level required from a branch manager. Fixing it on the card before hiring stops an employee being judged against a level nobody asked of him, and it makes the advertisement for the job honest. For the writing side see how to write a job description.
Clause 4: the example comes before the rating
A rating with no example is an impression. A manager who jots short dated examples during the period can rate at the end without selective memory, which is why the second sub-clause bars any rating with no event behind it. For the bias that creeps into ratings see bias in performance reviews.
Clause 5: the gap is the compass for training
A two-level gap in a leadership competency is not closed by one course. It needs a plan with assignments, a mentor and a review date. For the detail see measuring and closing a skills gap.
Clause 6: the framework does not punish on its own
Competencies describe growth, and it may not show in the numbers at once. Whoever wants a penalty for behaviour follows the violations route with the specific facts, not with a competency rating.
04An example: competencies of a team manager with the weights of the "manager" model
A team manager was appraised with the program's ready "manager" model, whose six criteria carry weights from its catalogue totalling 100. The scores out of 100 are illustrative inputs:
| Criterion | Group | Weight | Score | Contribution |
|---|---|---|---|---|
| Team leadership | Leadership | 20 | 70 | 14 |
| Delegating tasks | Leadership | 15 | 60 | 9 |
| Developing team members | Leadership | 15 | 55 | 8.25 |
| Decision making | Results | 15 | 80 | 12 |
| Meeting team targets | Results | 20 | 85 | 17 |
| Cost control | Results | 15 | 65 | 9.75 |
The contributions total 70 out of 100, which falls in the band "Meets expectations" by the program's band function. The leadership group averages 62.5 and the results group 77.5, so the difference between the two groups shows where development should be aimed. The number of criteria scoring below 65 is 2, and the lowest score is 55, which is where the written plan belongs. These are illustrative inputs. The figures come from the program's performance catalogue and band function.
05When this policy is not applied
Short temporary jobs
A seasonal worker hired for a few weeks does not get a competency card or a development plan. A description of the tasks and the safety instructions are enough.
The decision on basic pay
The framework feeds appraisal and promotion. It does not change basic pay or override the terms of the contract.
Disciplinary procedure
Behaviour that breaches the regulations goes through the violations route, not through lowering a competency rating. For that route see the policies page.
06Difficult cases and common mistakes
A technically strong employee who collaborates badly
Poor collaboration is not covered by technical skill. Record the two competencies separately, set a plan for the second with a specific example, and decide whether the job really needs a high level of it.
Two managers rate the same competency very differently
The indicators are vague or the examples are not recorded. Review the wording of the indicator and ask each manager for an event that supports the rating before any calibration.
Common mistake: a framework copied from another company
Competencies such as "innovation" and "entrepreneurship" in an activity that does not need them turn into a middling score that means nothing. Write what your own jobs really need.
Common mistake: a card that is never reviewed
A framework written once and never revisited falls behind the jobs. Make the annual review an item in HR's calendar.
Common mistake: tying a bonus to the score before people understand it
When a bonus rests on a rating the assessors were never trained to give, appraisal turns into bargaining. Run a learning year before linking pay.
07Steps to adapt the policy to your company
- 1
Choose the job families
Sales, operations, management and support services, for example, starting with the largest by headcount.
- 2
Write the competencies and indicators
Five to seven core competencies, each with a one-sentence definition and indicators for each level, shown to managers from several departments before approval.
- 3
Set the required level for each job
On one card per job, with the head of the job family.
- 4
Train the assessors
One session with real examples from your own activity: an event, its rating and the reason for it.
- 5
Link it to appraisal and training
Bring the competencies in as criteria in the appraisal cycle, and turn the gaps into a training need that goes to the manager.
08Competency framework checklist before approval
9 items
09Frequently asked questions
A skill is a specific ability that can be tested, such as using a program. A competency is a set of behaviours in which skill, knowledge and attitude work together, such as solving problems or dealing with a customer.
Five to eight, split between core and functional, a few more for those who lead a team. The more there are, the less depth the assessor gives to each.
Yes, at a level suited to his job. The formal assessment can wait until after probation while examples are recorded from his first day.
He presents his examples and asks the senior manager to review, and the outcome is recorded. If he is not satisfied he can file a grievance through the complaints and grievances route.
Yes, together with measured performance: they show whether the employee is ready for the level of the next job. For the detail see written promotion criteria.
At least once a year, and whenever the company's activity changes materially or a new job family is added.
