Your Tech Club
Back to all 51 profiles

Profile

A leave request is usually a formality, until two people ask for the same week and nobody is left.

The Leave Request Handler checks the balance, looks at staffing for that period and handles whatever causes no problem.

Anything that clashes goes to the manager with the full picture, not as a single request.

What it does, step by step

  1. Receive the requestThrough the HR system, Teams or a form.
  2. Check the balanceIs there enough leave, and of which type.
  3. Check staffingWho is already off in that period, and does staffing stay at the required level.
  4. Approve or referNo clash means approval; a clash goes to the manager with an overview.
  5. ProcessIn the HR system and in the calendars that depend on it.

Works with these systems

HR
Communication
Planning
  • APIs

Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.

What runs automatically and what does not

You stay in control.

Not every decision should be made automatically. For each workflow, we set out:

  • What can happen automatically.
  • What is put forward for approval first.
  • When a person is brought in.
  • What information is stored.
  • How actions are logged.

Is this a fit for your organisation?

A good fit if

  • Organisations with rotas or minimum staffing per day.
  • Businesses where leave requests currently go by email.
  • Situations with many part-timers and changing availability.

Less of a fit if

  • Small teams where everyone knows each other's diary.
  • Deciding on leave when there is a clash.

What it can deliver

  • Quick answers to requests that cause no problem.
  • Staffing problems that become visible before leave is granted.
  • Less back and forth about balances.

Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.

Frequently asked questions

Does an AI employee approve leave itself?

Only requests that meet all your rules: enough balance, no staffing problem, within the request period. Everything else goes to the manager. You decide exactly where the line is.

Does it take minimum staffing into account?

Yes, as long as it is recorded somewhere per team, day or shift. If it is not, it can only check the balance, and that is exactly where the clashes usually are not.

What happens if two people request the same period?

Both requests go to the manager with the overview. It does not decide who gets priority, because that is a judgement about people, not about rules.

Does this work with AFAS?

Yes, through the API. Processing happens in your HR system itself, so balances and records stay in one place.

How to put this to work

  1. 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
  2. 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
  3. 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.

More HR tasks