[{"data":1,"prerenderedAt":208},["ShallowReactive",2],{"marketing-blog-blog\u002Fre-issuing-a-lost-or-forwarded-pass-safely":3,"marketing-blog-related-blog\u002Fre-issuing-a-lost-or-forwarded-pass-safely":188},{"id":4,"title":5,"author":6,"body":7,"category":167,"date":168,"description":169,"draft":170,"extension":171,"image":172,"imageAlt":173,"imageCredit":174,"imageCreditUrl":175,"meta":176,"navigation":177,"path":178,"readTime":179,"seo":180,"stem":181,"tags":182,"__hash__":187},"blog\u002Fblog\u002Fre-issuing-a-lost-or-forwarded-pass-safely.md","Re-issuing a lost or forwarded pass safely","The CheckInHub team",{"type":8,"value":9,"toc":156},"minimark",[10,14,17,22,25,28,34,37,41,44,47,114,123,127,130,133,138,146,150,153],[11,12,13],"p",{},"Two guests reach the door with a problem. The first cannot find their\npass — the confirmation email is buried, the phone is new, the QR code is\nsimply gone. The second hands over a pass that scans perfectly but belongs\nto someone who already walked through ten minutes ago. Both need solving in\nseconds, and the way you solve them decides whether your gate means\nanything at all.",[11,15,16],{},"These are not edge cases. At any event of a few hundred people, someone\nwill lose a pass and someone will forward one, by accident or otherwise.\nA check-in that has no clean answer for either turns the door into a\nnegotiation, and a negotiation at the door is how queues form and how the\nwrong people get in.",[18,19,21],"h2",{"id":20},"the-lost-pass-is-an-identity-problem","The lost pass is an identity problem",[11,23,24],{},"When a guest cannot present their pass, the real question is not how to\nmake a new code. It is how confident you are that this person is who they\nsay they are. Re-issuing a pass to the right guest is a service. Re-issuing\none to the wrong guest is handing out access.",[11,26,27],{},"The safe path is to verify against the list, not the pass. The guest is on\nthe guest list under a name and an email. A steward finds them by name,\nconfirms a detail only they should know, and checks them in directly — no\nnew code required, because the scan was never the point. The pass is just a\nfast way to find a record. If the record can be found another way, the\nguest is in.",[29,30,31],"blockquote",{},[11,32,33],{},"A pass is a shortcut to a name on a list. Lose the shortcut and you fall\nback to the list, not to a stranger's word.",[11,35,36],{},"This is why a guest list that you can search by name in a second is worth\nmore than any clever code. When a steward can find a person without their\npass, a lost pass stops being a crisis and becomes a ten-second detour.",[18,38,40],{"id":39},"the-forwarded-pass-is-a-reuse-problem","The forwarded pass is a reuse problem",[11,42,43],{},"The second guest is harder, because their pass is genuine. It was issued\nto a real invitee. The problem is that the invitee already used it, or\nshared it, and now two people are trying to enter on one identity.",[11,45,46],{},"The defence here is that a pass can only be used once. The first scan\nchecks the guest in. The second scan of the same pass should not silently\nlet a second person through — it should flag that this pass has already\nbeen used, and route the situation to a steward who can decide what to do.\nMaybe the original guest popped out for air and is genuinely returning, in\nwhich case re-entry handling covers it. Maybe a screenshot did the rounds,\nin which case you have caught it.",[48,49,50,66],"table",{},[51,52,53],"thead",{},[54,55,56,60,63],"tr",{},[57,58,59],"th",{},"Situation",[57,61,62],{},"What the scanner should show",[57,64,65],{},"What the steward does",[67,68,69,81,92,103],"tbody",{},[54,70,71,75,78],{},[72,73,74],"td",{},"First scan, valid pass",[72,76,77],{},"Checked in, all clear",[72,79,80],{},"Wave them through",[54,82,83,86,89],{},[72,84,85],{},"Same pass, second scan",[72,87,88],{},"Already used, flagged",[72,90,91],{},"Verify, decide re-entry or refuse",[54,93,94,97,100],{},[72,95,96],{},"Pass for a name not on the list",[72,98,99],{},"Not recognised",[72,101,102],{},"Check the list by name",[54,104,105,108,111],{},[72,106,107],{},"Guest with no pass at all",[72,109,110],{},"Steward search by name",[72,112,113],{},"Verify identity, check in manually",[11,115,116,117,122],{},"The point of the table is that each case has a defined answer the steward\ndoes not have to invent on the spot. A door where every odd scan is a\nfresh judgement call is a slow door and an inconsistent one. We have\nwritten more on why\n",[118,119,121],"a",{"href":120},"\u002Fblog\u002Fwhy-a-signed-qr-pass-beats-a-screenshot","why a signed qr pass beats a screenshot",",\nand reuse detection is a large part of the reason.",[18,124,126],{"id":125},"doing-it-without-breaking-the-flow","Doing it without breaking the flow",[11,128,129],{},"The danger in handling these cases is that you build a second, slower lane\nfor problems and it becomes the lane everyone with any wrinkle joins. The\nbetter design keeps the resolution inside the normal flow.",[11,131,132],{},"A steward should be able to search the list by name, confirm a guest and\ncheck them in from the same device they scan with, in roughly the time a\nnormal scan takes. CheckInHub keeps the average check-in around eight\nseconds precisely so that the exceptions — the lost pass, the flagged\nreuse — do not balloon into multi-minute stops. The exception is handled\nat the front of the queue, not pulled out of it.",[134,135,137],"h3",{"id":136},"keep-a-record-of-what-you-did","Keep a record of what you did",[11,139,140,141,145],{},"Every re-issue and every flagged reuse is worth logging, lightly. Not for\nbureaucracy, but because patterns matter. One forwarded pass is a guest\nbeing helpful to a friend. Twenty forwarded passes from the same source is\na leak, and you want to know about it before next year. A door that quietly\nrecords its exceptions gives you that signal. Our note on\n",[118,142,144],{"href":143},"\u002Fblog\u002Flogging-incidents-at-the-door","logging incidents at the door","\ncovers how to capture this without slowing anyone down.",[18,147,149],{"id":148},"the-principle-underneath-all-of-it","The principle underneath all of it",[11,151,152],{},"Both problems come back to one idea: the pass is a convenience, and the\nlist is the truth. When you treat the scan as the only gate, a lost pass\nlocks out a real guest and a shared pass lets in a stranger. When you treat\nthe list as the gate and the pass as a fast way to reach it, both problems\nshrink to something a steward can resolve in seconds.",[11,154,155],{},"Build the door so that finding a guest by name is as easy as scanning one,\nso that a pass can only be spent once, and so that the steward always has a\ndefined next step. Do that and the two guests at the start of this piece —\nthe one who lost their pass and the one who borrowed someone else's — both\nget the right outcome, fast, without anyone behind them noticing a thing.",{"title":157,"searchDepth":158,"depth":158,"links":159},"",2,[160,161,162,166],{"id":20,"depth":158,"text":21},{"id":39,"depth":158,"text":40},{"id":125,"depth":158,"text":126,"children":163},[164],{"id":136,"depth":165,"text":137},3,{"id":148,"depth":158,"text":149},"QR codes & scanning","2024-02-09","A guest deleted their email, or shared their pass with a friend. Here is how to put it right at the door without opening a hole in the gate.",false,"md","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1544291276-a725341a8357?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop","A steward in a green high-vis vest","Koshu Kunii","https:\u002F\u002Funsplash.com\u002F@koshuuu?utm_source=checkinhub&utm_medium=referral",{},true,"\u002Fblog\u002Fre-issuing-a-lost-or-forwarded-pass-safely",5,{"title":5,"description":169},"blog\u002Fre-issuing-a-lost-or-forwarded-pass-safely",[183,184,185,186],"qr codes","scanning","passes","security","70WGqAfT1YKRWkTHmILKmcWYr8k65wxsIu8XUDtAevI",[189,196,202],{"to":190,"title":191,"description":192,"date":193,"category":167,"image":194,"readTime":195},"\u002Fblog\u002Fhandling-a-double-scan-at-the-door","When a pass has already been checked in: handling a double scan at the door","A pass that scans as already Checked in is not a fault. It is information. Here is what a second scan usually means and how to handle it calmly at the door.","2026-07-10","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1595079676339-1534801ad6cf?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",6,{"to":197,"title":198,"description":199,"date":200,"category":167,"image":201,"readTime":195},"\u002Fblog\u002Fkeeping-the-queue-moving-when-a-ticket-wont-scan","Keeping the queue moving when a ticket won't scan","Every so often a code refuses to read at the door. The mark of a good front desk is not that it never happens, but that the queue never notices when it does. Here is the fallback that keeps people moving.","2026-07-03","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1566806127671-e092f419a77e?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",{"to":203,"title":204,"description":205,"date":206,"category":167,"image":207,"readTime":195},"\u002Fblog\u002Fthe-eight-second-check-in-explained","The eight-second check-in, explained","What actually happens in the eight seconds a guest spends at the door, step by step, and why most of that time has nothing to do with scanning.","2026-06-19","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1662383729882-e03ce8e00887?ixlib=rb-4.1.0&w=1600&q=80&auto=format&fit=crop",1787334027041]