Employee Handbook in India: Guide & Template (2026)

An employee handbook is the document every company knows it should have, most companies eventually produce, and almost nobody reads. That last part is the problem worth solving. A handbook that sits unopened in a shared drive provides no legal protection, answers no questions, and shapes no behaviour. It is compliance theatre.

A good employee handbook does three jobs at once. It tells people how things work here so they stop asking HR the same twelve questions. It sets out the standards you will hold people to, which is what makes fair discipline possible. And it demonstrates, when challenged, that your organisation communicated its policies clearly and applied them consistently.

This guide covers what belongs in an Indian employee handbook, how to structure it, how to write it so people actually read it, what the legal considerations are, and how to keep it current once it exists.

What an Employee Handbook Is — and Is Not

An employee handbook is a consolidated statement of your workplace policies, procedures, benefits, and expectations, written for employees rather than for lawyers.

It is not the employment contract. The contract creates individually enforceable obligations between the company and one employee. The handbook describes the general policy framework everyone operates within. Most handbooks state explicitly that they do not form part of the contract and that the company may amend them — but you should be careful here, because the way you word that disclaimer affects what the handbook does and does not commit you to.

It is not a legal compendium. Nobody needs the full text of a statute in an employee handbook. What they need is the operative rule as it applies to them, in plain language, with a reference to where the detail lives.

It is not a substitute for management. A handbook cannot make a bad manager fair or a vague strategy clear. It can only make the rules knowable.

Why It Matters Legally

Several kinds of dispute turn on whether a policy was properly communicated.

If you dismiss someone for misconduct, one of the first questions is whether the conduct standard was known to the employee. A signed acknowledgement of a handbook containing the code of conduct is a considerably stronger answer than a manager's recollection of a verbal briefing.

If a harassment complaint arises, your obligations under prevention-of-sexual-harassment legislation include publishing a policy, constituting an internal committee, and conducting awareness. The handbook is a natural vehicle for the first, and a documented acknowledgement is evidence of the third.

If a data protection question arises, demonstrating that employees were informed about how their personal data is processed is far easier when there is a documented, acknowledged privacy notice.

If a dispute arises about leave, notice, working hours, or deductions, the handbook establishes what the employee was told the rules were.

None of this works if the handbook is a file nobody opened. Which is why acknowledgement tracking is not bureaucratic overhead — it is the whole point.

Structuring an Employee Handbook

Order matters. The most common structural mistake is opening with fifteen pages of legal disclaimers, guaranteeing that nobody reaches the part about how to apply for leave.

Lead with what people need most often. Bury what they need rarely.

Section 1: Welcome and Introduction

Short. Two pages at most.

• A brief welcome from leadership
• What the company does and who it serves
• Company values, described concretely rather than aspirationally
• What this handbook is for and how to use it
• Who to contact with questions
• How to find the current version

Values sections deteriorate into meaninglessness fast. "Integrity" tells nobody anything. "We tell customers when we have made a mistake, before they find out" tells everyone something. Write values as observable behaviours.

Section 2: Employment Basics

• Categories of employment: permanent, fixed-term, probationary, intern, consultant, and what differs between them
• Probation and confirmation: duration, review process, how confirmation is communicated
• Working hours: standard hours, core hours, flexibility arrangements
• Attendance and how it is recorded
• Weekly holidays and the annual holiday calendar
• Remote and hybrid working arrangements, if applicable
• Change of personal details and the obligation to keep records current

Section 3: Compensation and Payroll

• Pay cycle and pay date
• Salary structure components explained in plain terms — basic, allowances, employer contributions
• How to read a salary slip
• Statutory deductions: provident fund, ESI where applicable, professional tax, income tax
• Tax regime election and the annual declaration process
• Investment proof submission timelines
• Reimbursement categories, limits, and claim process
• Overtime eligibility and rates
• Salary advance or loan policy, if you have one
• Annual increment cycle and how decisions are made
• Variable pay or bonus structure, if applicable

This section prevents more HR queries than any other. Invest in it. Include a worked example of a salary slip with each line explained.

Section 4: Leave and Time Off

• Types of leave and annual entitlement for each
• Accrual mechanics: monthly, annually, on joining
• Pro-rating for mid-year joiners and leavers
• Application process and notice expectations
• Approval authority and what happens if a manager does not respond
• Carry-forward rules and caps
• Encashment rules
• Maternity, paternity, and adoption leave
• Bereavement leave
• Sabbatical or unpaid leave, if offered
• Leave during notice period
• Public holidays and any optional or floating holiday scheme
• What counts as unauthorised absence and the consequences

