Annual Increment Cycle: From Appraisal to Salary Revision

The annual increment cycle is the most consequential eight weeks in the HR calendar, and in most growing Indian companies it is also the least designed. Appraisal ratings arrive in a spreadsheet, a budget number arrives from finance, someone builds a merit matrix at 11 p.m., managers negotiate, letters go out late, and payroll discovers on the 25th that forty employees need arrears. This guide lays out how to run the increment cycle end to end — from setting the budget, through building a defensible merit matrix, to issuing revision letters and getting the arrears right in payroll — for HR managers, founders and payroll teams running teams of 50 to 2,000 people.

The premise here is simple: the annual increment cycle is a process, not an event. Treated as a process, it is predictable, explainable and fast. Treated as an event, it consumes six weeks of your year and produces a fresh crop of attrition.

What the increment cycle actually has to accomplish

Before designing anything, be clear about what the cycle is for. It has five jobs, and they pull in different directions:

1. Reward differentiated performance. People who contributed more should receive more, visibly enough that it matters.
2. Keep pay competitive. Salaries drift below market over time; the annual cycle is the main correction mechanism.
3. Fix internal inequities. Historic hiring decisions, mid-year promotions and negotiated offers create anomalies. The cycle is where they get repaired.
4. Stay inside the budget. Total compensation cost must land where finance planned it.
5. Be explainable. Every manager should be able to tell every employee why their number is what it is.

Most cycles fail at the fifth. The numbers may be defensible in aggregate and indefensible in conversation, because the logic connecting rating to rupees was never written down.

The increment cycle timeline

For a company with a financial year ending in March and increments effective 1 April, a sensible timeline runs like this. Adjust the anchor dates if your effective date differs.

The most common failure is compressing weeks 9 through 5 into ten days. Calibration and matrix work cannot be rushed without producing numbers you cannot explain.

Step 1: Set the increment budget

The budget is a percentage of the current annual salary cost of eligible employees. Three ways to arrive at it, usually used together.

Bottom-up from market movement. What are comparable companies in your industry, size band and cities doing this year? Use a reputable salary survey or aggregated market data if you can afford it; otherwise triangulate from recruiter conversations, offer data on candidates you hired and lost, and published industry commentary. Do not build a budget on anecdotes from three exits.

Top-down from affordability. What can the business fund without breaking gross margin or runway? For a funded startup, this is a runway calculation. For a profitable services business, it is a margin calculation. Get the constraint number from finance before you promise anything.

Risk-based. What is the cost of not increasing pay for specific critical groups? If you have twelve people holding a skill you cannot rehire in under four months, their number is not a budget decision, it is a retention decision.

Structure the budget in named pools, because a single blended number hides too much:

• Merit pool — the main performance-linked pool, typically the largest share.
• Promotion pool — funds the step-up for people moving to a higher level. Keep this separate so promotions do not cannibalise merit for everyone else.
• Market correction pool — funds fixing employees who are below the market range for their role regardless of performance.
• Equity/anomaly pool — funds internal fairness fixes.
• Retention reserve — a small discretionary pool held by HR and leadership for genuine flight risks identified late in the cycle.

A common split is something like 70% merit, 15% promotion, 8% market and equity, 7% reserve, but the right split depends entirely on how far your pay structure has drifted. If you have not corrected market positioning in two years, the market pool needs to be much larger this cycle.

Decide eligibility rules before you compute anything:

• Minimum service to be eligible (commonly six months as on the effective date)
• Pro-rating for employees with three to six months of service
• Treatment of employees on probation
• Treatment of employees serving notice or with a resignation submitted
• Treatment of employees on long leave, sabbatical or maternity leave — note that penalising an employee for statutory leave is both unfair and legally risky; the safe and correct default is to treat protected leave as active service for increment eligibility
• Treatment of employees on a performance improvement plan
• Treatment of employees who received an out-of-cycle correction in the last six months

Write these down and publish them. Half of all increment grievances are eligibility disputes, not amount disputes.

Step 2: Get ratings you can actually use

The merit matrix is only as good as the rating distribution feeding it. Three practical issues to solve.

Rating inflation. If 80% of your organisation is rated "exceeds expectations", the matrix has nothing to differentiate on and your budget gets spread evenly. Calibration is the fix — not a forced distribution, which creates its own damage in small teams, but a structured conversation.

Calibration that works. Run calibration by function, with 8–15 managers in a room (or a call) and an HR facilitator. Rules that make it productive:

