> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/managing-events/checking-in-host-registrants.md).

# Checking in Host registrants

If you're running a Host-registered event, **your registrants are already in Mobly** — they synced over when each guest filled out the form. Check-in at the door is a single swipe in the Mobly app, with no CSV upload required.

This article covers the Host event path. For events without Host registration (where you upload your own attendee list), see [How to check in leads](/help-center/the-hub/managing-events/how-to-check-in-leads.md).

## Before the event

Nothing to do. If your event uses Host for registration:

* Registrants flowed into Mobly automatically when they filled out the form (see [How registrants flow from Host into Mobly](/help-center/host/how-registrants-flow-into-mobly.md))
* Each lead is already attached to the event with **Registered** status
* The Mobly app shows them in the event's lead list, ready for check-in

**No CSV upload step.** If the existing check-in article tells you to upload a CSV first, that's the non-Host path — skip it.

## At the event — checking guests in

1. Open the **Mobly mobile app** and select the event (the event banner at the top of every screen tells you which event you're working in)
2. Tap into the event's **Leads** tab
3. When a guest arrives, find their name in the list (search is fastest for big rosters)
4. **Swipe right** on their row to check them in

That's it. The lead's status updates to **Checked In** in Mobly, and the Host side updates automatically — so the guest count in Host's analytics matches what you're seeing on the floor.

## Undoing an accidental check-in

If you check someone in by mistake:

* Find them in the lead list
* **Swipe left** on their row
* They go back to **Registered** status

The Host side reverts to match. Same instant sync.

## Walk-ins (guests who didn't pre-register)

If someone shows up who isn't on the registration list:

* Use the standard mobile-app lead capture — **Scan**, **Manual**, or **Upload** — to add them
* They land as a new lead in the event with **Scanned** status (different from Registered)
* They're not added back to Host's registration list — Host is for pre-registered guests; walk-ins live on the Mobly side only

For events where you expect a lot of walk-ins (and want to track which guests pre-registered vs. walked up), the Registered vs. Scanned status distinction in the lead table is your friend.

## The "no email" edge case

If a Mobly lead lacks an email address, Mobly **won't push that lead's check-in status back to Host** — there's no error shown to you, but the lead won't appear in Host's attendance data.

This rarely matters in practice (Host registrants almost always have an email since the form usually requires one), but it can come up for walk-ins or manually-added leads. The lead is checked in on the Mobly side; just not reflected in Host.

## Real-time reporting

While the event is running, both surfaces stay in sync:

* **Mobly** — the Hub's event detail page shows live check-in counts, lead-by-lead status, capture funnel
* **Host** — the event's registration dashboard shows registered vs. attended counts

If you're running a hybrid setup where Marketing watches Host's funnel and on-site staff use Mobly to check people in, both teams see the same numbers without doing anything special.

## Related articles

* [How to check in leads](/help-center/the-hub/managing-events/how-to-check-in-leads.md) — for events that don't use Host registration (CSV upload path)
* [How registrants flow from Host into Mobly](/help-center/host/how-registrants-flow-into-mobly.md)
* [How to capture a lead](/help-center/the-mobly-app/capture-and-enrichment/how-to-capture-a-lead.md) — for walk-ins at a Host event
* [How to prep for your upcoming event](/help-center/the-hub/managing-events/how-to-prep-for-an-event.md)


---

# 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.getmobly.com/help-center/the-hub/managing-events/checking-in-host-registrants.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.