--- title: "How Do You Verify Registrations at the Door? A Practical Event Door Check Guide" description: "Learn how to verify event registrations at the door without slowing down entry. This practical guide covers attendee lookup, QR check-in, walk-ins, duplicate registrations, identity exceptions, privacy, troubleshooting, and a ready-to-use event door check workflow." canonical: "https://meetwho.app/blog/event-door-check-registration-verification" language: "en" published: "2026-08-13T19:27:54.528+00:00" updated: "2026-08-13T19:27:54.927052+00:00" reading_time_minutes: "23" source: "MeetWho — the networking layer for events and communities" license: "Quote with attribution and a link to the canonical URL." --- # How Do You Verify Registrations at the Door? A Practical Event Door Check Guide ## TL;DR - An event door check connects the registration process that happened before the event with the attendee's physical arrival. - Registration verification answers a relatively narrow question: does this person have an eligible registration for this event? - If the event uses approval or waitlist workflows, the team should also understand how statuses such as approved, pending, or waitlisted affect entry. - The most reliable attendee check-in workflow has a simple normal path and a separate path for exceptions. - If the event uses QR check-in, staff can ask the attendee to present the code provided for registration or check-in. ## Key questions **What Is an Event Door Check?** An event door check connects the registration process that happened before the event with the attendee's physical arrival. The organiser already has a registration record; the door team's job is to retrieve that record, determine whether it is eligible for entry, and record that the attendee has arrived. **What Should Be Confirmed at the Door?** If the event uses approval or waitlist workflows, the team should also understand how statuses such as approved, pending, or waitlisted affect entry. Door staff should not have to invent rules when a guest arrives. **How Do You Verify Event Registrations at the Door?** The most reliable attendee check-in workflow has a simple normal path and a separate path for exceptions. The normal path should contain only the steps necessary to locate the registration, validate it, and record the attendee's arrival. **QR Check-In vs Manual Guest-List Verification** Both QR scanning and manual registration lookup can play a role in an effective check-in operation. The better choice depends on factors such as event size, arrival patterns, available devices, connectivity, staffing, and the complexity of the registration process. **When Should You Use Both?** For many events, the most practical setup is to use QR scanning as the primary event check-in method and keep manual attendee lookup available as a fallback. This gives straightforward registrations a fast path without leaving staff unable to help someone whose QR code is unavailable. **Event Registration Verification Methods Compared** No single verification method is ideal for every event. The right approach depends on attendance volume, event format, infrastructure, privacy requirements, and whether the organiser needs registration verification alone or stronger identity confirmation. ## Full article Title: "Event Door Check: How to Verify Registrations at Entry" Description: "Learn how to run an event door check, verify registrations, use QR check-in, handle exceptions, protect attendee data, and keep event entry moving." # How Do You Verify Registrations at the Door? A Practical Event Door Check Guide **Event door check** is the process of confirming that arriving guests have a valid registration, recording their arrival, and resolving registration issues without creating unnecessary queues. For most professional events, staff can verify attendees by scanning a QR code or finding their registration record, while a predefined fallback process handles missing names, duplicate check-ins, waitlisted guests, and technical problems. To verify a registration at the door, scan the attendee's QR code or locate their registration record, confirm that the registration is valid for the correct event, check its current check-in status, and mark the attendee as arrived. If the registration cannot be confirmed, move the case into a separate exception process instead of holding up the main entrance queue. The important distinction is that registration verification does not automatically mean proving someone's legal identity. The goal of an efficient **event registration verification** process is to establish whether the arriving person has an eligible registration and can proceed according to the organiser's entry policy. Some events may require additional identity checks, but that should be based on a genuine security, eligibility, accreditation, age, or regulatory requirement rather than treated as a default for every attendee. ## What Is an Event Door Check? An **event door check** connects the registration process that happened before the event with the attendee's physical arrival. The organiser already has a registration record; the door team's job is to retrieve that record, determine whether it is eligible for entry, and record that the attendee has arrived. Depending on the event, this may be done through a QR code, a name or email lookup, a registration reference, or another authorised verification method. A well-designed check-in process does more than confirm names on a guest list. It gives staff a consistent way to distinguish between straightforward admissions and cases that need attention. A valid attendee who has not yet checked in should move through the normal flow quickly, while a missing registration, duplicate record, pending application, or waitlisted attendee should follow an exception process defined before the doors open. ### Registration Verification vs Identity Verification Registration verification answers a relatively narrow question: **does this person have an eligible registration for this event?** Staff might establish that by scanning a QR code associated with an attendee record or by locating the attendee in the registration system and confirming the relevant status. Identity verification answers a different question: is the person standing at the desk demonstrably the individual associated with that registration? That may require additional evidence, such as an identity document, but not every event needs that level of verification. Organisers should avoid collecting or inspecting more personal information than is necessary for the event's legitimate entry requirements. ### What Should Be Confirmed at the Door? The exact checks depend on how the event has been configured, but staff typically need to confirm that the record belongs to the correct event, that its registration status qualifies for admission, and that it has not already been processed as checked in. If the event uses approval or waitlist workflows, the team should also understand how statuses such as approved, pending, or waitlisted affect entry. The objective is consistency. Door staff should not have to invent rules when a guest arrives. Before check-in begins, organisers should define which registration states allow entry, which require escalation, and what staff should do when the system does not immediately return a clear answer. ## How Do You Verify Event Registrations at the Door? The most reliable **attendee check-in** workflow has a simple normal path and a separate path for exceptions. The normal path should contain only the steps necessary to locate the registration, validate it, and record the attendee's arrival. A practical door-verification sequence looks like this: - **Ask for the attendee's registration or name.** Use the event's preferred check-in method, such as a QR code, while keeping an alternative lookup method available. - **Scan the QR code or find the registration record.** Make sure the result corresponds to the correct event and attendee. - **Confirm the registration is eligible.** Check the status the organiser has defined as valid for entry. - **Check whether the attendee is already checked in.** An existing check-in should be reviewed rather than automatically treated as misuse. - **Mark the attendee as checked in.** Recording arrival prevents the same registration from being processed repeatedly and creates an accurate attendance record. - **Complete any event-specific entry step.** For example, direct the attendee towards badge collection, the correct room, an orientation point, or the main event space. - **Move unclear cases to an exception process.** Missing registrations, waitlisted attendees, duplicate check-ins, and other discrepancies should be resolved without blocking the normal queue. ### 1. Ask for the Attendee's Registration or Name If the event uses QR check-in, staff can ask the attendee to present the code provided for registration or check-in. The purpose is to retrieve an existing record, not to collect the same information again at the entrance. For attendees who cannot access their QR code, an authorised name, email, or other registration lookup can serve as a fallback where the event system allows it. Check-in staff should also be mindful of privacy at a busy entrance. Asking an attendee to announce unnecessary contact information in front of other guests can expose data that has no operational value. Where possible, staff should use the minimum information required to locate the correct record. ### 2. Scan the QR Code or Find the Registration Record A QR code can reduce the need to type and search manually by taking staff directly to the associated registration workflow. The staff member can then confirm the record rather than relying on visual recognition of a confirmation email or a name on an uncontrolled list. When scanning is not possible, manual **attendee lookup** remains an important fallback. Similar names, spelling differences, changed email addresses, or an attendee opening the wrong confirmation message can all make a straightforward arrival appear more complicated than it is. The lookup process should therefore allow staff to check the record carefully before escalating the case. ### 3. Confirm the Registration Is Eligible Finding a record is not necessarily the same as confirming entry. An attendee may have submitted a registration but still be pending approval, or they may currently be on a waitlist. The door team should use the statuses and access rules established by the organiser rather than assuming that every record in the system represents confirmed admission. This is especially important for events that review applications or manage capacity through a waitlist. Staff should know in advance which status permits check-in and who has authority to resolve a disputed or unclear registration. ### 4. Check for an Existing Check-In Before recording another arrival, verify whether the registration has already been marked as checked in. A duplicate status can result from a previous staff action, an operational mistake, or a genuine registration issue, so it should not automatically be framed as fraud. Instead, move the case to the appropriate review process. This allows the normal check-in line to keep moving while a designated staff member determines what happened. ### 5. Mark the Attendee as Checked In Once the registration has been validated, record the attendee's arrival in the check-in system. This converts the registration from a pre-event record into an attendance record and reduces ambiguity if the same registration appears at the entrance again. Accurate check-in data also helps organisers distinguish between people who registered and people who actually attended. The door process should therefore include a clear final action rather than simply viewing a record and allowing the attendee through. ### 6. Complete Any Event-Specific Entry Step Verification may be followed by another operational step depending on the event. Attendees might need directions to a room, a physical badge from a separate desk, or instructions about where the programme begins. These tasks should remain distinct from registration verification so staff understand when check-in is actually complete. Keeping the process modular also makes responsibilities clearer. The person verifying registrations does not necessarily need to handle every other arrival task at the same station. ### 7. Route Exceptions to a Separate Process The most useful operational principle is simple: **keep normal check-in moving while exceptions are resolved separately**. A guest whose registration requires investigation can consume considerably more staff attention than someone whose QR code immediately returns an eligible record. Organisers should therefore establish who handles missing names, pending registrations, waitlisted attendees, duplicate check-ins, and walk-ins. Door staff can then follow a consistent escalation path rather than making individual access decisions under pressure. ## QR Check-In vs Manual Guest-List Verification Both QR scanning and manual registration lookup can play a role in an effective check-in operation. The better choice depends on factors such as event size, arrival patterns, available devices, connectivity, staffing, and the complexity of the registration process. **QR check-in** is particularly useful as a primary workflow because it can retrieve the relevant attendee record without requiring staff to search through a long list manually. Manual lookup remains valuable as a fallback when an attendee cannot access their code, the code cannot be scanned, or staff need another way to locate the registration. ### QR Code Check-In With QR-based check-in, an attendee presents a code connected to their registration, staff scan it, and the corresponding record can be reviewed for check-in. This reduces typing and avoids some of the practical problems caused by similar names or spelling variations. MeetWho supports QR check-in alongside event creation, attendee registration, approval workflows, waitlist management, announcements, and reminders. This allows organisers to keep **event registration and check-in** within the broader event-management workflow rather than treating arrival as an entirely separate process. ### Manual Attendee Lookup Manual lookup is useful when the attendee cannot access their QR code, the code is unreadable, or staff need to investigate a registration manually. Depending on the system, staff may search by name, email address, or another authorised registration identifier. This method is flexible, but it can take longer when several attendees have similar names or when registration details contain spelling differences. For that reason, manual lookup works best as a secondary path rather than the only method at a busy entrance. Staff should know which fields they are allowed to use and should avoid exposing complete attendee records unnecessarily while searching. ### When Should You Use Both? For many events, the most practical setup is to use QR scanning as the primary **event check-in** method and keep manual attendee lookup available as a fallback. This gives straightforward registrations a fast path without leaving staff unable to help someone whose QR code is unavailable. The two methods should support the same underlying entry policy. Whether a record is found by scanning or searching, staff still need to confirm that the registration is eligible, review its check-in status, and handle exceptions according to the organiser's predefined rules. ## Event Registration Verification Methods Compared No single verification method is ideal for every event. The right approach depends on attendance volume, event format, infrastructure, privacy requirements, and whether the organiser needs registration verification alone or stronger identity confirmation. Method Best suited to Main advantage Main limitation Recommended role QR code scan Structured event check-in Retrieves the relevant record without manual searching Requires an accessible code and functioning scanning device Primary workflow Name or email lookup Most event formats Flexible when a QR code is unavailable Can be slower with similar names or incorrect details Secondary workflow Printed guest list Connectivity fallback Can work without a live connection Can become outdated and expose more attendee information Emergency fallback Confirmation email or reference Registration troubleshooting Helps staff locate the registration Does not necessarily prove identity Supporting evidence ID verification Events with legitimate identity requirements Provides stronger identity confirmation Adds friction and privacy considerations Use only when justified The important point is proportionality. A professional meetup may only need an active registration record, while an event with controlled accreditation or another legitimate identity requirement may need additional checks. Organisers should select the least intrusive method that still meets the event's actual admission needs. ## What Do You Do When a Registration Cannot Be Verified? Even a well-prepared **event door check** will produce exceptions. The goal is not to eliminate every unusual case, but to make sure staff know what to do when one appears. A useful decision model is simple: Registration state Door action Valid and not checked in Check in Valid but already checked in Review as an exception Pending approval Follow organiser approval policy Waitlisted Follow waitlist policy Record not found Search alternatives and escalate Walk-in attendee Apply the predefined walk-in policy This structure prevents staff from making inconsistent decisions when queues are building. ### The Attendee Is Not on the Registration List If a registration cannot be found, staff should first check for simple causes. Confirm the spelling of the attendee's name, try an alternative authorised identifier, and make sure the registration relates to the correct event and date. If the event uses approval or waitlist statuses, staff should also check whether the attendee has a record that is not yet eligible for entry. A confirmation message supplied by the attendee may help locate the record, but staff should still follow the organiser's actual registration data and access rules rather than making an ad hoc admission decision. ### The Attendee Has Lost Their QR Code A lost QR code does not necessarily mean that the attendee needs to register again. If the registration system allows authorised lookup, staff can search for the existing record and verify its status manually. This is why a QR-first workflow should still have a fallback. An entrance process that depends entirely on one code, one device, or one communication channel can turn a minor attendee problem into an unnecessary queue. ### The QR Code Does Not Scan A QR code may fail to scan because the screen is too dim, the code is partially obscured, the attendee has opened the wrong code, or the scanning device is having difficulty. Staff can first ask the attendee to increase screen brightness and display the complete code. If scanning still fails, use the authorised manual lookup process. The objective is to verify the underlying registration, not to make successful QR scanning a condition of entry when another legitimate verification method is available. ### The Registration Has Already Been Checked In An existing check-in should be treated as an exception requiring review. It could indicate a previous staff action, a duplicate processing mistake, or another issue that needs clarification. Staff should avoid immediately accusing the attendee of misusing a registration. Instead, the case should move to the designated exception point, where someone with the appropriate authority can review the record without delaying other arrivals. ### The Attendee Is Still on a Waitlist or Pending Approval A registration record may exist without being eligible for admission. This matters particularly for events where organisers approve applications or manage capacity through a waitlist. MeetWho supports application approval and waitlist management, so organisers can establish these states before the event. Door staff should then follow the organiser's defined admission policy rather than changing a pending or waitlisted attendee's status simply because the person has arrived at the venue. ### Someone Wants to Register as a Walk-In Walk-ins should be handled according to a policy decided before doors open. Some events may allow on-site registration, others may accept it only while capacity remains, and some may not permit it at all. The check-in team should know which rule applies and who can approve exceptions. This keeps admission decisions consistent and prevents front-desk staff from improvising under pressure. ## How Should You Set Up an Event Check-In Desk? A strong check-in desk separates the normal attendee flow from problems that require investigation. The simplest structure is a main QR or registration line for straightforward arrivals and a separate help point for registration issues. This approach protects the fast path. Someone with an unreadable code or missing registration can receive proper attention without keeping every other attendee behind them waiting. ### Separate Normal Check-In From Exceptions Signage should make it clear where attendees need to go. If the event allows walk-ins, that process can also be separated from pre-registered attendee check-in where practical. The principle is operational rather than technological: **scan or search, verify, check in, and move on; investigate exceptions elsewhere**. A clear division of responsibilities makes the process easier for both staff and attendees. ### Prepare Staff Before Doors Open Before the first attendee arrives, staff should know which registration statuses are valid, how to use the check-in method, who can resolve exceptions, and what information they should avoid exposing at the desk. They should also understand the fallback process for lost QR codes, connectivity problems, pending registrations, waitlisted attendees, and walk-ins. A few minutes spent defining these rules in advance can prevent inconsistent decisions once the entrance becomes busy. ### Test Devices and Connectivity Check that devices are charged, QR scanning works as expected, required permissions are enabled, and the venue's available internet connection is usable before doors open. Where possible, test the workflow using appropriate test records rather than discovering configuration issues with the first real attendee. Organisers should also prepare a fallback that fits their event and software setup. That might involve an authorised alternative lookup method or a carefully controlled offline reference, but it should never expose more attendee information than staff genuinely need. #### Minimum Fallback Information A backup process should give staff enough information to determine whether an attendee has an eligible registration without exposing the entire attendee database. In many cases, a limited set of fields such as the attendee's name, registration status, and another authorised identifier may be sufficient. The fallback should also be current enough to reflect recent approvals, cancellations, or waitlist changes. A printed list created too early can quickly become inaccurate, which is why organisers should treat offline copies as controlled contingency tools rather than the primary source of truth. ##### Data Minimisation at the Check-In Desk Registration desks often operate in open, crowded spaces, so staff should only display or handle information that is genuinely required for admission. Full profiles, private notes, unnecessary contact details, or unrelated registration data should not be visible simply because someone is checking in. This principle of data minimisation reduces accidental exposure while keeping the process easier for staff. The practical question should be: what does the door team actually need to confirm this registration and record the attendee's arrival? ###### Avoid Unnecessary Exposure of Attendee Contact Details Do not leave lists containing email addresses, phone numbers, or other personal details openly visible on a registration desk. Where contact information is needed for lookup, staff should access it through an authorised process and avoid reading it aloud unnecessarily. ## How Can You Make Event Door Check-In Faster? A faster **event door check** usually comes from removing avoidable decisions rather than asking staff to work more quickly. Clear registration records, advance instructions, well-defined queues, and a separate exception process can all reduce friction before technology becomes the limiting factor. The best workflow also avoids turning the entrance into a second registration form. Information that can reasonably be collected before the event should generally be completed before attendees reach the door. ### Collect Accurate Registration Data Before the Event Consistent registration information makes attendee lookup easier. Organisers should decide which fields are genuinely necessary and use a structured registration process rather than collecting fragmented information across messages, spreadsheets, and unrelated forms. Where an event requires application approval or waitlist management, those statuses should also be resolved as far as possible before arrival. Door staff can then work from clear records rather than interpreting incomplete submissions in real time. ### Send Check-In Instructions Before Arrival Attendees should know where to enter, when check-in begins, what confirmation or QR code to have ready, and whether any additional documentation is genuinely required. Clear instructions reduce the number of questions that have to be answered at the entrance. MeetWho allows organisers to send announcements and reminders to registered attendees, making it possible to communicate practical arrival information before the event rather than relying entirely on signage at the venue. ### Use Clear Queue Signage Simple signage can help attendees choose the correct path before reaching the desk. For example, an organiser may separate pre-registered attendees from registration-help cases or permitted walk-ins. The wording should match the actual process. Too many queues or unclear labels can create more confusion than they solve, so the structure should remain as simple as the event allows. ### Avoid Collecting New Information at the Door Unless Necessary The primary purpose of check-in is to verify an existing registration and record arrival. Asking every attendee to complete additional forms, repeat previously supplied details, or answer unrelated questions adds friction to the normal path. If new information must be collected for a legitimate operational reason, organisers should decide in advance where that process belongs and whether it should happen before, during, or after entry. ### Assign One Person to Resolve Exceptions At events where staffing allows it, designating someone to handle difficult cases can protect the main check-in flow. That person can review missing registrations, approval questions, duplicate check-ins, and walk-in requests while other staff continue processing straightforward arrivals. The value is consistency as much as speed. When one person or clearly defined role owns exceptions, staff are less likely to apply different rules to similar situations. ## How Should Event Registration Data Be Handled at the Door? Registration verification requires access to attendee information, but access should remain proportionate to the task. Staff should see enough information to perform check-in without treating attendance as permission to expose an attendee's broader profile or contact details. Privacy expectations should be established before temporary staff or volunteers receive access to registration information. Where legal or regulatory requirements apply, organisers should verify the relevant obligations for the jurisdiction in which they operate. ### Show Staff Only What They Need A check-in role generally needs less information than an event administrator. Limiting the information available at the entrance can reduce accidental exposure while making the interface or reference material easier to use. Organisers should also consider who genuinely needs access after check-in begins. Registration information should not become an informal directory simply because several people are helping at the event. ### Avoid Public Attendee Lists Attendance at an event does not automatically mean that a person wants their profile, contact details, or participation exposed to everyone else. Networking and admission should therefore be treated as related but distinct experiences. MeetWho takes a privacy-first approach to networking. Rather than exposing a universally public attendee list, it uses organiser settings and participant permission to recommend relevant people among users who have opted in. Paid membership does not provide access to hidden profiles or private contact details, and MeetWho does not sell attendee lists. ### Define Who Can Access Registration Information Before the event, determine which staff members need access to registration data and what actions each role is expected to perform. Volunteers working at the entrance may need check-in access without needing broader administrative information. Clear responsibilities also help when an exception requires escalation. Staff should know who can make an admission decision instead of sharing registration data widely in search of an answer. ### Follow Applicable Privacy Requirements Privacy requirements differ between jurisdictions and event types. Organisers should rely on authoritative guidance from the relevant regulator when determining their obligations rather than assuming that one universal policy applies everywhere. For European events, official EU and national data-protection authority guidance can be used when applying principles such as data minimisation, purpose limitation, and appropriate handling of personal information. Legal claims should be verified before publication or implementation. ## How MeetWho Supports Registration, Check-In, and Event Networking MeetWho combines event creation, attendee registration, and networking tools within a single SaaS platform. Organisers can create an event for free, collect registrations, approve applications, manage waitlists, send announcements and reminders, and use QR check-in when attendees arrive. That makes MeetWho relevant to the full registration journey without changing the purpose of the door process. The entrance still needs a clear verification policy; the platform provides tools that help organisers manage the attendee records and check-in workflow supporting that policy. ### Create the Event and Manage Registrations Organisers can use MeetWho to create an event page, collect registrations, review applications, and manage waitlists. Online event links can also be shared only with registered attendees, while announcements and reminders help organisers communicate before the event starts. These capabilities can reduce the fragmentation that occurs when registration status, attendee communication, and arrival management are maintained in unrelated tools. ### Check Registered Attendees In With QR Codes MeetWho supports **QR check-in** for registered attendees. Organisers can use this as part of their event arrival workflow instead of relying solely on manually maintained guest lists. QR check-in should still sit within a broader operational process that covers exceptions. A failed scan, unavailable code, pending registration, or duplicate check-in still requires a clear policy and an authorised way to resolve the situation. ### Go Beyond Entry: Help Attendees Know Who to Meet Check-in answers whether someone has arrived. It does not answer the question many professional attendees face immediately afterwards: who in this room is actually worth meeting? MeetWho positions this layer as **Event Networking Intelligence**. Participants can create professional profiles describing what they are working on, what they are looking for, who they want to meet, and how they can help others. With participant permission and organiser privacy settings respected, MeetWho analyses those signals alongside event goals and shared interests to recommend relevant people. Instead of exposing everyone in a public attendee directory, recommendations are ranked and explained. Participants can see why a meeting may be useful, how both people might benefit, and potential conversation starters. They can send connection requests, message after a mutual connection, add private notes, create follow-up reminders, and manage their connection history after the event. The principle is captured in MeetWho's positioning: **“Know who to meet.”** The objective is not to maximise the number of contacts collected, but to help attendees make more relevant and mutually useful connections. ## Event Door Check Checklist ### Before Doors Open - Review which registration statuses permit entry. - Test the QR check-in workflow. - Confirm the authorised manual lookup method. - Assign staff roles and an exception owner. - Define rules for pending and waitlisted registrations. - Decide whether walk-ins are allowed. - Charge and test check-in devices. - Check available connectivity. - Prepare an appropriate fallback process. - Position clear queue and help-desk signage. - Limit attendee information to what staff genuinely need. ### During Check-In - Scan the QR code or locate the registration. - Confirm that the record belongs to the correct event. - Verify that the registration is eligible. - Check whether it has already been checked in. - Record the attendee's arrival. - Move unclear cases to the exception process. - Avoid exposing unnecessary personal information. ### After Check-In Starts - Monitor repeated issues and update staff instructions. - Keep admission decisions consistent. - Escalate unusual cases to the designated owner. - Maintain accurate attendance records throughout the event. ## Frequently Asked Questions About Event Door Checks ### How do you check if someone is registered for an event? Scan the attendee's registration QR code or search the authorised registration system using an appropriate identifier such as their name or email address. Confirm that the record relates to the correct event, has an eligible registration status, and has not already been checked in before recording the attendee's arrival. ### What is the fastest way to check attendees in? QR scanning can be an efficient primary method because it reduces manual searching and typing. The best setup still depends on attendee volume, staff, devices, connectivity, and the event's verification requirements. Keep a manual lookup or other authorised fallback available for cases where scanning is not possible. ### Do attendees need to show ID at event check-in? Not necessarily. Many events only need to confirm that an attendee has an eligible registration. ID may be appropriate where there is a legitimate identity, security, accreditation, age, or regulatory requirement, but organisers should not automatically request identity documents for every event. ### What happens if an attendee loses their QR code? If the registration system supports an authorised alternative lookup, staff can search for the attendee's existing registration and verify its status. Losing a QR code does not automatically mean the person needs to register again. ### Can you check guests in without a QR code? Yes, where the organiser's registration process provides another authorised way to find and verify the attendee record. A name, email address, registration reference, or other approved identifier may be used depending on the system and event policy. ### What should you do if someone is not on the attendee list? Check the spelling, try an alternative authorised identifier, confirm the event and date, and review any pending or waitlisted status that may apply. If the registration still cannot be verified, follow the organiser's exception or walk-in policy rather than improvising an admission decision. ### How do you handle duplicate event check-ins? Treat an existing check-in as an exception that needs review. Confirm whether it resulted from an earlier staff action, a processing mistake, or another registration issue. Avoid immediately assuming misuse and move the case away from the main queue while it is investigated. ### Should you print the event guest list? A printed list can be useful as a deliberately prepared connectivity fallback, but it can become outdated and may expose more attendee information than necessary. If one is used, restrict the fields to essential check-in information and control access to the document. ### How early should event check-in open? There is no single opening time that works for every event. Consider expected attendance, how concentrated arrivals are likely to be, venue access rules, the number of check-in stations, and how many verification steps each attendee must complete. ### How many check-in staff do you need? Estimate staffing from the expected peak arrival volume, the complexity of the verification process, the number of available stations, and the likely frequency of exceptions. Testing the planned workflow before the event provides a more useful basis for staffing than applying a universal attendee-to-staff ratio. ## Make Registration Verification Part of a Better Attendee Journey A good entrance process answers three questions efficiently: **Are you registered? Can we record your arrival accurately? What happens next?** The best workflows give straightforward registrations a fast path while directing missing, duplicate, pending, waitlisted, or otherwise unclear records into a controlled exception process. With MeetWho, organisers can **create an event for free**, collect and manage registrations, use QR check-in, and communicate with attendees before the event. Once participants are inside, MeetWho can also help opted-in attendees move beyond simply sharing a room and understand who they should meet, why that connection may matter, and how to start a meaningful conversation. **Create your event for free with MeetWho and turn registration, check-in, and professional networking into a more connected attendee journey.** --- Canonical HTML version: https://meetwho.app/blog/event-door-check-registration-verification Machine-readable site index: https://meetwho.app/llms.txt