• Managers present their proposed ratings for their team in one pass, with two sentences of evidence per person, before any discussion.
• The facilitator asks comparison questions, not judgement questions: "You've rated A above B — help the group understand the difference in impact."
• Nobody's rating changes without the manager agreeing in the room. Ratings changed behind a manager's back destroy the manager's ability to have the conversation later.
• The facilitator watches for the known biases: recency (the last six weeks dominating a twelve-month view), the halo effect, proximity bias favouring people the manager sees more often, and the tendency to rate quiet high performers lower than loud average ones.
• Document the outcome, including the rationale for any changed rating.

Rating scale design. A four or five point scale works. Five points with a clearly defined middle is generally easier to calibrate than four, which forces an artificial above/below split. Whatever the scale, define each point in behavioural terms, not adjectives. "Consistently delivers agreed outcomes and requires normal support" is usable; "Good" is not.

Separate performance from potential. Performance drives the increment. Potential drives promotion and development investment. Conflating them means you promote your best current performers into roles they are not suited for, and you underpay high performers who are happy where they are. Run a simple two-axis review — current performance against future potential — and use the two axes for different decisions.

Step 3: Build the merit matrix

The merit matrix converts a rating and a pay-position into an increment percentage. It is the single most useful artefact in the whole cycle because it makes the logic visible.

The two axes

Axis 1: Performance rating. Your calibrated rating.

Axis 2: Compa-ratio. This is the employee's current fixed pay divided by the midpoint of the salary range for their level and role. A compa-ratio of 0.85 means they are paid 15% below the midpoint; 1.15 means 15% above.

Why compa-ratio matters: two people with identical ratings should not get identical percentage increases if one is paid well below the range midpoint and the other is well above it. The one below should get more, because the goal is to move people towards the right place in the range over time. This is the mechanism that quietly fixes years of inequity without anyone having to announce a correction programme.

If you do not have salary ranges, you cannot compute compa-ratio, and you should build ranges before the next cycle. In the interim, substitute a rough band position (below/at/above the median pay for the level within your own company) as a proxy.

A sample matrix

The numbers below are illustrative only — your actual percentages must be derived from your own budget and market data.

Read the matrix and you can see the philosophy at a glance: performance matters most, position in range modulates it, low performers get nothing, and people already paid well above their range get modest increases even when they perform well — because their absolute rupee increase is already large.

Calibrating the matrix to the budget

Building the matrix is iterative:

1. Draft the matrix with your intended differentiation.
2. Apply it to your actual employee data.
3. Compute the total cost as a percentage of the current salary bill.
4. Compare with the merit pool.
5. Scale the matrix up or down proportionally and re-run.

Two or three iterations gets you there. Do this in a spreadsheet or, better, in an HR system that can model scenarios, because you will want to test three or four versions with leadership.

Check the shape, not just the total. Two matrices can cost the same and behave completely differently. Look at:

• The ratio between the top rating's average increase and the middle rating's. If a top performer gets 11% and a solid performer gets 9%, you have not differentiated meaningfully — the top performer will notice.
• The absolute rupee gap at each level. A 3% difference at a junior salary may be a few thousand rupees a year; the same 3% at a senior salary is meaningful. Differentiation that only shows up for senior people is a fairness problem.
• The number of zero-increment employees. If it is more than a small fraction, you have a performance management problem that an increment cycle cannot fix.

Handling promotions

Promotions should be funded separately and computed differently. A promotion increase has two components:

• A level movement component that brings the employee at least to the minimum of the new level's range, and typically to a point that reflects their readiness — often the lower third of the new range for a newly promoted person.
• A merit component for the performance year just completed.

Guard against two errors: promoting someone without moving their pay into the new range at all (a title-only promotion, which employees see through immediately), and moving them straight to the new range midpoint (which leaves no room for the next three years of increments).

Step 4: Manager review and guardrails

Once the matrix produces a first-pass number for everyone, give managers a controlled window to adjust. Controlled is the key word.

Give each manager a pool, not a free hand. A manager sees their team's matrix-generated numbers and a total pool equal to the sum. They may reallocate within the team, but the total cannot exceed the pool. This creates real trade-offs and surfaces the manager's actual priorities.

Set adjustment guardrails:

