Leave requests
Also called time off request, absence request, PTO request
Requested by the employee, routed to the right supervisor by role and kind of leave, and on the calendar the moment it’s approved. We build it to work the way you handle leave now.
Leave request
EmployeeD. Novak, Custodian
Kind of leavePersonal
DatesMar 9 to Mar 10
BuildingWashington Elementary
Routed toBuilding principal
When approvedAdded to the calendar
Submit
Video coming
Start to finish
From the request to the calendar.
Here’s how it runs in Flow Forms. The steps marked on its own happen without anyone, and everyone else is notified when it’s their turn.
- 1The employee
Fills it out on any device, no login. A printed code in the bus barn or the break room opens it, so staff who aren’t at a desk can ask from wherever they are.
- 2The routingOn its own
Sends it by role and kind of leave: a driver’s day off to transportation, an aide’s to the building principal, an unpaid stretch to whoever approves those.
- 3The supervisor
Approves it from any device, or sends it back with a note. Leave they’ve already approved is on their calendar, so they know who else is out. If it sits, reminders go out. If they’re out, it goes to their backup.
- 4The calendarOn its own
Approved leave goes onto the calendars of the people who need to know, so whoever schedules coverage or routes sees who’s out without being told.
- 5HR and payroll
See approved leave as it adds up, and pull the month together when payroll closes instead of matching paper forms to absences.
- ✓On fileOn its own
Every request keeps who asked, for what, who approved it, and when. If anyone edits it later, the edit is logged.
What it handles
The details, built in.
- Staff who aren’t at a deskDrivers, custodians, and kitchen staff ask from a printed code, no login.
- The right approverRouted by role and kind of leave, so nobody reads the form first to forward it.
- Who’s already outApproved leave on the calendar of whoever plans around it.
- When the supervisor is outIt goes to their backup, so a request never waits on one person.
- Payroll at month endApproved leave pulled together and exported, not reconstructed from paper.
Yours needs something that isn’t here?
Bring it to the first call. We’ll build it in while you walk us through how it works.
Book a conversation →How it varies
Every organization handles leave a little differently.
We don’t start from a standard leave form. We start from how yours runs today. And when something changes, like a new kind of leave or a new approver, tell us and we change it.
We build it to yours.
- Who approvesBy building, by department, by role, or by the kind of leave.
- Kinds of leavePersonal, vacation, bereavement, professional, unpaid, and whatever else your agreement lists.
- NoticeHow far ahead it’s due, and what happens to a request made the morning of.
- Who needs to knowWhoever schedules coverage, dispatch, the front office, or payroll.
- BalancesChecked by the supervisor, by HR, or in your payroll system before it’s approved.
Questions
About leave requests.
Does this replace our absence management system?
Can different kinds of leave go to different approvers?
How do staff without a computer submit a leave request?
What happens when two people ask for the same days?
Does it track leave balances?
Bring us yours.
We’ll build it with you.
Tell us how leave gets requested and approved now, who signs off, and who needs to know when someone’s out. Not a demo. A conversation about your process.
Book a conversationOften run alongside leave requests
See every process →- Personnel actions Hires, transfers, pay changes, each on its own path.
- Professional development requests One request for the group, a sign-off from each attendee.
- Onboarding Everything before the first day, finished by everyone with a part.