Badges for the people who never registered

Every conference has two populations. Delegates, who registered and paid and are in the system. And everybody else — speakers, chairpersons, faculty, the organising committee, volunteers, the AV crew, invited guests.

The second group is usually managed in a spreadsheet, and their badges get printed separately on the morning, in a slightly different design, because they were never in the registration list.

This is backwards. They are the people delegates are trying to find.

Why they are not just "free tickets"

The obvious shortcut is to issue each of them a complimentary registration. It works for about a week, and then the numbers stop making sense:

• your bookings count now includes twelve people who never booked;
• your tickets sold includes them too;
• revenue per attendee is quietly wrong;
• and every report you export needs the same mental exclusion.

Worse, a comped booking in a paid tier tells your own dashboard you sold a ticket at that price. Six months later nobody remembers why the conference appears to have sold fifteen more delegate passes than it collected money for.

They are not bookings. They should not be stored as bookings.

What they actually need

Exactly two things, and they are the same two a delegate gets:

A badge, so they get through the door and so people can see who they are. It should carry their role where a delegate's carries their ticket type — Speaker, Chairperson, Volunteer, Organising Committee — because that is what everyone in the room is scanning for.

A certificate, afterwards, with wording that matches what they did.

Both should come off the same machinery as the delegates'. Not a similar template — the same one. If the speaker badges are visibly different from the delegate badges, they read as improvised, and at a medical conference that is the opposite of the impression you want on the people you invited.

They should scan at the door too

This is the part most events skip, and it is free once the badge exists.

Give each of them a code on their badge and record their arrival like anyone else's. Three reasons:

• your head count for the day is actually right, rather than being delegates plus a guess;
• a volunteer at the door does not have to know every speaker by sight;
• and if a speaker's certificate says they were there, you can show that they were.

The code needs to be distinguishable from a delegate's booking reference, so the door knows which list to check — but that is an implementation detail, not something anybody standing at the door should have to think about.

Removing somebody is not deleting them

People drop out. A speaker cancels, a volunteer does not turn up.

Do not delete the record. Their badge may already be printed, and their attendance rows have to keep pointing at something. Deactivate them instead: the badge stops scanning, they drop out of the print run, and the history stays intact.

Collect them early

The practical failure is timing, not tooling. The team list is always the last thing assembled, because it is the list that is "obvious" to whoever is organising — they know who the speakers are.

Ask for it at the same time you open registration, with the same fields you would ask a delegate for: name, designation, institution. You will need all three on the badge, and chasing a professor for their correct affiliation the night before the print run is a conversation worth avoiding.