• Maximum deviation from the matrix number without HR approval — say, plus or minus 3 percentage points.
• A hard floor and ceiling per rating so a "meets" employee cannot end up above an "outstanding" one.
• Mandatory written justification for any adjustment beyond the guardrail.
• No adjustment permitted for employees rated below expectations.

Watch for pattern problems in manager adjustments. Run a quick analysis before sign-off: are adjustments systematically favouring one gender, one location, one tenure band, or the people who sit near the manager? These patterns are almost always unconscious and almost always visible in the data. Fixing them at this stage is cheap; discovering them in an exit interview is not.

Set a deadline and enforce it. Managers who miss the window get the matrix number applied as-is. Publish that rule in advance and then actually apply it, once. The following year, everyone meets the deadline.

Step 5: The equity and anomaly review

Before anything is locked, run a structured review that the matrix cannot do on its own.

Pay equity check. For each level and role family, compare average pay across gender and, where relevant, other groupings. Where a gap exists, investigate whether it is explained by legitimate factors — tenure in role, performance history, location, specific skills — and where it is not, use the equity pool to close it. Do this every cycle; gaps that are not actively closed widen automatically, because percentage increases preserve existing differences.

New joiner compression. If you have hired externally in the last twelve months at rates above your existing team's pay, you have compression: newer employees paid at or above longer-tenured ones at the same level. This is one of the most reliable predictors of resignation among your existing team. Identify it explicitly and fund corrections.

Below-minimum check. Anyone paid below the minimum of their level's range should be brought to the minimum regardless of performance, unless they are new to the level and on a defined ramp.

Statutory floors. Verify that no employee's revised structure falls below applicable minimum wage requirements for their category, skill classification and state, and that any statutory obligations tied to the wage definition are correctly applied to the new structure. Minimum wage rates are notified state-wise and revised periodically — confirm the current applicable rates rather than relying on last year's file.

Retention risk overlay. Combine the increment list with whatever attrition risk signals you have — engagement scores, recent internal applications, manager flags, time since last increase — and check that your genuine flight risks have received a number that reflects their value. If not, this is what the retention reserve is for.

Sanity checks before sign-off. A short list that catches most errors:

• Anyone with an increment above the maximum in the matrix
• Anyone with a zero increment who is not rated below expectations
• Anyone whose revised pay exceeds the maximum of their level's range
• Employees who received an out-of-cycle increase in the last six months and are also getting a full merit increase
• Employees who have resigned but are still in the file
• Duplicate employee records
• Total cost against budget, by department and by level

Step 6: Restructure the salary correctly

An increment is not just a bigger number. The revised salary structure has to be built properly, because the structure drives statutory contributions, taxes and take-home.

Get the wage definition right. The labour codes framework has moved towards a definition of wages under which specified allowances beyond a defined proportion of total remuneration get pulled back into "wages" for calculating statutory benefits. Practically, this means structures that historically loaded a large share into allowances to keep basic pay low face a rebalancing, with knock-on effects on provident fund contributions, gratuity accrual and other wage-linked entitlements. The increment cycle is the natural moment to bring structures into line, because you are already reopening every salary. Confirm the current applicable position with your compliance advisor before you rebuild your structure template — the specifics of implementation and effective dates have moved over time and vary in application.

Model the take-home impact. A restructure that increases basic pay increases provident fund contributions, which reduces net take-home even as cost-to-company rises. If you do not model and explain this, you will get a wave of "my increment reduced my salary" tickets. Prepare a simple illustration showing old and new CTC, old and new take-home, and the reason for the difference. Give it to managers before conversations, not after.

Handle the tax regime interaction. Employees choose a tax regime and submit declarations; a mid-year revision changes the projected annual income and therefore the monthly TDS for the remaining months. Make sure your payroll recomputes projected tax on the revised annual figure rather than continuing on the old projection, or you will have a large catch-up deduction in the final quarter and a very unhappy set of employees in February. Encourage employees to review their investment declarations after the revision.

Keep the structure consistent. Resist the temptation to design bespoke structures per employee. One structure template per level, with components derived by formula, means payroll can process changes without manual intervention and audits are trivial.

Step 7: Letters, communication and conversations

Sequence matters. The manager conversation should happen before the letter lands, not after. An employee who learns their number from a system notification while their manager is in a meeting has had a bad experience regardless of how good the number was.

Prepare managers properly. Run a 60-minute session covering:

