Staff Holiday Booking in Slack & Teams (UK)

Your UK team probably runs on Slack or Microsoft Teams all day, so why is booking annual leave still a spreadsheet-and-email job? This is a UK-focused guide to staff holiday booking right inside the chat your team already uses, with the working-days, bank-holiday, carryover, and GDPR details a UK people team actually needs.

How do staff book annual leave in Slack or Teams?

TimeLeaf makes staff holiday booking happen right inside Slack or Microsoft Teams, where your team already works all day. An employee types a request, picks the dates, and a manager gets an interactive approve or decline message in the chat tool they already have open. No spreadsheet someone forgets to update.

Here's the flow. An employee requests time off from the TimeLeaf dashboard or mobile interface, choosing any leave type you've defined: annual leave, sick, personal, parental, unpaid, bereavement, jury duty. Their direct manager gets a Slack DM (or a Teams notification) with approve and decline buttons. One tap, and the employee gets a confirmation message back. The balance is only deducted once the request is approved, never when it's submitted, so a pending request never quietly eats someone's allowance.

A couple of things worth knowing up front:

• Slack and Teams matching is by email. TimeLeaf maps Slack users (and Entra ID / Azure AD directory entries) to employees by their email address, so there's no separate login to chase.
• It's a Professional-plan feature. The Slack and Microsoft Teams integrations, like time tracking and directory sync, start on the Professional plan and above. The Starter plan covers leave, the team calendar, email notifications, blackout periods, and CSV export, but not the chat integrations.

If you're also juggling rotas, the guide to shift scheduling and leave management shows how time off and shift cover sit together in one place.

Working-days and public-holiday calendars (and bank holidays)

Yes, TimeLeaf calculates annual leave against working-days and public-holiday calendars, so a request that spans a weekend or a bank holiday doesn't burn allowance for days nobody was due to work. You set the working week and the holiday calendar per leave policy.

For a UK team that means a Monday-to-Friday working pattern with England and Wales (or Scotland, or Northern Ireland) bank holidays excluded from the deduction. Book the week around the August bank holiday and TimeLeaf counts four days off your allowance, not five. You assign these calendars per policy, so a part-time or compressed-hours pattern can have its own rules without affecting full-time staff.

This is policy-level configuration, set once and applied to everyone on that policy. The guide to setting up leave policies covers how the working-days and holiday calendars fit together with the rest of a policy ruleset.

Carryover, accrual, and pro-rated allowances for new starters

A mid-year joiner shouldn't get a full year's holiday on day one, and TimeLeaf handles that automatically. It builds pro-rating, accrual, and carryover into each leave policy, so a new starter in September gets an allowance scaled to the time left in the period without you doing the maths.

You've got a few levers per policy:

• Fixed or accrued allowance. Give the whole allowance up front, or accrue it monthly or on the hire anniversary.
• Pro-rating for new starters. A mid-year joiner gets an allowance scaled to the time left in the period, automatically.
• Carryover rules. None, unlimited, or capped at a set number of days into the next period.
• Start-of-period accrual by default. Switchable to end-of-period if your policy works that way.

Reassign someone to a different policy mid-year (say, part-time moving to full-time) and TimeLeaf recalculates the balance rather than leaving you to do the maths. This is the kind of rule that gets messy in a spreadsheet the moment your headcount passes a couple of dozen people. The small-business PTO tracking guide walks through why that breaks down as you grow.

Blackout periods: managing leave around your busy season

A blackout period restricts leave during your peak weeks, but TimeLeaf flags those requests for a manager to decide rather than hard-blocking them. Requests inside a blackout window trigger a warning and notify the manager, who can approve, decline, or apply a per-employee exception.

This matters because real life has exceptions. A retailer locking down December still wants to approve the team member who booked a wedding eight months ago. So blackout periods warn and notify rather than slam the door. You can set per-employee exceptions and a manager can override. Blackout periods are available on every plan, including Starter.

The same flagging-not-blocking logic applies to overlapping requests: TimeLeaf surfaces the conflict for a manager rather than silently rejecting the second person to ask.

Half-days and documentation requirements

TimeLeaf supports half-day leave and per-policy documentation requirements. If you enable half-days on a leave type, staff can book a morning or afternoon off; if a policy requires documentation (a sick note, for example), TimeLeaf enforces it on those requests.

A few related policy controls:

• Half-day bookings when enabled on the leave type, alongside single and multi-day requests.
• Required documentation per policy, so a sick-leave type can demand a note while annual leave doesn't.
• Advance-notice minimums, so a request for tomorrow can be held to a different standard than one booked a month out.
• Request statuses of Pending, Approved, Declined, and Cancelled, with the balance restored automatically if an approved request is later cancelled.

Does it handle GDPR and EU data residency?

Yes. TimeLeaf's managed cloud runs on Microsoft Azure in West Europe (Netherlands), giving you EU data residency, and GDPR tooling (data export, deletion requests, consent handling) is available on every plan, including Starter.

On the security side, data is encrypted with AES-256 at rest and TLS 1.2+ in transit with HSTS, each tenant gets its own isolated database schema, and audit logs are retained for 12 months. Role-based access control separates Admin, Manager, and Employee permissions. SSO/SAML is available from the Professional plan, including SSO via a Microsoft account for Teams-based organisations. If you cancel, your data is retained for 30 days before deletion.

For a UK or EU people team, that combination of West Europe hosting plus all-plans GDPR tools is usually the deciding factor over a US-hosted competitor. You can read more in the documentation.

Booking holiday from Slack or Teams: what you need

To run staff holiday booking through Slack or Microsoft Teams, you need the TimeLeaf Professional plan or above and a few minutes of setup. Here's the short version.

• Connect your chat tool. Slack or Microsoft Teams, plus optional Entra ID / Azure AD directory sync that re-syncs every six hours to keep your employee list current.
• Set your leave policies. Working-days and bank-holiday calendars, accrual or fixed allowance, carryover, and any blackout periods for your busy season.
• Choose approval routing. Default routes to the direct manager (falling back to HR if none); multi-level escalation above a day threshold is available on Professional, and fully custom workflows on Business and above.
• Add a daily digest if you want one. TimeLeaf can post a who's-off summary (default 8:00 AM) to Slack and notify a team absence channel, so nobody's surprised by an empty desk.

When you're ready to try it, every plan has a 7-day free trial (a credit card is required) and most teams are set up in under 30 minutes. See the pricing page for the plan that fits your headcount, or jump straight to signing up.