Be precise. Vagueness in a leave policy generates disputes with total reliability. "Leave should be applied for in advance" invites an argument; "leave must be applied for at least three working days in advance except in the case of sickness or emergency, in which case the employee must inform their manager on the first day of absence" does not.

Note that statutory leave entitlements vary by state under Shops and Establishments legislation. If you operate in multiple states, either run a single policy set at or above the most generous applicable requirement, or clearly identify state-specific variations.

Section 5: Benefits

• Group health insurance: coverage, dependants covered, sum insured, claim process, network hospitals
• Life and accident cover, if provided
• Retirement benefits: provident fund, gratuity, corporate NPS if offered
• Wellness programmes, counselling support, employee assistance
• Learning and development budget and how to access it
• Referral bonus scheme
• Any allowances: internet, phone, transport, meals
• Employee discounts or perks

Include the practical detail. The single most common insurance question is "is my parent covered and how do I add them," and the handbook should answer it.

Section 6: Code of Conduct

This is the section that carries the most legal weight, so it deserves careful drafting.

• Expected professional behaviour
• Conflict of interest: what constitutes one, disclosure obligations
• Outside employment and moonlighting: your actual position, stated clearly
• Gifts and hospitality: limits and disclosure
• Anti-bribery and anti-corruption
• Confidentiality obligations, during and after employment
• Intellectual property ownership
• Use of company property and systems
• Social media conduct
• Dress code, if you have one and it matters
• Substance use policy
• Anti-discrimination and equal opportunity commitment
• Workplace violence and threatening behaviour
• What constitutes misconduct and gross misconduct, with examples

The moonlighting section deserves particular thought. Blanket prohibitions are increasingly difficult to sustain and increasingly resented. A disclosure-and-approval framework — outside work permitted subject to disclosure, no conflict of interest, no use of company resources, no impact on performance — is usually more defensible and more realistic than a ban nobody follows.

Section 7: Prevention of Sexual Harassment

This must be a standalone, prominent section. Include:

• The definition of sexual harassment, in the statutory sense
• Clear statement of zero tolerance
• Scope: who is covered, including contractors, interns, and visitors where applicable
• Composition of the internal committee with names and contact details
• How to file a complaint, including timelines
• The inquiry process in outline
• Confidentiality protections
• Protection against retaliation
• Consequences of a finding
• Consequences of a knowingly false complaint
• External escalation options

Update the committee member names whenever they change. A handbook listing an internal committee member who left two years ago is worse than useless — it actively obstructs someone trying to complain.

Section 8: Performance Management

• The performance cycle and its timing
• Goal-setting approach
• Review frequency and format
• Rating scale, if you use one, and what each level means
• How ratings connect to increments and promotions
• Feedback expectations, including upward and peer feedback
• Performance improvement process, described fairly
• Promotion criteria and process
• Internal job posting and mobility policy

Employees consistently report that the performance process is the least transparent part of working life. Documenting it properly is a low-cost trust intervention.

Section 9: Learning and Career Development

• Career levels and progression framework
• Training available and how to access it
• Certification and external course support, including any service commitment attached
• Mentoring or coaching programmes
• Internal mobility process

If you attach a service commitment to funded training — a common practice — state it explicitly here and in the individual agreement. Retrospective surprises about repayment obligations generate disproportionate ill will.

Section 10: Health, Safety, and Wellbeing

• Emergency procedures and evacuation
• First aid arrangements and trained personnel
• Incident and accident reporting
• Employees' compensation coverage
• Ergonomics and workplace setup, including for remote workers
• Mental health support and how to access it
• Fitness for work and return-to-work after extended illness

Section 11: Data Privacy and IT

• What employee personal data the company collects and why
• How it is stored, who can access it, and how long it is retained
• Employee rights regarding their data
• Acceptable use of company IT systems
• Bring-your-own-device policy, if applicable
• Monitoring: what is monitored and what is not, stated honestly
• Password and security requirements
• Incident reporting for suspected breaches
• Use of AI tools at work

The AI usage point has become non-optional. Employees are using generative AI tools whether or not you have a policy, and the risk of confidential information being pasted into third-party systems is real. State clearly which tools are approved, what may and may not be entered into them, and what disclosure is required for AI-assisted work product.

