A Complete Guide to HR Policies

Every organisation runs on rules, whether they are written down or not. In a five-person startup, the rules live in the founder's head. By the time you reach twenty or thirty people, that stops working: two managers approve leave differently, a new joiner asks whether Saturdays are working days, and nobody is sure what happens to unused leave in March.

HR policies fix this. A good policy tells employees what to expect, tells managers how to decide, and gives you a fair, consistent answer when a hard situation comes up. This guide walks through what to cover, how to write policies people will actually read, how to roll them out, and how to keep them current.

What an HR policy is (and what it is not)

An HR policy is a written statement of how your organisation handles a specific area of employment: leave, attendance, pay, conduct, separation, and so on. It sets the rule and the reason for it.

It helps to separate three related documents:

• Policy: the rule. "Employees get 18 days of earned leave per calendar year."
• Procedure: the steps. "Apply for leave in the HR system at least five working days in advance; your manager approves or rejects within two working days."
• Employee handbook: the collection. A single, readable document that brings your policies together for employees.

Keeping these separate makes updates easier. You can change the approval steps without rewriting the rule, and you can update one policy without reissuing the whole handbook.

Why written policies matter

• Consistency: employees in different teams get the same answer to the same question.
• Fairness and trust: people accept decisions more easily when the rule was known in advance.
• Legal protection: Indian labour law requires certain things to be documented, and a clear policy is your first line of evidence if a decision is challenged.
• Less manager guesswork: managers spend less time escalating routine questions to HR.
• Faster onboarding: new joiners learn how things work in one sitting, not over six months.

Legal context for Indian employers

Your policies sit on top of the law, never below it. A policy can be more generous than the statutory minimum, but it cannot take away a statutory right. A few areas to keep in mind:

• Standing orders: establishments above the applicable worker threshold must have certified standing orders covering classification of workers, working hours, leave, and misconduct. The Industrial Relations Code updates these thresholds and rules, so check what currently applies to you.
• Shops and Establishments Acts: each state sets its own rules on working hours, weekly offs, leave, and registers. Your leave and attendance policies should match the state where each employee works.
• Labour Codes: the four Labour Codes (Wages, Social Security, Industrial Relations, and Occupational Safety, Health and Working Conditions) consolidate many older laws. Central and state rules continue to be notified, so review wage definitions, leave, and working-hour provisions against current notifications.
• POSH: organisations with ten or more employees must have an Internal Committee and a written policy on preventing sexual harassment at the workplace.
• Maternity benefit: statutory maternity leave and related benefits must be reflected in your leave policy.

The core policies every organisation needs

You do not need forty policies on day one. Start with the ones that answer the questions employees ask most often, then add others as you grow.

How to write an HR policy: step by step

1. Start with the problem

Write down the questions or disputes that prompted the policy. If managers keep asking whether half-day leave is allowed, your leave policy must answer that clearly. Policies written to solve real questions are shorter and more useful than ones copied from a template.

2. Gather inputs

Talk to a few managers and employees. Ask what is confusing today and what feels unfair. Check what the law requires for your state and headcount. Look at how you handle the issue in practice now, because a policy that contradicts current practice will either be ignored or cause friction.

3. Use a consistent structure

Every policy should follow the same layout so people know where to look:

1. Purpose: one or two sentences on why the policy exists.
2. Scope: who it applies to (all employees, full-time only, a specific location).
3. Definitions: any terms that could be read two ways.
4. Policy statement: the actual rules.
5. Procedure: how to apply, who approves, timelines.
6. Exceptions: who can approve exceptions and how they are recorded.
7. Owner and review date: who maintains it and when it will next be reviewed.

4. Write in plain language

Write the way you would explain the rule to a new joiner over coffee. Short sentences. Active voice. Concrete numbers instead of vague words.

5. Include worked examples

Examples remove ambiguity. For a leave encashment rule, show the calculation: "If your basic salary is ₹30,000 a month and you encash 5 days, you receive ₹30,000 ÷ 30 × 5 = ₹5,000, subject to tax." For a late-mark rule, show what happens on the third late mark in a month.

6. Decide who can grant exceptions

No policy covers every case. Name the person or role who can approve an exception, and require that exceptions be recorded. Otherwise exceptions quietly become the new rule.

7. Review and approve

Share the draft with a few managers and, ideally, a legal reviewer. Get sign-off from leadership. Record the version number and effective date.

Example: a simple leave policy outline

Here is how the structure above looks for a leave policy at a 40-person company:

• Purpose: to give employees time to rest and handle personal needs while keeping work running smoothly.
• Scope: all full-time employees, including those on probation.
• Leave types: earned leave (18 days a year, accrued monthly), casual leave (6 days), sick leave (6 days), plus statutory maternity and other leave as per law.
• Carry-forward: up to 15 days of earned leave carry forward; casual and sick leave lapse on 31 December.
• Applying: planned leave 5 working days in advance; sick leave on the day, with a medical certificate for more than 2 consecutive days.
• Approval: reporting manager within 2 working days.
• Holidays: published list of national and festival holidays each December for the next year.
• Owner: HR; reviewed every January.

Rolling out a new policy

A policy that sits in a shared folder nobody opens is not a policy. Plan the rollout:

1. Announce it: send a short note explaining what is changing, why, and from when.
2. Brief managers first: they will get the questions, so make sure they understand the rules and the reasons.
3. Publish it in one place: a single, searchable location that every employee can access, including on mobile.
4. Collect acknowledgements: ask employees to confirm they have read core policies such as the code of conduct and POSH policy. Keep the record.
5. Configure your systems: if the policy changes leave accrual or attendance rules, update your HR system on the same effective date so the software and the document agree.
6. Hold a short Q&A: fifteen minutes in a team meeting clears up most confusion.

If you use Qrew HR's employee records and document management, you can store policies centrally and track acknowledgements alongside each employee's profile. Leave and attendance rules can be configured in Leave Management so the system applies the policy automatically.

Enforcing policies fairly

• Apply rules consistently. Treating a senior employee differently from a junior one for the same issue erodes trust quickly.
• Document decisions. When you take action under a policy, record what happened, which clause applied, and what was decided.
• Follow due process for misconduct. Give the employee a chance to explain before any disciplinary action, as your standing orders or conduct policy require.
• Give managers a simple escalation path. When a case does not fit the policy, they should know exactly whom to ask.

Reviewing and updating policies

Policies go stale. Laws change, the company grows, and new ways of working appear. Build a review rhythm:

• Annual review: check every policy once a year against current law and practice.
• Trigger-based review: review immediately when a law changes, when you open in a new state, or when the same question keeps reaching HR.
• Version control: keep previous versions with their effective dates. If a dispute arises about an event last year, you need to know which version applied.
• Communicate changes: summarise what changed rather than asking people to reread the whole document.

Common mistakes to avoid

• Copying a large company's handbook word for word. It will not fit your size, your state, or your culture.
• Writing rules you do not intend to enforce. Unenforced rules teach people that policies are optional.
• Leaving out the "how". A rule without a procedure creates as many questions as it answers.
• Ignoring state differences when you have employees in more than one state.
• Forgetting contractors and interns. Say clearly whether each policy applies to them.
• Letting policies and system settings drift apart, so the handbook says one thing and the leave balance says another.

HR policy checklist

• Core policies drafted: conduct, leave, attendance, pay, POSH, separation
• Each policy has purpose, scope, rules, procedure, exceptions, owner, review date
• Reviewed against central and state law for every location
• Approved by leadership with version number and effective date
• Managers briefed before employees
• Published in one accessible place
• Acknowledgements collected for core policies
• HR system configured to match
• Annual review date set