How to Handle Walk-Ins, Attendee Corrections and Badge Reprints Onsite

TL;DR

• Walk-ins should be registered in the event registration platform and synchronized with the onsite check-in system.
• Once the new record reaches the kiosk, the attendee can check in and print their badge normally.
• Attendees should be able to review and correct permitted details at the kiosk before printing.
• Simple badge reprints can also be completed at the kiosk using the existing attendee record.
• Changes involving payment, identity, registration type or access permissions may require staff approval.
• Keep standard check-in and simple exception handling self-service wherever possible.
• Use an assisted escalation point for issues that cannot be resolved at the kiosk.
• Offline mode can support records already loaded onto the device, but new walk-in data may still require connectivity to reach the registration platform.
• Track walk-ins, corrections and reprints so the next event can be staffed and stocked more accurately.

The standard attendee journey is straightforward: find the registration record, check in and print the badge.

Real events are rarely that tidy.

Someone arrives without registering. Another attendee notices that their company name is outdated. A badge is lost between the hotel and the venue. A speaker has changed roles, or an exhibitor needs a replacement credential.

These situations do not have to become registration-desk emergencies. With the right onsite event registration workflow, most walk-ins, corrections and badge reprints can be handled through the kiosk without sending attendees through a separate manual process.

The goal is not to eliminate exceptions. It is to make them ordinary.

How should onsite teams handle check-in exceptions?

A reliable process has three levels:

1. Self-service resolution: The attendee completes the correction or reprint directly at the kiosk.
2. Assisted resolution: A staff member helps with a lookup, missing record or permitted change.
3. Authorized escalation: Changes involving payment, identity or access permissions are reviewed by an authorized team member.

Most attendees should remain inside the standard kiosk flow. Only exceptions requiring a business or security decision should move to an escalation point.

This prevents a minor spelling correction from receiving the same treatment as a ticket upgrade or access-level change.

Read more: How to prepare your onsite team for registration day

Why walk-ins, corrections and reprints create queues

Exceptions become bottlenecks when the check-in system and registration platform operate separately.

Common problems include:

• Walk-in details being written on paper
• Staff manually creating badges
• Corrected information not reaching the badge printer
• Attendees being sent between different desks
• Reprints requiring a new record
• Registration changes failing to update access permissions
• Staff being unsure which changes they can approve
• Every issue being escalated to the same person
• Preprinted badges making last-minute corrections difficult
• Connectivity problems delaying synchronization

The delay is rarely caused by the correction itself. It is caused by the number of disconnected steps needed to complete it.

A better workflow keeps attendee information, check-in status, badge printing and access permissions connected.

Exception-handling workflow at a glance

The exact workflow depends on the event’s registration platform, permissions and security requirements. The principle remains consistent: solve the issue as close to the kiosk as possible.

How to handle walk-in attendees

A walk-in is someone who arrives without an active registration record available to the onsite check-in system.

The cleanest workflow is:

1. Collect the required registration information.
2. Add the attendee to the event registration platform.
3. Apply the correct ticket, attendee category and payment status.
4. Synchronize the new record with the onsite check-in system.
5. Make the attendee available at the kiosk.
6. Let the attendee review their permitted details.
7. Complete check-in.
8. Print the correct badge.

Once the attendee record is available, the rest of the journey should look like a normal check-in.

Keep the registration platform as the source of truth

Avoid creating a temporary badge record that exists only inside the printing system.

If the attendee is added directly to the event’s registration platform, their information remains available for:

• Attendance reporting
• Confirmation communications
• Payment records
• Membership information
• CRM or marketing automation workflows
• Session registration
• Access control
• Post-event reporting

The onsite check-in system should consume the new attendee record rather than creating an isolated version that must be reconciled later.

Learn more about connecting registration platforms with onsite event systems.

What information should a walk-in provide?

Collect only the information needed for registration and the event’s agreed workflows.

This may include:

• Full name
• Company
• Job title
• Email address
• Ticket or attendee category
• Payment status
• Dietary or accessibility information where required
• Session choices
• Consent or communication preferences
• Access permissions

