For most people, check-in is simple: Scan the ticket → Confirm the result → Admit the attendee

If something does not look right, move the person to your help point and use Solve Ticket Problems at the Gate.

Before you start scanning

Open the Tambala check-in page and make sure the correct event is selected.

If you are helping as a Teammate, sign in with your own Tambala account and use the access given to you by the organiser.

Do not use another staff member's account unless the organiser has specifically instructed you to do so.

Scan the ticket

Ask the attendee to have their Tambala ticket ready.

Then:

Open the Camera check-in option.
Point the camera at the ticket QR code.
Wait for Tambala to process it.
Check the result shown on screen.

If Tambala confirms the ticket is valid and unused, check the attendee in and allow them to enter.

Do not admit someone simply because the QR code looked genuine. Wait for Tambala to confirm it.

Keep the line moving

Most attendees should take only a few seconds to process.

If a QR code will not scan after a couple of attempts, do not keep the entire queue waiting.

Move the attendee to the help point and continue scanning the next person.

The help point can use Lookup (by name or email), manual ticket entry or another method to solve the problem.

This is one of the most important habits for a smooth gate.

Use Lookup when someone cannot show a ticket

If the attendee cannot find their QR code, use Lookup where available.

Search using the information Tambala allows, such as their name or email.

Confirm you have found the correct person and ticket before checking them in.

Use Lookup before creating a replacement or treating the person as a walk-in.

They may already have a valid ticket in the system.

Enter the ticket code manually when needed

If the QR image cannot be scanned but the ticket code can still be read, use the manual Token option where available.

Enter the code and wait for the result.

Treat the result exactly like a camera scan.

Only admit the attendee when Tambala confirms the ticket.

Check groups one ticket at a time

One person may have bought several tickets for family or friends.

Each ticket represents an entry.

Make sure each person has a valid unused ticket unless Tambala provides a specific group check-in option.

If Tambala shows related tickets from the same order, use that information to see which have already been used and which remain available.

Do not assume that one QR code admits the whole group.

Pay attention to ticket types

The check-in result will show the ticket type.

This can help staff identify people who need a different entry route, badge or experience, such as VIP attendees.

Make sure the attendee receives what their actual ticket allows.

Do not upgrade someone at the gate simply because they ask.

If a change is needed, send them to the event manager.

Handle walk-ins through the manager

If someone arrives without a ticket, first check whether they already purchased one.

Use Lookup.

If no ticket exists and the event accepts walk-ins, send the attendee to the designated manager or walk-in point.

Walk-ins should be recorded properly through Tambala where that option is available.

Do not let people into a paid event informally simply because the queue is busy.

Use batch check-in only where appropriate

If Tambala provides batch check-in, a trusted event manager may use it for organised groups.

This can be useful when several valid ticket codes need to be processed together.

It should not be used to bypass normal ticket verification.

If one of the tickets fails, investigate that ticket separately.

Work safely across several devices

Several teammates may be scanning tickets at different gates.

Make sure everyone is working on the same event.

If Tambala shows that a ticket has already been used, treat it as used even if another teammate or device performed the first check-in.

Do not assume your scanner is the only source of truth.

Watch the live numbers

Tambala will show how many tickets have been checked in and how many remain.

Use this during the event.

If a large number of people are still expected, you may need to keep more scanners open.

If queues are building, move another trained teammate to the main line where possible.

The numbers can also help the organiser understand how attendance is progressing.

Do not make exceptions casually

Gate staff will sometimes hear:

“My friend already went inside with the ticket.”

“I paid, but I cannot find it.”

“I know the organiser.”

“Just let me through and I will sort it later.”

Do not make the decision based only on the story.

Check Tambala records.

If the answer is unclear, send the person to the manager.

This protects the event and also protects the attendee whose ticket may have been copied or used by someone else.

After the rush

When arrivals slow down, check that devices are still connected and that check-ins are recording correctly.

If a teammate's device has stopped working, move them to another check-in point rather than letting them continue with an unreliable process.

At the end of the event, the organiser can review the final check-in numbers and any unresolved cases.

The important thing to remember

At the main gate, your job is simple:

Valid and unused → Check in.

Unclear or failed → Send to help.

Do not turn the main queue into a support desk.

A fast gate comes from separating normal entry from unusual problems.

For any ticket that does not pass normally, use Solve Ticket Problems at the Gate.

For preparing staff, devices and permissions before the event, see Prepare Your Event Check-In.