Casual leave (CL) is short-notice paid time off for personal reasons that don’t need a doctor’s note or weeks of planning: a family errand, a sudden appointment, a day you just need. Most Indian employers allow 6 to 12 days a year, capped at two or three days per request, and it doesn’t carry forward once December 31 passes.
Casual leave sits in an odd spot in Indian labour law. Earned leave has the Factories Act behind it. Sick leave usually needs medical proof. Casual leave has neither. It exists mostly because state Shops and Establishments Acts require it, and because it’s genuinely useful for the HR team that has to keep operations running while people deal with ordinary life.
That looseness is also why so many companies get it wrong. Some treat CL like a fourth category of sick leave. Others let it quietly merge with earned leave until nobody can tell the two apart on a payslip. Neither is correct, and neither is illegal. That’s exactly the problem: there’s no single national rulebook forcing consistency.
Employees confuse these three constantly, and the confusion shows up as HR tickets. Here’s the difference in one table.
| Leave Type | Purpose | Typical Days/Year | Carry Forward? | Encashable? |
|---|---|---|---|---|
| Casual Leave | Short, unplanned personal reasons | 6 to 12 | No, lapses Dec 31 | No |
| Sick Leave | Illness, usually needs a certificate past 2 to 3 days | 7 to 12 | Limited, state-dependent | Rarely |
| Earned Leave | Planned time off, accrued through the year | 12 to 30 | Yes, up to a cap | Yes, the one category that usually is |
The practical difference that matters most: earned leave is the one employees treat as savings. Casual leave is the one they treat as a release valve. Build your policy around that distinction and most of the disputes disappear on their own.
There’s no single number, which frustrates people who want a clean answer. What exists instead is a patchwork of state rules and company norms that cluster around a similar range.
| Category | Typical CL Entitlement | Governing Rule |
|---|---|---|
| Central Government employees | 8 days/year | CCS (Leave) Rules, 1972 |
| Maharashtra (private sector) | 8 days/year | Maharashtra Shops & Establishments Act |
| Delhi (private sector) | 12 days/year | Delhi Shops & Establishments Act |
| Tamil Nadu (private sector) | 12 days/year | Tamil Nadu Shops & Establishments Act |
| Karnataka (private sector) | No separate CL quota, folded into sick/earned leave | Karnataka Shops & Establishments Act |
Treat these as a starting reference, not gospel. State rules get amended, and your own state’s act may set a different number for your establishment size and category. If you’re building a policy from scratch, checking the current Shops and Establishments Act for every state you operate in beats copying a number off a blog post, including this one.
For Central Government staff specifically, the CCS Leave Rules are more prescriptive than most private-sector policies. Employees get 8 days a year, with a 3-day cap per spell (extendable to 5 with a Restricted Holiday attached). Half-day CL is allowed. Unused days lapse hard on December 31, with no grace period and no rollover.
In practice, most CL requests fall into a handful of buckets:
None of these need justification documents in most policies. That’s deliberate: CL exists precisely so employees don’t have to build a paper trail for ordinary life.
Full-time confirmed employees are the default case every policy is written for, but three groups routinely get overlooked.
Part-time employees are usually entitled to CL on a pro-rata basis tied to hours or days worked, not the full quota a full-timer gets. Check your state’s Shops Act, since the pro-rata formula isn’t standardized.
Contract and consultant staff engaged through a vendor or on a fixed-term contract typically fall outside the company’s CL policy entirely. Their leave terms, if any, come from the contract itself or the staffing agency, not the client company’s handbook.
Probationary employees, as covered below, often have CL withheld or capped until confirmation. It’s a detail that trips up a lot of new joiners who assume day-one entitlement.
Government leave rules are written down and enforced uniformly. Private sector rules are set by each company within the boundaries of the state Shops Act, which is why two offices of the same company in different cities can legally run different CL policies.
| Aspect | Central Government (CCS Rules) | Private Sector (typical) |
|---|---|---|
| Annual entitlement | 8 days, fixed | 6 to 12 days, company-set within state limits |
| Max consecutive days | 3 (up to 5 with a Restricted Holiday) | 2 to 3, varies by employer |
| Half-day leave | Explicitly permitted | Usually permitted, not guaranteed |
| Approval basis | Discretionary, tied to workload | Discretionary, manager-approved |
| Year-end treatment | Lapses Dec 31, no exceptions | Lapses Dec 31 in almost all policies |
This is the one rule that holds almost everywhere. Unlike earned leave, unused CL simply disappears at year-end. No payout, no rollover into January. If your HR software shows a running “CL balance” that survives into the new year, that’s a configuration bug worth fixing before an employee notices and asks for money.
Two to three consecutive days is the norm. Ask for a week of casual leave and most managers will (correctly) push back and ask why this isn’t earned leave instead. CL was never meant to cover planned vacations. Using it that way is the single most common misuse HR teams report.
Many companies don’t activate CL until an employee clears probation, sometimes 3 to 6 months in. During probation, unplanned absences typically get handled as loss-of-pay or, informally, manager discretion. Spell this out in the offer letter; new hires ask about it more than almost anything else in the leave policy.
Prefixing or suffixing CL to a public holiday or weekend is standard practice, and for Central Government staff, it’s explicitly permitted under CCS rules. Private employers vary. Some cap how many CL days can touch a long weekend to stop it becoming a de facto vacation policy.
Most workplaces have simplified this to three steps:
A short application reads something like this:
Subject: Casual Leave request, [Your Name], [Date]
Hi [Manager], requesting casual leave on [date] for a personal matter. [Colleague] will cover my open items. Will be reachable on email if anything urgent comes up.
CL is the right tool for a sudden family matter, a same-day appointment, a landlord visit, a half-day for a bank errand that only happens during business hours. It’s the wrong tool for a planned trip, a wedding you’ve known about for two months, or stacking CL across three quarters to avoid ever touching your earned leave balance.
The pattern worth watching for as HR is an employee who consistently takes CL on Mondays or Fridays. It’s not automatically a problem, but it’s a pattern that deserves a conversation before it becomes policy abuse, and it’s exactly the kind of thing that’s invisible in a paper register and obvious in three clicks on a proper attendance dashboard.
Two mistakes show up again and again in the policies we come across. First, companies write a CL policy once and never revisit it against the state Shops Act after opening an office in a new city, so the Bangalore team and the Delhi team end up quietly operating under different legal entitlements without HR fully realizing it. Second, companies don’t distinguish CL from sick leave in their system, so an employee “borrows” sick days as casual leave and the year-end sick leave utilization report looks nothing like reality.
Neither mistake is dramatic on its own. Both compound badly at audit time, and both are avoidable with leave categories that are actually enforced in software rather than left to a spreadsheet and good intentions.
Manually reconciling CL balances across even 50 employees is tedious. Across 500, it’s a liability. A proper time and attendance system applies your CL policy automatically: accrual, the year-end lapse, the consecutive-day cap, probation holds, so nobody has to remember the rule, because the system won’t let a request violate it in the first place. It also gives you the pattern visibility that a paper register can’t: which team is burning through CL fastest, whether Monday/Friday clustering is happening, whether a policy needs adjusting before it becomes an absence management problem instead of a leave-tracking one.
There’s no single central law mandating it nationwide. It’s typically required under state Shops and Establishments Acts, which is why entitlement varies by state rather than being fixed federally.
Yes. CL is generally granted at the employer’s discretion when business needs allow it. It’s an authorized absence, not an automatic entitlement the moment it’s requested.
No. Almost universally, unused CL lapses on December 31 and doesn’t roll into the new calendar year.
Yes, casual leave is fully paid. Taking it doesn’t reduce salary the way loss-of-pay leave does.
Casual leave covers short, unplanned absences and lapses each year with no payout. Earned leave accrues over time, can usually be carried forward up to a cap, and is often encashable when unused.
Most policies allow half-day CL, split into pre-lunch and post-lunch halves. It’s useful for a single appointment rather than losing a full day’s balance.
Two to three consecutive days is the typical cap. Central Government employees can extend to five days if a Restricted Holiday is attached.
Often not immediately. Many companies activate CL only after probation ends, commonly 3 to 6 months into employment. Check your offer letter or employee handbook for the exact window.
Usually yes, though some employers cap how many CL days can be attached to a long weekend specifically to prevent it functioning as unofficial vacation time.
It’s typically treated as unauthorized absence and can be converted to loss-of-pay, depending on company policy. Always route the request through your manager or HRMS first, even for a same-day emergency.
Routing leave requests correctly, and keeping an accurate record of what was approved and when, is exactly what HR software is built to handle consistently.