Leave and absences, built into your GPS clock-in

The leave request, from the employee's side

The employee scans a QR code, identifies themselves with their PIN, chooses their dates (morning, afternoon, full day or several days), views their balances in real time and signs directly on screen. Simple, even for an agent with no email address.

Approval, from the manager's side

• Approval or rejection with a mandatory reason
• Automatic balances per employee, leave type and year
• Customizable types (paid leave, RTT, sick leave, unpaid…)
• PDF sheet, time-stamped and signed, with the approver's name

A clear calendar view

View all absences on a monthly grid, grouped by team. You approve a pending request directly from the calendar.

Synced with the schedule

Approved absences are immediately reflected in the schedule: an employee on leave can no longer be scheduled, which avoids assignment errors.

The leave process, as it really happens

In most service companies, a leave request starts as a piece of paper or a text message, sits on a desk for a while, comes back verbally, and ends up in a balance spreadsheet kept by a single person. Nobody is sure of the counters, requests overlap, and sometimes a staff member is scheduled while on approved leave.

“My staff don't have computer access”

They don't need it. The request is made from a QR code displayed on the premises: the staff member scans it, enters their PIN, and accesses their own balances and request history. They choose their dates, specify whether it is a full day, a morning or an afternoon, sign with their finger, and send.

No app, no username, no work email needed - the same principle as QR code clock-in.

“My leave balances are never up to date”

The balance used is not entered by hand: it is recalculated from the requests actually approved. It therefore cannot drift from reality, which is the structural flaw of a spreadsheet - where one forgotten approval skews the counter for the rest of the year.

You set the counters per employee, per type and per year, and the staff member sees their remaining balance when making a request, which eliminates a good share of impossible requests.

“How do I avoid scheduling someone who is on leave?”

The check is done by the app, not by your vigilance. If you try to place a staff member on approved leave in a slot, the schedule refuses and tells you so. When copying a week, the affected slots are automatically excluded and listed, so you know exactly which ones to reassign.

“I need to approve with full knowledge”

Before approving, you can open the absence calendar directly from the request, with the requester's row highlighted and the requested dates outlined. You immediately see whether another staff member from the same area is already absent during the period, instead of approving blindly and discovering the conflict a week later.

A refusal requires a reason, which is sent to the employee - avoiding decisions perceived as arbitrary.

“I need written proof”

Each request can be generated as a PDF form: employee identity, type of absence, dates and duration in working days, the requester's handwritten signature, then the approver's name with the date and time of the decision. It is the document to file in the personnel record, generated without re-entry.

Absences, scheduling and hours: a single source

Absences don't live in an isolated corner. They block scheduling, appear in the team calendar, and are cross-checked with the hours actually clocked when you prepare payroll. This continuity is what eliminates month-end gaps between what was planned, what was worked and what must be paid.