• The company's compensation philosophy in plain language
• How the matrix works, so managers can explain the logic without disclosing others' numbers
• How to explain a below-expectation number honestly
• What not to say: "I fought for you but HR refused", "The budget was cut", "I don't know how this was decided". All three are common, all three are corrosive.
• The CTC-versus-take-home explanation, with an example
• Where to send questions they cannot answer

Structure the conversation. A workable shape:

1. Recap the year's performance with specific examples (this should not be new information if you have run regular check-ins).
2. State the rating and the reasoning.
3. State the increment, the new structure, and the effective date.
4. Explain how the number was arrived at — rating, position in range, budget context.
5. Discuss what would change the number next year.
6. Answer questions; commit to coming back on anything unanswered within 48 hours.

The letter itself. Keep it clean and unambiguous:

• Employee name, ID, designation, department
• Effective date of revision
• Revised annual CTC and the component-wise breakup
• New designation and level, if promoted
• Confirmation that all other terms of employment remain unchanged
• A note that statutory deductions apply as per applicable law
• Authorised signature

Send letters through a system with a delivery record and an acknowledgement. Emailed PDFs with no acknowledgement trail become a problem when someone claims they never received a revision.

Handle the disappointed well. Some people will be unhappy. The response protocol:

• The manager listens fully before responding.
• If the employee raises a factual error — wrong rating input, missing achievement, incorrect eligibility — HR reviews it and corrects it if warranted. This should be rare but must be possible.
• If the employee disagrees with the judgement, the manager holds the line and moves the conversation to what would change next year.
• Do not renegotiate a number because someone pushed hard. If you do it once, it becomes the system, and the people who negotiate least — often your quietest strong performers — get systematically underpaid.

Step 8: Payroll execution and arrears

The cycle is not over until payroll is correct.

Effective date discipline. Decide the effective date and hold it. If letters are delayed, the effective date does not move; arrears are paid instead.

Arrears computation. For each affected employee, arrears equal the difference between the revised and previous monthly gross for each month from the effective date to the month of implementation. The details that get missed:

• Arrears are taxable in the year of receipt and change that month's TDS materially. Communicate this, or the payslip will look wrong to the employee.
• Provident fund and other statutory contributions apply on the arrears where the components attract them; confirm treatment for each component with your compliance advisor.
• Employees who exited between the effective date and the implementation date may still be entitled to arrears for the period they served. Have a rule and apply it consistently.
• Employees who had loss of pay during the arrear period need pro-rated arrears.
• Where arrears relate to earlier periods, employees may be eligible for specific relief under the income tax provisions dealing with arrears; make them aware that this relief exists and that they should consult their tax advisor, and be prepared to provide the period-wise breakup they will need.

A pre-release checklist for payroll:

• Revised structures loaded for every employee on the approved list, and no one else
• Total revised salary cost matches the approved budget
• No negative net pay for any employee after the restructure
• Statutory contribution calculations recomputed on the new structure
• Projected annual tax recomputed for the remaining months
• Arrears computed, reviewed and separately visible on the payslip
• Revision letters issued and acknowledged before or with the payslip
• A variance report comparing this month's payroll with last month's, line by line, for anything unexpected

Payslip transparency. Show arrears as a distinct line item with the period it covers. A single inflated "basic" line with no explanation generates more tickets than anything else in the cycle.

Step 9: Close the loop

Four weeks after the cycle, run a short review with the people who executed it.

• How many grievances were raised, and what were the top three causes?
• How many manual corrections did payroll have to make?
• How long did each phase actually take versus plan?
• What percentage of managers held the conversation before the letter?
• What did the pay equity analysis show, and what remains to be fixed next cycle?
• Which parts of the process existed only in one person's head?

Write the answers down. Next year's cycle should start from this document, not from a blank page.

Also track the outcome that matters most: regretted attrition in the ninety days after increments. A spike concentrated in a particular team or rating band tells you something specific about how the cycle landed, and it is far more informative than an overall attrition number.

Common mistakes in the annual increment cycle

Announcing the budget percentage to everyone. If you say "the average increment is 9%", every employee below 9% feels below average, including solid performers. Communicate the philosophy, not the average.

Running increments without salary ranges. Without ranges you have no compa-ratio, no way to detect below-range employees, and no way to control range maximums. Building ranges is a two-to-four week project and it improves every subsequent cycle.

Letting promotions eat the merit budget. Separate pools, always.

Delaying letters and paying arrears every year. Arrears are a recoverable one-off; making them an annual tradition tells the organisation that HR cannot hit a date.

