A check-in audit trail: who let whom in, on which phone, and whether it was offline.
Every WebMobi event has a History screen. Its Check-ins tab lists every scan and every by-name check-in — web and app, online and offline, repeats included — with the staff member, the device, the session and the time it happened at the desk. Nothing in it can be edited or deleted.
Staff member and device on each check-in · offline check-ins labelled, with their desk time · repeat scans kept, not counted
What it is
The check-in audit trail is the Check-ins tab of an event’s History in WebMobi. It answers the questions a count cannot: who was let in, by which member of staff, on which phone, into which session, at what time — and whether that phone had a signal when it happened. Walk-ins appear with who added them. Every physical scan is a row, including the repeats that did not change a count.
It is for the people accountable for the door: a security or venue lead who must show who entered, an organiser settling a dispute about a session, a compliance officer who needs to see that staff used their own accounts. It also covers the second half of History — who changed the event itself — and is plain about what History does not record.
WebMobi Event App Builder · Build and launch your event app yourself.
WebMobi Event App Builder is a self-service event app builder that helps conference organizers, associations, agencies and event teams create and launch branded event apps — with registration, check-in (including offline check-in and walk-ins), session attendance, agenda, speakers and exhibitors in one platform.
Opening History
There are three ways in, all to the same read-only screen in a web browser:
- From the event page, choose the History tile. It opens on Content changes.
- From the Event Check-In page, open the menu at the top right and choose Check-in history. It opens on Check-ins.
- From the Enterprise Check-in Console, choose Check-in history.
History is visible to the event creator, organization owners and admins, and teammates with the Edit event permission. Anyone else is told the event was not found, so History does not even reveal that an event exists.
The Check-ins tab: one row for every scan
A line above the list gives the total — N scans recorded, including repeats. Rows are newest first, 100 at a time, each with two lines:
| On the row | Meaning |
|---|---|
| Name and email | The attendee. A Walk-in label means they were registered at the door. |
| The time on the right | When the check-in happened at the desk — for an offline check-in, the arrival time, not the time the phone reconnected. |
| Offline, with Synced | Made in the app with no connection; Synced is when it reached WebMobi. |
| Session title or Whole event | Where the check-in counts. |
| QR scan or By name | How the person was found: their badge, or a search by name or email. |
| By … | The staff member signed in on the device. |
| Device … | The phone that made the check-in, when one was recorded. |
What each outcome means
| Label | Meaning |
|---|---|
| Checked in | Recorded an arrival. |
| Checked out | Recorded a departure, from a door scanning In / Out or Out only. |
| Already inside (not counted again) | A repeat scan of someone already checked in. Kept as evidence, not counted. |
| Already outside (no change) | A check-out scan of someone who was not inside. |
| Checked out (no check-in recorded) | A check-out with no arrival before it — usually a door in the wrong mode. |
| Checked in (synced late) | An arrival that reached WebMobi after the departure it belongs to, completing the visit. |
Offline check-ins, proven
When a phone checks people in with no signal, the check-ins wait on that phone and are sent when it reconnects. History is where you prove they arrived: each one is labelled Offline, shows the time it happened at the desk and the time it synced. A row is labelled Offline when the app marked it as made offline, or when it reached WebMobi more than a minute after the desk time.
Before the doors open, the event’s Check-In page shows the other half of the picture: an Active Devices card listing each device that scanned for the event, when its check-ins last reached WebMobi in the event’s time zone, and how many of its scans arrived more than two minutes late in the last day. A device that hasn’t synced may still hold scans — so the end-of-day routine is every phone at zero pending, then the Offline rows in History. How offline check-in works.
Walk-ins: who added them, and whether desks joined up
When an event has walk-ins, a Walk-ins added list appears above the check-ins: each person registered at the door, their email, when they were added and by which staff member. It is also the check that walk-ins added on several phones joined up — the same person added on two phones with the same email appears once here, with each phone’s check-ins listed against them. Two rows for one person means two different emails were typed. Walk-in registration.
The other tab: who changed the event
Content changes lists changes to the event, its sessions, speakers, sponsors, exhibitors, ticket types, registrations, branding and team — grouped by day, newest first, each entry one sentence naming who made it. Select an entry to see every field before and after. Removals are marked with a red edge and a “N removed” label, and the entry keeps the whole record as it was.
- Filter by person, by source (Web, AI, Import, API, System), by what changed, by kind of change (Added, Edited, Removed, Published, Unpublished, Imported) and by date.
- Typical uses: Any change → Removed to find what disappeared from the agenda; Anything → Sessions with a date to see what moved that day.
- Edits to the event’s details on the web, and changes made through AI, name the person. Most other dashboard changes — session, speaker, sponsor and exhibitor edits, spreadsheet imports, registrations — show “The system”: the change and its before and after are recorded, but not who made it.
Answering the usual questions
| The question | Where to look |
|---|---|
| Who let this person in, and when? | Check-ins. Find the name; read the time, By and the device. |
| Were these check-ins taken with no signal? | Look for Offline and the Synced time on the row. |
| Why is this attendee counted once when scanned three times? | The later scans read Already inside (not counted again). |
| Did this person really attend the workshop? | Rows with that session title and Checked in. For a full per-session list, use the attendance report. |
| Who changed the start time of this session? | Content changes → Anything → Sessions → Edited; select the entry for the old and new time. |
What History does not record
An audit trail is only useful if you know its edges. These are WebMobi’s, as the product guide states them:
- Staff members are recorded on check-ins from 17 September 2026. Earlier check-ins show “Not recorded”, and the line at the top of the tab says how many.
- Online check-ins made by name or as a walk-in record no device yet. Check-ins on the web show no device.
- Most dashboard changes, spreadsheet imports and registrations are not yet attributed to a person; they say “The system”.
- History cannot undo, edit or delete anything — so a wrong check-in cannot be removed from the record either.
- History is read on screen. It cannot be exported or downloaded, and it is not in the mobile app.
For a second line of evidence, give every staff member their own account through the event’s Team page: a shared login makes History name one account for every check-in. Setting up staff on the check-in app.
What it does not do
Written down here so you find out now, not on event day.
No staff member before 17 September 2026
Check-ins made before then show “Not recorded” in place of the staff member.
Some check-ins have no device
Online check-ins made by name or as a walk-in, and every check-in made on the web, record no device.
Cannot be exported
History is viewed on screen only; there is no download of the audit trail.
Cannot be corrected
Nothing in History can be edited, undone or deleted. Rehearse on a separate practice event so test scans never enter the real record.
“The system” instead of a name for many content changes
The before and after are recorded; who made a dashboard edit, an import or a registration change is not yet.
Mixed time zones
The Check-ins tab uses the time zone of the computer you view it on; content changes are shown in UTC without a label.
Walk-ins list capped
Walk-ins added shows the 500 most recent walk-ins.
Web only, managers only
There is no History screen in the mobile app, and people without management access to the event cannot see it.
Read the step-by-step guides
The screens, labels and checks for each step are in the product guide on events.webmobi.com.
Event History and check-in audit trail
Who changed the event and who checked in whom — staff member, device, offline or not, repeat scans.
Check-in on multiple phones: what syncs and what doesn’t
What each phone keeps, what meets on the server, and laying out desks with no signal.
Event-day dry run: prove your team is ready
Rehearse check-in on a practice event, including a two-phone no-signal drill.
Admin access, walk-ins, Check-in Console, dates and event URL
Who can run the desk, adding a walk-in on the web, and the History check-in audit.
What each plan includes is on the pricing page.
FAQ
How do I find out who checked a particular person in?
Open the event, choose History, then the Check-ins tab. Each row shows the attendee, the time at the desk, the session or Whole event, QR scan or by name, the staff member after “By”, and the device when one was recorded.
How can I tell whether a check-in was made offline?
Offline check-ins carry an Offline label and a Synced time. The time on the right of the row is when the check-in happened at the desk, not when the phone reconnected.
Can a History entry be edited or deleted?
No. The History screen has no edit, undo or delete control, for check-ins or for content changes. It only shows what was recorded.
Someone was scanned twice. Were they counted twice?
No. The second scan is listed as “Already inside (not counted again)”. History keeps every physical scan, including repeats, but attendance counts the person once.
Why does a check-in say “Not recorded” instead of a staff member?
Staff members have been recorded on check-ins since 17 September 2026. Earlier check-ins show “Not recorded”, and the line at the top of the tab says how many there are.
Who can open an event’s History?
The event creator, owners and admins of your organization, and teammates who accepted an invitation to the event with the Edit event permission. Anyone else is told the event was not found.
Can I export the History?
No. History is read on screen only. Attendance files come from the Analytics and Check-In pages.
Which time zone does History use?
The Check-ins tab shows times in the time zone of the computer you view it on; content changes are shown in UTC.
Know who let whom in — and be able to show it.
Create your event, give each staff member their own account, and read the record in History after every session.