Why Startups Should Write HR Policies Early Even if Nobody Reads Them

An Indian employer needs a written POSH policy from the first employee, a leave policy under most state Shops and Establishments Acts, and documented working hours from day one. Putting these in place once is faster than the disputes, terminations, and POSH penalties they prevent. The smaller the team, the smaller the job.

A POSH policy is required from your first employee. A leave policy is required in most states under the Shops and Establishments Act. Working hours have to be documented too. Most founders learn this after the first dispute, not before. The work to put these in place is small at five employees and grows the longer it is delayed. New hires calibrate to whatever is around them. Once a handful of them have negotiated their own version of leave or working hours, undoing that takes more than a memo. Writing the starter set early is cheaper than rewriting later, and it leaves a paper trail that holds up in front of a conciliation officer.

Trusted by 4,000+ companies across India. 50 free credits on signup.

Policies That Are Not Required, But Prevent Most Common Disputes

These are not statutory mandates for early stage startups. They are the policies that, in their absence, generate the most friction as the team grows.

Code of conduct

Most founders assume their team shares the same baseline on what is acceptable behaviour. That assumption holds for five people who know each other. It does not hold at twenty. A code of conduct is what you point to when that assumption turns out to be wrong. It also makes disciplinary action defensible, because the standard was written down before the incident, not after.

Disciplinary procedure

Indian labour courts and conciliation officers want to see that you followed a process: warning, show cause notice, inquiry, decision. If none of that is documented, the termination becomes much harder to defend regardless of the underlying reason. A one page procedure written before any dispute arises is worth considerably more than a detailed explanation after.

Compensation and benefits policy

The offer letter states the CTC. The payslip shows something different. The employee assumed the difference was an error. This is a predictable sequence and it happens because nobody explained how CTC translates to take home pay before the person joined. A short policy covering salary structure, variable pay timelines, and statutory deductions prevents most of it.

Remote and hybrid work policy

When it is unwritten, remote work is governed by whatever each manager decides in the moment. That produces inconsistency across teams, resentment from employees who feel they were treated differently, and leave or attendance disputes with no clear basis for resolution. The policy does not need to be long. It needs to state expectations clearly.

Expense reimbursement policy

Field sales teams and client facing roles accumulate expenses quickly. Without a written policy, approval becomes a negotiation each time. What gets reimbursed, how long it takes, and who needs to approve it should be decided once in writing, not repeatedly in conversations that produce different answers.

Confidentiality and data handling

Employees in fintech, healthtech, and SaaS handle sensitive data as a matter of course. Most of them have no clear idea what their obligations are unless someone has written it down. The policy should cover what counts as confidential, how to handle it, and, importantly, what carries over after the person leaves. That last part is what matters when an employee takes client relationships to a competitor.

Why Writing Policies Early Is Easier Than Writing Them Later

The argument is not that early stage startups need long policy documents. It is that the cost of writing them early is low, and the cost of not having them grows with headcount.

• Informal norms calcifyWhen leave, working hours, and conduct are managed informally, employees develop their own understanding of the rules based on what they observe around them. By the time a startup tries to formalise these, some employees have leave balances calculated informally, others have been allowed to work hours that differ from what a policy would state, and introducing written rules feels like a change rather than a clarification.
• Disputes are harder to resolve without documentationA leave dispute, a termination, or a harassment complaint is significantly harder to handle when there is no written policy to refer to. Indian labour courts and conciliation officers expect documented processes to have been followed. The employer who cannot produce a written disciplinary procedure, a leave record, or a complaint handling process is at a structural disadvantage.
• New hires calibrate to what is writtenA five person team can operate on shared understanding. A thirty person team cannot. Each new hire who joins without a written policy framework forms their own expectations from what colleagues tell them. Those expectations diverge and the gap between what employees believe they are entitled to and what the company intended grows over time. Policies from the outset mean every new hire gets the same starting point.
• Investors and acquirers look for thisDuring due diligence, the absence of HR documentation is a flag. A startup that cannot produce a POSH policy, leave records, or documented employment terms creates uncertainty about liability that acquirers and investors price into their assessment. Companies with clean HR documentation close faster and with fewer conditions.

Frequently Asked Questions

When should an Indian startup write its first HR policies?

As soon as there are employees beyond the founding team. A basic leave policy, code of conduct, and POSH policy can be written in a day and prevent a disproportionate amount of ambiguity. Waiting until the team reaches 20 or 50 people means correcting inconsistencies that have already formed.

What HR policies are legally required for Indian startups?

The POSH Act requires a written sexual harassment policy for all employers. For establishments with 10 or more employees, an Internal Complaints Committee is also mandatory. Most state Shops and Establishments Acts require a leave policy and working hours documentation. EPF and ESI documentation becomes mandatory once those headcount thresholds are crossed.

Does the POSH Act apply to startups with fewer than 10 employees?

The written sexual harassment policy requirement applies to all employers regardless of headcount. The Internal Complaints Committee is mandatory only at 10 or more employees. Startups with fewer than 10 employees refer complaints to a district level Local Complaints Committee, but the written policy remains a requirement for all.

What happens if a startup has no HR policies and a dispute arises?

Without written policies, disputes are resolved by reference to verbal understandings, which are difficult to establish and often contradicted by both parties. A leave dispute without a written policy, or a termination without a documented disciplinary process, places the employer in a weak position before a labour court or conciliation officer.

Can HR policy templates be used by Indian startups?

Templates are a reasonable starting point. They should be reviewed for alignment with the applicable state's Shops and Establishments rules, the company's actual practices, and any sector specific requirements. A template not adapted to the company's context creates its own problems when tested against a real situation.

How does Offrd help with HR policy generation?

Offrd's HR policy generator produces policies configured to the company's state, headcount, and industry. Policies are generated as formatted documents ready to issue. The platform also handles offer letters, payslips, and probation letters from the same employee record, so every document the employee receives comes from the same source of truth.