Be honest about monitoring. Employees discover the truth eventually, and a handbook that understated monitoring damages trust far more than one that stated it plainly.

Section 12: Grievance and Disciplinary Procedures

• How to raise a concern, with more than one channel
• Escalation path if the first channel is the problem
• Timelines for acknowledgement and resolution
• Whistleblower protection
• Disciplinary process: investigation, opportunity to respond, decision, appeal
• Range of disciplinary outcomes
• Suspension pending inquiry

The principle underlying any defensible disciplinary process is that the employee knows the allegation, has a genuine opportunity to respond, and is heard by someone who has not already decided. Describe your process in a way that reflects that.

Section 13: Separation

• Resignation process and notice period by level
• Notice buyout, if permitted, and how it is calculated
• Garden leave, if applicable
• Termination grounds and process
• Full and final settlement: components and timeline
• Return of assets
• Exit interview
• Documents issued: relieving letter, experience letter, Form 16
• Provident fund transfer or withdrawal guidance
• Post-employment obligations: confidentiality, non-solicitation
• Alumni and rehire policy

Section 14: Acknowledgement

A short, dated acknowledgement that the employee has received the handbook, had an opportunity to ask questions, and agrees to comply with the policies in it. Capture it electronically with a timestamp.

Writing a Handbook People Will Actually Read

Structure gets you halfway. Writing gets you the rest.

Use second person. "You may carry forward up to 30 days of earned leave" reads better than "Employees may carry forward a maximum of thirty (30) days of Earned Leave."

Cut the legalese. Reserve defined terms and formal construction for the few places where precision genuinely requires it. Everywhere else, write like a person.

Front-load the answer. Start each policy with the rule, then the exceptions, then the process. Readers who need only the rule should not have to read three paragraphs of context.

Use worked examples. A leave accrual example with actual numbers communicates more than three paragraphs of description. Same for salary slips, notice period calculations, and reimbursement limits.

Add tables for anything with variation by level, tenure, or state. Notice periods by grade, leave entitlements by category, insurance sums by band.

Keep paragraphs short. Three to four sentences. Dense blocks of text on a screen do not get read.

Include a genuine table of contents with links. People use handbooks as reference documents, not as books. Make search and navigation work.

Add an FAQ. Collect the questions HR actually gets and answer them directly. This is often the most-visited part of the whole document.

Say what you do not do. If you do not offer a particular benefit, saying so plainly is more useful than silence, which people interpret as an oversight and ask about.

Test it. Give a draft to five employees at different levels and ask them to find the answers to ten specific questions. Watch where they struggle. Fix those parts.

Legal Considerations for Indian Employers

Consistency With Contracts

The handbook must not contradict individual employment agreements. If your standard contract says three months' notice and the handbook says one month, you have created ambiguity that will be resolved against you.

Audit for consistency whenever either document changes.

Statutory Minimums

The handbook cannot provide less than the law requires. This is more complicated than it sounds for multi-state employers, because leave entitlements, working hours, and other conditions vary under state Shops and Establishments legislation.

Two workable approaches. Set your policy at or above the highest applicable state minimum and apply it uniformly, which is administratively simple and generous. Or state the base policy and include a clear annexure of state-specific variations, which is more precise and more work.

Do not set the policy at the lowest state's minimum and hope.

Right to Amend

Include a clause reserving the right to amend policies, with a commitment to communicate changes. Be aware that unilateral reduction of established benefits can be challenged as a change to conditions of service, particularly where the benefit has been consistently provided over a long period. Amending to add or clarify is straightforward; amending to take away requires care and often consultation.

Not Part of the Contract

Most handbooks state that they do not form part of the employment contract. This has a real advantage: it keeps the handbook amendable without individual consent. It also has a limitation: you cannot then rely on it as a contractual term when it suits you.

The practical approach is to keep genuinely contractual matters — notice period, compensation, confidentiality, IP assignment — in the employment agreement, and keep the handbook for procedural and policy matters.

Acknowledgement Records

Retain acknowledgement records for the full retention period applicable to employment records. Electronic acknowledgement with a timestamp and version identifier is far more reliable than a signed paper page that has to be located five years later.

Critically, capture acknowledgement of each version. An acknowledgement of the 2023 handbook does not establish knowledge of a policy introduced in 2025.

