How to Write an Employee Handbook: An SMB Guide

An employee handbook is the one document every new joiner receives and almost nobody reads. That is usually the handbook's fault, not the reader's. Most handbooks are assembled from templates, written in a register somewhere between a legal contract and a corporate brochure, and structured so that finding the answer to "how much notice do I need to give for leave?" takes four minutes and two guesses.

This guide shows how to write an employee handbook that people actually use — one that answers real questions quickly, holds up if it is ever tested, and does not need rewriting every time the business changes shape. It is written for HR managers, founders and operations leads at small and mid-sized Indian companies building their first proper handbook, or replacing one that has quietly stopped being true.

What a handbook is for, and what it is not

Be clear about the job before you start writing.

A handbook is:

• A single place employees can find how things work here
• A record that policies were communicated, with a date and an acknowledgement
• A consistency mechanism, so two managers give the same answer to the same question
• A cultural artefact — the tone tells people more about the company than the content does
• A defensive document, in the narrow sense that a documented, communicated and consistently applied policy is far stronger than an informal practice

A handbook is not:

• An employment contract. Your appointment letter is the contract. The handbook should state explicitly that it is not a contract and that the company may amend it, while noting that terms in the appointment letter prevail where they conflict.
• A legal compilation. It should reference statutory rights, not reproduce statutes.
• A substitute for management. No policy makes a weak manager consistent.
• A finished object. It is a living document with a version number and a review date.

The most common failure mode is a handbook written to protect the company from every conceivable scenario. It becomes long, defensive and unusable, and because nobody reads it, it protects nothing. A handbook that is read is worth more than a handbook that is comprehensive.

Verify before you publish: statutory entitlements, leave rules, notice requirements, working hours and state-specific obligations vary by state, establishment type and employee category, and change with notifications. Have your final draft reviewed by a labour law advisor for your jurisdictions before issuing it.

Before you write: seven decisions to settle

Handbook projects stall in the middle because these decisions were not made at the start.

1. Who is it for? One handbook for all employees, or separate versions for corporate and operations populations? Multi-state or multi-entity groups often need a common core with state or entity annexures. Decide now — retrofitting is painful.

2. What is in the handbook versus in a standalone policy? Handbooks work best as a navigable summary with links to detailed policies for complex areas (POSH, data protection, travel and expense, ESOP). Put the everyday answers in the handbook and the exhaustive procedure in the linked policy.

3. Who owns it? One accountable owner, usually the HR head, plus named owners for each section. Without section owners, updates never happen.

4. What is the tone? Pick a register and hold it. Write in plain language and in the second person ("you"), avoid legalese except where precision genuinely matters, and cut every sentence that exists to sound serious rather than to convey information.

5. Where will it live? A PDF emailed on day one is the weakest option — it is instantly stale and unsearchable in practice. A page in your HR system, searchable and versioned, with acknowledgement tracked against the employee record, is dramatically better.

6. How will changes be handled? Define an amendment process: who approves, how much notice for material changes, and how acknowledgements are re-collected.

7. What is the review cadence? Annual as a minimum, plus event-driven reviews when the law changes, when you enter a new state, or when headcount crosses a threshold that triggers new obligations.

The handbook structure that works

Here is a structure that covers what Indian employers need without sprawling. Roughly 30 to 45 pages is a reasonable target for a company under 500 people.

Section 1: Welcome and how to use this handbook

Two pages maximum. A short welcome, what the handbook covers, the disclaimer that it is not a contract, the effective date and version, who to contact with questions, and a one-page index of the twenty most-asked questions with page references. That index page will be the most-used page in the document — build it deliberately.

Section 2: About the company

Mission, what the company does, values, and a brief organisational overview. Keep values to three to five, and write one line under each explaining what it looks like in practice. Values without behavioural translation are decoration.

Section 3: Employment basics

• Employment categories: permanent, fixed-term, probationary, intern, apprentice, consultant. Define each and state which policies apply to whom. This single table prevents dozens of downstream questions.
• Probation and confirmation: duration, how performance is reviewed, extension possibility, and what changes on confirmation.
• Working hours and weekly off: by category, cross-referencing the attendance policy.
• Attendance and punctuality: the summary, with the detailed rules in the attendance policy.
• Employment verification and background checks: what is checked and the consequence of misrepresentation.
• Personnel records: what the company keeps, the employee's duty to keep it current, and how to request corrections.

Section 4: Compensation and payroll

