Score cards: how the overall rating is built

Score cards: how the overall rating is built

A score card turns each employee's self-assessment, reviewer assessment, goals and feedback into one Overall score out of 100, using weights you choose. Use this article to understand where each number on a score card comes from, why someone scored what they did, and how to check an Overall score by hand. To create or change a score card, see Setting up a score card.

Where: Performance › Team performance › Score Card › open a score card

You need: the Admin right

How to check one person's Overall score by hand

  1. Open Team performance › Score Card and select the score card.
  2. In Employee Scores, find the person. Note their Self, Reviewer, goal and Feedback scores.
  3. Read the four weights from the strip above the table.
  4. Multiply each score by its weight, add the four results, and divide by 100.

For example, with weights of Self 20%, Reviewer 40%, Goal 20% and Feedback 20%, an employee scoring Self 80, Reviewer 70, Goal Progress 50 and Feedback 60 gets (80×20 + 70×40 + 50×20 + 60×20) ÷ 100 = 66.

If you can't reproduce someone's score this way, you can't explain it to them either. Check one person before you share any results.

The four scores

Every score is shown out of 100. Assessment and feedback scores are 0 to 5, multiplied by 20, so a 4 shows as 80.

ColumnWhere it comes from
SelfThe average of the employee's own self-assessment scores in the score card's assessment cycles. See How assessment scores are calculated.
ReviewerThe average of every reviewer's score on those self-assessments. With two reviewers, each review counts once.
Goal ProgressUsed when Goal score based on is Goal Progress. The average progress the employee has recorded across their goal cycles, 0 to 100%. Cycles that haven't been reviewed yet still count.
Goal ScoreUsed when Goal score based on is Reviewer's KPI score. The reviewer's KPI ratings, weighted by KPI weight and goal priority, averaged over completed reviews only and multiplied by 20. An employee with no completed review shows 0.
FeedbackThe average star rating of feedback about the employee. It is not limited to the score card's cycles or dates.
OverallThe four scores combined using the weights, which always total 100%.

What counts, and what doesn't

  • No cycles selected means all cycles. The card then shows All Cycles, and Self, Reviewer and goal scores average every cycle the employee has been in.
  • Who appears. With cycles selected, the table lists everyone in at least one of them. With none selected, it lists every active employee.
  • A missing score counts as 0. Someone who isn't in any of the goal cycles scores 0 for the goal column, and that 0 is weighted into their Overall like any other score.
  • The Start Date and End Date don't filter anything. They label the score card and decide where it falls in the analysis view. Choosing the cycles is what decides which results count.
  • Inactive employees are left out.

Live figures and saved figures

The Score Card page works everything out again each time you open it, so it always reflects the latest answers and ratings.

Each time a score card is saved, KAMI also stores a copy of every employee's scores. The talent grid in Kai AI (BETA) and the Performance tab on an employee profile read that stored copy, not the live page. A score card is saved when you create it, apply new weights or rename it.

So the stored copy can fall behind the page. To bring it up to date, open the score card, select Adjust Weights, then Apply without changing anything.

How the Overall is shaded

In Employee Scores, the Overall is shaded in three bands: 80 and above, 50 to 79, and below 50. The other cells are shaded from lower to higher.

The talent grid uses different cut-offs: below 60 is Below, 60 to 79 is Meets, and 80 and above is Exceeds. See Performance scores and the talent grid.

What Happens Next

  • Changing the weights, cycles or goal source changes everyone's Overall at once, on the page straight away and in the stored copy a moment later.
  • Answers, ratings and feedback given after you open the page appear the next time you open it.
  • Nothing in KAMI acts on a score. What follows is a management decision.

Tips

  • Agree the weights with whoever owns the review policy before you build the card. They are your company's definition of performance, in numbers.
  • Select the cycles deliberately. Leaving them empty mixes every cycle anyone has ever done, including pilots and abandoned ones.
  • Keep a separate score card per period, each with its own cycles and dates, rather than editing one card. The talent grid needs two or more dated cards to show a trend.
  • Don't weight feedback heavily unless feedback is given to everyone. A person nobody gave feedback about scores 0 for it.
  • Use Goal Progress mid-cycle and Reviewer's KPI score at year end. Progress is what employees have recorded; the KPI score is what their reviewer has confirmed.
  • Keep the weights stable between periods. Changing them makes this year's results incomparable with last year's.

Troubleshooting / FAQ

Q: Why is someone's Overall so low when their assessments are good? Look for a 0. They may not be in the goal cycles, or have no feedback, and that 0 still carries its weight.

Q: Why does an employee show 0 for Goal Score? Goal score based on is Reviewer's KPI score, and their goal review isn't complete yet. Only completed reviews count.

Q: A cycle ran but doesn't seem to count. It isn't selected on the score card. Open Adjust Weights and add it under Assessment Cycles or Goal Cycles.

Q: Does feedback only count for the score card's period? No. Feedback is averaged over everything the employee has received.

Q: The talent grid shows a different score from the Score Card page. The grid reads the copy stored when the score card was last saved. Save it again to refresh it.

Related articles