Designation

Designation is the job title an employee formally holds, recorded in the appointment letter and carried on the employee master. Software Engineer, Assistant Manager, Regional Sales Head and Chief Financial Officer are designations.

It answers the question of what the person is called, not what they do. That sounds like a small distinction and it is the source of most of the confusion around the term. Two people with the same designation in the same organisation frequently do unrelated work, and two people doing identical work across two organisations frequently hold different designations.

The designation is what appears on a business card, an email signature, an experience letter and a background verification response. That last one is why it is worth recording accurately even when it seems cosmetic.

A designation is the title used externally, a grade fixes the pay band and approval limits, and a role is the actual scope of work and reporting line. Three related fields sit on the employee record and each does a different job. Organisations that conflate them run into trouble at promotion time.

Keeping grade separate from designation is what allows an organisation to give someone a title change without a pay band change, or a pay increase without a title change. Merging the two fields removes that flexibility and forces every recognition decision to become a compensation decision.

The reverse problem is more common in fast-growing companies: grades exist on paper but nobody maintains them, so designation becomes the only signal of seniority, and it drifts.

Designation inflation happens because titles are free and increments are not. A manager who cannot fund a raise can often approve a title change, and over a few cycles the organisation accumulates senior-sounding designations attached to unchanged work.

Three consequences follow, and they arrive later than the decision.

• The title stops carrying information internally. When a third of the sales organisation is a Senior Manager, the designation no longer distinguishes anyone.
• It creates a ceiling problem. An employee made Assistant Vice President at twenty-eight has nowhere obvious to go, and the next recognition has to be real.
• It transfers badly. Hiring managers discount inflated titles from known employers, so the employee carries a designation the market does not accept and may take a nominal demotion to move.

The defensible version is a published title structure with stated criteria for each level, applied consistently. It is more work than approving a title on request and it is the only thing that keeps designations meaningful over a few years.

A common assumption is that the designation settles statutory questions. It generally does not.

Whether an employee falls within the definition of a worker or a workman under Indian labour legislation turns on the nature of the duties performed and, in some cases, the wages drawn. Calling someone a Manager does not by itself place them outside those definitions if the work is not managerial or supervisory in substance. The same applies to overtime eligibility and to coverage under establishment-specific rules.

Nor does designation decide payroll treatment. Provident fund and ESI coverage are driven by wages and by the establishment's applicability, not by the title. Gratuity turns on continuous service. Professional tax turns on the state and the salary slab.

The practical point for HR is that a title cannot be used to engineer an exemption. Where the substance of the work does not match the label, the label is what gets set aside.

A designation change should leave a trail, even when nothing else changes.

• Issue a letter. A promotion letter or a revised appointment letter is what the employee will produce years later, and a verbal change with only a system update behind it is hard to evidence.
• Record the effective date. Backdating a designation to suit an appraisal cycle creates a mismatch with payroll records and with any experience letter issued in between.
• Keep the history. The employee record should show the sequence of designations with dates, because background verification asks for exactly that and an answer that contradicts the candidate's own account causes problems for them.
• Update downstream systems together: email signature conventions, approval workflows tied to grade, and the payroll master where the designation prints on the payslip.

Where a designation change accompanies a genuine change in duties, say so in the letter. Where it does not, the letter should still be issued and the grade left unchanged, which is the honest record of what happened.

Organisations that keep designations meaningful have usually written the structure down. It does not need to be elaborate.

The last row is the one most often skipped and the one that causes the most resentment. Where engineering titles run two levels ahead of the rest of the organisation for the same scope, people notice, and the comparison is made in the appraisal conversation rather than in a structural review.

Two decisions are worth making explicitly. Whether individual contributors can reach senior titles without managing anyone, which determines whether good specialists have to become poor managers to progress. And whether external-facing titles may differ from internal ones, which is common in sales and is worth permitting deliberately rather than allowing informally.

Review the structure when the organisation changes shape rather than annually. A ladder designed for sixty people stops describing three hundred, and the drift shows up first as an unusual number of requests for title changes.