How do you accept an event-tech shortlist after you leave the hall?

In brief: one test list, one written pass/fail

• Awards and happy-path demos are not acceptance.
• Use a disposable test roster the vendor cannot pre-seed with only VIPs.
• Walk name change, ticket transfer, and multi-gate check-in on the same person.
• Prove offline scan/search (and badge print if you need it); then reconnect and handle conflicts in the open.
• Exhibitor scan ≠ exportable lead—check consent layers and who may export.
• Record results on a checklist before procurement signs.

Why leaving the hall is the real shortlist moment

On the floor you are buying under noise: lighting, seed data, a network the booth controls. At home you can insist on your list, your phones, and a network you can switch off. That is the only environment that looks like opening morning.

If a vendor will only re-demo on their laptop with their sample event, you have not left the hall. Acceptance is a shared screen on a test event you can break.

Build a test list the booth cannot stage

Create ten to twenty people the week after the show—mix of paid, free, pending approval, and one substitute name. Include at least one ticket type that should print a different badge template. Give each person a unique email you control.

• Seed honesty. Ask the vendor not to pre-load “perfect” VIPs. If they must import a sample, replace half the rows with yours before any scan.
• One protagonist. Pick one attendee who will take every exception in sequence so you are not comparing different people across tools.
• Devices you will use. Staff phones and, if badges matter, the desktop client and printer model you expect onsite—not only the booth iPad.

Walk the full path: change, transfer, multi-gate

This is not the booth’s three oral questions. It is the same story executed end to end on the test list.

Fail the vendor if staff invent a spreadsheet join to keep the story coherent. The acceptance bar is one attendee identity across registration, scan and badge—not a clever operator.

Offline scan, then reconnect without magic

Download the list. Turn the network off. Scan and search. If you print at the desk, print once offline. Then reconnect.

• What must still work offline (for a door that claims offline): validate a code already on the device list; search by name; queue check-ins with the time they happened; print from a cached template if printing is in scope.
• What may require the server: brand-new walk-in registration, issuing a new ticket code, or any change that only the server can finalise—write that limit down so sales cannot call it “full offline.”
• Two devices, same person, both offline. Neither phone can know the other scanned. On reconnect, the second hit should surface as a conflict for a human—not a silent merge. Holding the queue on a guess is worse than admitting twice and reviewing later.

Detail on the four meanings of “works offline” lives in the Wi‑Fi failure guide. Acceptance only needs the pass/fail on your devices.

Exhibitor scan: permission and export, not just a counter

If your show has a floor, finish acceptance with a stand scan—not a slide about lead volume.

• Scan a badge with no share consent: visit recorded, identity withheld where the product claims that behaviour.
• Scan with consent layers on: only the allowed fields appear.
• Export CSV: row count may be lower than on-screen visits; only consented-for-export rows leave; who may export is an admin permission you can name.

Visibility rules are spelled out in what exhibitors see on a badge scan. For acceptance, photograph or export the proof into the checklist.

Write it into a procurement acceptance checklist

1. 01

   Identity path

   • Name change and transfer kept one person across desk and print
   • Multi-gate behaviour documented (block / warn / allow) with report evidence

2. 02

   Offline path

   • Scan + name search worked with network off after download
   • Reconnect uploaded queued times; dual-offline conflict visible to a person
   • Walk-in / new ticket limits stated in writing

3. 03

   Floor path (if applicable)

   • No-consent scan ≠ exportable identity
   • Export permission and consent columns verified on a real CSV

4. 04

   Sign-off

   • Date, vendor, test event ID, devices used, pass/fail per row
   • Open issues assigned before contract signature—not “training will cover it”

Treat a failed row as a commercial fact. Discounted pricing does not repair a door that needs a spreadsheet at 08:55.