Skip to main content

​
Overview

A leave request connects employees, approvers, balances, inbox items, wallcharts, and reports. Use this workflow to test whether your first Teamper setup is ready for employees. The first test request should prove that an employee can submit leave, the assigned approver can approve or reject it, and the result appears where employees, managers, and admins expect to see it.

​
Who can use this

Employees can submit leave requests. Department approvers, line managers, and custom approvers can review requests assigned to them. Company admins and HR admins can review setup, reporting, and visibility.

​
Before you start

Confirm:
  • The employee has an active employee record.
  • The employee has a department or team when their route uses Department approvers.
  • The employee has one configured route: Department approvers, Line manager, Custom, or No approver.
  • The selected route has active approvers, unless it is No approver.
  • The employee has a holiday calendar.
  • The employee has a leave policy.
  • The leave type and leave policy rule are active.
  • The employee or test user can sign in to Teamper.

​
How it works

  1. An employee creates a leave request.
  2. Teamper checks the selected dates, sessions or times, leave type, overlap, and available balance.
  3. A manual route submits the request as pending. No approver and self-approver routes submit it as approved.
  4. The assigned department, line manager, or custom approver reviews the request. A No approver or self-approver route approves it automatically.
  5. For a manual route, the approver clicks Approve or enters a Reject reason and clicks Reject.
  6. Teamper updates the employee view, manager view, wallchart, inbox, and reports.

​
Step-by-step guide

​
1. Submit the request

  1. Sign in as the test employee.
  2. Open the employee dashboard or request leave area.
  3. Create a leave request.
  4. Select the leave type.
  5. Select the start date and end date.
  6. For daily leave, choose the starting and ending sessions.
  7. For hourly leave, choose the start time and end time.
  8. Add a reason.
  9. Review the total duration.
  10. Click Submit Request.

​
2. Review the pending request

  1. Confirm the employee can see the submitted request.
  2. Confirm the request status is pending.
  3. Confirm the selected leave type, dates, duration, and reason are correct.

​
3. Approve the request

  1. Sign in as an approver resolved from the employee’s route.
  2. Open the approval request.
  3. Review the request details and balance context.
  4. Click Approve.
  5. Confirm the request status changes to approved.

​
4. Reject the request

  1. Sign in as an approver resolved from the employee’s route.
  2. Open the approval request.
  3. Enter a Reject reason.
  4. Click Reject.
  5. Confirm the request status changes to rejected.

​
5. Check visibility

  1. Confirm the employee can see the final status.
  2. Confirm the manager or approver view reflects the decision.
  3. Check the wallchart for approved leave visibility.
  4. Check leave request reports for the submitted request and its status.

​
What employees see

Employees can see their submitted request, request status, selected leave type, dates, duration, reason, and leave balance context.

​
What managers see

Approvers can see requests assigned to them and make an approval decision. An employee’s route can use their department or team’s direct approvers, line manager, or selected custom approvers. No approver and self-approver routes are automatic.

​
What admins see

Admins can review requests, balances, reports, employees, departments, approvers, and setup records that affect the request.

​
Example test

An employee in the Engineering department submits one day of Annual Leave. The Engineering approver opens the request, checks the reason and balance, and clicks Approve. The employee sees the request as approved, the wallchart shows the leave, and the admin can find the request in reporting.

​
Troubleshooting

​
The employee cannot submit the request

Check the employee’s leave policy, active leave type, active leave policy rule, selected dates, overlapping requests, and available balance.

​
The request overlaps with another request

Choose different dates or cancel the existing request if it is no longer needed.

​
The approver cannot see the request

Check the employee’s current Leave approver route. Then confirm that its line manager, custom approvers, or exact department or team approvers are active and can sign in.

​
A backdated request is rejected

Teamper accepts a start date up to seven days before the company’s current date. A request starting earlier is rejected. A backdated request must also stay within the current leave balance period.

​
The reject button is disabled

Enter a Reject reason before clicking Reject.

​
The request is approved but not visible where expected

Check the request dates, wallchart filters, employee department, and report filters.

​
Frequently asked questions

​
Can submitted requests be edited?

No. Submitted leave requests cannot be edited. If the request is wrong, cancel it when cancellation is available and submit a new request.

​
What statuses should I expect?

The first workflow commonly uses pending, approved, and rejected. Cancelled requests may appear when a request is cancelled instead of reviewed.

​
Who should run the first test?

Use one test employee and a real approver from the route you want to validate. Test automatic approval separately if you plan to use No approver or a self-approver route.