Daily workflow
Leave approval
Make absence decisions with enough context to protect the schedule.
Owner: ManagerLeaveScheduleNotificationsResources
Walkthrough video
Leave approval walkthrough
A short product video or annotated screenshot showing this workflow from the operator's point of view.
What happens
Follow this routine when your team is doing this work for real.
- 1Review awaiting requests by project and date.
- 2Check request duration, balance, attachments, and message.
- 3Check whether the member has scheduled jobs during the requested dates.
- 4Approve or reject with a clear decision note.
- 5Verify balance updates and schedule availability.
- 6Confirm approved leave appears as a schedule window and job conflict context.
- 7Follow up on conflicts before affected jobs are dispatched.
What this uses
The records Flowdexa connects behind the scenes.
- Members
- Leave belongs to a team member and can affect any job assigned to that member.
- Schedule
- Approved leave becomes a schedule window so managers can see coverage gaps.
- Jobs
- Jobs scheduled during approved leave can show conflict warnings when the same member is assigned.
- Payroll
- Leave approvals affect attendance context and payroll review.
Before you call it done
Run these checks to make sure the workflow is actually working end-to-end.
- The responsible role can complete the workflow without owner access.
- Required customer, service, schedule, resource, or payroll records are connected.
- Blocked work has a visible reason and a named next owner.
- Managers can see the status in daily operations or reports.
Next
Keep learning daily workflows
Use the workflow index when training another role or moving to the next part of daily operations.