• Pay cycle and pay date: the cut-off, the pay date, and what happens when the pay date falls on a holiday.
• Salary structure: the components, the difference between CTC, gross and net, and where to find the personal breakup. Do not publish individual numbers here — explain the framework.
• Statutory deductions: provident fund, state insurance where applicable, professional tax, and income tax withheld at source, described in plain language with a pointer to the self-service portal for details.
• Tax declarations and proof submission: the annual cycle, the deadlines, and what happens if proofs are not submitted.
• Reimbursements: what is claimable, limits, and the submission process.
• Overtime, allowances and incentives: eligibility and how they are computed.
• Increments and reviews: the cycle, what drives an increment, and an explicit statement that increments are not guaranteed.
• Payslips and Form 16: where to access them and by when.

Employees judge an employer heavily on payroll clarity. This section repays every hour spent making it precise.

Section 5: Leave and time off

The most-read section by a wide margin. Cover each leave type in the same format: who is eligible, how much, how it accrues, how to apply, notice required, approval, carry-forward, encashment, and interaction with holidays and weekly offs.

Typical leave types to address:

• Earned or privilege leave
• Casual leave
• Sick leave, and when a medical certificate is required
• Public holidays, with a pointer to the location-wise annual list
• Maternity leave and related benefits
• Paternity or partner leave, where offered
• Bereavement leave
• Marriage leave, where offered
• Compensatory off for weekly off or holiday working
• Unpaid leave and sabbatical, where offered
• Leave during notice period — state the rule clearly, because it is contested more than any other

Include a worked example. One short illustration of how a mid-year joiner's earned leave accrues answers more questions than three paragraphs of description.

Section 6: Workplace conduct

• Code of conduct: the behavioural standard, written as expectations rather than prohibitions where possible.
• Anti-harassment and POSH: a clear summary of the policy, the Internal Committee members and how to reach them, the complaint process, and the assurance against retaliation. The detailed policy sits alongside as a standalone document, as required.
• Anti-discrimination and equal opportunity.
• Conflict of interest and outside employment: what must be disclosed, and to whom. Cross-reference your moonlighting policy if you have one.
• Gifts, hospitality and anti-bribery.
• Confidentiality and intellectual property: summarised, with the binding terms in the appointment letter and any separate agreement.
• Substance use, workplace safety and emergency procedures.
• Social media and public communication: what employees may say about the company, and who is authorised to speak for it.
• Company property and acceptable use of IT systems.

Section 7: Performance and development

• The performance cycle: goal setting, check-ins, review, calibration, outcomes
• How ratings are used, and how they connect to increments and promotions
• Promotion and internal mobility: how roles are posted and who is eligible
• Learning and development: what is available, what needs approval, any bond or claw-back on funded programmes
• Managing underperformance: the improvement plan process, in outline

Section 8: Health, safety and wellbeing

• Insurance and benefits: group health, personal accident, term life, with a pointer to the benefits document for coverage detail
• Employee assistance or counselling support, if offered
• Workplace safety expectations, incident reporting, first aid
• Facilities: crèche, canteen, transport, where applicable
• Ergonomics and remote work setup, if relevant

Section 9: Work arrangements

• Remote and hybrid working: eligibility, expectations, the in-office pattern, equipment
• Travel policy summary: approvals, class of travel, allowances, and where the detailed policy lives
• Relocation and transfer

Section 10: Grievances and dispute resolution

• How to raise a concern, and the escalation path
• The grievance committee or mechanism, and expected timelines
• Whistleblower protection and any anonymous reporting channel
• The disciplinary process in outline, including the principle that employees will be given an opportunity to respond before adverse action

Section 11: Separation

• Resignation: notice period, how to resign, notice buyout if applicable
• Exit process: handover, clearance, asset return, exit interview
• Full and final settlement: what it includes and the expected timeline
• Relieving and experience letters: what is issued and when
• Post-employment obligations: confidentiality, and any restrictive covenants as set out in the appointment letter
• Absconding: what happens when an employee stops attending without information

Section 12: Acknowledgement

A short acknowledgement page — or, better, a digital acknowledgement captured in your HR system with a timestamp against the employee record. The acknowledgement should confirm that the employee has received the handbook, has had an opportunity to ask questions, and understands that the handbook may be amended.

Writing it well: practical craft

Lead with the answer. Start each policy with the rule, then the exceptions. "You have 18 days of earned leave a year" before "Earned leave is credited on a pro-rata basis in accordance with the leave policy as amended from time to time."

Use the second person. "You must apply at least three working days in advance" beats "Employees shall be required to make application not less than three working days prior."

Give numbers, not adjectives. "Reasonable notice" means nothing. "Three working days" means something.

