QR code ticket check-in: a small-event door checklist

QR code ticket check-in needs a clear answer before each person enters: does this ticket permit admission to this event, and has that admission already been used? Prepare the device, rehearse the results and give unresolved cases a separate place to wait.

For a small workshop, studio masterclass or seated performance, one organizer may handle the scanner while a colleague welcomes arrivals and answers directions. If you are still setting up the event page and sales, start with the workshop ticket checklist.

Decide what a successful check-in means

Write one admission rule for the session. For example: each issued ticket admits one participant to the printmaking workshop on 18 November, and entry is recorded once. Decide how you will handle late arrivals and anyone who leaves and asks to return. Check the provider's supported rules before promising re-entry.

A QR code carries data, such as a ticket identifier or private link. The admission service must then check the ticket against its records and record the accepted entry. Creating a QR image with a generic generator does not create an issued admission or maintain a record of its use.

Keep three results distinct during rehearsal: accepted now, already admitted and unresolved. A camera recognizing the pattern, a phone vibration or an opened web link does not by itself prove that the admission record changed. Read the actual result before waving the person through.

The Hebrew Takbull scanning guide describes its checks for ticket validity and prior use, followed by a status update. Check ticket validity, prior use and operator permissions with your own provider.

Assign the scanner and the exception decision

Name the person permitted to operate the scanner and the person who resolves unclear bookings or payments. At a very small event, both jobs may belong to the owner. Have a helper direct the queue while the owner investigates so that the discussion does not happen across arriving guests.

Check permissions using the intended operator's account on the actual phone. Some services provide staff scanner roles; others restrict admission to the owner. Do not share an owner's password to work around a missing role. If your service only permits one operator, plan a single controlled entry point and give helpers tasks that do not require admission access.

Write down who can approve a ticket replacement, check a payment or decide a late-arrival exception. Approval still needs a usable admission record. An organizer saying “I know this person” should lead to the agreed verification process and a recorded decision, with the venue's participant limit preserved.

Use this before-doors checklist

Run the checklist where people will enter, with the actual lighting and network. Ticket Tailor's preparation guide tells its users to load the relevant event door lists in advance and check event access. Follow your provider's preparation steps; a downloaded list does not establish that every admission function works without a connection.

Check	Evidence to look for before opening
Event selection	The scanner shows the correct session, date and location
Operator access	The intended account can perform the permitted admission action
Camera	Permission works and a test ticket scans in the entrance lighting
Power	Phone is charged, with a tested charger or power bank available
Connection	The admission service responds from the entrance on the intended network
First use	A supported test admission changes to the expected used state
Second use	The same ticket cannot silently admit another participant
Unavailable ticket	A cancelled or invalid test ticket receives a distinct result
Recovery	The organizer can use the documented ticket lookup or replacement route
Queue	Guests needing help can step aside without blocking entry or the exit

Use a supported test mode or clearly identified organizer-controlled tickets. Keep rehearsal admissions separate from the event's attendance count. If your provider has no test mode, ask how to rehearse without consuming a real attendee's ticket. Do not assume that a used ticket can be reset.

Give arrivals a short, repeatable sequence

Ask the guest to open their ticket before reaching the scanning point. Keep a printed event name and arrival instructions visible, without displaying a real ticket code. People who cannot use a phone need a documented alternative that the provider and organizer can support.

At the scanner, follow this sequence:

1. Confirm that the person is attending the selected session.
2. Ask for one participant's ticket and scan it through the approved admission tool.
3. Read the returned state and wait for a definite accepted result.
4. Let that participant enter and direct them to the correct room.
5. Refer any unclear result to the named organizer before accepting another admission from that ticket.

If a buyer purchased several places, check how many individual admissions were issued. One order number may cover several people. Match each arriving person to an unused admission through the provider's supported flow. If companions arrive separately, explain how each can access their own ticket without sharing the same code repeatedly.

Avoid reading email addresses aloud or showing the guest list to the queue. Move a booking lookup to the side and use only the details needed to find and verify the relevant record. Keep private ticket links out of shared chat groups and promotional screenshots.

Keep an exception table beside the scanner

Adapt the labels below to the states your tool actually displays. Use the table to agree on actions and responsibilities.

Result or problem	Action at the entrance	Who resolves it
Valid and accepted now	Admit the person attached to that unused admission	Authorized scanner operator
Already used	Pause; check the earlier entry and whether the wrong ticket was shown	Designated organizer
Missing email or unreadable screen	Use the supported lookup or private recovery route; verify the matched record	Organizer with the required access
Payment pending	Check the trusted payment record; wait for valid admission issuance	Person responsible for payment confirmation
Cancelled or revoked	Keep entry paused; investigate the cancellation and current entitlement	Designated organizer
Wrong event or date	Find the correct booking or explain the mismatch privately	Designated organizer
Timeout or lost connection	Treat the outcome as uncertain and follow the tested recovery plan	Authorized operator and organizer

An already-used result can follow an accidental repeat scan, a companion presenting the wrong code or someone sharing a screenshot. Establish what happened before making an accusation. Check the prior admission information the service makes available, then use its documented replacement or recovery process if needed.

Check a payment screenshot against the collection record, then confirm the existing order through the agreed process. Avoid asking for another payment while the first remains unresolved. A free or complimentary ticket should still have its own issued admission and recorded entry.

Rehearse a connection failure before guests arrive

Test the connection at the actual door, then test the provider's documented recovery behavior. Decide which phone or network you can switch to, who makes that decision and how to prevent two people from acting on an uncertain scan. Never record an unknown outcome as a successful entry merely to keep the line moving.

If the screen times out after a scan, the service may already have recorded the admission. Check the existing result before starting a fresh admission attempt or replacing the ticket. Where the tool provides a retry action, follow that documented route. A later “already used” message needs checking against the unresolved scan and the person still waiting in front of you.

Offline admission requires explicit provider support and its own operating procedure. A saved guest list or cached QR image cannot establish whether another device has just accepted the same ticket. If the service requires a live connection, pause entry until an authorized operator can verify and record admission. Keep guests informed and the entrance clear while the organizer restores the connection.

Work through a 24-person arrival example

Suppose a fictional workshop has twenty-four issued admissions. At 17:50, eighteen participants have been accepted. The remaining six admissions are unused. Count the exception cases separately from the eighteen people already inside.

A buyer arrives with a companion but shows a ticket that was already used by someone in their party. The organizer finds the second, unused admission in the same order and checks in the companion through the supported process. The count becomes nineteen. The first ticket remains used.

Next, a guest cannot open the confirmation email. The organizer locates and verifies an unused admission through the documented recovery route, then records the entry. The count becomes twenty. A third guest's scan times out. The operator checks the existing record and confirms that this guest's admission was accepted during that attempt. The guest enters; the count becomes twenty-one.

Three issued admissions remain unused: 24 − 21 = 3. The timeout did not create a second entry, and the order with two tickets did not become a single admission. A buyer still awaiting payment would remain outside this issued-admission total until the relevant confirmation and issuance were complete.

Put the final door plan in the operator's hands

Before opening, give the operator the event name, arrival window, approved scanning steps, exception contact and connection recovery procedure. Add a short instruction for guests: “Please open your ticket before reaching the entrance. If you cannot find it, speak to the organizer beside the check-in point.”

For an event you hope to manage with Skedful, contact the team with your date, country, number of admissions and door setup. Confirm ticketing availability, who may operate admission and the supported recovery process before committing to that setup.