Skip to content
Language: EN

How are NFC badges used at an event?

As an identifier that a reader looks up, rather than as a store of information. The badge says who, and each system in the hall decides what that means: admitted, registered for this session, or a lead for this exhibitor.

The badge is an identifier

The useful design writes an opaque identifier, and everything about the person lives in the event system.

A reader at a door sees the identifier, asks the system who it is and whether they may enter, and acts on the answer.

That keeps personal data off an object worn in public all day, and it means a badge reassigned before the doors open costs nothing but a database change.

Writing names and contact details onto the badge itself is the alternative, and it is worse on privacy, on flexibility and on correction.

What it is used for

Entry, where a tap replaces a visual check and produces a count.

Session attendance, where readers at room doors record who was where, which is what sponsors and speakers ask about afterwards.

Lead capture, where an exhibitor taps a visitor's badge and receives their details from the event system rather than from the badge.

And access levels, where the same badge means different things at different doors because the system decides rather than the badge.

What it does not do

It does not let two attendees exchange details by touching badges. Both badges are passive, so neither can power or read the other.

It does not work without the system behind it. A badge alone is a number.

It does not identify anyone by itself, which is a privacy feature rather than a limitation.

And it does not survive being the only record. A badge is a token, and the event system is the truth.

What the whole thing depends on

The lookup. Every tap ends in a question to a system, and that system has to answer in a hall full of people with a connection that may be poor.

That is where event deployments fail: not at the tag, which is trivially reliable, but at the network between the reader and the answer.

So the two questions that decide a badge deployment are what happens when the connection drops, and what happens when a badge does not read.

Both have to be answered before the doors open, because both will happen on the day.

Frequently asked questions

Should the badge hold the attendee's name?

Usually not in the chip. An opaque identifier resolved by the event system is better for privacy and lets you correct records without reissuing badges.

Can badges track people around a venue?

Only where readers are placed, since a badge is passive and reports nothing on its own. What is recorded is a matter of where you put readers and what you tell attendees.

Do exhibitors need special equipment?

They need something that reads a badge and reaches the event system, which is usually a phone with an application or a supplied reader.

What happens if the network fails?

Everything stops unless the readers can work offline and reconcile later. That is the question to ask a supplier first.