Do not turn the walk-in process into an unnecessarily long form. Required fields should be clearly separated from optional information.

What if the walk-in needs to pay?

Payment should be completed through the approved registration or payment workflow before the attendee is issued a paid credential.

The kiosk can support the check-in and printing stage once the registration record reflects the appropriate status.

Staff should know:

• Who can approve complimentary access
• Which payment methods are accepted
• Whether invoicing is permitted
• How payment status reaches the kiosk
• What happens if synchronization is delayed

These are business rules, not printing decisions, so they should be agreed before the event.

How to keep walk-ins from blocking the main line

Walk-ins usually take longer than pre-registered check-ins because new information must be collected.

That does not mean every walk-in requires a completely separate registration desk.

Use a simple routing model:

• Standard attendees proceed directly to available kiosks.
• Walk-ins begin the registration process through the approved onsite form or with staff assistance.
• Once their record is synchronized, they use the kiosk to check in and print.
• Only payment, identity or approval issues remain with staff.

Clear signage matters. Attendees should know whether they need to register first or can proceed directly to a kiosk.

During anticipated walk-in periods, position a team member near the entrance to identify unregistered attendees before they join the standard check-in flow.

Read more: How to reduce attendee queue time at event check-in

How to handle attendee corrections at the kiosk

Attendees should be able to review permitted information before their badge prints.

Common corrections include:

• Name spelling
• Company name
• Job title
• Preferred name
• Badge display name
• Missing information
• Minor formatting issues

A simple correction flow is:

1. The attendee scans their QR code or uses name lookup.
2. The kiosk displays the permitted attendee details.
3. The attendee selects the field that needs correction.
4. The updated information is confirmed.
5. The badge is produced using the corrected record.
6. The change synchronizes with the connected registration platform where supported.

This removes the need to print an incorrect badge first and then create a replacement.

Not every field should be editable

Separate display corrections from controlled registration changes.

The kiosk should make ordinary corrections easy without allowing attendees to grant themselves access or change commercial registration details.

Protect the original record

For events with stronger audit or security requirements, record:

• Which field changed
• The previous value
• The new value
• When the change occurred
• Whether the attendee or a staff member made the change
• Whether approval was required

This provides a clear history without slowing every routine correction.

How to handle badge reprints

Lost, damaged and incorrect badges are unavoidable.

A controlled badge-reprint workflow should be quick enough for the attendee and traceable enough for the organizer.

The basic process is:

1. Locate the attendee using QR scanning or name lookup.
2. Confirm that the correct attendee record has been selected.
3. Review the badge information.
4. Correct any permitted errors.
5. Select the appropriate reprint reason.
6. Produce the replacement badge at the kiosk.
7. Record the reprint against the attendee.
8. Apply any credential-security action required by the event.

Simple reprints should not require the attendee to complete a new registration.

Useful reprint reasons

Track why badges are being reproduced:

• Lost badge
• Damaged badge
• Printing error
• Attendee-information correction
• Access change
• Role or category change
• Badge not collected
• QR code not scanning
• Staff test

These reasons help identify whether the event has a process, material or training problem.

For example:

• Frequent printing errors may indicate a badge-template or hardware issue.
• Large numbers of name corrections may indicate poor registration-data quality.
• Repeated damaged badges may suggest the selected material is unsuitable.
• Unusual reprint activity may require a security review.

Explore on-demand event badge printing for walk-ins, updates and replacement badges.

What happens to the original badge?

The answer depends on how the badge is used.

For a basic networking event, a replacement may simply reproduce the attendee’s original information.

For events using badges for access control, lead retrieval or session scanning, the organizer may need a stronger process.

Consider whether the workflow should:

• Preserve the attendee’s existing permissions
• Generate a new credential identifier
• Invalidate the previous QR code
• Record the old and new badge identifiers
• Require identity confirmation before reprinting
• Alert security after repeated reprint requests
• Limit who can issue replacement credentials

The replacement badge should reflect the attendee’s current authorized status. Staff should not manually recreate access labels from memory.

