01
Patron taps
The phone touches the verifier in a door staffer's hand. No handing a device over, no passing a phone back and forth, no queue for a fixed kiosk.
Bars and nightclubs
A door decision in seconds, with nothing kept afterwards.
Door staff make a judgement call every few seconds, in bad light, with a queue behind the person in front of them. LaurelID gives them a cryptographic answer instead of a squint.
01 · The problem today
The door is the hardest place to check an ID
Physical ID checking at a door is a skill, and it degrades exactly when you need it most: late, loud, dim, and busy. Staff are asked to spot a sophisticated fake in under two seconds while managing a queue and a person who does not want to be delayed.
The common fix — a barcode scanner that logs every entry — solves the wrong problem. It creates a nightly file of who was at your venue and when, which is a subpoena target, a breach liability, and a marketing temptation that regulators are increasingly unsympathetic toward.
02 · The LaurelID workflow
How the check actually runs here.
02
Verifier answers
One screen, one outcome, one next action. Verified means proceed; under 21 means refuse per your policy; unable to verify means run your normal manual check.
03
Door keeps moving
The result clears itself, so the next patron never sees the last one's screen, and staff never scroll back through a history.
03 · The privacy advantage
No entry log means no entry log to lose
A LaurelID check produces no record of who came in. There is no name, no birth date, no scan image, and no repeat-visitor identifier — so there is no file that can be requested, breached, or repurposed.
What you do get is the operational number you actually use: how many checks happened at this door, on this night, with what outcome mix. That is enough to staff a shift. It is not enough to build a customer profile, and that is the point.
04 · Deployment
What a rollout looks like in this setting.
Scoped during qualification against your real floor, not assumed from a template.
Dimension Shape
Posture Handheld, carried by door staff
Placement At the door, plus a charging position inside
Network Outbound HTTPS; checks continue through outages
Training Three outcomes and three actions
Fallback Your existing manual check, unchanged
05 · Limitations
Where LaurelID is the wrong answer here.
If one of these is a hard requirement for you, it is better to know now than three weeks into a pilot.
Not every patron has a mobile ID
Mobile ID adoption is real but partial. Expect a mixed door for the foreseeable future: mobile IDs on the LaurelID path, everyone else on your existing procedure. A pilot measures your actual mobile-ID share, which is usually the number operators most want.
It does not judge whether the phone is theirs
LaurelID proves that the presented credential attests to 21+. Whether the person holding the phone is the person the credential describes remains a staff judgement, exactly as it is with a physical card.
06 · Other settings
Nearby verticals.
Liquor retail
Retail age checks happen mid-transaction, under time pressure, with a line forming. The check needs to be fast, defensible, and free of the data exhaust that a scan log leaves behind.
Cannabis retail
Cannabis retail sits under strict age rules and equally strict scrutiny of what operators keep about their customers. A check that collects nothing is easier to defend than a check that collects carefully.
Stadiums and venues
A venue's age checks all happen in the same twenty minutes, on the worst network of the week, run by staff who may be working their first event. Everything about that is a design constraint.
Pilot LaurelID in bars and nightclubs.
Thirty days, one location, two to five verifiers, and a written readout against metrics you agree to first.