Skip to main content

Deleting shifts from the roster

How to delete shifts from the HosPortal roster using three different methods.

Written by Shiela Fajardo
Updated this week

Feature summary

HosPortal provides three methods for deleting roster shifts: delete an entire row of shifts, delete specific shifts using multi-select, or delete a single shift.

When to use this

Delete an entire row or column — remove all shifts for a specific role within the currently displayed date range (e.g., an entire week for the Cardiac call)

Multi-select delete — remove multiple specific shifts across different roles or non-consecutive days

Delete a single shift — remove one specific shift

Step-by-step instructions

Method 1: Delete an entire row of shifts

1. Click the Edit button at the top right of the screen.

2. Hover over the role name in the far-left column (e.g., 1st Call, Cardiac call). Click the three-dot menu icon that appears.

3. Select Delete from the menu.

4. A confirmation pop-up will appear. Type delete into the input field, then click the Delete button to confirm.

Note: This method removes all shifts in that row for the currently displayed date range only. This can also be applied to remove all shifts in a column.

Method 2: Delete specific shifts using multi-select

1. Click the Edit button.

2. Click the Actions button in the top-right corner and select Multi-select from the dropdown menu.

3. Click each shift you wish to delete. Selected shifts are highlighted with a blue border.

4. Click the Bulk edit (X) button that appears at the top of the screen, where X is the number of selected shifts.

5. Select Delete from the dropdown menu.

6. A confirmation pop-up will appear. Type delete into the input field, then click the Delete button to confirm.

Method 3: Delete a single shift

1. Click on the shift.

2. In the Edit shift pop-up box, click the Delete button.

Confirmation

After completing any method, a Shifts deleted confirmation message briefly appears at the top of the screen and the roster updates.

Did this answer your question?