Should badge reprints happen at a separate desk?

Not necessarily.

When a reprint uses an existing attendee record and requires no approval, it can usually happen directly at the kiosk.

A separate assisted point is useful when the issue involves:

• Disputed identity
• Payment
• Access permissions
• Ticket upgrades
• Duplicate registrations
• Suspicious reprint activity
• Missing registration records
• A registration-platform error
• An approval that the attendee cannot provide

The goal is not to send every exception elsewhere. The goal is to stop unresolved cases from occupying a standard kiosk while staff investigate.

How to prepare the check-in area

A practical check-in layout may include:

Self-service kiosk area

For:

• Standard QR check-ins
• Manual name lookup
• Permitted corrections
• Simple badge reprints

Walk-in registration point

For:

• Creating new registration records
• Completing payment
• Capturing required consent
• Applying the correct registration category

Once completed, the attendee proceeds to the kiosk.

Escalation point

For:

• Identity disputes
• Access-level changes
• Payment problems
• Duplicate records
• Registration-platform issues
• Security review

The escalation point does not need to dominate the check-in area. It needs to be clearly marked, staffed by someone with the right permissions and positioned so that unresolved cases do not block the primary flow.

What happens when the internet connection drops?

Offline mode can keep many check-in and badge-printing workflows moving during a temporary connectivity problem.

When the relevant attendee data has already been downloaded onto the kiosk, teams may continue to:

• Scan QR codes
• Use attendee lookup
• Check attendees in
• Review available attendee details
• Print badges
• Reprint existing badges
• Record onsite activity for later synchronization

When connectivity returns, the locally recorded activity synchronizes with the connected platform.

The limitation for new walk-ins

A completely new walk-in record may still need to be added to the event registration platform before it becomes available at the kiosk.

If connectivity is unavailable, the registration platform may not be able to send the new record to the onsite system immediately.

Plan a fallback for this situation. Depending on the event setup, that may involve:

• Restoring connectivity through a backup network
• Holding the new registration until synchronization becomes available
• Using an approved temporary registration process
• Issuing a controlled temporary credential
• Reconciling the record once systems reconnect

Do not present offline mode as a substitute for pre-event data preparation or reliable onsite connectivity. It is a fallback that keeps already prepared workflows operating during disruption.

Read more: How offline event check-in and badge printing work

Train staff for decisions, not button presses

Kiosks should handle the routine steps. Staff training should focus on the decisions that technology cannot make independently.

Every onsite team member should know:

• Which fields attendees may edit
• Which changes require approval
• Who approves registration upgrades
• How walk-ins are added
• How long synchronization normally takes
• When a badge can be reprinted
• Whether identity must be verified
• How old credentials are handled
• What to do during a connectivity problem
• Who handles technical escalation

Run rehearsals using real scenarios:

• A walk-in who needs to pay
• A delegate with a spelling error
• A VIP whose company has changed
• An attendee without a QR code
• A lost badge
• A duplicate registration
• A speaker incorrectly registered as a general attendee
• A walk-in during an internet disruption
• A reprint request for a secure access badge

A team that has rehearsed these situations will resolve them calmly and consistently.

What should you measure?

Track exception activity alongside normal check-in performance.

Useful metrics include:

• Number of walk-ins
• Average walk-in processing time
• Corrections completed
• Most frequently corrected fields
• Total badge reprints
• Reprints by reason
• Reprints by attendee category
• Duplicate records
• Registration sync delays
• Exceptions requiring staff approval
• Peak exception periods
• Stock used for reprints
• Check-in time for standard versus exception cases

These figures help improve:

• Registration-form design
• Data-cleanup processes
• Staffing
• Kiosk placement
• Badge-stock quantities
• Attendee communications
• Access-control procedures
• Future integration testing

A high correction rate is not simply an onsite problem. It may indicate that registration data was incomplete or outdated before the event.

How fielddrive handles onsite exceptions

fielddrive’s event check-in solution connects attendee lookup, check-in and on-demand badge printing in one onsite workflow.

Attendees can use the kiosk to:

