These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Gig Workers HRMS
- Process
- Leave request to decision
Leave request to decision
Leave requests work best when the reviewer sees the employee, leave type, dates and current balance in one case. The request's status distinguishes preparation, submission, approval, rejection, cancellation and time taken.
Step by step
-
Leave type Admin
Admin reviews the applicable leave type's country, employee class, accrual method and documentation rule.
- Establish category and accrual context
- Updates Leave types
-
Balance Admin
The reviewer checks the employee's accrued, taken and pending amounts for that leave type as of the relevant date.
- Review available and pending time
- Updates Leave balances, Employees
-
Request Employee
Employee enters the start and end dates, reason and documentation when applicable, then submits the request.
- Capture dates, reason and employee
- Updates Leave requests
-
Decision Admin
Admin examines the request against the balance and records approval or rejection. The reviewer should use the named approver reference to make ownership clear.
- Approve or reject the submitted request
- Updates Leave requests, Leave balances
ApprovalA person approves before the work moves on. -
Follow-through Employee
The team checks how the approved absence affects the work period and eventually records the taken state when the time has occurred.
- Check actual period and taken state
- Updates Leave requests, Timesheets
Who does what
Roles and permissions- Employee
- Prepares and reads their own request; Admin reviews and records the decision; Payroll Admin checks approved leave during payroll preparation; HR Business Partner maintains employment context.
Set up Gig Workers HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.