Answer the question people actually ask. Under each policy, imagine the three questions an employee would ask a colleague and make sure the text answers them. For leave: How much do I have? How do I apply? What if my manager doesn't respond?

Show, with examples. A worked example of a leave accrual, a notice period calculation, or a reimbursement claim is worth several paragraphs.

Use tables for anything with variation by category. Eligibility, entitlement, notice period, approval level — all better as tables.

Cut hedging. Phrases like "generally", "usually", and "at the discretion of management" scattered through a policy tell employees the rule is not real. Use discretion language only where discretion genuinely exists and say who exercises it.

Keep formatting consistent. Same heading structure for every policy. Predictability is what makes a reference document usable.

Version everything. Header or footer on every page: version number, effective date, owner. When someone quotes the handbook back to you, you need to know which version they are quoting.

A before-and-after example

Before: > Employees are expected to inform their reporting manager in a timely manner in the event that they are unable to report to work due to illness or other unforeseen circumstances, and may be required to furnish appropriate documentation at the discretion of management.

After: > If you are unwell and cannot work: message your manager before 10:00 am on the day. If you are away for three or more consecutive days, send a medical certificate to hr@company.com within two working days of returning. Your manager approves sick leave in the HR portal.

The second version is shorter, tells the employee exactly what to do, names the timelines, and is far easier to apply consistently.

A worked example: one leave policy page, written properly

Abstract advice about style is less useful than a model. Here is what a single handbook page looks like when it follows the rules above. Treat the numbers as placeholders for your own entitlements.

---

Earned leave

What you get. 18 days of earned leave per financial year, credited at 1.5 days per completed month of service.

When it is credited. On the first day of each month, for the previous completed month. If you join on or before the 15th, that month counts as a completed month; if you join after the 15th, crediting starts the following month.

How to apply. Raise the request in the HR portal. Give at least 5 working days' notice for 1–2 days, and at least 15 working days' notice for 3 or more consecutive days. Your reporting manager approves. If your manager has not responded within 3 working days, the request escalates automatically to their manager.

Weekly offs and holidays. Weekly offs and public holidays falling inside an approved earned leave period are not deducted from your balance.

Carry-forward. You may carry forward up to 30 days into the next financial year. Anything above 30 days lapses on 31 March.

Encashment. You may encash up to 10 days once per financial year, in March, subject to retaining a minimum balance of 5 days. Encashment is taxable as salary.

On exit. Your unused balance is paid out in the full and final settlement, calculated on basic salary.

During notice period. Leave during your notice period requires approval from your manager and the HR head. Approved leave does not extend your last working day unless HR confirms otherwise in writing.

Worked example. Priya joins on 10 August. She is credited 1.5 days on 1 September (for August), and 1.5 days on the first of each following month. By 31 March she has earned 12 days. She takes 4 days in December, leaving 8 days, which carry forward in full.

---

That page is roughly 300 words, answers every routine question, and can be applied identically by any manager in the company. Compare it with the two-page version most handbooks contain, which typically answers fewer of these questions and requires an HR email to resolve.

Policies that should live outside the handbook

Some subjects are too detailed, too regulated, or too frequently updated to sit inside the main document. Keep a short summary in the handbook and maintain the full text separately, linked from it.

The rule of thumb: if the content changes more than once a year, or requires legal review to change at all, it belongs in a linked policy rather than in the handbook body. This keeps the handbook stable enough to be worth reading.

Making the handbook work for an operations workforce

Handbooks written by corporate HR teams tend to assume a laptop, an email address and an hour of reading time. For retail, manufacturing, logistics and field populations, that assumption breaks immediately. Four adaptations make the difference.

Format for the phone. Most frontline employees will read this on a five-inch screen, in a break, standing up. Short sections, large headings, one idea per screen. A single long PDF is effectively unreadable in this context.

Lead with what affects their pay. For frontline teams, the questions are overwhelmingly about attendance, shifts, overtime, leave, and how salary is calculated. Put those first, not after eleven pages of values and organisational structure.

Translate. A version in the primary local language of each site is not a nicety. Comprehension of terms of employment is the entire point of the exercise, and it matters most for the population least likely to read English legal prose.

Communicate in person, then document. For these teams, the handbook supports the conversation rather than replacing it. Run a fifteen-minute induction with the supervisor, using a one-page summary card, then record acknowledgement digitally. The card should cover: shift timings and weekly off, how to mark attendance, how to apply for leave, how to raise a grievance, safety essentials, pay date and payslip access.

