How to Write an Employee Handbook for Indian SMBs

Every growing company reaches the moment when "ask Priya from HR" stops working as a policy framework. A new manager improvises a leave decision, two employees get different answers to the same question, an investor's diligence list asks for the employee handbook — and suddenly the absence of one document is generating risk, friction, and awkward Slack threads. This guide shows you how to write an employee handbook for an Indian SMB: what goes in it, what the law expects, how to draft each section, how to roll it out so people actually read it, and how to keep it alive as you scale.

It is written for founders and HR managers building their first handbook or rescuing an outdated one. A note on scope: a handbook summarises and communicates policies; it does not replace employment contracts, statutory obligations, or specialised policy documents (POSH, code of conduct for listed entities, and so on) — it stitches them into one navigable, human-readable home. And because laws vary by state and change over time, have counsel review the final draft; this article is practical guidance, not legal advice.

What an employee handbook is — and is not

It is a single, organised reference of your employment practices: how leave works, how pay works, what conduct is expected, how problems get raised and resolved. Its jobs are consistency (same answer for everyone), transparency (answers findable without asking), speed (managers decide from a common script), and protection (documented, uniformly applied policies are your best evidence of fair process in any dispute).

It is not an employment contract. The contract (appointment letter and annexures) creates the individual legal relationship; the handbook states general policies that can evolve. Keep the hierarchy explicit in the handbook itself: statute prevails over everything; the signed contract prevails over the handbook for individual terms; the handbook governs where the contract is silent. Include a clear reservation: the company may amend policies prospectively with notice.

It is also not a legal codex. If it reads like an Act, nobody will use it, and its practical value collapses to zero. The craft is writing plainly enough for a first-week employee while staying accurate enough for a labour officer.

Handbook, standing orders, and HR policy manual

Three artefacts get confused:

• Certified standing orders are a statutory instrument applicable to certain industrial establishments above headcount thresholds (historically under the Industrial Employment (Standing Orders) Act, with states applying it variably to commercial establishments; the Industrial Relations Code carries the concept forward). If your company falls in scope, the certified standing orders govern the matters they cover, and your handbook must align with them. Most small services/tech SMBs historically fall outside certification requirements — verify your position by state and sector.
• The HR policy manual is the detailed internal version — process maps, approval matrices, SOP-level detail for HR's own use.
• The employee handbook is the employee-facing layer: shorter, warmer, and linked to the detailed policies where depth exists.

Small companies can merge the last two; past ~100 employees, separating them keeps the handbook readable.

The legal spine: policies that are effectively mandatory

Before style, cover the floor. For most Indian SMBs, the following are statutory or near-statutory:

• POSH policy and Internal Committee details. Establishments with 10 or more employees must have a prevention-of-sexual-harassment policy and a properly constituted Internal Committee; the handbook should state the policy, the IC's composition and contacts, and the complaint route. This is the least optional page in the book.
• Leave and holidays per your state's Shops & Establishments framework. Your leave policy must meet the state floor (earned/casual/sick leave and holiday rules vary by state); multi-state employers must decide state-wise schedules or a harmonised superior policy.
• Working hours, overtime, and weekly offs consistent with state law, including any night-shift conditions.
• Maternity benefits per statute, and related facilities where applicable (crèche provisions at qualifying headcounts).
• Wages and deductions practices consistent with wage laws (pay dates, permissible deductions), plus statutory registrations that touch employees (PF, ESI, PT, LWF) explained in plain words.
• Equal opportunity and disability inclusion. Establishments covered by the Rights of Persons with Disabilities framework at qualifying sizes should publish an equal-opportunity policy; smaller employers benefit from adopting one regardless.
• Data privacy notice for employees. With the DPDP regime operational, tell employees what personal data you process and why, and how to raise privacy requests — see our DPDP for HR guide.
• Grievance route. A named, escalating path for workplace grievances; certain thresholds and sectors have formal committee expectations, and every size benefits from clarity.

Anything above this floor — flexible work, parental leave beyond statute, wellness benefits — is strategy, and where your handbook becomes a recruiting document rather than a compliance artefact.

Structure: the table of contents that works

A field-tested skeleton for an Indian SMB handbook, in reading order:

1. Welcome and how to use this handbook — founder's note, what the handbook is/isn't, the precedence clause, effective date and version.
2. Who we are — mission, values translated into behaviours (three lines each, with examples), a short history.
3. Employment basics — employment types (full-time, fixed-term, intern, consultant boundaries), probation and confirmation, background verification, personnel records and how to update them, notice periods by level (aligned to contracts).
4. Working hours and attendance — hours, flexibility norms, hybrid/remote rules, attendance capture method, late/short-day handling, overtime policy.
5. Leave and holidays — every leave type with accrual, application, carry-forward, encashment; holiday calendar mechanics; state variations; the leave application process in your HRMS.
6. Compensation and payroll — pay date, payslip access, salary structure overview, reimbursements, statutory deductions in plain words, tax declarations and proof cycles, advances/loans if offered.
7. Benefits — insurance, wellness, parental leave, learning budgets, anything you're proud of.
8. Performance and growth — cycle, ratings philosophy, promotions, PIP overview stated fairly.
9. Code of conduct — professional behaviour, conflicts of interest, gifts, anti-bribery basics, moonlighting/dual-employment stance, media/social media, dress norms if any.
10. Workplace safety and respect — POSH policy and IC, anti-harassment and anti-bullying beyond POSH, safety basics, substance policy.
11. IT, security, and data — acceptable use, confidentiality, IP assignment reference (contract governs), device and access rules, employee data privacy notice, AI-tool usage rules.
12. Communication and expenses — meeting/communication norms if you have strong ones, travel and expense summary.
13. Grievances and discipline — how to raise issues (multiple routes), investigation principles, disciplinary framework and proportionality, appeal path.
14. Separation — resignation process, notice and recovery, exit process, F&F timeline, alumni references.
15. Acknowledgment — version, effective date, and the employee's acknowledgment mechanism.

Two structural rules: nothing in the handbook should exist only in the handbook (each section links to the governing detailed policy or system), and every section should answer the three questions employees actually have — what applies to me, how do I do it, who do I ask.

Drafting guidance, section by section

Welcome and values

Write the founder's note like a human: why the company exists, what you promise employees, what you ask of them. Then translate values into observable behaviour ("Bias for action: we ship a v1 this week rather than debate a v3 this quarter") — abstract nouns don't guide anyone. This is also where tone is set: the handbook should sound like your best manager on a good day — clear, warm, unambiguous.

Employment basics

Precision here prevents disputes later. Define employee categories and what each means for benefits eligibility. State probation length, what confirmation depends on, and what happens if it's extended — silence on extension is a classic gap. Cross-reference our probation policy guide for the mechanics. Explain personnel records: what you keep, where, and the employee's duty to keep details current (bank, address, nominee — nominations for PF/gratuity/insurance deserve an explicit prompt).

Hours, attendance, and flexibility

Say what is actually true. If you are hybrid with anchor days, write the anchor days and the exception process. If field staff mark attendance by GPS, say so and link the tracking-transparency note. Cover the unglamorous cases that generate most tickets: forgot-to-punch regularisation, half-days, working on holidays and comp-off rules.

Leave

The most-read chapter. For each leave type: eligibility, accrual timing, application lead-time, documentation (keep it minimal), carry-forward/encashment, and what happens on exit. Write the sandwich-leave rule (holidays between leave days) explicitly, whichever way you decide. State-specific holiday lists belong in an annexure updated annually, not hard-coded in the body.

Compensation and payroll

Demystify the payslip: one diagram of a sample payslip with each line explained converts a hundred future questions into zero. State the pay date honestly (and the weekend/holiday rule), the reimbursement cycle, and the tax-proof calendar. Plain-words explanations of PF, ESI, PT, and gratuity — two sentences each with links to deeper guides — earn enormous goodwill.

Conduct

Resist the urge to legislate everything. Anchor on principles (integrity, respect, confidentiality), then be specific only where ambiguity is dangerous: conflicts of interest (define, with examples and a disclosure route), gifts thresholds, external work/moonlighting stance, public commentary about the company, and use of company data with AI tools. Each specific rule should exist because you can name the failure it prevents.

