Decide which leave types you need and what each is for, then fix the accrual basis, the reset date, the approval chain and the notice you expect. Settle carry-forward and encashment. Write the edge cases down explicitly: probation, notice period, part-month joiners, negative balances. Statutory minimums vary by state and change, so confirm them with a qualified advisor.
Begin with purpose rather than with a list copied from another company. Each type you create must answer a question nobody else answers: earned leave is planned time off that accumulates, sick leave covers unplanned illness and usually asks for evidence beyond a threshold, casual leave absorbs short personal errands, maternity and paternity leave follow their own statutory footing, bereavement and marriage leave are goodwill provisions, and unpaid leave is the release valve when a balance runs out. Add compensatory off if your operations create it. Resist the temptation to add a type for every scenario someone raises, because a policy with a dozen categories generates constant misclassification and makes the balance meaningless to the person reading it. If two types have the same rules and the same evidence requirement, they are one type with two reasons.
Three decisions sit here and they interact. First, accrual basis: leave can be credited at the start of the year, monthly as it is earned, or per completed period of service. Monthly accrual is fairer to leavers and joiners but produces smaller, fiddlier balances; upfront credit is simpler to explain but creates a recovery problem when someone resigns having used more than they earned. Second, the cycle: calendar year, financial year or joining anniversary. Anniversary cycles feel equitable and are painful to administer because every employee has a different reset date. Third, rounding: whether a part-month of service earns a part-day, and how that fraction is displayed. Fix these three before configuring anything in [leave management software](/leave-management-software), because changing an accrual basis after balances exist means recalculating history.
Approval design is where policies quietly fail. Decide who the approver is by default - almost always the reporting manager - and what happens when that person is themselves on leave, has left, or is the applicant. A policy without a delegation rule produces requests that sit unanswered until the employee simply takes the day. Then set expectations rather than absolutes: planned leave should carry advance notice proportionate to its length, sick leave is applied for after the fact by definition, and long absences deserve a second approver because they affect staffing and cost. Say explicitly whether an unapproved application defaults to approved or rejected after a period, because leaving that undefined is how disputes start. Finally, decide who can approve retrospectively and record that they did.
This is the clause employees read most closely and policies write most loosely. Three treatments exist and you must name which applies to each type: lapse at the end of the cycle, carry forward into the next one, or encash. Carry-forward normally comes with a ceiling and sometimes with an expiry, so state both. Encashment needs a defined basis, a defined trigger and a statement of whether it happens annually or only at exit. Also decide the order of consumption when someone has both carried-forward and current-year balance, because taking the older balance first protects the employee and taking the newer one first protects the company, and whichever you choose should be visible rather than buried in a system setting. Statutory rules constrain some of these choices and differ by state, so confirm your position with a qualified advisor.
A leave application that spans a weekend, a public holiday or a rostered week-off needs a stated rule, and different organisations reach different answers legitimately. Say whether intervening non-working days are counted against the balance or excluded. Say what happens when a holiday falls inside a long absence. Then handle the shift population separately: for someone on a rotating roster, a day off is not a fixed calendar day, so leave has to be measured against the roster rather than against Monday to Friday, and your holiday calendar may differ by site or state. Sandwich rules, where non-working days between two leave days are charged, are common and unpopular, so if you use one, write it plainly instead of letting people discover it from a balance they cannot explain.
Four cases produce the majority of disputes and none of them appear in a standard template. Probation: does leave accrue during it, can it be taken, and what happens to accrued balance if the probation fails. Notice period: whether leave can be applied for at all, whether it extends the notice, and how balance is settled. Part-month joiners and leavers: the proration rule and how it rounds. Negative balance: whether the system permits it, up to what point, and how it is recovered at exit. Add a fifth if you employ across locations - which site's holiday calendar and which state's rules apply to a transferred employee. Write each of these as a sentence in the policy document, not as a configuration someone discovers later.
Configure the rules once, then test them against the awkward cases rather than the ordinary ones: a joiner mid-month, a leaver with a negative balance, an application spanning a holiday, a retrospective sick leave, a transfer between sites. Publish the written policy where employees actually look, which normally means alongside their balance in the [self-service portal](/employee-self-service-portal) rather than in a shared drive nobody opens. Then hold the line on changes. Every exception granted outside the policy becomes precedent, so route them through a single owner who records the reason. Review annually, before the cycle resets rather than after, and check the exception log first: repeated exceptions of the same kind are the policy telling you which clause is wrong.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
