Mission Evaluation and Success Score: How They Work

Summing up an employee's performance over a period in a single number is hard, and a number alone is never enough. Still, award, promotion and development decisions need a comparable measure. How reliable that measure is depends on how well its components are defined.

This article covers mission (responsibility) evaluation, which measures the "work itself" side of performance, and how it combines with competencies and targets into a success score.

What is mission evaluation?

Mission evaluation measures how well an employee fulfils the core responsibilities of their role. Unlike targets, it covers the ongoing, everyday requirements of the job rather than a change for the period. Unlike competencies, it assesses the outcome of a responsibility rather than behaviour.

To avoid confusion with work items in task and project management: here a "mission" is not a task card but an area of responsibility attached to the position.

Department responsibility items

In HibritİK, mission evaluation is based on responsibility items defined per department. Because people doing similar work in the same department are assessed against the same items, results are comparable.

How to write a good responsibility item:

• Concrete: "Checks supplier invoices and submits them for approval before the due date."
• Observable: the manager must be able to see whether it was done.
• Single-focused: do not bundle several responsibilities into one item.
• Reasonable in number: very long lists make the evaluation superficial.

1–5 scoring and mandatory comments

Responsibility items are scored from 1 to 5 by the employee's manager. Writing down score definitions in advance helps different managers use the scale the same way:

Score	Example definition
5	Clearly exceeds expectations; a role model for others
4	Exceeds expectations
3	Meets expectations
2	Partly below expectations; development needed
1	Clearly below expectations

Rather than leaving everything to the end of the period, managers who keep short notes throughout avoid scores driven by the last few weeks. Activity records in task tracking and the approval history of completed work are good sources for those notes.

In HibritİK, giving an item a score of 1 requires a comment. This rule prevents the lowest score from being given without a reason; the comment becomes the substance of the feedback for the employee and the basis for discussion in an appeal or a calibration meeting.

The weighted success score

At the end of the period three components come together:

1. Mission score: the evaluation of responsibility items.
2. Competency score: the multi-rater competency result, combining manager, direct report and peer ratings with their relationship weights.
3. Target score: the achievement rate of measurable targets.

These three are combined using the weights you configure in settings to produce the overall success score. An organisation with mostly operational roles might weight missions more heavily, while one going through transformation might prioritise targets. What matters is setting and announcing the weights at the start of the period.

A simplified example

To see the effect of weights, take a hypothetical case. Suppose settings give missions a weight of 40% and competencies and targets 30% each. An employee scoring 80 out of 100 on missions, 70 on competencies and 90 on targets gets a weighted average of 80 × 0.4 + 70 × 0.3 + 90 × 0.3 = 32 + 21 + 27 = 80. A higher target weight would push the result up; a higher competency weight would pull it down. The example only illustrates the logic of weighting.

If targets are capped at 100%, an employee who far exceeds a target still tops out at 100% on it, so an outstanding result in one component cannot fully cover gaps in the others. The example also shows why weights must be set at the start of the period: changing them after results are visible directly affects who qualifies for awards and erodes trust in the process.

Reports: from score to decision

A success score is not an end in itself but an input to decisions. HibritİK's success reports make that step easier:

• Success report: mission, competency, target and overall scores per employee.
• Department report: for comparing score distributions across departments.
• Award eligibility report: brings together the employees eligible for awards. Awards are linked to performance through award management in the Corporate Services module.
• Training needs report: derives development needs from low-scoring areas; planned trainings can be recorded with their participants.

All reports export to Excel, and employees can view their own evaluations and reports in the mobile apps.

When using the reports, read the success score together with its components rather than on its own. Two people with the same overall score may be strong in different areas, one in targets and the other in competencies, and the right development step differs for each. Looking at the component breakdown for award and training decisions also makes it easier to explain the reasoning to employees.

Step-by-step rollout

1. Write responsibility items for each department together with its managers.
2. Document the 1–5 score definitions and share them with managers.
3. Set mission, competency and target weights in settings.
4. Start the period and track completion.
5. Run the reports and calibrate if needed.
6. Base award and training decisions on the reports and discuss them with employees.

Common mistakes

• Copying responsibility items straight from job descriptions without making them measurable.
• Starting evaluations without written score definitions.
• Leaving low scores unexplained.
• Treating the success score as a final verdict and skipping the conversation.

Get started with HibritİK

Department responsibilities, 1–5 scoring, a weighted success score and decision reports are ready to use in the Performance Management module. Plan your period end to end with our review period checklist and start your 14-day free trial.