Rejecting Shift Trade Requests
Reject a shift trade request and provide a reason for your decision!
Yasir Ehsan avatar
Written by Yasir Ehsan
Updated over a week ago

Objective

The objective of this tutorial is to show you how to reject shift trade request.

Overview

Access from your: Computer
Applies to: Managers, Supervisors, Schedulers, Employees

After you receive the notification of a shift trade, it will be your responsibility to reject shift trade request.

Things to know before you begin:

  1. Being a Manager/Supervisor, you will not receive email/SMS notification, if you have assigned a 'Scheduler' permission to that position from which employee is requesting shift trade.

  2. You all can view and manage shift trade requests by 'Managing Shift Trade' widget on the Dashboard Notification Panel as well as via email/SMS as per the defined settings under the settings module.

  3. Managers need to click on each individual request to see the details of each request.

  4. The Humanity conflict checker is also featured in the sidebar, letting managers know for which potential cover a conflict would be created if they were to assign the shift to that person. If no conflict is present, there will be a check mark next to that employee’s name.

Rejecting a Shift Trade Request

Step 1: Go to the 'Dashboard' Module, click 'Manage Shift Trades' widget from the dashboard widget panel as shown in Image 1.

Image 1

Step 2: Click 'Would like to trade this shift' to review it and decide if you want to accept or reject it as shown in Image 2.

Image 2

Step 3: Click 'Reject’ as shown in Image 3.

Image 3

 

Note: Check the box next to employee’s name to select a specific person for rejecting.

That's it, the request will be rejected and rejection will be sent to all employee(s).

Step 4: Click ‘Reject Request’ as shown in Image 4 to confirm the rejection of the shift trade by adding the reason for rejection.

Image 4

If you have any further queries, please don't hesitate to reach us at support@humanity.com. Happy Scheduling!
 

Did this answer your question?