· 21 min read
How should an event check age-restricted tickets and identification?

Someone reaches your entrance with a paid ticket and a photo of their passport on their phone. Their friends are already inside. The scanner accepts the ticket, but your door team isn't sure whether that photo proves they're old enough to enter. Behind them, the queue keeps growing.
You want that decision settled before anyone arrives. Set an admission policy with your venue, specify the evidence staff can accept, and agree who handles a doubtful document or a disputed refusal. At the door, confirm ticket validity and age eligibility as separate checks. Where alcohol is served, agree the additional service controls with the licence holder too.
A paid ticket proves a purchase. It doesn't, by itself, prove the holder's age or give staff permission to ignore an entry restriction. Equally, an awkward booking problem shouldn't automatically become an accusation that someone is using false identification.
This guide explains how to connect your ticket terms, identification checks and exception process so staff can make a fair decision without negotiating a new rule with every customer. Legal requirements differ by location, licence and activity. The examples below show why those differences matter; your venue and relevant authority need to confirm the rules for your event.
Decide exactly what the age restriction applies to
Start with the experience you're selling. Is the whole event restricted, is only a particular room restricted, or can younger people attend while alcohol service remains controlled? Those arrangements need different tickets, signs and instructions.
For an adults-only club night, the age decision belongs before admission to the restricted event. For a mixed-age concert, entry permission and permission to buy alcohol may differ. An adult accompanying a younger attendee doesn't automatically change either rule. Agree any accompaniment conditions before describing the ticket as suitable for families.
Write down why the restriction exists. It could follow the premises licence, a particular activity, the venue's policy or your own event conditions. That explanation helps you identify who can clarify the requirement. It also stops a promoter's casual promise from becoming a supposed exception at the entrance.
Next, define when someone must meet the threshold. Use the event's local date and any relevant timing rule confirmed by your venue. A birthday between purchase and attendance needs a clear answer. So does a multi-day pass when the holder becomes eligible partway through the programme.
Don't bury these questions in a general safety document. Keep a short admission policy that the ticketing lead, venue manager and security supervisor have agreed. Connect it to your wider event security plan, including who receives a dispute and who can pause admission if conditions become unsafe. Everyone should be applying the same current version.
Confirm local rules before choosing acceptable identification
There isn't a worldwide list of documents that every event can accept. A passport, driving licence, proof-of-age card and digital credential may have different status in different places. Even within one country, the relevant authority and a specific licence can change the answer.
For example, California's Department of Alcoholic Beverage Control describes identification acceptable for alcohol sales. Its guidance includes current government identification and specific exceptions for passports and military identification. It also identifies documents that aren't acceptable, including school identification and foreign driving licences. That's a California alcohol-service example, not a universal event-entry standard.
England and Wales changed their approach in September 2026. The government's announcement on digital proof of age confirms that digital verification became an option for alcohol sales. You shouldn't copy an older physical-document-only policy without checking whether it still describes the current rules.
The practical first step is a conversation with the person responsible for the premises and relevant activity. Ask them to confirm acceptable evidence, any stricter licence conditions, staff training and what happens when eligibility can't be established. Get the answer in writing and use it to prepare your public policy.
If you're touring the same event across venues, repeat that check for each stop. Reusing the event name, ticket template and production team doesn't make the local conditions identical. Put the location and policy version on the staff instructions so an old briefing can't be mistaken for tonight's rules.
Make the policy useful before someone buys
Your event page should answer the question a buyer would ask out loud: "Can I come, and what do I need to bring?" A small "18+" or "21+" label doesn't explain acceptable evidence, accompaniment or whether the restriction applies to the entire event.
State the minimum age for attendance, the relevant date, accepted forms of proof and any conditions for younger attendees. Explain whether original physical documents are required, which digital process you support if applicable, and where someone can ask about an unusual document before travelling. Use wording approved for your actual arrangements.
Put that information where a buyer will encounter it before paying. Repeat the essential arrival instructions in the confirmation and pre-event reminder. If a group buyer receives the message, ask them to pass it to everyone attending. One person's ability to buy several tickets doesn't establish the eligibility of the rest of the group.
Be particularly clear about photographs and screenshots. A photo of a physical document and a verified digital credential are different things. Avoid the phrase "digital ID accepted" if your staff can only accept specific services through a particular checking process. Buyers need to know whether their chosen option will work at your entrance.
Explain the route for a refused entry complaint without claiming that your terms override consumer rights. Have your event refund policy reviewed for the markets where you sell. The door team should know whom to contact about a refund; they shouldn't invent a legal answer while someone is upset outside the venue.
Before sending the reminder, check the wording against these practical questions:
Could someone buying for a friend tell whether that friend is eligible? State the rule for the person attending, rather than assuming the buyer and holder are the same person.
Could an international visitor work out which of their documents is accepted? Provide the approved categories and a contact for questions; avoid a vague instruction to bring "normal ID".
Could a person using your accepted digital option complete the process with what they bring? Explain the supported method and the approved fallback without promising that every identity app works.
Could support answer a question without consulting several contradictory pages? Check the event description, ticket wording and reminder together. Correct inconsistencies before sending the message, and tell the entrance lead which version staff should use tonight.
Keep ticket checking and age checking distinct
Design the entrance sequence around the decisions staff need to make. A ticket check answers whether the presented ticket is valid for this event and admission. The age check answers whether this person meets the relevant condition. Record admission only at the agreed point once the required checks are complete.
That sequence needs testing on your actual equipment. If a ticket has already been marked as used before an age issue appears, staff need a supported way to handle the record. They mustn't promise that scanning again will resolve it or start deleting information to make the next attempt work.
Loopyah's event ticketing and door tools let door managers scan QR tickets from their phones using their own accounts. That gives the ticketing job a defined process and access level. Your event still needs an agreed method for checking age evidence and deciding whether the person may enter.
Don't describe a successful ticket scan as "identity verified" unless a separate approved process has actually established that. The wording matters because another staff member may later rely on the result. Someone admitted to a mixed-age event may still need an age check at the bar.
Walk through the sequence with the venue before opening. Check where someone presents identification, when the ticket is scanned, who controls onward movement and where a referral happens. A sensible order on paper can fail if the desks face opposite directions or the person reviewing documents can't communicate with the scanner operator.
Train staff to check the person as well as the document
An acceptable document type is only the starting point. Staff also need to establish that it belongs to the person presenting it, that the information is readable and that it meets the applicable validity requirements. A genuine document borrowed from an older friend doesn't establish the holder's eligibility.
Use training and reference material approved by your venue or responsible provider. Give staff sufficient light and a place to inspect evidence without rushing. Tell them what a normal check involves and when uncertainty should go to a supervisor. Asking an untrained ticket assistant to recognise every document issued worldwide is a poor staffing decision.
Prepare the relevant birthday cutoff before the shift and verify it with another responsible person. Make clear how staff handle the exact boundary date. They should read the full date rather than estimate age from the birth year or try to calculate it while a customer argues about the queue.
Ask staff to compare the person with the photograph reasonably and respectfully. Appearance changes. A haircut, disability, religious clothing or a gender presentation different from an old photograph needs careful handling under the agreed process, rather than a loud public challenge. A quieter review can protect dignity while still establishing whether the evidence is sufficient.
Consistency matters most when the entrance gets busy. If staff abandon the check for confident customers or familiar faces, your written policy no longer describes the event you're running. Make it easy to call for help and reinforce that a supervisor referral is an expected part of the job.
Support digital proof through a real checking process
If you want to accept digital age evidence, first confirm the local legal position and the service your venue will use. A customer showing an app screen doesn't establish that your team has verified it. Staff need a process they can actually perform.
For alcohol sales under premises licences and club premises certificates in England and Wales, the Home Office's September 2026 licensing guidance requires digital identification to be checked through a certified, registered digital verification service. Visual inspection alone isn't sufficient. An agreement must provide verification to at least medium confidence. Acceptance is optional, age estimation isn't qualifying digital proof, and an existing licence condition expressly preventing digital identification may require a variation. These mandatory conditions exclude activities authorised by temporary event notices; confirm those arrangements separately with the responsible authority.
With those requirements confirmed, test the customer journey with the chosen provider. Check what the attendee presents, what the staff member sees and how the result is connected to the person standing there. Agree how a failed check differs from an unavailable service. Neither should silently become a successful verification.
Have a documented fallback that remains within the applicable policy. Tell buyers about it before they travel, including any accepted physical alternative. A dead phone, failed reader or lost connection shouldn't force a junior staff member to choose between breaking the rules and inventing an unfamiliar technical fix.
Keep the staff briefing specific to your service. "We accept digital ID" is marketing wording. The door team needs to know which approved process to follow, what constitutes a completed check and whom to call when the process doesn't finish.
Give uncertain cases somewhere to go
Some cases won't be resolved at the first check. The document may be damaged, the name may differ from the booking, or a ticket holder may have misunderstood the policy. Agree a supervised review point where staff can examine the actual issue without stopping every other arrival.
Explain the referral neutrally. "My supervisor needs to check this document against our policy" describes what's happening. "This is fake" makes an accusation the first staff member may not be equipped to support. Customers are more likely to understand the process when someone tells them who is reviewing the case and what happens next.
The reviewer needs real authority and access to the current policy. They may confirm that an unfamiliar document is acceptable or correct a ticketing error. Their role doesn't give them permission to waive a legal requirement, disregard a licence condition or approve someone because a sponsor complains.
Record a clear outcome and tell the person what it means. They may be admitted after the uncertainty is resolved, asked to provide another accepted form of evidence, or refused entry under the applicable rule. If the problem is a ticket record, refer it to the ticketing lead rather than treating every exception as an age issue.
One person should coordinate the decision and customer-service handoff. If the supervisor needs advice from the venue manager, explain the wait and keep the person informed.
Prepare for the exceptions you're likely to see
Start with missing identification. Staff should explain the accepted options and follow your review process. A friend vouching for someone, a bank card or a social profile shouldn't become an improvised substitute because the person has already bought a ticket. Any alternative must already be approved for your circumstances.
For expired or damaged evidence, use the rule agreed with the venue. Don't ask staff to decide how much damage is acceptable based on how persuasive the customer sounds. If the policy requires a current document and the holder can't provide one, the reviewer needs to explain the resulting decision plainly.
Treat a name mismatch as a question to resolve. The ticket may have been bought by a friend, transferred through an approved process or issued under a different name. Establish whether your ticket conditions require a named holder and what evidence the approved correction process needs. Age eligibility still belongs to the person attending.
Group bookings need individual decisions where the policy requires them. An older buyer holding everyone's tickets doesn't prove the age of each attendee. Let the group know who has completed the checks and who needs review, without discussing private document details with their friends.
For suspected altered or borrowed identification, follow the security provider's and relevant authority's procedure. Don't instruct ordinary ticket staff to seize documents, search phones or confront someone physically. The plan should identify the trained person who receives the concern and what the first staff member does while waiting for assistance.
Agree who can refuse entry and who can review it
A fair policy becomes difficult to apply if nobody wants to own an unpopular decision. Name the roles that can make an initial refusal, review the evidence and communicate the final outcome. Include deputies and break coverage so the process doesn't disappear when the supervisor leaves the entrance.
The person handling booking complaints may be different from the person responsible for licensed alcohol service or security. Make those boundaries clear. A box-office manager can resolve an incorrect ticket record without deciding that the bar should accept an unsuitable document. A promoter can explain a guest-list mistake without overruling the venue's restrictions.
In Great Britain, the SIA's guidance on event-staff licensing distinguishes ordinary stewarding from activities that may require a security licence. Confirm the actual duties with your provider. Calling someone a ticket checker doesn't settle whether the work you assign them is permitted.
Include complimentary tickets, performers' guests, sponsor allocations and staff bringing friends in the briefing. Nobody should arrive through a side entrance on the assumption that a free ticket removes an age condition. Where crew or performers have a different authorised arrangement, document that arrangement separately and brief the responsible team.
Support staff when they apply the policy correctly. If a senior person overturns a decision, they should explain the factual reason through the proper channel. Quietly admitting someone after telling staff to be strict teaches the team that the real rule is whoever knows management gets in.
Keep refusals calm and customer service accountable
A refusal can be upsetting even when the rule is clear. The customer may have travelled, paid for accommodation or planned the evening with friends. Acknowledge the immediate problem without making a promise you can't keep. Explain the specific condition that hasn't been met and the review route available.
Separate that conversation from any threatening behaviour. A polite customer disputing a document decision needs an explanation. A person creating an immediate safety concern needs the venue's security response. Staff should know when to stop debating and request assistance under the agreed procedure.
Don't announce someone's date of birth or document details across a queue. Keep the conversation as private as the location allows. If a companion helps communicate, address the attendee directly and ask how they want to receive the explanation. Provide an accessible way to contact support afterwards.
Give the customer a useful follow-up route. That might mean a written reason category, the customer-service contact and an order reference. Keep any refund decision with the authorised person and applicable terms. "Security said no" is rarely enough information for the support team to understand whether a booking error, unclear advertising or missing evidence caused the problem.
Review your own mistakes honestly. If the event page described acceptable evidence inaccurately, correcting the page and briefing staff may prevent more disputes. Handle affected buyers through the proper customer-service process. Blaming the first person who noticed the contradiction leaves the underlying problem waiting for the next arrival.
Keep entry checks from creating an unsafe queue
Age checks take time, especially when a document needs review. Plan their position and staffing with the venue rather than adding an extra inspection after the entrance layout has been approved. Your queue should still allow people to ask for help or leave safely.
HSE's crowd-control guidance for events says queues shouldn't obstruct emergency access and people need a safe way out. Use that requirement when choosing your review point. An efficient desk is no help if its waiting area blocks a doorway or pushes arrivals into moving traffic.
Measure the whole admission process during a realistic rehearsal. Include taking out identification, completing the approved check, presenting the ticket and handling an ordinary question. A scanner's fastest result won't tell you how quickly a staffed entrance can admit your actual audience.
Staff the referral process as well as the main lanes. If every uncertain case takes the same supervisor away from routine admissions, the remaining team may start rushing. Use our guide to check-in staffing and lanes for the broader capacity decision, then include the age-check tasks in your event-specific test.
Give the venue lead a way to see when conditions are deteriorating and decide what action is needed. That may involve redirecting arrivals, adding agreed staff or pausing admission under the established plan. Don't make the response "stop checking properly until the line gets shorter". The check needs to remain reliable during the period when most people arrive.
Record the outcome without collecting everyone's identity
Looking at age evidence doesn't automatically create a reason to keep a copy. Decide what information you need to run the event, resolve a dispute and meet applicable obligations. Ask your responsible adviser about the lawful basis, retention period and access controls before collecting additional personal information.
The UK's Information Commissioner's Office explains the data minimisation principle: personal information should be adequate, relevant and limited to what is necessary. For your operation, consider whether recording that a required check was completed is sufficient, rather than copying the document used.
For a disputed refusal, an operational record might include the time, entrance, relevant ticket reference, reason category, reviewer and action taken. Agree those fields with the responsible organisation. A full birth date, home address or document number should need a specific justified purpose rather than being collected out of habit.
Don't ask staff to photograph identification on personal phones or paste it into a general team chat. That creates copies you may struggle to control or delete. Use the approved record system and restrict access to the people handling the issue. Keep welfare information out of routine ticketing notes unless the responsible process requires it.
Tell attendees what happens to information you actually collect. If a digital verification provider processes data, understand its responsibilities and explain the relevant process accurately. Avoid claiming that no data is processed simply because your door team sees only an eligibility result. Check the whole arrangement before making that promise.
Rehearse a complete arrival before opening
Use an ordinary example rather than an elaborate emergency. Imagine a ticket holder arriving with evidence your policy accepts. Follow them through the identification check, ticket scan and any marker your venue uses. Ask the staff members to explain what they've established at each point.
Then change one fact. The customer has a valid ticket but only a screenshot of a document. Does the first checker know what to say? Can the reviewer be reached? Does the ticket remain in the correct state while the case is considered? Follow the process until the customer has a clear outcome.
Try a mixed-age example too if your event permits younger attendees. Someone is old enough to enter but doesn't meet the alcohol-service threshold. Confirm how that distinction reaches the bar team and what further checks remain necessary. Don't assume that a marker issued at admission settles every later sale.
Include shift changes and re-entry. Decide how the team confirms the right person is returning and whether another age check is required under your arrangements. A damaged or transferred wristband needs a defined review process. Staff should never have to infer a person's eligibility solely because they say they were inside earlier.
Finish with the person making the opening decision. They should know whether the equipment works, the responsible staff are present and the agreed policy can be followed. If a critical part isn't ready, identify who must resolve it before admissions begin. Opening on time doesn't make a missing control disappear.
Try this with a group booking
Imagine a hypothetical mixed-age music event where the venue permits younger attendees under agreed conditions. A buyer arrives with several friends and holds all their tickets. One person has acceptable evidence for the alcohol-service threshold. Another has acceptable evidence for admission but doesn't meet that higher threshold. A third has only a document photograph that your agreed policy doesn't accept.
The first task is to check each person's permission under the policy. The buyer's age and order confirmation don't settle the others' eligibility. Your team follows the agreed ticket sequence, applies the appropriate admission outcome for each person and refers the unresolved evidence to the supervisor. The people whose checks are complete shouldn't be confused with those still waiting for a decision.
Now follow the referred person. The supervisor confirms that the photograph doesn't meet the policy, explains the accepted alternatives and establishes whether an approved alternative is available. If it isn't, the supervisor communicates the decision and provides the customer-service route. Staff don't mark the person as age verified simply to close the enquiry, and they don't describe the document as counterfeit when the issue is that its presentation isn't accepted.
Finally, follow the attendees admitted inside. The bar team applies its own agreed service controls. The marker or ticket result must communicate only what it actually establishes. If someone changes clothes, loses a wristband or returns through another entrance, staff use the documented process rather than relying on a friend's account of the earlier check. Ask the venue to confirm that these handoffs meet its requirements before using this example as your rehearsal.
Review what the door team actually encountered
After the event, ask the entrance team which cases caused uncertainty and whether the written instructions answered them. Look for repeated problems, such as one misunderstood document rule or a reminder email that never reached group attendees. Those are practical improvements you can make before the next ticket goes on sale.
Compare the referral records with customer-service messages. A low number of complaints doesn't prove the process worked if staff quietly waved people through. A high number of referrals may reflect unclear information rather than poor checking. Read the reasons before deciding what to change.
Keep the next version specific. Update the accepted-evidence wording, improve the reminder or clarify the supervisor's authority where the review shows a gap. Retest any changed digital process with the provider. Ask the venue to confirm that the revised instructions still match its current requirements.
Before your next event, a buyer should be able to tell what they need to bring, and a staff member should be able to explain what happens if they don't. Start by agreeing that policy with the venue and security provider. Then run one realistic arrival all the way through it, including the difficult decision your team would otherwise have to improvise outside.
Author: By the Loopyah Content Team
The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.









