Paternity & Adoption Leave Policy: India Guide 2026

Paternity and Adoption Leave Policy: A 2026 Guide for Indian Employers

Maternity leave in India has a well-known statutory backbone. Paternity leave and adoption leave do not — and that gap is exactly why a well-designed paternity leave policy for India and a thoughtful adoption leave policy have become two of the sharpest talent-differentiation tools available to HR teams and founders in 2026. Most private-sector employers in India are free to design these benefits however they choose, which means two companies in the same city, same industry, and same size can offer wildly different experiences to a new parent. For HR managers and founders building a parental leave HR guide for their own organisation, that freedom is both an opportunity and a source of real risk if the policy is vague, inconsistently applied, or bolted on as an afterthought.

This guide walks through how to design, document, roll out, and administer paternity and adoption leave policies for an Indian SMB or startup in 2026 — including how surrogacy leave typically fits in, how payroll and HRMS systems should treat these leave types, and the pitfalls that trip up even well-intentioned employers.

A note before we start: this article deliberately avoids citing specific statutes, sections, or court rulings, because paternity and adoption leave for most private-sector employees in India are governed by company policy, not a single central law that applies uniformly to every employer. Government (public sector) employees are covered by separate central and state service rules that are periodically revised. If you need to confirm current entitlements for government staff, or if your organisation falls under a specific state or sector-specific rule, always verify with your legal/HR compliance advisor and the latest official notifications rather than relying on any blog post — including this one.

---

Why Paternity and Adoption Leave Are Still "Company Policy" in India

The current landscape

Unlike maternity benefits, which have a long-standing central law that sets a floor for most establishments, paternity leave for private-sector employees in India is not backed by an equivalent nationwide statute. What exists instead is a patchwork:

