Many founders treat HR policies as something to write once the team reaches a certain size. In practice, the absence of clear policies causes more friction on the way there. A basic leave policy, a code of conduct, and a few compliance-relevant documents do not take long to put together. Having them in place avoids the ambiguity that tends to surface at the worst possible moments.
Trusted by 4,000+ companies across India · 50 free credits on signup
Indian labour law imposes specific policy requirements on employers, some from the first hire and others once the company crosses headcount thresholds. The most immediate obligation is the POSH Act, which requires a written sexual harassment policy for all employers regardless of size.
State Shops and Establishments Acts require that working hours, weekly off, and leave entitlements be documented and communicated to employees. The exact requirements vary by state, but most require an employer to maintain records of leave taken and ensure employees are aware of their entitlements. A written leave policy satisfies both requirements.
Once a startup crosses 20 employees, PF registration becomes mandatory and the PF policy, which explains how contributions are calculated and when they are deposited, should be part of the offer letter and onboarding documentation. ESI at 10 employees in most states triggers similar documentation obligations.
The Prevention of Sexual Harassment at Workplace Act, 2013 requires all employers to have a written policy against sexual harassment and to display it prominently. For establishments with 10 or more employees, an Internal Complaints Committee is also mandatory. Smaller employers must report complaints to a district-level Local Complaints Committee.
State Shops and Establishments Acts specify minimum leave entitlements: earned leave, casual leave, and sick leave. The number of days varies by state. A written leave policy should state the entitlements, the process for applying, carry-forward rules, and encashment terms on exit. An absent policy means leave is managed ad hoc, which creates inconsistency and disputes.
Most state Shops and Establishments Acts set maximum daily and weekly working hours and specify overtime rates. A written policy documenting the company's working hours, break entitlements, and overtime approach puts the employer on solid ground if a dispute arises about unpaid hours.
Once the applicable thresholds are crossed, the company's obligations under PF and ESI should be documented clearly for employees. This includes the contribution rates, how take-home is affected, and the process for transfers or withdrawals on exit. Many salary disputes stem from employees who did not understand these deductions before their first payslip.
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.
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.
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.
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 before the person joined. A short policy covering salary structure, variable pay timelines, and statutory deductions prevents most of it.
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 the expectations clearly.
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 informal conversations that produce different answers.
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, crucially, what carries over after the person leaves. That last part is what matters when an employee takes client relationships to a competitor.
The Prevention of Sexual Harassment at Workplace Act, 2013 is one of the most frequently misunderstood compliance obligations for Indian startups. The written policy requirement applies to all employers regardless of the number of employees. There is no headcount threshold for the policy itself.
The Internal Complaints Committee, which is the body responsible for receiving and investigating complaints, is mandatory for establishments with 10 or more employees. A startup with fewer than 10 employees is not required to form an ICC but is still required to have a written policy. Complaints in that situation are handled by a Local Complaints Committee set up at the district level by the government.
The policy must be displayed prominently at the workplace and communicated to all employees at the time of joining. Employers are also required to organise awareness sessions at regular intervals. Failure to constitute an ICC when required, or failure to handle a complaint in accordance with the Act, attracts penalties including fines and cancellation of licences.
The argument is not that early-stage startups need complex policy documents. It is that the cost of writing them early is low and the cost of not having them grows with headcount.
When 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.
A 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.
A 5-person team can operate on shared understanding. A 30-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.
During due diligence, the absence of HR documentation is a flag. A startup that cannot produce a POSH policy, leave records, or documented employment terms for its employees creates uncertainty about liability that acquirers and investors price into their assessment. Companies with clean HR documentation close faster and with fewer conditions.
Offrd's policy generator produces HR policies configured to the company's details. Combined with offer letters, payslips, and onboarding documents, every HR document the employee receives comes from the same source, built on the same record.
Offrd generates policies based on the company's state, employee count, and industry. Leave, code of conduct, POSH, and related documents come out formatted and ready to issue. The output accounts for state-specific rules rather than a single national template that may not apply to how the company actually operates.
Offer letters from Offrd reference the company's leave structure, notice period, and probation terms as configured. The employee's first document reflects the policies rather than sitting separately in a folder nobody looks at.
The onboarding flow collects the employee's acknowledgment of company policies alongside their KYC documents. If a dispute arises later about whether an employee knew the rules, there is a timestamped record from day one.
Payslips are generated from the salary structure already configured in Offrd. Components and deductions appear exactly as the offer letter described them. The gap between what an employee expected and what they received is where most early salary disputes start. Consistency between the two closes that gap.
Policies, offer letters, payslips, and onboarding from the same employee record. No minimum headcount.