Skip to main content

Handling Missed Shifts on Timesheets (No-Shows)

How you can handle no-call no-shows and other missed shifts in timesheet views

When staff miss shifts, it can be easy to get confused about what action you should take on their timesheet. The answer depends on what actually happened.

Did your staff no-show?

If your staff no-showed, there's nothing you're required to do from here. The shift won't be exported to payroll if there are no times set in the timesheet for it. The shift will also be deducted from the staff's attendance reporting.

If you'd like to specifically record them as absent, you can mark the shift as a no-show, which lets you easily track and report when the employee is not turning up to their shifts.

To get started, first navigate to Settings > All Settings > Timesheet Settings > No Shows and tick "Enable no shows".

Click Update Settings to save changes. You can then configure the no-show reasons on this page by clicking Manage Reasons:

You can then add to, delete or edit the existing reasons, which are used in the app or timesheet to mark a shift as a no-show.

Web

  1. After enabling no-shows, you'll see a new button in the timesheet letting you mark a shift as such:

  2. Click this button and then choose one of the no-show reasons configured in timesheet settings

  3. The shift will appear as follows:

    Remove the no-show by clicking the button on the right of the shift again

Reporting on no-shows

You can use the Shift Report and the Attendance Report to see an employee's no-shows.

Use the Shift Report to see individual shifts and their reasons by adding the No show and No show reason columns:

Use the Attendance Report to see total no-shows for a certain period by adding the No Show Shifts column:


Did your staff forget to clock in?

When staff miss shifts, you'll see that the shift still appears on the timesheet, with red boxes indicating what was missed.

If your staff did work, you can type in the boxes to manually enter their actual start and finish times.

Did this answer your question?