• Scan their QR code
• Look up their registration by name
• Review permitted attendee details
• Correct information before printing
• Check in
• Print or reprint their badge

Walk-ins are handled by adding the attendee to the connected event registration platform. Once the record synchronizes with fielddrive, the attendee becomes available at the kiosk and can complete check-in without unnecessary delay.

Badge reprints can also take place at the kiosk using the attendee’s existing record. This helps preserve the correct badge template, attendee category and configured access information.

For smaller events expecting up to 500 attendees, fielddrive Easy Badging combines compact kiosks, QR or name-lookup check-in, attendee-detail corrections, walk-in support and onsite sticker printing.

Onsite exception checklist

Before the event:

• Define which attendee fields can be edited.
• Define which changes require approval.
• Assign ownership for walk-in registration.
• Confirm the payment workflow.
• Test registration synchronization.
• Test every badge category.
• Test corrections before printing.
• Test reprints.
• Confirm credential-invalidation requirements.
• Load attendee data for offline fallback.
• Prepare a backup connectivity option.
• Train staff using realistic exception scenarios.
• Set up clear signage.
• Confirm the escalation contacts.

During the event:

• Keep self-service kiosks available for routine exceptions.
• Identify walk-ins before they enter the standard flow.
• Monitor registration synchronization.
• Track correction and reprint reasons.
• Keep replacement badge stock nearby.
• Move unresolved approval cases to the escalation point.
• Confirm that offline devices synchronize after reconnection.

After the event:

• Review walk-in totals.
• Review correction patterns.
• Investigate unusual reprint activity.
• Reconcile any temporary registrations.
• Confirm that every device synchronized.
• Compare exception-processing times.
• Update registration forms and staff training for the next event.

Frequently asked questions

Can walk-in attendees register and print a badge onsite?

Yes. The attendee is added to the event registration platform, and the new record synchronizes with the onsite check-in system. Once available at the kiosk, the attendee can check in and print their badge.

Can attendees correct their details at the kiosk?

Yes. Attendees can review and correct permitted information before printing. Fields connected to payment, registration type, identity or access may require staff approval.

Can an attendee reprint a badge at the kiosk?

Yes. The attendee’s existing record can be located, reviewed and used to produce a replacement badge. The organizer may apply additional verification for secure credentials.

Does a reprint create a new attendee record?

It should not. A badge reprint should remain connected to the attendee’s existing registration record.

What happens to access permissions after a reprint?

The replacement badge should use the attendee’s current authorized category and permissions. High-security events may also invalidate the original credential or issue a new identifier.

Can walk-ins be processed while the system is offline?

Records already loaded onto the kiosk can continue through offline workflows. A completely new walk-in may require connectivity so the registration platform can create and synchronize the attendee record.

Should walk-ins use a separate check-in desk?

Not always. The new registration may be completed through an onsite form or with staff assistance. Once the record synchronizes, the attendee can use the same kiosk flow as other attendees.

How can organizers reduce badge corrections?

Use clear registration fields, allow attendees to review their information before the event, test field mapping and let attendees confirm permitted details at the kiosk before printing.

How much extra badge stock should be prepared for reprints?

The amount depends on attendance, event length, badge material and previous reprint rates. Review historical reprint data and add a suitable contingency buffer.

How should duplicate attendee records be handled?

Review the records before printing, identify the correct registration and merge or deactivate the duplicate according to the registration platform’s process. Avoid issuing two active credentials unless the event specifically requires it.

Make exceptions part of the normal check-in flow

Walk-ins, corrections and badge reprints are not signs that the event has gone wrong. They are normal parts of onsite operations.

Problems begin when the technology, staff and registration platform treat every exception as something unexpected.

Let attendees resolve simple issues at the kiosk. Keep walk-in data connected to the registration platform. Escalate only the changes that require a commercial, identity or access decision.

When those workflows are designed and tested in advance, attendees receive the right badge without being sent from one desk to another, and the main check-in flow keeps moving.

To see how fielddrive handles attendee check-in, walk-ins, corrections and onsite badge printing, request a fielddrive demo.

‍