How to make a performance review fair: let the score come from the work

Example scenario: Picture a technical service company in Kadıköy. At the end-of-period meeting the manager is reviewing two technicians. One is visible in the office, speaks up in meetings, and answers questions on the spot. The other leaves for the field early, comes back in the evening, and rarely talks, but the list of jobs they closed is long. In the meeting, the one who comes to mind first is the one who was in sight.

This is not bad intent. When the measure is left to memory, two biases start working on their own. The first is recency: what happened in the last few weeks is remembered more vividly than what happened at the start of the period. The second is visibility: whoever works in the office is assumed to have put in more effort than whoever works in the field.

It looks the same from the employee's side. They do not know where they stand during the period. The score arrives at the end as a surprise, the first question is what it was based on, and the answer is usually an impression. That is where the argument begins.

Before a measure goes into the score, put these questions to it. If any answer is no, the measure either stays out or gets redefined.

• Can they influence it: if an outcome outside the person's control goes into the score, the measure becomes a penalty rather than a reward.
• Does it leave a trace: a closed job, a delivery date, a visit report, something you can open and check later.
• Is it the same for everyone: are two people in the same role measured by the same rule.
• Is it open in advance: was the rule written at the start of the period and shown to the team.

In a sales team, measuring closed sales alone punishes the rep who was given the hardest territory. Add answered enquiries, quotes sent on time, and feedback from customers, and the measure starts to see the work that was actually in the person's hands. The result still counts, just not on its own. Every added measure goes through the same four questions: is it in the person's hands, does it leave a trace in the record, is it the same for everyone in the role, and was it written down at the start of the period.

An attendance device records exactly who passed through the door and when. That is valuable data, but it is only one side of the question. At an electrical contractor in Ümraniye, the site supervisor goes straight to the construction site in the morning and drops by the office around midday. A table that only reads the door log shows him as late every single day.

Attendance should count towards the score, but not alone and not without the reason. If there is a record next to the late clock-in showing where the person was at that hour, the manager does not have to collect explanations; the reason can be read from the record. We looked at the problems of attendance data itself in our article on where attendance data breaks down.

The same weights do not suit every role. For a field technician, visits and field reports weigh most; for a sales adviser, quotes and customer feedback; in accounting, work closed on time. The role sets the weight, not the person. That way two people in the same role are weighed on the same scale.

Watch for one trap when writing weights: whatever is easy to measure gets heavier. Clock-in time is easy to measure, customer satisfaction is hard. If the easy one pulls ahead on its own, the measure drifts back to where you started, which is the clock.

When writing the rule, it helps to bring someone who does the job every day to the table. A rule that looks fair on paper can produce odd results in the field, and the person doing the work is the first to notice. The rule is written once and stays fixed for the period; any change applies for the next period, announced to everyone.

The reward can be tied to the rule as well: an extra day off, a thank-you card, first pick of leave dates, or whatever else the company decides. Having the reward written down in advance keeps the decision from depending on the mood in the meeting.

A score nobody sees turns into an argument at the end of the period. A score that is visible gives direction during it. At a furniture showroom in Nişantaşı, an adviser checks their own card on the phone in the middle of the month and sees that they never entered the reports for a couple of customer visits. They fill them in the same day, and there is nothing left to discuss at month end.

There is a boundary here. Performance data is personal data and is processed under KVKK, Turkey's data protection law. Employees should know which of their data is processed and what they are scored on. The team seeing the same rule and ranking is not the same as everyone seeing another person's personal details; who can see which detail is decided by permissions.

In Corex360, attendance, task, field, and customer records sit on the same core. A late clock-in, a closed job, a field report, a won quote, and a thank-you from a customer all land in those records, and the Team pulse turns them into a score with the weights you wrote. The score comes from the record. In the Corex360 Team pulse, events such as a late arrival, a completed task, a closed quote, and a customer's thanks turn into a score; the manager writes the reward rule, and the employee of the month comes out of the record. We describe the setup in our page on staff performance review software that builds the score from the record.

Write down the roles first: not job titles, but the work that gets done. Then list, for each role, the work that leaves a trace in the record. After that, set the weights with the people who do the work, and write the reward on the same page. Finally, show the rule to the team at the start of the period and keep looking at the same table throughout.

The rule protects the manager too. A decision made at the end of the period reads not as a personal preference but as the result of a rule everyone knew in advance; an employee who objects is shown the record, not told an impression.

Reviews are also tied up with leave and attendance records; if a week on leave lowers the score, the reason should be written on the card. You can see how attendance and leave flow to the accounting side in a day in the accounting and HR team.