The HR Generalist Guide to Policy & Handbook Design: The Rules of the Game

Chapter 13 of The HR Generalist's Blueprint

The Employee Handbook is, without much competition, the most boring document in the company. It's also one of the most important. It's your first real line of defense in a labour dispute, and if you fire someone for misconduct without a clear, signed policy defining exactly what that misconduct was, you'll likely lose that case.

Policies in India tend to suffer from a specific problem: they're often lifted from old US templates or written in a legalese nobody actually reads for pleasure or comprehension. If your employees can't understand the leave policy, they can't follow it, and that's not really their failure, it's yours.

Legalese Versus Plain English

A policy exists to change behavior, not to demonstrate how formal your legal department can sound.

The first fix is killing the jargon outright. Words like "aforesaid," "notwithstanding," and "hereinafter" are administrative ego dressed up as precision, and they translate easily into plain alternatives, "as mentioned before," "even though," "from now on," without losing a shred of legal meaning.

The second fix is training your HR team to write actively rather than passively. Compare "deduction of salary shall be effected for any unapproved absence from duty," which reads as threatening and vague, against "if you take an unapproved leave, it will be marked as Loss of Pay (LOP) and deducted from your monthly salary," which is direct, unambiguous, and genuinely easier to actually follow.

The third fix is the "what-if" test. A good policy answers the employee's real questions before they have to ask them out loud. "Employees are entitled to 15 days of Sick Leave" leaves too much open, what if I'm sick for 16 days, what if I'm still on probation. A stronger version closes those gaps directly: "Probationary employees are not entitled to paid Sick Leave. A doctor's certificate is mandatory for Sick Leave exceeding three consecutive days. Any leave beyond 15 days requires pre-approval from HR."

The Handbook Audit Nobody Runs Often Enough

If your handbook hasn't been touched in the last 18 months, you're probably legally exposed without realizing it. The Indian work landscape has shifted meaningfully, and most handbooks haven't caught up.

Remote and hybrid work is usually the biggest gap. A handbook written in 2019 quietly assumes everyone's in the office from 10 to 7, which simply isn't true anymore for most organizations. A real remote-work section needs to define eligibility clearly, who actually can work from home (manufacturing plant workers generally can't, for instance), equipment ownership, who pays for broadband and power, and what happens to company assets when someone resigns, and how productivity actually gets measured, particularly whether activity trackers are in use, which needs to be disclosed clearly to avoid a privacy dispute later.

Digital conduct is the second gap. An employee's personal LinkedIn or Instagram post can genuinely damage your brand now in a way that simply wasn't true a decade ago. A firm but simple clause covers most of it: employees may not post company information, client names, or anything that could be read as harassment on their personal social media if their profile identifies them as working here.

Leave carry-forward rules round out the audit. These vary meaningfully by state under India's Shops & Establishments Act, so the policy needs to clearly state the expiry date (December 31st or March 31st, whichever applies), the maximum carry-forward cap, and the encashment process at Full & Final settlement. Leave this vague and you'll find yourself disputing the final settlement amount with a departing employee, which is a worse conversation to have than simply writing the clause clearly the first time.

Enforcement Is Where HR Trips Itself Up

A top-performing Sales Manager gets caught faking an expense claim for a client meal. The manager's instinct is often, "let it go, John's our best biller, just give him a warning." That instinct, however understandable, is a genuine trap. If a junior analyst gets punished for the exact same thing next month, you've just opened the door to a real discrimination claim, because the only defense you had was consistency, and you just gave it up.

Consistency really is the only shield available in an environment where favoritism is already a common complaint. The policy has to apply to the CEO and the security guard with equal weight. If an exception is genuinely warranted for some rare, valid reason, document that reason in writing in the employee file; the documentation is the proof it was a reasoned decision rather than simple favoritism.

POSH complaints deserve zero discretion whatsoever. Any formal complaint has to go straight to the Internal Committee immediately. If HR tries to informally mediate a POSH complaint to protect a senior leader, that's not a judgment call, it's a decision that can expose HR personally to criminal liability under Indian law.

Before moving into the final operational chapters, a quick honest check: did you run a random policy past a non-HR manager recently, and did they understand it without needing you to explain it? Has a detailed Remote Work annexure been added, including asset return at FnF? Read your FnF settlement clause again, is the formula for notice buy-out and leave encashment actually airtight? And look back at your last three disciplinary actions, were the consequences genuinely consistent across departments, or did some people get treated more gently than others?

By Mit – AN HR Professional