Every attendee who has taken a spot on an upcoming, ongoing or past shift carries a status on their reservation. There are nine, and this article explains what each one means and how a reservation moves between them.

Upcoming shifts

1. Reserved. The attendee holds a spot on an upcoming shift. Admins are notified when somebody reserves.

The reservation is confirmed straight away only when the opportunity has Instant Book enabled. With Instant Book disabled, reserving produces Shift request pending instead (status 8).

2. Attendance confirmed. The attendee was asked to confirm within 48 hours of the shift start time, and confirmed that they are coming.

Ongoing or past shifts

3. Checked-in. The attendee reserved a shift and was checked in.

Checking in without checking out does not run up unlimited hours. The status stays Checked-in indefinitely with only the check-in timestamp recorded. Either the attendee claims their hours or an admin logs them, which moves the status to Hours logged. Admins are notified on check-in.

A reservation showing Checked-in can belong to a shift that is still running or one that has already finished.

Past shifts

4. Not logged. The attendee reserved a shift, the end time has passed, and they were never checked in. This status also stays put indefinitely until the attendee claims hours or an admin logs them.

5. Hours logged. Five routes lead here:

1. Reserved, then checked in and checked out (by QR code, on-site kiosk, or an admin).
2. Reserved, never checked in, then claimed hours retroactively from their profile and an admin approved the claim.
3. Reserved, never checked in, then an admin used Log hours from Schedule and the Actions menu.
4. Never reserved, then used the general Claim Hours feature retroactively and an admin approved the claim.
5. Never reserved, then an admin used Assign or log past shifts from Schedule and the Actions menu.

Attendees are notified once hours are logged.

6. Absent. Five routes lead here, and all of them end with an admin marking the person absent:

1. Reserved, checked in, then marked absent afterwards.
2. Reserved, never checked in, then marked absent.
3. Reserved, never checked in, an admin used Log hours, then marked them absent.
4. Never reserved, claimed hours retroactively and had the claim approved, then was marked absent.
5. Never reserved, an admin used Assign or log past shifts, then marked them absent.

Only admins can mark somebody absent, and the attendee is notified when it happens.

7. Hour claim pending. Somebody submitted an hour claim, either for a past shift they had reserved or for one generated through the general Claim Hours feature. Admins are notified of a new claim and can approve or decline it. Approving moves the status to Hours logged.

The two statuses that only exist without Instant Book

These last two appear only on opportunities with Instant Book disabled, because that is the only setting where a reservation becomes a request first.

8. Shift request pending. Somebody asked to reserve a shift and the request is waiting for an admin to approve or decline it. Admins are notified of a new request. A pending request does not consume a spot.

9. Shift request declined. Somebody asked to reserve a shift and an admin declined the request.

Summary

• Upcoming: Reserved, Attendance confirmed.
• Ongoing or past: Checked-in.
• Past: Not logged, Hours logged, Absent, Hour claim pending.
• Instant Book off only: Shift request pending, Shift request declined.
• Checked-in and Not logged both sit still until hours are claimed or logged. Neither accrues time on its own.
• Only an admin can mark somebody Absent.

Where to go next

• Instant Book, or request to book?
• How Do Declined Shift Requests Work on Vome?
• Hour claims: letting people log their own hours
• How should people check in?