Language

Where a significant portion of your workforce is not comfortable in English, provide translations. In some contexts, state legislation requires notices in the local language. Beyond compliance, a handbook people cannot read achieves none of its purposes.

Rolling Out a Handbook

Publishing is not rolling out.

Announce it properly. A message from leadership explaining why the handbook exists and what it is for, not a link dropped in a channel.

Brief managers first. Give them the handbook a week early with a summary of what changed and answers to the questions they will be asked. A manager who cannot answer basic questions about a new policy undermines it.

Run a live session. Walk through the structure, highlight what is new, and take questions. Record it for people who cannot attend and for future joiners.

Make acknowledgement easy. One click from the email, in the system people already use. Every additional step costs you completion rate.

Track completion and chase. Report acknowledgement rates by team. Managers who see their team at 60 percent while peers are at 100 percent will act.

Integrate into onboarding. New joiners should acknowledge the handbook as part of day-one paperwork, not weeks later.

Set a review date. Put it in the calendar at publication.

Keeping It Current

A handbook decays. Policies change, committee members leave, benefits get renegotiated, and legislation moves. An out-of-date handbook is a liability, because it evidences that you told employees something that is no longer true.

Version control. Every handbook has a version number and an effective date on every page. Superseded versions are archived, not deleted — you may need to demonstrate what the policy was at a particular past date.

Named owner. One person accountable for the document, with a standing calendar reminder.

Trigger-based updates. Certain events should automatically trigger a handbook review: any change in the internal committee, any change to insurance terms, any change to the leave or notice policy, any new office location or state, any significant legislative change, and any organisational restructuring that changes reporting or escalation paths.

Annual review. Even absent triggers, review annually. Walk each section with the relevant owner — finance for payroll and reimbursement, IT for security and acceptable use, legal for conduct and separation, HR for everything else.

Change log. Maintain a visible summary of what changed in each version. Employees are far more likely to re-read a handbook when they can see a two-line summary of what is different.

Re-acknowledge material changes. Minor clarifications do not need re-acknowledgement. Changes to conduct standards, disciplinary process, leave entitlements, or data handling do.

Scaling the Handbook With the Company

The right handbook for a 15-person company is not the right handbook for a 500-person company, and trying to write the larger one too early wastes effort on policies you do not need yet.

Under 25 Employees

Keep it short — perhaps 15 pages. Prioritise the sections that prevent the most confusion and carry the most legal weight: leave, payroll basics, code of conduct, prevention of sexual harassment, data and IT use, and separation. Skip elaborate performance frameworks and career ladders you have not built yet. A handbook describing a promotion process that does not exist damages credibility more than its absence would.

At this size, much of the culture is transmitted directly by the founders. The handbook's job is to capture the rules, not the culture.

25 to 100 Employees

This is the stage where informal knowledge starts failing. New joiners no longer sit within earshot of everyone who knows how things work, and the founders no longer personally onboard each hire.

Expand the handbook to cover performance management, benefits in detail, grievance procedures, and the working arrangements you have settled into. Add the FAQ. Introduce version control if you have not already, because this is the stage where policy drift begins.

100 to 500 Employees

Multi-location and multi-state complexity typically arrives here, bringing state-specific leave and working-hours variations. Add the state annexure or standardise upward.

Formalise the career framework, internal mobility, and disciplinary process, because at this size decisions increasingly get made by people who do not know each employee personally, and consistency depends on written standards rather than shared judgment.

Acknowledgement tracking becomes genuinely necessary rather than merely good practice — you can no longer verify by memory who has seen what.

Above 500 Employees

Consider splitting the handbook into a core document plus function-specific or location-specific supplements, so that a warehouse employee is not navigating policies written for the engineering team. Maintain a single source of truth for shared policies to prevent the supplements from diverging.

At this scale, invest in searchability and analytics. Knowing which sections employees actually look up tells you where confusion concentrates, and that is a better guide to what needs rewriting than any internal review.

Handbook Build Checklist

Preparation

• Inventory existing policies, wherever they currently live
• Identify gaps against the section list above
• Identify contradictions between existing documents and contracts
• Confirm statutory minimums for every state where you operate
• Confirm current internal committee composition
• Confirm current insurance terms and benefit details
• Agree the ownership and approval path

Drafting