Safety and respect

State the POSH policy in full or summarise with a link to the standalone policy; either way, IC names/contacts and the complaint route must be current — an outdated IC list in the handbook is a compliance finding, not a typo. Extend respect norms beyond the statute: bullying, discrimination on any protected or decent-society ground, and a bystander-reporting route.

IT and data

Cover acceptable use, access discipline (no credential sharing), device rules including BYOD if allowed, incident reporting ("tell us fast beats tell us never"), and the employee privacy notice: categories of data processed, purposes, retention in plain terms, and the contact for privacy requests. Add your AI-usage rule — what may and may not be pasted into external tools — since this is now among the most common conduct questions.

Grievances and discipline

Describe multiple raising routes (manager, HR, skip-level, anonymous channel if you have one) and commit to acknowledgment timelines. For discipline, state the philosophy (proportionate, investigated, documented), an illustrative — expressly non-exhaustive — list of misconduct, and the process arc: inquiry, representation, outcome, appeal. Avoid promising rigid step sequences ("first offence always gets a warning") that handcuff you in serious cases; promise fairness of process instead. For serious misconduct in covered establishments, formal domestic enquiry norms apply — link your detailed guide.

Separation

Walk the exit calmly: how to resign (in the system, not by vanishing), notice by level, buyout terms if offered, handover expectations, asset return, F&F timeline and components, and what references/relieving letters look like. A fair, predictable exit chapter is quietly one of your best recruiting documents — candidates read how you treat leavers.

A sample chapter, annotated

To make the style concrete, here is a compressed model of a leave-chapter opening, with commentary on why each move matters:

Leave at Meridian You accrue 1.5 days of earned leave (EL) on the first of every month — 18 days a year. EL is for planned time off: apply in CozyHR at least 5 working days ahead, and your manager approves or discusses alternatives within 2 working days. Sick leave (SL): 8 days a year, credited in January. For 3+ consecutive days, attach any medical note; for less, we trust you. Carry-forward: up to 30 EL days total; beyond that, excess lapses each January. EL is encashed at basic pay when you leave. The sandwich rule, plainly: if you take Friday and Monday off, the weekend is not counted as leave. Holidays inside a leave block don't consume balance either. Example: Asha joins on 10 March. Her March EL is prorated to 1 day; her SL for the year is prorated to 6.5, rounded to 7. She applies for 26–30 May (5 working days, 1 holiday in between): 4 days of EL are deducted. Questions or edge cases → HR helpdesk, "Leave" category. State-specific holiday lists are in Annexure B.

What this little excerpt does deliberately: leads with the number people want; uses second person and bold sparingly for scan-ability; states process with named timelines on both sides (employee applies 5 days ahead, manager responds in 2); makes the trust posture explicit on sick notes; kills the two classic dispute generators (sandwich rule, proration) with a plain statement and a worked example; and routes exceptions somewhere specific. Every chapter of your handbook can follow this pattern: number → process → edge cases → example → escape hatch. Write one chapter this way and the rest inherit the voice.

Writing style rules

• Second person, active voice. "You accrue 1.5 days of earned leave each month" beats "Employees shall be entitled to…".
• Short sentences, real words. If a sentence needs a lawyer to parse, move it to the contract or rewrite it.
• Examples over abstractions. One worked example per complex rule (leave proration, notice recovery) prevents most misreadings.
• Honest hedges only where needed. "Manager discretion" is acceptable when bounded ("your manager may approve up to two remote weeks; beyond that, HR").
• Bilingual consideration. If a meaningful share of your workforce reads Hindi or a regional language more comfortably, translate at least the safety, POSH, grievance, and leave chapters; comprehension is the point.
• Inclusive language throughout. Gender-neutral phrasing, no assumptions about family structures, disability-aware wording.

The drafting process: four weeks, realistically

