You’re in a client meeting, your phone buzzes, and it’s a holiday request. To deal with it you’d need to log in, find the request, check who else is off, and click approve. So you leave it, and three days later the person asks if you’ve seen it. Approving a holiday request by email fixes that, as long as the email carries enough to decide on and the button is safe to press.
How approving a holiday request by email works
The idea is simple. When someone books leave, their approver gets an email with the details and two buttons: Approve and Decline. One press, and the decision is made and recorded as if they’d done it in the app.
What makes it work in practice is what sits around the button:
- The right person gets the email. Not a shared mailbox and not “whoever’s around”: the person’s own approver.
- The email says enough to decide. Dates, the type of leave, the reason if there is one, and what it takes off the person’s allowance.
- The button can’t be pressed by accident. A link scanner or a preview pane opening the link shouldn’t approve anything.
- The decision is on the record. Who approved, when, and that it came from the email.
What the approver needs to see before they approve
An approval made blind is just a rubber stamp. Before pressing Approve, an approver usually wants to know:
- Which dates, and whether they’re half days.
- What kind of leave: annual leave, TOIL, an appointment.
- What it deducts. “Deducts 3 days” settles most questions about whether someone has enough left.
- Who else is off. The one that catches people out. Two of a three-person team away the same week is a problem you want to spot now.
If the email doesn’t show the clash, the approver should be one click from the wallchart. If you set a rule for how many can be off at once, the system should warn about the clash before the request reaches anyone.
Can you refuse a holiday request by email?
Yes. A decline is a decision like an approval, and it’s worth giving a reason. The law also has something to say about timing.
Under regulation 15 of the Working Time Regulations 1998, a worker gives notice of leave they want to take, and an employer can give a counter-notice telling them not to take it on particular days. For statutory leave, that counter-notice has to be given at least as many days in advance as the leave requested (legislation.gov.uk, WTR reg 15, checked 27 October 2026). Acas puts it the same way: an employer must let the worker know beforehand by at least the same amount of time as the leave they asked for, and should have a good business reason (Acas, Asking for and taking holiday, checked 27 October 2026). An employer can refuse particular dates, but cannot stop someone taking their leave altogether (gov.uk, Holiday entitlement: booking time off, checked 27 October 2026).
A contract can set different notice rules, and where it does, the contract applies. If a refusal is likely to be disputed, talk to Acas or an employment solicitor first.
The practical point is that a fast decision is a fair one. A request decided the same day by email leaves time to rearrange. A request left for a fortnight may not.
Is it safe to approve leave from an email?
It’s a fair question. An email can be forwarded, and a link in it can be opened by software. These are the safeguards that matter:
- Opening the link changes nothing. The link opens a short confirmation page that names the request and says who you’re acting as. Only pressing the button on that page records the decision.
- Each link works once. After it’s used, or once the request has been decided, it stops working. If someone else got there first, the page says so.
- Links expire. An old email can’t approve a request weeks later.
- Only approvers get buttons. The person who booked the leave never receives a link that could approve their own request.
- Sign-in can be required. If you’d rather nobody could act from a forwarded email, you can require approvers to be signed in before the button works.
That’s how Sign2Approve Time off handles it. The approver’s email shows the reason, the type, the dates and what it deducts, then Approve and Decline. Decline with reason opens a comment box, and you can require a reason for every decline. Each link is single use and expires after seven days. The decision is recorded on the request’s audit trail, marked as made from email.
Who should get the approval email?
The email is only as good as the person it goes to. In Sign2Approve Time off, a request goes to the person’s own named approver if they have one; otherwise their line manager; otherwise their department’s approvers. Nobody approves their own leave. Where a request goes to several people, the first to act decides it and the others’ copies close, so nobody approves something already declined.
If the approver doesn’t act, reminders and escalation keep it moving. Requests waiting on you also sit in one Inbox alongside contracts and expense claims to approve, so you have one list, not three.
For approvers who live in Microsoft Teams or Slack, the same decision can be made there.
Setting it up so it runs itself
A few choices, made once, save most of the chasing:
- Name an approver for everyone. Line manager by default; a named person where the reporting line doesn’t fit.
- Decide whether declines need a reason. It’s kinder, and it’s a better record.
- Set your clash rule. How many from a department can be off at once, and whether going over warns or blocks.
- Decide on sign-in. One-click is quicker; requiring sign-in is tighter. Pick what suits your team.
For the wider question of who signs off what across contracts, leave and expenses, read Approvals: who should sign off what.
Sign2Approve Time off lets approvers decide leave from the email, free for up to 5 people: see Time off.