• Write in plain second-person language
• Include worked examples for leave, salary, notice, and reimbursement
• Use tables for anything varying by level, tenure, or state
• Add a linked table of contents
• Add an FAQ section built from real queries
• Include version number and effective date on every page

Review

• Legal review for conduct, disciplinary, separation, and data sections
• Finance review for payroll, reimbursement, and benefits
• IT review for security, acceptable use, and AI policy
• Manager review for practical workability
• Employee usability test with real questions
• Consistency check against the standard employment agreement

Rollout

• Leadership announcement
• Manager pre-brief
• Live walkthrough session, recorded
• One-click electronic acknowledgement
• Completion tracking by team with escalation
• Integration into onboarding flow

Maintenance

• Named owner assigned
• Annual review calendared
• Trigger events documented
• Change log maintained
• Archived versions retained
• Re-acknowledgement process defined for material changes

Frequently Asked Questions

Is an employee handbook legally required in India?

There is no single statute requiring a consolidated handbook. However, several individual policies are effectively mandatory — a prevention-of-sexual-harassment policy for covered employers, communication of terms of employment, and various display and record obligations under state legislation. A handbook is the practical way to meet these obligations coherently rather than through a scatter of separate documents.

How long should a handbook be?

Long enough to answer the questions people actually have, and no longer. For a small company, 20 to 30 pages is often sufficient. For a larger multi-state employer, 50 to 80 pages is common. Length matters far less than navigability — a well-indexed 70-page document is more usable than a poorly organised 25-page one.

Should the handbook be part of the employment contract?

Usually not. Keeping it separate lets you amend policies without individual consent. Keep contractual essentials — notice, compensation, confidentiality, intellectual property — in the employment agreement, and use the handbook for policies and procedures.

Can we change the handbook whenever we want?

You can amend policies with proper communication, and you should reserve that right explicitly. However, unilateral removal of established benefits can be challenged, particularly where the benefit has been provided consistently over a long period. Adding and clarifying is straightforward; taking away requires care.

Do we need different handbooks for different states?

Usually not. One handbook with a state-variations annexure is easier to maintain than several parallel documents. Alternatively, set uniform policies at or above the highest applicable statutory minimum.

What about employees who do not read English comfortably?

Provide translations for the languages your workforce actually uses. In some states, certain notices are required in the local language. Beyond compliance, an unread handbook does nothing.

How do we get people to actually read it?

You largely will not get people to read it cover to cover, and that is fine. Design for reference use: strong navigation, working search, a good FAQ, and short answers near the top of each section. Then make sure the sections people genuinely need on day one — leave, payroll, insurance, conduct — are covered in induction directly.

Should contractors and consultants receive the handbook?

Provide relevant extracts — conduct, confidentiality, data security, site safety, and prevention-of-harassment provisions — rather than the full document. Giving independent contractors the full employee handbook, including benefits and performance management, can undercut the independence of the arrangement.

How often should it be updated?

At minimum annually, and immediately on any trigger event such as a change in the internal committee, insurance terms, leave policy, notice policy, or new location.

What is the single most common mistake?

Writing it once and never touching it again. The second most common is failing to track acknowledgements, which removes most of the legal value the document would otherwise have.

Making the Handbook Useful

The difference between a handbook that works and one that does not comes down to three things: whether people can find answers in it, whether it reflects what actually happens, and whether you can prove people received it.

The first is a writing and structure problem. The second is a maintenance problem. The third is a systems problem — and it is the one most companies handle worst, because acknowledgement tracking through email attachments and spreadsheets fails quietly. Six months later nobody can say with confidence which version any given employee acknowledged, or when.

Hosting the handbook in the system employees already use for payslips, leave, and attendance solves several problems at once. New joiners acknowledge it during onboarding. Version changes trigger fresh acknowledgement requests automatically. Completion is visible by team. And when someone needs to know the leave carry-forward rule at four in the afternoon, they find it in the same place they applied for leave.

CozyHR hosts policy documents with version control, tracks acknowledgements by employee and version with timestamps, pushes re-acknowledgement requests when you publish a material change, and gives employees searchable access alongside their payslips and leave balances. Your handbook stops being a file in a drive and becomes a working part of the employee experience.

If your handbook is currently a PDF someone emailed out eighteen months ago, try CozyHR and give it somewhere to live.

This article provides general guidance and does not constitute legal advice. Employment law and state-specific requirements change; have your handbook reviewed by qualified counsel before publication.