How to write a leave policy two managers will apply the same way

Two managers read the same leave rule last quarter and reached different answers, and both can show you the sentence they relied on. One allowed a half-day at short notice and did not deduct it; the other refused the same request and recorded a loss of pay. Both employees have now spoken to each other, and the question has arrived on your desk with an implication of favouritism attached.

The policy document is not silent. It says employees are entitled to a number of days, that leave should be applied for in advance, and that approval is at the discretion of the reporting manager. Every word of that is true and none of it settles the case.

Entitlements are not decisions

Almost every leave policy in a growing business is an entitlement document. It states what people get. What it does not state is what happens in the handful of situations that actually generate disagreement, which is where managers are left to improvise.

• Leave applied for after it was taken, because the person was ill.
• Leave requested at short notice during a delivery week.
• Two people in the same small team asking for the same days.
• A request that takes someone past their available balance.
• Leave taken during probation, or immediately after confirmation.
• A manager who is unavailable when the request needs an answer.
• Leave adjoining a public holiday or a weekly off.
• A pattern — the same employee, the same day of the week, repeatedly.

There are usually fewer than ten of these. Write down the answer to each and most inconsistency disappears, because managers are no longer being asked to invent a position under pressure while the employee waits.

Write cases, not principles

A principle sounds better and performs worse. "Approval is at the manager's discretion, having regard to business requirements" is a sentence two reasonable people can use to justify opposite decisions. A case is specific enough that they cannot.

SITUATION                     RULE                              WHO
-------------------------------------------------------------------
Applied after the fact,       Allowed, with intimation on the    Mgr
due to illness                first day of absence; regularise
                              within N working days of return

Short notice in a delivery    Manager may refuse, must offer     Mgr
week                          alternative dates in writing

Two requests, same days,      Earlier application prevails;      Mgr
same small team               if same day, manager decides and
                              records the reason

Request exceeds balance       Not approved as paid leave;        HR
                              treated as loss of pay unless
                              approved as an exception by <role>

Manager unavailable > N days  Escalates automatically to the     HR
                              next level, not to the founder

Note the last column. Every rule has an owner, and the escalation rule names a level rather than a person. Policies that route exceptions to the founder by default are how founders end up approving leave for people they have never met.

The four questions a leave policy must answer

1. 1

   Who approves, and who approves when they are away

   By role, with a named deputy. The absence of a deputy is the single most common reason a request escalates to the founder.

2. 2

   By when must it be applied for, and by when answered

   Both directions. Most policies set a notice period for the employee and no response time for the manager, which is where resentment builds.

3. 3

   What happens when it is refused

   Refusal is legitimate and should be normal. What must be defined is that a reason is recorded and, where the policy requires it, alternative dates offered.

4. 4

   How the balance is calculated, and where an employee can see it

   If an employee cannot see their own balance, every application becomes a question to HR first. Visibility removes more queries than any other single change.

Make the balance visible before anything else

If you change one thing, change this. When an employee cannot see their own leave balance, three things follow: every application starts with a query to HR, every disagreement becomes an argument about arithmetic nobody can check, and the accrual rule quietly lives in a spreadsheet formula written by somebody who has since left.

Making balances visible is the core of what attendance, shift and leave work is for — one set of rules, each request with a named approver and a cut-off, and a balance the employee can check without asking. Once that exists, the policy stops being a document people argue over and becomes something they consult.

Brief the managers, not just the staff

Policies are usually circulated to everyone and briefed to nobody. Managers are the ones who will be asked, and they are the ones who need the cases. A single session walking through the eight situations above — what the rule is and why — does more for consistency than reissuing the document.

It is also the moment to agree that a refusal is acceptable. Managers approve leave they should refuse mostly because nothing has told them refusal is legitimate, and the resulting inconsistency is then blamed on the policy. Handled together with the rest of the attendance, shift and leave rules, this stops being a leave problem and becomes what it actually is — a question of who decides what, which is the same question running underneath most HR process work.

How you will know it worked

Not by the absence of complaints. By two smaller signals: leave questions stop reaching the founder, and when two employees compare their treatment, the difference has a reason both of them can be told. That is all consistency means in practice — not that everyone gets the same answer, but that the reason for a different answer is written down somewhere before it is needed.

Rolling it out without a revolt

A tightened leave policy is easy to introduce badly. Announced as a document, it reads as a withdrawal of trust, and the first refusal under the new rules is treated as proof. Two things prevent that.

First, introduce the visibility before the rules. Give people their balances, accurately, for a month before anything changes. It is a concession rather than a restriction, and it establishes that the arithmetic is now something both sides can see.

Second, brief the cases as protections rather than limits. The rule that a manager must respond within a set time, and must offer alternative dates when refusing, is a rule in the employee's favour. Most of the eight cases are, if they are explained in that order.

Expect a month of testing, where the edge cases you did not anticipate arrive in quick succession. Write each one down and add it to the rules rather than deciding it privately — otherwise you have simply recreated the original problem with a longer document. Each unanticipated case is a missing rule, and capturing them is how a policy becomes something managers actually consult. Where the same cases keep recurring across departments, it usually points at a structural question about who decides what, which belongs with HR policies and governance rather than with leave.