HR & Management

How to Conduct an Employee Performance Review That Is Actually Useful

A practical performance review process from a Nepali workplace: preparation, evidence, a one-page form, a meeting agenda, and the wording that keeps the conversation fair.

Cover illustration for “How to Conduct an Employee Performance Review That Is Actually Useful”

Most appraisal problems are not created in the appraisal meeting. They are created months earlier, when nobody agreed on what the job was supposed to deliver, and nobody wrote anything down.

By the time review day arrives, the manager is working from memory and the employee is working from memory as well. Both are sincere. Neither is reliable.

I have sat on both sides of that table, and I have prepared appraisal documentation for offices of very different sizes. What follows is the process I would use today if I had to run a fair review cycle for a small or mid-sized team in Nepal.

This article describes practical HR administration. Employment requirements vary by organisation and can change, so check current Nepal labour rules and your own HR policy, and take qualified advice for anything unusual.

Before the cycle starts

Three things need to exist before the first review form is printed:

  1. A current job description for every role. One page is enough: purpose, main duties, reporting line, and the decisions the person can make alone.
  2. Agreed objectives. Written where both people can see them, with a measure and a date attached.
  3. A record system that already works. If attendance, leave, and completed work are not recorded during the year, the review becomes a debate about memory.

I use the SMART objective format for step two, and the free SMART Objective Tracker to keep objectives, targets, and progress in one place. It is a spreadsheet, not a system, but the important part is that a manager and an employee can both read the same page.

What evidence to prepare

A review should be a summary of things that already happened, not a surprise announcement. Before the meeting, the reviewer should collect:

Evidence Where to find it What it shows
Objective progress Objective tracker or work plan Whether the agreed targets were met
Attendance and leave Attendance register Reliability and patterns over months, not days
Completed deliverables Reports, files, submissions Output rather than activity
Documented feedback Emails, notes, minutes Whether issues were raised at the time
Training and certificates Personnel file Development that has already happened
Disciplinary or commendation records HR file Anything that changed expectations

If a serious concern exists and it is written nowhere, the honest conclusion is usually that the process was not followed — not that the employee failed. Say so internally and fix the process.

The one-page review form

A short form gets completed properly. Mine has six parts:

  1. Role and review period — job title, dates covered, reviewer, date of meeting.
  2. Agreed objectives — each objective, its target, the result, and a rating.
  3. Core responsibilities — five or six standard duties with a simple rating.
  4. Competencies — job knowledge, quality, teamwork, communication, initiative.
  5. Employee’s own comments — written by the employee, before or during the meeting.
  6. Agreed actions for the next period — including any support, training, or resource needed, with dates.

Rating scales should be defined on the form itself. “Meets expectations” means nothing if the definition of the expectation is not printed next to it.

Running the meeting

A useful review meeting takes 45 to 60 minutes. The structure I use:

  • First five minutes: purpose and tone. Review the period, not the person’s worth. Make it clear that this is a working discussion.
  • Then the employee speaks first. Ask what went well, what was difficult, and what they would change. Write down what they say.
  • Then the evidence. Go through the objectives one by one. Use the record, not adjectives. “The monthly report was submitted within the deadline in nine of twelve months” is a fact. “You are not reliable” is an opinion and will end the conversation.
  • Then the hard part. If performance is below expectation, state the gap once, clearly, with the evidence, and then move to what support is needed. Do not repeat the same complaint four times in four different ways.
  • Then next period. Two or three priorities maximum, written down and dated, with a follow-up date for each.
  • Finally, a summary in plain language. “So what we agreed is: X by March, Y by June, and I will arrange the training in November.” Ask the employee to confirm it.

Wording that keeps the discussion fair

Some sentences I have learned to use, and some I have learned to avoid:

Instead of Try
“You are not a team player.” “In the March and April stock counts, the task was assigned to you and completed by someone else. What happened?”
“Everyone says your work is slow.” “Two of the five reports were late against the agreed dates. Where is the bottleneck?”
“You need to improve your attitude.” “In two meetings, the client’s questions were answered with one word. What would help you handle these differently?”
“Do better next year.” “Next period, the target is 40 verified files per month, reviewed weekly. Let us meet on the 15th of each month.”

The pattern is the same everywhere: describe the observation, not the personality; give the number or the example; ask what happened; agree the next step.

Documentation and confidentiality

  • Complete the form during or immediately after the meeting. Not a week later.
  • Ask both people to sign the form. A signature means the discussion happened, not that the employee agrees with every rating.
  • If the employee disagrees, record the disagreement. A form that only records the manager’s view is not a record; it is a statement.
  • Keep appraisals in the personnel file, in a locked cabinet or a restricted folder, and share them only with those who need them.

Common mistakes I have seen

  1. No objective, then a rating. If it was never agreed, it cannot be scored.
  2. Once-a-year feedback. Reviews should confirm a pattern of conversations, not replace them.
  3. Copy-paste reviews. Identical wording across five employees is visible to everyone and destroys trust in the process.
  4. Rating inflation to avoid conflict. A year of “excellent” ratings followed by a performance problem is very hard to defend.
  5. Forgetting the follow-up. An agreed action with no owner and no date is a wish, not a plan.
  6. No employee input. The form has a comments section for a reason. Use it before, not after, the ratings are finalised.

A simple calendar that works

  • Month 1: Job descriptions reviewed; objectives agreed and signed.
  • Quarterly: Short check-in, 20 minutes, written note of progress.
  • Two weeks before the review: Reviewer prepares evidence; employee completes self-assessment.
  • Review meeting: 45–60 minutes, form completed on the day.
  • One week after: Agreed actions entered into the tracker with dates.
  • Next cycle starts: Objectives for the new period agreed before the old ones are closed.

Run that cycle once and the next one becomes much easier, because you will finally have written evidence from the year before.

Join the conversation

Was this article useful?

Views are counted only with analytics consent. Ratings, likes, and helpful votes are sent only when you choose them.

—article views
Rate this article
Loading ratings…

Your feedback helps improve future articles.

Community discussion

Comments 0

Comments are reviewed before they appear publicly. Be respectful and avoid sharing private information.

No approved comments yet. You can be the first to share a useful thought.

Add a comment

No account or login is needed. Your comment is emailed for moderation and is published only after approval in the CMS.

Sent securely through Web3Forms. Your email is used only to follow up if needed and is not included in the public comment.