1. Week 1 — inventory. Collect every existing policy, email ruling, and unwritten practice. List open questions where practice is inconsistent ("do we pay for holiday work or comp-off?"). Decide each with leadership — the handbook project's hidden value is forcing these decisions.
2. Week 2 — draft. Write from the skeleton above, one chapter per sitting, linking detailed policies. Steal structure from your best-written existing policy; keep voice consistent (one writer, others review).
3. Week 3 — review. Three passes: managers (is it operable?), a small employee panel (is it clear? what's missing?), and counsel (statutory alignment, state variations, discipline/exit language). Reconcile; resist scope creep to a policy-manual rewrite.
4. Week 4 — finalise and stage rollout. Version-stamp (v1.0, effective date), publish to your HRMS/ESS, configure acknowledgments, brief managers first, then announce.

Rollout and acknowledgment

• Managers first. A 45-minute walkthrough with managers a week before launch, focused on what changed and how to answer questions, prevents the worst outcome: managers contradicting the new book in week one.
• Launch with the three changes that matter. Nobody reads 40 pages on day one; the announcement should name the two or three policies that changed and link the rest.
• Digital acknowledgment. Host the handbook in your ESS and capture acknowledgments there — versioned, timestamped, reportable. Paper signatures in a drawer defeat the purpose. New hires acknowledge during onboarding; existing staff within a stated window with reminders.
• Searchability beats structure. The handbook's real interface is search ("comp off", "notice buyout"); hosting it as searchable pages in your HRMS outperforms a PDF attachment every time.
• FAQ the first month. Collect every question asked in the first 30 days; publish a living FAQ; fold the top items into the next version.

Keeping it alive: governance

A handbook decays the day it ships. Light governance keeps it true:

• One owner (HR lead) with authority to accept/reject change requests; a change log at the back of the book.
• Two review triggers: the calendar (annual full review, aligned to statutory updates and your compliance calendar) and events (a new law, a new benefit, an incident exposing a gap — update within the month).
• Version discipline. Semantic-ish versioning works: v2.1 for a clarified clause, v3.0 for material changes requiring re-acknowledgment. Material changes get communicated as changes, not silently republished.
• Consistency audits. Twice a year, sample five real HR decisions (a leave denial, a discipline outcome, an exit) against the book. Divergence means either the practice or the book is wrong — fix whichever it is, deliberately.
• Metrics. Acknowledgment coverage, search queries with zero results (your gap list), policy-related helpdesk volume trending down.

Worked example: zero to v1 at a 60-person startup

"Halyard", a 60-person Bengaluru SaaS startup, ran on tribal knowledge: policies lived in six Notion pages, four email threads, and the founder's memory. Two triggers forced the handbook — a Series A diligence checklist, and a messy dispute where two employees received different notice-period answers.

Inventory (week 1). HR listed 31 policy questions, of which 11 had no decided answer, including comp-off, moonlighting, and probation extension. Leadership decided all 11 in two working sessions — the founders later called this the project's real payoff.

Draft (week 2). One writer (the HR lead) drafted from a skeleton like the one above, at roughly a chapter per day. The POSH policy already existed as a standalone document and was summarised with a link; IC contacts were updated in the same pass — they were two exits stale, a fix worth the whole exercise.

Review (week 3). Manager review surfaced operability gaps ("the book says approve leave in 2 days; I'm on customer sites — can it be 3?"). An employee panel of five flagged jargon and asked for worked examples in leave and payroll. Counsel corrected two things: a US-template "at-will" sentence that had crept in from a borrowed doc, and the disciplinary chapter's over-promised step sequence.

Ship (week 4). v1.0 published in the ESS with digital acknowledgment; managers briefed on the three changed policies (comp-off formalised, moonlighting disclosure route added, probation extension capped and defined); all-hands announcement ran ten minutes. Acknowledgment hit 95% in two weeks with automated reminders doing the chasing.

Aftermath. Policy questions to HR dropped visibly within a quarter, and — the metric nobody predicted — new-manager onboarding time fell, because "read chapters 3–5 and the manager annex" replaced a month of osmosis. The diligence checklist item took one link to close. Total cost: about 25 working hours and one counsel review.

The pattern scales down further: at 20 people, the same process fits in a fortnight with a 20-page book. The forcing function — deciding the undecided — is the same at every size.

Common mistakes to avoid

• Copy-pasting a foreign template. US-style at-will language, FMLA references, and alien leave constructs mark the book as unread by its own company — and can contradict Indian law.
• Promising more process than you'll deliver. Every "always within 5 working days" is a commitment; audit them before printing.
• Writing the maximum-severity voice. Handbooks drafted as if every employee is a future defendant poison culture for the 98% who aren't.
• Hard-coding volatile facts. Names, rates, and holiday lists go in annexures or linked pages; the body should survive a year without edits.
• Shipping without manager briefing. The book answers employees; managers answer everything else — unbriefed managers improvise, and improvisation is what the handbook exists to end.
• Treating acknowledgment as protection while enforcing inconsistently. In any dispute, your practice is evidence as much as your prose. The book must describe what you actually do.

The statutory-link map

Use this quick-reference table while drafting, to keep each chapter anchored to its legal source and its update trigger:

The table is deliberately generic — anchors vary by state, sector, and headcount, and implementation of the labour codes continues to evolve. Its job is to make sure every chapter has a named legal owner in your compliance calendar, so statutory drift gets caught by process rather than by incident.

Frequently asked questions

Is an employee handbook legally required in India?

No single statute mandates "a handbook", but several obligations effectively require written, communicated policies — POSH policy for 10+ employees, leave rules meeting state floors, equal-opportunity policy under disability law at qualifying sizes, privacy notices under the DPDP regime, and certified standing orders where applicable. A handbook is the practical vehicle that satisfies the communication half of these duties.

Handbook or individual policy documents — which should come first?

If you have nothing, write the handbook first as the umbrella and let its chapters be the policies at SMB scale. Where a domain needs procedural depth (POSH, disciplinary process, expense claims), spin out standalone policies and let the handbook summarise and link. Never maintain the same rule in two places with two wordings.

Can the handbook be changed unilaterally?

Policies can generally be amended prospectively with notice, and the handbook should reserve that right — but individual contractual terms cannot be worsened unilaterally, and covered establishments must align with certified standing orders. Material changes deserve communication and fresh acknowledgment; significant changes to terms may need contractual handling. When in doubt on a specific clause, take advice.

How long should our handbook be?

As short as truthfulness allows. Most SMB handbooks land between 25 and 50 well-spaced pages or their web equivalent. Past that, move detail into linked policies. The right length test: a new hire can read it in one sitting and a manager can find any answer in under a minute.

Do interns and consultants get the handbook?

Interns: yes, with an annexure noting which chapters apply (conduct, safety, IT always; leave/benefits per intern terms). Consultants: no — giving genuine independent contractors the employee handbook blurs classification lines you want kept sharp; give them a focused conduct-and-confidentiality note instead. See our consultant vs employee guide.

What should we do about policies we're not ready to formalise?

Leave them out rather than writing aspirations. A handbook that promises a career framework "coming soon" ages badly. Ship v1 with what is true; add chapters as reality catches up — that is what versioning is for.

English only, or translated?

Match your workforce. If shop-floor, field, or support staff read a regional language more comfortably, translate at minimum the safety, POSH, grievance, leave, and payroll chapters, and state which version prevails in interpretation (usually English) while committing to keep translations current.

How does the handbook interact with our HRMS?

The HRMS is where the handbook becomes enforceable reality: leave rules configured as the book states, attendance and overtime per the hours chapter, acknowledgments captured against versions, and policies hosted searchably in the ESS. Divergence between system behaviour and handbook text is the most common source of "the policy says X but the system does Y" tickets — review both together at every version bump.

Conclusion

An employee handbook is your company's operating system made legible: the promises, rules, and processes that let a hundred people act consistently without asking a hundred questions. Build it on the statutory spine, structure it for findability, write it like a good manager talks, decide the undecided as you draft, roll it out through managers, and govern it like living software — versioned, owned, and audited against real practice.

The fastest way to make the book real is to host it where work happens. CozyHR lets you publish the handbook in the employee self-service portal with versioned acknowledgments, configure leave/attendance/payroll to match its chapters exactly, and answer the "what's our policy on…" questions with a search box instead of a queue outside HR's desk. Draft the book, then let CozyHR run it — try it free and retire "ask Priya" as your policy engine.

This article is general information, not legal advice. Statutory applicability varies by state, sector, and headcount, and rules change — have counsel review your handbook before adoption.