> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/check-in-app-overview/scan-member.md).

# How to Scan a Member

### Before you begin (Prerequisites)

* **Device**: Check-In App by Peoplevine installed and logged in on an iPad.
* **Member**: The member has an active membership.
* **Scanner** (optional): A Bluetooth (BLE) QR code scanner can be paired with the iPad. It scans cards quickly even when the app is minimized. The iPad camera also works for scanning QR codes.

### Instructions

#### Check in via QR/barcode scan

1. Open the Check-In App on the iPad.
2. Tap the **scan icon** at the top of the left dock — the camera activates.
3. Point the camera at the member's membership card, event ticket, guest pass, or voucher QR code. If you are using a paired Bluetooth (BLE) QR code scanner, scan the code with the scanner instead.
4. When the system matches the code to an active record, the member is checked in and appears in the **Arrived** list.

> Backend validation prevents reused QR code screenshots from being checked in — the system verifies each QR code against the database in real time.

> **Scan alerts**: After a scan, the app shows a **toast message** for anything staff should notice — including **VIP**, **Birthday**, and **Anniversary** on a successful check-in, and the reason on a failed scan (e.g., pending card, or check-in not allowed). For the full list of failed-check-in messages by status, see [Member Statuses at Check-In](/products/check-in-app-overview/member-statuses-checkin.md).

5. If no match is found, try a manual lookup instead — see [How to Look Up a Member Manually](/products/check-in-app-overview/manual-lookup.md).

#### Open the check-in card

After a member is checked in, tap their card in the **Arrived** list to open the check-in card. From here you can:

* View the activities and reservations the member has booked for the day (dining reservations, events, and integrated bookings).
* Tap a specific reservation to review its details, such as the number of guests and the date.
* Add a staff note attached to a reservation. You can set a note as **open** or **closed** — an open note acts like a task ticket, visible to your staff as a to-do item.
* Tap the member's scan to open an Apple Wallet–style view showing the other cards the member holds, such as vouchers or guest passes.

To check in a guest, see [Guest Passes — Overview](/products/check-in-app-overview/guest-passes-overview.md).

### What Happens Next

* The member appears in the **Arrived** list, which can be filtered by date, location, or type (members, guests, all).
* Bookings from integrated platforms (Book4Time, SevenRooms, Opera OHIP) sync in real time and appear on the check-in card.

For a video walkthrough, see the [Check-In Scans guide](https://screeching-catfish.clueso.site/share/2f284de7-45b9-4732-9f76-bf1abf4b108e).

*Last updated: 2026-06-11*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/check-in-app-overview/scan-member.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
