Requests from the phone
Staff request time off in the app; managers approve or decline with a comment.
Requests, approvals and balances in the same app as the roster, so approved time off never collides with a published shift.
Staff request time off in the app; managers approve or decline with a comment.
Remaining entitlement is visible to the employee, which removes most of the questions.
Approved leave blocks the person in scheduling, so you cannot plan them by mistake.
Holiday, sickness, unpaid and your own categories, per country or site policy.
See who is away in a given week before you approve the next request.
Absence data exports alongside hours for payroll.
Requests sent by message get approved verbally and then forgotten when the schedule is built. Keeping requests, approvals and the roster in one place means the plan reflects reality.
Most leave admin is answering the same question: how many days are left. When people can check that themselves, the manager only handles the actual decision.
Before you commit to any workforce software, get these points in writing — from us and from every other vendor. Our answers are below; we go deeper in the demo.
Yes. We provide a DPA under Art. 28 GDPR and sign it with you before your team starts using the app.
Hosting and database run on Supabase. The exact region and the sub-processor list are set out in writing in the DPA — not only on request.
Location sharing is opt-in per person — refuse it and clock-ins still record, just without coordinates. Reporting and access scope can be restricted per role. The contested points are settings you negotiate concretely in a works agreement.
Time and absence records stay for the legal retention period, then are deleted. All core and time data exports as CSV/Excel — you take your data with you when you switch.
Yes, absence types and allowances are configured per policy.
Yes, new requests appear for the approver responsible.
Approved leave blocks the person in the schedule.
Yes, as its own absence type.