Which HR policies you actually need, and in what order

A founder of a sixty-person business asked for an employee handbook. What arrived from a template was forty-one policies covering everything from social media conduct to a sabbatical scheme the business had never offered. It was circulated, acknowledged by nobody in particular, and produced exactly one visible effect: when a genuine dispute arose about notice during probation four months later, the handbook was consulted and did not answer the question.

This is the normal outcome of policy-by-template. Length is mistaken for coverage, and the questions that actually arise are the ones nobody wrote down because they seemed obvious at the time.

What a policy is for

A policy exists to settle a recurring question in advance, so that it is not decided differently each time by whoever happens to be asked. That is the entire purpose, and it gives a usable test: if you cannot name the question it answers, and the last two times that question came up, you do not need the policy yet.

The corollary is that policies written ahead of any experience are usually wrong in the specifics, because they are written from a template's assumptions rather than from how the business actually operates. It is better to have eight policies that reflect real decisions than forty that describe an imaginary organisation.

The eight that carry most of the weight

1  LEAVE
     Types, entitlement, how to apply, notice expected,
     what happens to unused balance, who approves.

2  ATTENDANCE AND WORKING HOURS
     Hours, late arrival, remote or hybrid rules,
     shift change process, who decides exceptions.

3  PROBATION AND CONFIRMATION
     Length, what is assessed, who decides, what
     happens if it is extended, notice during it.

4  EXIT AND NOTICE
     Notice both ways, handover expectation, final
     settlement timing, what is returned.

5  CODE OF CONDUCT
     Expected behaviour, conflict of interest, gifts,
     confidentiality, consequences.

6  GRIEVANCE
     How a concern is raised, to whom, what happens
     next, and the alternative if it concerns your
     own manager.

7  DISCIPLINARY
     Stages, who decides, right to be heard,
     what is recorded.

8  POSH / ANTI-HARASSMENT
     Statutory in India for most employers. Treat
     separately and take proper advice on it.

   EVERYTHING ELSE CAN WAIT UNTIL SOMEBODY ASKS.

The first four are where nearly all day-to-day friction lives. The next three are where the expensive disputes live, and they are usually written after the first expensive dispute rather than before it. The eighth sits apart and is addressed below.

The questions a policy must answer

Most policies fail not because the position is wrong but because the document describes a principle without specifying the mechanics. Four things turn a statement into something usable.

1. 1

   Who decides

   By role, not by name. A policy that says "approval from management" will be interpreted differently by each person who reads it, and the resulting inconsistency is what produces the grievance.

2. 2

   By when

   Every step that involves waiting needs a stated timeframe. "Leave requests should be submitted in advance" is not operable; a specific notice period is.

3. 3

   What happens in the exception

   The exception is why people read the policy. A leave policy that covers planned leave and says nothing about emergencies has skipped the case that generates the query.

4. 4

   What happens if it is not followed

   Not necessarily a punishment - often just the practical consequence. A policy with no stated consequence is a preference, and it will be treated as one.

Applied to the eight above, this is perhaps twenty pages in total. Considerably shorter than the template handbook and far more likely to resolve something.

POSH and anything statutory

The anti-harassment policy is in a different category from the other seven and should be treated that way. In India it carries statutory requirements for most employers, including obligations around committee constitution, process and reporting, and getting the detail wrong carries real consequences.

This guide deliberately states no legal position on it, gives no thresholds and no figures. What a business can usefully do internally is establish readiness: whether a policy exists and has been communicated, whether the committee is constituted and its members are known to employees, whether anyone has been trained, whether a route to raise a complaint is published, and whether anyone owns the annual obligations.

Those five questions are answerable in an afternoon and will tell you whether you have a gap. What specifically applies to your organisation, and how each requirement must be met, should be confirmed with a qualified professional familiar with your sector and state rather than inferred from any general article, including this one. The same caution applies to anything touching statutory leave, working hours, notice and final settlement, which vary and change.

Writing them so people read them

• One page each where possible. A policy nobody finishes reading has not been communicated, whatever the acknowledgement record says.
• Write in the second person. "You must give two weeks' notice" is clearer than "employees are required to provide notice of not less than two weeks", and it is read as addressed to the reader.
• Lead with the common case. Most people consulting the leave policy want to know how much they have and how to apply. Put that first and the edge cases after.
• Say what it does not cover. A line pointing to the relevant policy or person for adjacent questions prevents the document being stretched to answer things it was never written for.

The part everyone skips: keeping them alive

Policies do not fail on the day they are written. They fail eighteen months later, when the business has changed, three of them contradict each other, and nobody can say which version is current because two exist on different drives.

Two fields on every policy prevent most of this: a named owner by role, and a review date. The owner is whoever would have to answer a question about it anyway; the review date creates a forcing function that otherwise does not exist. A policy without both quietly expires while remaining formally in effect, which is the worst of both arrangements.

Version control matters more than it sounds. When a dispute arises the question is what the policy said at the time, and a business that cannot answer that is in a weak position regardless of the merits. Keeping a single current version in one place, with the date of the last change, is most of what a policy and document centre provides and is achievable without one if somebody owns it.

A sensible starting sequence

For a business with nothing written down, the order is not the list above but something more pragmatic: write the two that generate the most queries this month, usually leave and attendance. Circulate them, see what questions they fail to answer in the first six weeks, and amend. Then write the next two.

This produces documents that match the business rather than a template, and it produces them at a rate the organisation can absorb. Policies issued in a batch of forty are read by nobody; two at a time, each solving a visible irritation, get read because they are relevant.

The exception is anything statutory, which cannot wait for the query to arise. That should be addressed early and with proper advice, and it is the one part of HR policies and governance work where the cost of being late is not simply inconvenience. Where the underlying issue turns out to be that nobody knows what the current process actually is — as opposed to what the document says — an HR process audit is the faster route, because writing a policy to describe a process that does not work simply documents the problem. For everything else, the eight above, written properly and reviewed annually, are what a well-run HR policies and governance framework consists of at this size.