• Central government employees (and many state government employees) are entitled to paternity leave under their respective service rules, with specific durations and conditions defined by the government from time to time.
• Private-sector employees generally have no default statutory entitlement to paternity leave. Whatever they receive comes entirely from their employer's HR policy, employment contract, or (occasionally) an industry-specific settlement or award.
• Adoption leave follows a similar pattern: some government service rules extend defined adoption-related leave to government employees (often linked to the adopting parent's gender and the age of the child at adoption), while private employers again set their own rules — and many private companies still have no adoption leave policy at all.
• Surrogacy leave is the least standardised of all. A small but growing number of companies extend maternity-equivalent or adoption-equivalent leave to intended parents (commissioning parents) who have a child via surrogacy, but this is almost entirely voluntary in the private sector.

This is genuinely different from maternity leave, where most HR teams are simply implementing a known statutory minimum. With paternity and adoption leave, HR is often designing the policy from a blank page — which is precisely why so many companies end up with inconsistent, informal, or manager-discretion-driven practices that create fairness problems later.

Why more companies are going beyond the bare minimum anyway

Even in the absence of a strong nationwide statutory mandate for private employers, a growing number of Indian startups, mid-sized companies, and even some large enterprises have voluntarily introduced generous, formalised paternity and adoption leave policies. The reasons HR leaders commonly cite include:

• Talent attraction and retention. In competitive hiring markets — tech, fintech, professional services, D2C — a strong parental leave policy (for all parents, not just birthing mothers) is a visible, easy-to-compare benefit that candidates weigh alongside compensation.
• Gender-equity signalling. Employers increasingly recognise that if only mothers get meaningful leave, the implicit message is that childcare is "her job" — which can quietly reinforce bias in hiring, promotion, and return-to-work decisions for women. Generous paternity leave is one lever to rebalance that.
• Employer branding and DEI commitments. Many companies now publish parental leave benefits publicly (careers pages, ESG/DEI reports, employer review sites) as proof points of inclusive culture.
• Reducing attrition after a life event. New parents — of any gender, and whether the child arrived by birth, adoption, or surrogacy — are a flight risk if they feel unsupported. A clear, generous policy reduces the odds of losing someone shortly after they return from leave.
• Levelling the field for adoptive and LGBTQ+ parents. Policies that treat adoption leave and surrogacy leave with the same seriousness as biological parenthood send a strong signal of inclusion, particularly important for single parents and same-sex couples building families.

The practical upshot for HR managers and founders: you are not filling in a statutory form. You are building a genuine people-strategy document. Treat it that way.

---

Designing a Paternity Leave Policy

A good paternity leave policy India employers can defend, administer consistently, and be proud of needs to answer five core questions clearly: how long, who qualifies, when it can be taken, what proof is needed, and how it interacts with pay and other leave types.

1. Duration options

There is no single "correct" number of days. In practice, Indian private employers cluster around a few common bands:

• Statutory-minimum-style / conservative: 3–5 working days, often unpaid or paid at the employer's discretion. Common among smaller, cost-conscious businesses or those just starting to formalise the benefit.
• Mid-market standard: 7–15 calendar or working days, fully paid. This is a common "we take this seriously but haven't gone all-in" band for growth-stage startups and mid-sized companies.
• Progressive / talent-differentiator: 15–30 days, sometimes extending to 4–6 weeks, fully paid, occasionally with an option to extend using unpaid leave or accrued PTO.
• Flagship / marquee benefit: Some companies (often larger tech firms or those explicitly competing on benefits) offer durations approaching or matching a chunk of maternity leave, positioned as full parity between parents.

There's no universally "correct" number — pick a duration that fits your company's stage, budget, and the message you want to send, and be honest with yourself about whether you can sustain it as headcount grows.

2. Eligibility criteria

Define eligibility explicitly rather than leaving it to interpretation. Common eligibility variables include:

• Employment type: Full-time employees only, or also fixed-term/contract employees? Many policies exclude interns, consultants, and gig workers, which should be stated explicitly (and ideally revisited as your workforce mix evolves).
• Minimum tenure: Some companies require a minimum period of continuous service (e.g., completion of probation, or 3–6 months of employment) before paternity leave becomes available. Others offer it from day one as a hiring differentiator.
• Number of children: Decide whether the benefit applies for every child or is capped after a certain number (e.g., first two children only) — a common practice mirrored from maternity policy design.
• Definition of "father"/"second parent": Modern policies increasingly use gender-neutral or inclusive language — "co-parent," "second parent," or "non-birthing parent" — so the policy naturally extends to same-sex couples, adoptive fathers, and partners in different family structures, rather than assuming a biological, heterosexual pairing.
• Marital status: Decide explicitly whether the policy requires the employee to be legally married to the child's other parent, or whether it also covers unmarried parents, live-in partners, or single fathers via other legal means. This should be a conscious, documented decision, not a silent assumption.

3. Timing and flexibility

Rigid "take it all in one block, starting the day of birth" policies often don't reflect real family needs. Consider building in flexibility:

• Window to avail the leave: Many companies allow paternity leave to be taken any time within a defined window — commonly somewhere between 1–6 months around the expected/actual date of birth — rather than forcing it to start on day one.
• Splitting the leave: Progressive policies allow the leave to be split into two or more blocks (e.g., a short block right after birth, and a second block a few weeks later when the birthing partner returns to more independent recovery, or when childcare arrangements change).
• Advance notice requirements: For planned events (adoption placement dates, expected delivery dates), ask employees to give reasonable advance notice — while acknowledging that births don't always follow a due date, so the policy should allow for short-notice activation.
• Interaction with weekends and holidays: Clarify whether paternity leave is counted in calendar days or working days, and whether weekly offs/public holidays falling within the leave period are absorbed into the leave count or extend it. Most fair-to-employee policies count only working days, so a weekend in the middle doesn't "use up" leave — but you must decide and document this, because it directly affects perceived generosity and payroll leave-balance calculations.
• Interaction with other leave types: State clearly whether paternity leave can be combined with annual/earned leave, comp-offs, or sick leave to extend the total time off, and whether any unused paternity leave lapses if not used within the eligible window (most companies do not allow carry-forward of paternity leave, similar to how maternity leave typically isn't carried forward).

4. Documentation requirements

Keep this proportionate — you're verifying a real, joyous life event, not conducting an audit. Typical documentation includes:

• Birth certificate (can usually be submitted after leave, since it's often not available immediately at birth) or a hospital discharge summary/birth intimation as interim proof.
• A simple internal leave application/notification form, ideally submitted through your HRMS, specifying expected or actual date of the event.
• For adoption-linked paternity/co-parent leave, the relevant adoption order or agency confirmation (see adoption leave section below).

Avoid demanding documentation that is invasive or hard to obtain quickly — a short grace period to submit final paperwork after the leave starts is good practice.

---

Designing an Adoption Leave Policy

Adoption leave policy design in India is less mature than maternity/paternity leave in many companies, largely because adoptive parents are a smaller (though not negligible) population, and it's easy for the topic to simply get skipped when building leave policies. That's a missed opportunity — a clear adoption leave policy is one of the most meaningful, low-cost signals of inclusivity a company can offer.

1. Eligibility

Key questions to resolve explicitly in policy language:

• Age of the adopted child: Most company adoption leave policies set an age threshold for the adopted child — commonly somewhere in the range of "below 3 years" or "below school-going age" — beyond which the leave duration may be shorter or the benefit may not apply at all, mirroring the reasoning that a very young child requires more intensive early bonding and caregiving time. Some companies choose not to cap this at all; others tie it to guidance in relevant service rules for government employees as an informal benchmark. Whatever threshold you choose, state it clearly.
• Legal adoption requirement: Leave should typically be contingent on a legally recognised adoption process (formal adoption order/registration), not an informal or in-process arrangement, to keep the policy administrable and consistent.
• Single parents: Explicitly confirm that single adoptive parents (regardless of gender) are eligible for the same leave a two-parent household would receive, since a single parent has no partner to share caregiving duties with — arguably needs the leave more, not less.
• Same policy for both adoptive parents: A well-designed policy offers a substantial, "primary caregiver"-style leave to whichever parent will be the primary caregiver after adoption (commonly using maternity-equivalent duration), and a shorter "secondary caregiver" leave (paternity-equivalent duration) to the other parent — rather than assuming gender determines who is the primary caregiver. For same-sex couples or households where roles don't map to a traditional mother/father split, let the couple designate who takes the primary vs. secondary leave.
• Multiple adoptions: Decide whether the benefit is available for every adoption event or is capped (similar to the "number of children" question in paternity leave).

2. Duration benchmarks

Common patterns companies use as a starting point (again, illustrative — not authoritative):

• Primary adoptive parent: Ranges from 8–26 weeks depending on company generosity, often set to mirror or approach the organisation's own maternity leave duration.
• Secondary adoptive parent/co-parent: Ranges from a few days to 4–6 weeks, often mirroring the company's paternity leave duration.
• Age-based tapering: Some companies offer full-duration leave for children adopted below a certain age (e.g., under 1 or under 3 years) and a reduced duration for older children, reflecting a judgment that infants and toddlers require more intensive early-bonding time — though this is a policy design choice, not a legal requirement, so make sure it's applied consistently rather than case-by-case.

3. Documentation needed

• Adoption order from the relevant court/authority, or an official adoption agency placement letter/certificate.
• Any registration confirmation from the applicable adoption regulatory body, where relevant to the adoption route taken.
• An internal leave request specifying the expected placement/handover date (adoption timelines can shift, so build in flexibility for the leave start date to move within a reasonable window).

4. A word on inclusive language

Whatever benchmarks you land on, write the policy in gender-neutral, family-structure-neutral language wherever possible ("adoptive parent," "primary caregiver," "co-parent") rather than defaulting to "mother" and "father." This keeps the policy naturally inclusive of single parents, same-sex couples, and non-traditional family structures without needing constant amendment.

---

Surrogacy Leave: General Considerations

Surrogacy leave is the newest and least standardised category, and it's worth addressing directly in your policy rather than leaving intended parents to guess whether they're covered.

A few general principles that many progressive Indian employers apply:

• Extend maternity-equivalent leave to the commissioning/intended mother, and paternity-equivalent (or a bespoke) leave to the other intended parent, on the reasoning that the caregiving and bonding needs of a family built via surrogacy are functionally similar to those of a family built via adoption.
• Require reasonable documentation, such as confirmation of the legal surrogacy arrangement and the child's birth, while being mindful that surrogacy involves sensitive personal circumstances — keep documentation requests minimal and handle all details with strict confidentiality.
• Clarify eligibility for same-sex couples and single intended parents, since surrogacy is one of the family-building routes more commonly used by these groups; an inclusive, clearly worded policy avoids ambiguity and potential discrimination claims.
• Treat this as a genuinely evolving area. Because there is limited standardisation and the legal and regulatory landscape around surrogacy arrangements continues to develop, it's worth reviewing this section of your policy periodically with legal counsel, and being explicit internally that HR will handle surrogacy-leave requests on a compassionate, case-by-case basis within the policy's general framework if a scenario isn't explicitly covered.

Because surrogacy law and practice can shift, keep this section of your policy general in wording and commit internally to a periodic legal review, rather than hard-coding specifics that might become outdated.

---

Payroll and HRMS Treatment: Getting the Backend Right

A policy is only as good as its execution — and execution runs through payroll and your HRMS. This is where many companies with a "nice policy on paper" quietly fail employees through inconsistent processing.

Setting up leave types correctly

In your HRMS, paternity, adoption, and surrogacy leave should generally be configured as distinct leave types, not lumped into generic "casual leave" or "other leave" buckets. This matters for three reasons: accurate reporting (you can't measure utilisation or plan headcount coverage if the data is buried under a generic category), audit-readiness (if you're ever asked to demonstrate consistent application of the policy, you need clean records), and employee trust (employees should be able to see a clearly labelled leave balance for the benefit they were promised, not have it disappear into an ambiguous bucket).

Recommended leave-type configuration:

• Paternity Leave — separate code, with configurable eligibility rules (tenure, employment type) built into the leave type where your HRMS supports it.
• Adoption Leave (Primary Caregiver) and Adoption Leave (Secondary Caregiver) — two distinct codes if your policy differentiates duration by caregiving role, so reporting and balances stay clean for each.
• Surrogacy Leave — its own code if volume/policy specifics justify it, or nested under adoption-leave logic with a tag if your HRMS allows sub-categorisation.
• Each leave type should carry its own configuration for: accrual (typically these are granted as a lump sum on eligibility trigger, not accrued monthly like earned leave), carry-forward rules (usually not carried forward — use it within the eligible window or lose it), and encashment rules (most companies do not allow encashment of unused paternity/adoption leave, since the purpose is time with a new child, not a payout — but state this explicitly).

Full pay vs. partial pay

Decide and document explicitly whether paternity/adoption/surrogacy leave is:

• Fully paid (most common approach among companies that offer the benefit at all — since duration is usually short relative to maternity leave, full pay is the norm and the strongest retention/goodwill signal).
• Partially paid (e.g., a percentage of base pay), used by some cost-conscious employers, especially for longer adoption-leave durations for the primary caregiver.
• Unpaid beyond a certain point — for example, fully paid for the first X days/weeks and unpaid (or drawn from accrued PTO) beyond that.

Whatever you choose, make sure your HRMS payroll engine is configured to apply the correct pay treatment automatically based on the leave type and, if relevant, the number of days already availed — manual payroll adjustments for parental leave are a common source of errors and employee grievances.

PF, ESI, and statutory contributions during leave

A frequent point of confusion for HR and payroll teams: how do provident fund (PF) and Employee State Insurance (ESI) contributions work during paid leave periods?

• During fully paid leave, since the employee continues to draw salary (paternity/adoption/surrogacy leave being treated as paid leave, similar to earned leave), PF and ESI contributions generally continue to be deducted and contributed as they would during any normal paid period, calculated on whatever salary is actually paid out during that leave.
• During unpaid leave periods, since there's no salary being paid, there is typically no wage base to calculate PF/ESI contributions on for that period — but treatment can vary based on your specific compliance setup, so this should always be confirmed with your payroll compliance provider or statutory auditor rather than assumed.
• Gratuity and continuity of service: Paid leave periods (including paternity/adoption leave, when treated as paid leave) generally count toward continuous service for benefits like gratuity eligibility, but confirm this treatment with your compliance advisor, particularly for longer unpaid stretches.

Because statutory contribution rules and thresholds are revised periodically by the relevant authorities, do not hard-code these treatments into your HRMS without a periodic compliance review — a change in wage ceilings or contribution rules can silently make your configuration incorrect if nobody checks it.

Return-to-work provisions

Good HRMS and policy design should also plan for the transition back to work:

• Automatic leave-balance reactivation: Ensure the employee's regular leave balances (earned/casual/sick leave) resume normal accrual immediately on return, and that the system doesn't erroneously continue to show them as "on leave" past their return date — a surprisingly common glitch when leave end-dates aren't updated promptly.
• Phased return-to-work options: Some companies allow a short period of reduced hours or work-from-home flexibility immediately after parental leave ends, before resuming full in-office/standard schedule — decide if this is part of your policy and, if so, how it's tracked (as a distinct arrangement, not as continued leave).
• Manager and buddy check-ins: Build a lightweight, HRMS-triggered reminder for the manager and/or HR to check in with the returning employee in the first week and first month back, to catch any friction early (workload dumped on them immediately, feeling out of the loop, unclear priorities).
• Protecting performance reviews and appraisals: Explicitly state that time on paternity/adoption/surrogacy leave will not negatively affect performance ratings, variable pay proration (beyond what's fair and transparent), or promotion timelines in a way that penalises the employee for taking the leave they were entitled to.

---

Communicating and Rolling Out the Policy

A policy that lives only in an HR handbook PDF nobody reads is functionally the same as having no policy. Roll it out deliberately:

1. Publish it clearly and accessibly. Put the full policy in your HRMS employee portal or intranet, not just in an onboarding PDF. Make it searchable and easy to find whenever an employee needs it — not just at onboarding.
2. Announce it actively, don't just publish it passively. A short all-hands or email announcement when the policy is introduced or updated helps normalise the benefit and signals genuine organisational commitment, rather than a buried compliance document nobody notices.
3. Create a simple how-to-apply guide. A one-page "how to apply for paternity/adoption leave" walkthrough (ideally embedded in your HRMS leave-application flow) reduces friction and support queries — employees shouldn't have to guess how far in advance to apply or what documents are needed.
4. Brief managers separately and specifically (see next section) — this is often the single highest-leverage step in ensuring the policy works as intended in practice, not just on paper.
5. Revisit and communicate updates. If you change durations, eligibility, or pay treatment, communicate the change clearly and update the HRMS configuration and documentation simultaneously — a mismatch between the written policy and the system configuration is a common source of disputes.

Manager training: the step most companies skip

Even the most generous written policy fails if managers subtly discourage employees from using it — through comments like "are you sure you need the full leave," heavier post-return workloads dumped without warning, or quietly deprioritising the leave-taker for the next project or promotion cycle. Manager training should cover:

• The policy's actual entitlements, so managers don't misinform their team or unintentionally set incorrect expectations.
• Explicit messaging that taking full entitlement is normal and expected, not something to feel guilty about or to be talked out of.
• How to plan for coverage in advance (see backup planning below), so a team's workload doesn't quietly become the leave-taker's problem to solve before they can leave with a clear conscience.
• Neutral, fair treatment in performance and project-allocation decisions both before and after the leave — managers should be explicitly told that penalising someone (consciously or unconsciously) for taking parental leave is a serious issue, not a minor lapse.
• How to handle informal comments or "jokes" from other team members that create a subtly discouraging culture around fathers or adoptive/second parents taking leave (see stigma discussion below).

---

Common Pitfalls to Avoid

1. Inconsistent enforcement

The single most damaging pattern: one team's manager approves generous, flexible paternity leave without friction, while another team's manager quietly discourages it or nitpicks documentation. This isn't just a morale problem — it creates real fairness and potential discrimination exposure. Centralise approval logic in your HRMS wherever possible (eligibility checks, documentation checklist, standard leave duration) so it doesn't come down to individual manager discretion.

2. No backup or workload planning

If a team has no plan for covering a departing employee's work, the informal pressure to "just check in occasionally" or "keep an eye on Slack" during leave becomes almost inevitable — quietly defeating the purpose of the leave. Build a lightweight backup-planning requirement into your leave-approval workflow: when someone applies for paternity/adoption leave, prompt the manager to document a coverage plan as part of the approval process, not as an afterthought once the leave has already started.

3. Stigma around fathers and second parents taking leave

Even in companies with generous written policies, cultural stigma can suppress actual utilisation — fathers may feel that taking the full leave signals a lack of seriousness about their career, or worry (sometimes correctly) that it will be held against them informally. Combating this requires visible action, not just policy text:

• Have senior leaders (especially male leaders, where relevant) visibly take their own paternity leave and talk about it openly — visible role-modelling from the top does more than any policy memo.
• Track utilisation rates by gender/leave type as an internal metric, and treat low utilisation among eligible fathers as a signal to investigate, not a sign that "people don't need it."
• Make it clear in manager training (see above) that discouraging leave-taking, even subtly, is not acceptable.

4. Treating adoption and surrogacy as afterthoughts

Because adoptive and surrogacy-based parents are a smaller population, it's easy for their leave provisions to be vaguely worded, missing from the policy entirely, or informally "figured out" case by case when a request comes in. This creates inconsistency and can feel exclusionary to the employees affected. Write these sections with the same rigor as your maternity and paternity sections, even if you expect them to be used less frequently.

5. Payroll/HRMS misconfiguration

A written policy promising, say, "15 days fully paid paternity leave" is undermined if the HRMS leave type is misconfigured to auto-deduct from casual leave balances, or payroll doesn't recognise the leave type and processes it as unpaid by default. Whenever you introduce or update a policy, walk through an actual test case in your HRMS/payroll system before the first real request comes in — don't debug it live on an employee's first paternity leave application.

6. No clarity on holidays/weekly offs within the leave window

If your policy doesn't specify whether public holidays or weekly offs falling within a leave period are absorbed into the leave count, you'll get inconsistent, ad hoc decisions each time a request happens to span a long weekend — and employees will notice and compare notes.

---

Sample Policy Structure and Checklist

Use this as a starting skeleton — adapt durations, eligibility, and specifics to your own company's decisions and legal review.

Sample Paternity & Adoption Leave Policy — Section Checklist

• [ ] Purpose and scope — one paragraph on why the policy exists and who it covers (full-time employees, contract employees, etc.)
• [ ] Definitions — "eligible employee," "primary caregiver," "secondary caregiver," "co-parent," "immediate family," etc., written in gender-neutral, family-structure-inclusive language
• [ ] Paternity leave
• [ ] Duration
• [ ] Eligibility (tenure, employment type, number of children cap)
• [ ] Window for availing leave (e.g., within X months of birth)
• [ ] Splitting rules (can it be taken in more than one block?)
• [ ] Documentation required and submission timeline
• [ ] Pay treatment (full/partial/unpaid tiers)
• [ ] Adoption leave
• [ ] Eligibility (legal adoption requirement, child's age threshold, single-parent eligibility)
• [ ] Primary vs. secondary caregiver duration and how the couple designates roles
• [ ] Documentation required
• [ ] Pay treatment
• [ ] Surrogacy leave
• [ ] Eligibility for intended parents
• [ ] Duration benchmarks (mirrored to maternity/paternity/adoption sections)
• [ ] Documentation required, with confidentiality commitment
• [ ] Interaction with other leave and holidays
• [ ] Treatment of weekly offs/public holidays within the leave period
• [ ] Interaction with earned/casual/sick leave
• [ ] Carry-forward and encashment rules (typically none)
• [ ] Payroll and statutory treatment
• [ ] PF/ESI contribution treatment during paid vs. unpaid periods
• [ ] Gratuity/continuity-of-service treatment
• [ ] Impact (or explicit non-impact) on variable pay/appraisal cycles
• [ ] Application process
• [ ] How and when to apply (HRMS workflow reference)
• [ ] Advance notice expectations, with allowance for unplanned early arrivals
• [ ] Approval workflow and escalation path if a manager is unavailable
• [ ] Manager responsibilities
• [ ] Coverage/backup planning requirement
• [ ] Non-retaliation and fair-treatment commitment
• [ ] Return-to-work provisions
• [ ] Reactivation of standard leave balances
• [ ] Phased return options, if offered
• [ ] Check-in cadence
• [ ] Review cadence — commit to revisiting the policy (e.g., annually) to reflect changes in company size, competitive benchmarking, and any relevant regulatory updates

---

Illustrative Leave Duration Benchmarks by Company Type

The table below is illustrative only — a snapshot of common patterns HR teams report seeing across the Indian private sector, not an authoritative standard or a legal requirement. Actual policies vary widely even within the same category, and you should benchmark against your specific industry and talent market rather than copying this table directly.

Always verify current entitlements for government employees against the applicable, currently in-force service rules rather than any general benchmark table, and treat every private-sector row above as a design reference point — not a compliance floor.

---

Frequently Asked Questions

1. Is paternity leave legally mandatory for private companies in India? For most private-sector employers in India, there is no single nationwide statute mandating paternity leave the way there is for maternity leave. It is generally offered voluntarily as a matter of company policy. Government employees are covered separately under applicable service rules. Always check whether any state-specific, sector-specific, or company-specific obligation applies to your organisation, since rules can vary and are periodically updated.

2. Do we have to offer the same paternity leave duration to every employee, or can it vary by role/seniority? Best practice, and generally the safer approach from a fairness and morale standpoint, is to apply the same duration and eligibility rules to all similarly situated employees (e.g., all full-time employees past probation), rather than varying it informally by role or seniority — which can create perceptions of unfairness and potential discrimination concerns. If you do want tiered benefits (e.g., unpaid leave for contractors vs. paid leave for full-time staff), state the distinction clearly and apply it consistently.

3. Can an employee take paternity leave in more than one block? That's entirely up to your policy design — there's no external rule dictating this. Many progressive companies do allow splitting paternity leave into two or more blocks within a defined window after birth, to accommodate real family needs (e.g., a short block immediately after birth and another later on). If you allow splitting, document the rules (minimum block size, total window, advance notice) clearly so it's administered consistently.

4. How should we treat adoption leave differently for the primary vs. secondary caregiver? Many companies offer a longer, maternity-equivalent duration to whichever adoptive parent will be the primary caregiver, and a shorter, paternity-equivalent duration to the other parent — letting the couple decide who takes which role, rather than assuming based on gender. This approach also naturally extends to same-sex couples and non-traditional family structures.

5. Does paternity or adoption leave count toward PF and ESI contributions? When the leave is fully paid, salary continues to be paid out, so PF and ESI contributions generally continue to apply on that paid salary just as they would during any other paid leave period. During unpaid leave, there is typically no wage base for that period. Because contribution rules and wage ceilings are revised periodically, confirm the exact current treatment with your payroll compliance provider rather than assuming it stays constant.

6. What documentation should we ask for, and when? Keep documentation proportionate: a birth certificate or hospital discharge summary for paternity leave, and an adoption order or agency confirmation for adoption leave, are typical asks. Because official documents (like a birth certificate) aren't always immediately available, it's reasonable to allow employees to start their leave based on a simpler interim confirmation and submit final paperwork within a short grace period afterward.

7. How do we handle an employee who wants to take paternity leave for a child born via surrogacy? Most employers who address this extend paternity-equivalent (or a bespoke) leave to the non-birthing intended parent, similar to how they'd treat a birth or adoption, since the caregiving and bonding rationale is functionally similar. Since this is a less standardised and more sensitive area, it's worth having HR review these requests with extra care for confidentiality and consulting legal counsel if your policy doesn't yet explicitly address surrogacy.

8. How do we make sure managers don't quietly discourage employees from taking their full paternity/adoption leave? This requires active management, not just a written policy: brief managers specifically on the policy and on non-retaliation expectations, build backup-workload planning into the leave-approval workflow so managers aren't left scrambling, track leave utilisation rates as an internal signal, and encourage visible role-modelling from senior leaders who take their own leave. A policy that exists only on paper, without this active reinforcement, often sees much lower real-world utilisation than intended — especially among fathers.

---

Conclusion

Because paternity and adoption leave in India sit largely outside a single unifying statute for private employers, the responsibility for getting this right falls squarely on you — the HR manager or founder designing the policy. That's real work: setting durations, eligibility, documentation, and pay treatment; configuring payroll and HRMS systems correctly; training managers to protect leave-takers from stigma and unfair treatment; and revisiting the policy as your company grows and benchmarks shift. Done well, though, it's one of the most cost-effective, high-impact levers available for building an inclusive culture and standing out to the talent you want to hire and keep.

If you're building or refreshing your paternity, adoption, or surrogacy leave policy, the administrative side doesn't have to be manual. CozyHR lets you configure custom leave types — paternity, adoption (primary/secondary caregiver), surrogacy, and any other category your policy needs — with the eligibility rules, pay treatment, and documentation workflows built directly into the system. Leave balances, approvals, payroll integration, and compliance-ready records are handled automatically, so your policy works the same way for every employee, every time. Try CozyHR to see how automated leave policy configuration and tracking can take the operational load off your HR team while you focus on getting the policy itself right.