Appraisal Letter

Issuing only a revised cost to company figure is the common shortcut, and it produces the recurring problem: the employee cannot check their own payslip against the letter, and payroll ends up explaining the difference between a headline figure and a monthly net every year.

Indian appraisal cycles commonly run to a financial year starting in April, with letters issued in June or July and revisions effective retrospectively. That gap has consequences the letter should deal with explicitly.

• Arrears for the intervening months are payable, and the letter should say when. An unstated payment date produces queries from every recipient in the same week.
• Decide whether arrears are applied to their original months or paid in the current cycle. The choice affects the period the amount is attributed to for contribution computations and the tax year it falls in, and it should be a recorded decision rather than a system default.
• Provident fund and other contributions on the revised wages for the retrospective period have to be computed and remitted, not just the salary difference.
• Tax deducted at source for the year should be recomputed on the revised annual figure, so the remaining months absorb the change rather than leaving a shortfall in March.
• Where an employee resigned between the effective date and the issue date, the position on their arrears and their eligibility should be settled by policy rather than case by case.

• Avoid future promises. A line saying the position will be reviewed again in six months, or that a promotion will follow on completion of a project, is read as a commitment and produces a grievance when it does not happen.
• Be careful with performance-linked language. Describing a payout as assured, or as part of the salary, can make a variable component something you must pay regardless of outcome.
• State discretion where it exists, and then exercise it consistently. A reserved discretion applied differently to two similar cases is what a grievance is built on.
• Do not use the letter to introduce unrelated changes, such as a longer notice period or a new restrictive covenant, buried among the numbers. A change to terms should be visible and agreed.
• Keep it consistent with the appointment letter and the policy. Where three documents say different things about notice or variable pay, the employee will rely on the most favourable.
• Where the outcome is no increase, say so in writing with the reason. Employees who receive nothing and hear nothing assume they were overlooked, and the assumption is usually more damaging than the decision.

• Issue every letter in the same cycle. Staggered issue is read, correctly, as a signal about who mattered.
• Have the manager deliver the outcome in conversation before the letter arrives. A letter that is the first the employee hears of their rating turns a decision into an ambush.
• Record acknowledgement, and keep the version issued. Where a revision is later disputed, the document actually given to that person is what matters, not the template.
• Make sure payroll and the letter come from the same source of truth. A structure typed into a letter and separately keyed into payroll will differ for somebody.
• Keep the assessment behind the rating, not only the outcome. Where a rating drives a payout or a later decision, the record of how it was reached is what defends it.
• Check the aggregate before issuing anything. A distribution of ratings that differs sharply by gender or by location within the same role is worth examining before the letters go out rather than after.

Verify the definition of wages under the Code on Wages, 2019 and its effect on contribution and gratuity computations under the Code on Social Security, 2020 when a structure is revised, and the tax deduction position on retrospective arrears under the Income-tax Act, 2025.