Using the increment to solve a performance problem. A zero increment is not a performance conversation. If someone is genuinely underperforming, that needs a documented process, not a silent salary decision in April.

Ignoring the internal-versus-external gap. If your increments run at 8% while the market pays 25% to switch, increments alone will not retain anyone. That is a hiring-rate and career-path problem, and it needs a different conversation with leadership.

Skipping the equity analysis because the sample is small. Small numbers make statistical claims weak, but they do not make individual unfairness acceptable. Look at the individuals.

No documentation of decisions. Two years later, when someone asks why an employee's pay is where it is, "we don't know" is not an answer you want to give.

Frequently asked questions

When should the annual increment cycle be effective?

Most Indian companies align the effective date to the start of the financial year on 1 April, which keeps the increment, the appraisal year and the tax year in sync and simplifies TDS projections. Some companies use 1 January to align with global parents, and some use employee anniversary dates. Anniversary-based cycles spread the workload but make budget control and internal comparison much harder; for most organisations under a few thousand people, a single annual cycle is simpler and fairer.

What is a merit matrix and do small companies need one?

A merit matrix is a grid that converts a performance rating and an employee's position in their salary range into an increment percentage. Even a 60-person company benefits from one, because it forces you to state your logic before you see individual names, which is the single best defence against bias and negotiation pressure. A small company's matrix can be a simple three-by-three grid; the point is that it exists and is applied consistently.

Should employees be told the increment budget percentage?

Share the philosophy and the process; be cautious with the average number. Telling employees the average makes anyone below it feel penalised even when their number reflects a fair rating. What genuinely helps is transparency about how decisions are made — that ratings are calibrated, that position in the salary range affects the number, that promotions are funded separately. Several organisations now publish their salary ranges and matrix structure without publishing individual outcomes; that is a defensible middle position.

How do we handle increments for employees who joined mid-year?

Set a clear rule: full eligibility above a service threshold (commonly six months as on the effective date), pro-rated increments for a defined band below it, and no increment for very recent joiners whose offer already reflects current market rates. Publish the rule with the cycle communication so nobody has to ask.

Do employees on maternity or other statutory leave get increments?

They should be treated as active service for increment eligibility, and their performance should be assessed on the period they worked rather than penalised for the period of protected leave. Denying or reducing an increment because of statutory leave is unfair and carries meaningful legal risk. Build this into your eligibility rules explicitly so it does not depend on an individual manager's judgement.

How do we explain that CTC went up but take-home went down?

This usually happens when the revised structure increases basic pay, which increases provident fund contributions and possibly other wage-linked deductions. Prepare a simple side-by-side illustration showing old and new CTC, the changed components, the increased statutory contributions, and the resulting take-home. Emphasise that the increased contribution is the employee's own retirement savings, not a loss. Give this to managers before the conversations begin.

What should we do about employees already paid above their salary range maximum?

Give them a smaller percentage increase, or in some cases a one-time lump sum instead of a permanent increase, so the base does not drift further out of range. Be transparent about why: their pay is already ahead of the range for the role, and the path to a larger increase is movement to a higher level. Handle this in the conversation carefully — it is easy for a strong performer to hear "you're capped" as "you have no future here."

How do we run the increment cycle when the business cannot afford one?

Be direct rather than silent. Communicate early that the merit pool is constrained this year and explain the business reason. Protect two things if you can: corrections for anyone below the range minimum or below statutory floors, and a targeted pool for genuine critical-skill retention. Consider non-cash levers — additional leave, learning budgets, title and scope changes, flexible working — but do not present them as a substitute for pay, because employees see through that instantly. Most importantly, tell people when the next review will happen and then keep that date.

Bringing it together

A well-run increment cycle has four qualities: a budget agreed before ratings are known, a matrix that makes the rating-to-rupees logic explicit, an equity review that catches what the matrix cannot, and a payroll execution that lands on the effective date without arrears. None of these require sophisticated tooling. They require sequencing, discipline and a willingness to write the rules down before you know whose name they apply to.

The cycles that go badly are almost never the ones where the budget was small. They are the ones where nobody could explain the number.

CozyHR connects appraisals, salary ranges, increment modelling, revision letters and payroll in one place, so your merit matrix flows straight into revised structures and correctly computed arrears without a spreadsheet handover. Explore CozyHR and make your next increment cycle the one that finishes on time.