Request and approval
Employees submit in a few clicks. Managers approve with context. Nothing sits in email.
Time
Leave requests that route. Balances that are real. Attendance tied to the same record payroll uses.

The problem
Leave should not live in a group chat.
Set leave types, balances, and policies once. Route requests to the right approvers. Teams see who is away before they plan the week.
Capability
Employees submit in a few clicks. Managers approve with context. Nothing sits in email.
Who is off, when, and whether coverage holds.
Annual, sick, and custom types. Accrual, carryover, maximums.
Presence and exceptions in the same system as the employee record.
Patterns by department, not a scavenger hunt.
Hours and presence finance can use without a side spreadsheet.
Outcomes
The workflow is the process.
Payroll reads the same numbers.
The calendar is the source, not a rumour.
Policy does the first pass.
Workflow
Types, accruals, and approvers.
Submit, route, approve. The calendar updates.
Attendance and leave sit on the record payroll uses.
FAQ
Yes. Set policies, accrual, carryover, and approval chains to match how your company works.
Attendance and leave live on the same employee record payroll uses, so finance is not reconciling a separate tracker.
Yes. A shared calendar shows leave and presence so coverage is planned in the open.
See how Recurr handles time off and attendance.