Test comprehension, not receipt. Ask three questions a week after induction: When is your weekly off? How do you apply for leave? Whom do you tell if something unsafe happens? If people cannot answer, the handbook has not done its job, however many acknowledgements you have collected.

Connecting the handbook to onboarding

A handbook delivered as a day-one attachment is a formality. A handbook woven into the first month is a tool.

Before day one. Send the handbook with the offer or joining kit, not on the first morning. New joiners actually read documents in the gap before they start, when they have time and are motivated to know what they have signed up for.

Day one. Cover only what they need immediately: attendance and hours, leave application, pay date, whom to ask for help, and the code of conduct. Fifteen minutes, not ninety.

Week one. Collect acknowledgement, after questions have been answered rather than before. An acknowledgement signed before the person has had a chance to ask anything is a weaker record than one signed after a documented Q&A.

Week two to four. Drip the rest through onboarding tasks: benefits enrolment triggers the benefits section, the first expense claim triggers the reimbursement section, the first goal-setting conversation triggers the performance section. Policies read at the moment they become relevant are remembered; policies read in bulk are not.

Day 30 check-in. Ask what was confusing. New joiners are the only people in your company who read the handbook with fresh eyes, and their confusion is the most accurate diagnostic you will ever get. Log it, fix it in the next version.

On confirmation. A short refresher on the policies that change at confirmation — notice period, leave entitlement, benefits eligibility — closes the loop.

This sequencing costs no extra effort. It simply moves content to the moment it is useful, which is the difference between a document that is filed and a document that is used.

Common mistakes to avoid

Copying a foreign template. Handbooks built from templates written for other jurisdictions import concepts that do not apply here and omit obligations that do — appointment letters, statutory registers, POSH committee details, state-specific leave rules.

Turning the handbook into the contract. Detailed compensation terms, restrictive covenants and termination terms belong in the appointment letter. Duplicating them in the handbook creates conflicts and makes routine handbook updates legally fraught.

Writing policies you will not enforce. An unenforced policy is worse than no policy: it establishes a practice inconsistent with your written rule, which is exactly the situation you were trying to avoid.

Vague disciplinary language. "Strict action will be taken" tells nobody anything. Describe the process, not the threat.

Ignoring the operations population. If half your workforce is field-based or shift-based, a handbook written entirely around office norms will be ignored by half your workforce.

Skipping acknowledgement. Communication you cannot evidence is communication that did not happen, at least in any process that later depends on it.

Letting it go stale. A handbook that still references a policy you abandoned two years ago undermines every other policy in the document.

Making it impossible to search. A 90-page PDF is a filing cabinet. Employees will ask their manager instead, and the manager will improvise.

Building it: a six-week plan

Week 1 — Inventory and decisions. List every existing policy, note the owner, the last review date and whether it is still true. Make the seven decisions above. Agree the structure.

Week 2 — Draft the core. Sections 3, 4, 5 and 11 — employment basics, pay, leave and separation. These are the highest-traffic sections and the hardest to get right. Draft them first while energy is high.

Week 3 — Draft the rest. Conduct, performance, wellbeing, work arrangements, grievances.

Week 4 — Review. Three parallel reviews: a labour law advisor for compliance, a finance or payroll lead for the compensation section, and two or three employees from different populations for usability. The employee review is not optional — it is the only one that tells you whether the document is readable.

Week 5 — Revise and design. Incorporate feedback, apply consistent formatting, build the index page, set version control.

Week 6 — Launch. Publish in your HR system, run a short all-hands or team-level walkthrough covering what changed, collect acknowledgements, and brief managers on where to point people.

Then, immediately: schedule the next review, assign section owners, and set a reminder for the annual cycle. The project is only over when maintenance is somebody's named job.

Keeping it alive

Track questions. Every question an employee asks HR that the handbook should have answered is a defect. Log them, and use the log to prioritise the next revision.

Update on triggers, not just on schedule. New state of operation, headcount threshold crossed, statutory change, new benefit introduced, incident that revealed a gap.

Re-acknowledge material changes. Minor edits do not need a fresh acknowledgement; changes to leave, pay, conduct or separation terms do.

Keep a change log. A one-page table at the back listing version, date, sections changed and a one-line summary. It costs nothing and saves considerable confusion later.

Measure use. If your handbook lives in a system, look at which pages are opened. Low traffic on a section you expected to be popular usually means it is hard to find, not that nobody cares.

Roles, responsibilities and the approval trail

A handbook only produces consistency if someone owns each part of it and someone applies it the same way twice. Set out the ownership explicitly, ideally in a short appendix.

