What are the different attendee statuses? What do they mean?
Every attendee that is has taken up a spot to an upcoming, on-going or past shift has a status associated to their reservation.
Upcoming shifts
1) Booked: The attendee is booked/reserved for an upcoming shift.
Admins get notified when an attendees reserves a shift
The reservation would be auto-confirmed if the shift exists within an opportunity that has Instant Book enabled. If Instant Book is disabled, then once the user reserves the shift, the status would be Shift Request Pending (see status #8).
2) Attendance confirmed: The attendee was sent a notification to confirm their attendance within 48 hours of the shift start time and they confirmed that they're attending.
On-going / Past shifts
3) Checked-in: The attendee reserved a shift and was checked-in.
If the attendee checks-in but never checks-out, the Checked-in status will remains as such indefinitely with a check-in time stamp (i.e., 10:00 am). It is up to the attendee to claim hours or for the admin to log their hours to update the shift status to Hours logged. This also means that the attendee will not get "unlimited" hours! Admins get notified when attendees check-in!
If an attendee has the Checked-in status, the shift can be either on-going or in the past
Past shifts
4) Not logged: The attendee reserved a shift > The shift end time has passed > The attendee was never checked-in.
If the attendee reserved a shift and never checked-in, the Not logged status will remain as such indefinitely. It is up the attendee to claim hours or for the admin to log their hours to update the shift status to Hours logged.
5) Hours logged: There are 5 scenarios whereby an attendee could have this status.
Attendees will get notified when they've logged hours
- The attendee reserved a shift > They checked-in and checked-out (via the QR code, on-site kiosk or by an admin)
- The attendee reserved a shift > Never checked in > They claimed hours on the past reserved shift from their profile retroactively > The hour claim was approved by an admin.
- The attendee reserved a shift > Never checked-in > An admin used the Log hours action from the admin portal > Schedule > Actions dropdown
- The attendee never reserved a shift > They claimed hours by using the general Claim Hours feature from their profile retroactively > The hour claim was approved by an admin.
- The attendee never reserved a shift > An admin used the Assign/Log past shifts action from the admin portal > Schedule > Actions dropdown
6) Absent: There X scenarios whereby an attendee could have this status:
Only admins can mark attendees as absent. Attendees will get notified when they've been marked as absent.
- The attendee reserved a shift > They checked-in > Later, they were marked as absent for the shift by an admin
- The attendee reserved a shift > Never checked in > Later, they were marked as absent for the shift by an admin
- The attendee reserved a shift > Never checked-in > An admin used the Log hours action from the admin portal > Schedule > Actions dropdown > They were marked as absent by an admin
- The attendee never reserved a shift > They claimed hours by using the general Claim Hours feature from their profile retroactively > The hour claim was approved by an admin > Later, they were marked as absent by an admin
- The attendee never reserved a shift > An admin used the Assign/Log past shifts action from the admin portal > Schedule > Actions dropdown > Later, they were marked as absent for the shift by an admin
7) Hour claim pending: A Vome User submitted an hour claim for a past shift that they reserved or for a shift that they generated from the general Claim Hours feature.
Admins get notified when there's a new pending hour claim. Admins can approved or decline the hour claim. If approved, the shift status becomes Logged hours
8) Shift request pending: A Vome User requested to reserve a shift and the shift request was approved by an admin
Admins get notified when there's a new pending shift request
This is only applicable if the shift exists within an opportunity that has Instant Book disabled.
9) Shift request declined: A Vome User requested to reserve a shift and the shift request was declined by an admin
This is only applicable if the shift exists within an opportunity that has Instant Book disabled.
Related Articles
What are the different attendee statuses? When do notifications get sent?
Every attendee scheduled for a shift has an associated status related to their reservation at different points in time before, during and after a shift. Here is a breakdown of each status, when they can occur, and the affiliated notifications: ...What is the attendance confirmation feature? What does the green check mark mean when I see it on the attendee's profile picture?
Whenever a user is reserved for an upcoming shift, there's a notification that they receive (email and push) 48 hours prior to the shift start time asking them to confirm their attendance. If the user chooses to confirm their attendance, you will see ...How do Form statuses work?
Form statuses on Vome are visible to admins only. Volunteers cannot see their form status and will not be notified if the form status changes. You can update form statuses as an internal applicant tracking system for the admin team managing the ...How does the check-in/out portal work on Vome? How do I generate the QR code and/or the on-site kiosk?
In order for an attendee to be able to check-in and check-out of their shifts, they must be reserved for a shift on the current day when they're trying to check-in/out(i.e. on the attendees list for an upcoming shift). If you wish to manually to ...How do I mass log hours from the Schedule?
1. Go to the Schedule page 2. On the top right, click on Actions 3. Select Log hours for past attendees 4. If relevant, filter by date range, advanced filters by Attendees status (i.e. Not logged, Checked-in), opportunity or anything else. 5. Select ...