> 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/control-panel-overview/events-engine-overview/check-in-attendees.md).

# How to Check In Event Attendees

There are two live paths to check an attendee in: the **Control Panel guest list** (manual click) and **QR ticket scanning** (with an iPad running the Check-In App, or a compatible Bluetooth scanner connected to the iPad). Both write to the same record so the dashboard counts stay in sync regardless of which method the door team uses.

> **Note**: You cannot scan QR tickets with an iPhone. The Check-In App requires an iPad or a connected Bluetooth scanning device. NFC tap is not supported for event tickets — QR scan only.

### Before you begin (Prerequisites)

* **Event Setup**: The event must exist and have registrations or ticket sales. See: [How to Set Up an Event](/products/control-panel-overview/events-engine-overview/create-event.md).
* **For QR scanning**: an iPad running the Peoplevine Check-In App, or a Bluetooth scanner paired with the iPad. See: [Check-In App — Overview](/products/check-in-app-overview.md).

### Method A — Manual check-in from the Control Panel

Best when the front desk has a laptop and the iPad isn't in play.

1. Navigate to [**SELL > Manage Events**](https://control.peoplevine.com/events).

> **Note (Pro Dash):** Navigate to **SELL > EVENTS > Manage Events**.

2. Click on the event to open its dashboard.
3. Click **ATTENDEE LIST** to open the guest list.
4. Search for the attendee by name, or filter by **Ticket Type**.
5. Click **CHECK IN** next to their name.
6. An **already used** tag replaces the Check-In and Cancel buttons. On the main event detail page, the status shows as "checked in".

For the full guest-list reference (filters, search, register-from-CP, export), see: [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.md).

### Method B — QR scanning at the door

Use this when attendees present their digital ticket on a phone or as a printed QR.

Scan with the **Peoplevine Check-In App** on iPad (camera or paired Bluetooth scanner). See: [Check-In App — Overview](/products/check-in-app-overview.md).

| Scan                      | Result                                                                                                                |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **First scan**            | *Valid ticket* — the attendee is checked in (records `scan_date`, status → *Checked In*).                             |
| **Second scan**           | Records a second timestamp, exported as `scan_out`. Guests aren't typically scanned out, but a repeat scan logs this. |
| **Third (or later) scan** | *Already redeemed* — no further action; the system prevents double check-in.                                          |

> **Note**: The Check-In App scans event **tickets** at the door. Browsing the event RSVP list and tapping a member to check in is **not** available from the app — use Method A (Control Panel guest list) for click-style check-in, or Method B for QR scans.

### Live event dashboard

While you're checking attendees in, keep the event dashboard open in another tab or on a monitor at the door. It shows:

* **Total Revenue** — live tally of ticket sales (or RSVPs).
* **Awaiting** — number of registered attendees who have not yet checked in.
* **Checked-In** — number of attendees who have arrived.

Use these counts as a real-time indicator of arrival pace and capacity utilisation.

### Best Practice

* **Decide your method per event.** A small RSVP-only social can run entirely on Method A (search and click). A 200-person ticketed event runs faster with Method B (QR scan + iPad).
* **Use a Bluetooth scanner for high-traffic events** — faster than the iPad camera at the door.
* **Train staff on the scan sequence.** After check-in, a repeat scan logs a second timestamp and any further scan returns *Already redeemed* — explain this to staff so they don't mistake it for a broken ticket.
* **Watch for shared tickets.** When a member shared the ticket, the **guest's name** is on the entry with the member listed underneath.
* **For RSVP-only events with no QR**, train staff on Method A (manual click) and decide ahead of time whether you'll honour walk-ins from non-registered members.

### What Happens Next

* **On the member side**: The check-in is recorded on their CRM profile. Post-event campaigns triggered by *checked-in* status (if configured) add the member to the send queue. See: [How to Set Up Event Emails](/products/control-panel-overview/events-engine-overview/setup-event-emails.md).
* **On the admin side**: Awaiting decreases by 1, Checked-In increases by 1. Export at any point shows scan\_date (and scan\_out if a ticket was scanned a second time).
* **Next step**: [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.md) · [How to Set Up Event Emails](/products/control-panel-overview/events-engine-overview/setup-event-emails.md).

*Last updated: 2026-06-12*


---

# 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/control-panel-overview/events-engine-overview/check-in-attendees.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.