Alongside ownership, define who may grant an exception. Almost every handbook eventually meets a case it did not anticipate — an employee needing eight weeks of unpaid leave for a family emergency, a role that genuinely cannot follow the standard notice period. Naming an exception approver, requiring the reason to be recorded, and reviewing exceptions quarterly turns improvisation into a controlled process. It also generates the best possible input for the next revision: a pattern of similar exceptions is a policy that needs changing.

Measuring whether the handbook is working

Four indicators tell you more than any amount of internal opinion.

Acknowledgement completeness. The proportion of current employees who have acknowledged the current version. Anything below full coverage is a process gap, not an employee problem — chase it through the same workflow you use for any onboarding task.

Repeat question volume. Track the questions HR answers that the handbook already covers. High volume on a covered topic means the content exists but cannot be found, which is a structure or search problem.

Manager consistency. Ask three managers the same policy question separately. Divergent answers point precisely at the sections that need rewriting.

Time to answer. Give a new joiner five common questions and time how long it takes them to find each answer in the handbook. Under a minute each is the target. This test takes fifteen minutes and is more informative than a full readability audit.

Review these each time you revise. A handbook that scores well on all four is doing the job — regardless of whether it is thirty pages or forty-five.

Frequently asked questions

Is an employee handbook legally required in India? There is no standalone statutory requirement to publish a handbook as such. However, several underlying obligations are effectively met through documented and communicated policies — issuing appointment letters, maintaining a POSH policy and committee, notifying working conditions, and communicating terms of employment. A handbook is the practical vehicle for many of these, which is why most employers maintain one even though the document itself is not separately mandated.

Can a handbook be treated as part of the employment contract? It depends on how it is drafted and referenced. Most employers include an express statement that the handbook is not a contract, that it may be amended, and that the appointment letter prevails in case of conflict. Even with that language, consistently applied policies can shape expectations, so avoid writing anything you are not prepared to follow. Have your disclaimer reviewed by a legal advisor.

How long should an employee handbook be? For a company under 500 employees, 30 to 45 pages is usually sufficient. Length is a poor proxy for quality — a handbook that answers the twenty most common questions in the first three pages is more useful than one that covers eighty scenarios in a hundred pages.

Do we need separate handbooks for different states or locations? Usually one core handbook plus location annexures works best. The core covers company-wide policies; the annexure covers holiday lists, state-specific leave entitlements, professional tax, working hours and any local statutory variation. This avoids maintaining several near-identical documents.

How do we handle handbook acknowledgement for a distributed workforce? Digital acknowledgement in your HR system is the cleanest route: the employee opens the document, confirms receipt, and the confirmation is timestamped against their record. This is far more reliable than a signed page that has to be scanned, filed and located again years later.

How often should the handbook be reviewed? At least annually, plus whenever a triggering event occurs — a statutory change, entry into a new state, a headcount threshold that brings new obligations, or a significant change to benefits or working arrangements.

Should the handbook be available in local languages? Where a significant part of your workforce is more comfortable in a language other than English — common for shop-floor, retail and field teams — a translated version materially improves comprehension. If you translate, keep one version as the authoritative text and say which one it is.

What is the difference between the handbook and the appointment letter? The appointment letter is the individual, binding employment contract: role, compensation, notice period, confidentiality and any restrictive covenants. The handbook describes company-wide policies and how things work. The letter is specific and contractual; the handbook is general and typically amendable.

Can we change a policy in the handbook unilaterally? Company policies can generally be amended, provided the handbook says so, the change is communicated with reasonable notice, and the change does not conflict with the individual employment contract or reduce a statutory entitlement. Changes affecting compensation or contractual terms require a different approach and legal input. Never change a policy retrospectively.

Conclusion: write it for the person with a question

The test of a handbook is not whether it is thorough. It is whether an employee at 9 pm, wondering whether they can take leave next Thursday, finds the answer in under a minute and trusts it.

That standard shapes everything: the index page at the front, the plain second-person language, the numbers instead of adjectives, the worked examples, the consistent structure, and the fact that it lives somewhere searchable rather than in an email attachment from onboarding day. It also shapes what you leave out — every paragraph that exists to cover a scenario that has never occurred is a paragraph between your employee and their answer.

Build the first version in six weeks, get it reviewed by a lawyer and by actual employees, publish it where people can find it, and put the review date in someone's calendar. That is a better handbook than most organisations several times your size have.

CozyHR keeps policies, acknowledgements and employee records in one place, so your handbook is searchable, versioned, and acknowledged with a timestamp against each employee — and new joiners get the current version automatically, not last year's PDF. If your policies are scattered across drives and inboxes, take CozyHR for a spin.