Event Check-in Without an App: One Link, One PIN, Any Phone

You can run event check-in without installing an app: open one link in a browser on any phone or tablet, enter the event's four digit PIN, and scan the QR code on a ticket or type its code. Staff need nothing from an app store, which matters when volunteers arrive at 7am with whatever phone they own.

Why Would a Conference or Exhibition Skip the Check-in App?

Because an app is a small project nobody scheduled. Someone has to tell fifteen volunteers to download it, someone's phone has no storage, someone forgot their store password, and someone else is still on a version from last year. The queue forms while you troubleshoot.

A browser has none of those problems. Every phone has one, nothing needs installing, and the person who turns up to staff the door can be checking people in within a minute of being handed a link. For a congress, a trade fair or an association conference with a rota of helpers who change every morning, that is the difference between a smooth door and a sticky note that says "ask Dave".

How Does Check-in with One Link and One PIN Work?

The organiser sends the check-in link to door staff. Staff open it on a phone or tablet, type the four digit PIN, and they are in. There are no staff accounts to create, no passwords to reset and nothing to revoke when the day ends.

From there a ticket is found two ways: scan the QR code on the ticket (or the attendee's phone), or type the code, including the nine digit ticket number printed on every ticket. The screen shows the attendee's name, email, phone, company, ticket and pass type, so staff can see at a glance whether this is a delegate, a visitor or a speaker. Repeat scans are flagged, and refunded or unpaid tickets are refused, as are test tickets on a published event.

What the door does not show is the long tail of registration answers, only company and the basics. That is deliberate: staff at the door need to know who someone is, not read a questionnaire. If your team needs something more at the door, tell us what it is on the contact page.

What Does a Busy Door Look Like with Browser Check-in?

Think in lanes. One phone per lane, each running the same link. A lane that is quiet can help the busy one, because any phone can pick up any ticket. Our guide on checking in a thousand attendees with phones works through the lane maths in more detail, including how many staff a 40 minute arrival peak really needs.

A few habits keep the line moving:

• Ask attendees to have their ticket or QR code open before they reach the front. A phone screen with the brightness turned up scans faster than one that has just dimmed.

• Give each lane staffer a second tab with the attendee's ticket number typed ready, for people whose QR code will not load.

• Put one person at the front of the queue who does nothing except tell people to open their tickets. It is the quickest speed-up in events and requires no software.

What About Badges?

The staffed phone scanner checks people in; it never prints. Badge printing at check-in runs through the Badge Kiosk: a laptop with a printer beside it, where visitors type their ticket number, check the details, and print their own badge. Printing checks them in. The staffed lane and the kiosk work side by side, so people who want a human go to the desk and people who want speed go to the kiosk.

Badge designs use live answers from your registration form, so the badge matches the attendee type without anyone retyping a thing. The check-in page and the badge printing page show the two halves together.

Can the Same Phones Check People into Sessions?

Session scanning is a separate job at a separate door. For a workshop, a CPD session or a keynote with a capacity, session scanning works per session: one scan admits or refuses, a re-entry is flagged, and every device at that door shows a running count of admissions against capacity. Organisers can afterwards see who attended each session and when they first came in, with a spreadsheet.

That is useful at a training day where you need to show who sat which session, and at a conference where a popular talk fills up and the volunteer at the door needs a number rather than a hunch. It also keeps the entrance check-in simple: the main door asks "are you registered?", and each session door asks "are you booked in?".

Who Should Hold the PIN?

One named person per shift, ideally the lead volunteer or the registration manager. The PIN is for the event rather than the person, so you can share it with a rota without creating accounts, and change who holds it from one morning to the next. Staff sessions last twelve hours, which covers a long show day, and the link is no use without the PIN, so a forwarded email is not an open door.

Keep the link and the PIN out of the same message if you can, and send both on the morning rather than a fortnight ahead. It is a small habit, and it means a rota change on day two does not leave an old message floating around.

How Does This Compare with Other Check-in Tools?

The table sets out what three competitors say about check-in on their own pricing pages, as read between 4 and 6 November 2026: Eventleaf, Eventcombo (page updated 22 October 2026) and Zoho Backstage. A pricing page does not describe every feature, so "not stated" means exactly that.

Coming soon: offline check-in. Need it for your event? Tell us about the venue and what its connection is like.

What Should You Set Up the Week Before?

Do a dress rehearsal. Create two or three test tickets, open the link on the phones your staff will really use, and scan them. Check that each phone can see the screen in the lighting of the entrance. Agree who holds the PIN, and write the link on the rota so nobody has to ask for it at 7am.

Then decide what happens to the queue when one lane jams: usually the answer is a second lane and a kiosk. Registration, badges and check-in are connected, and a plan that thinks about all three before the doors open is the one that survives the first hour.