An internet connection is easy to ignore when it works.
Tickets are scanned, payments are processed, staff communicate, customer records update and sales data appears on screen without anyone thinking about the network underneath it.
Then the connection disappears.
At an event, that can quickly become more than a technical inconvenience. A failed connection can affect entry, payments, communication and access to operational information at exactly the moment when the team has the least time to solve the problem.
The answer is not simply to buy a faster connection.
It is to design the event so that one network failure does not become a failure of the entire operation.
Know What Depends on the Internet
The first step is to map your dependencies.
Ticket scanning may require a live connection, or it may support offline validation depending on the ticketing platform. Payment terminals may have their own connectivity requirements and offline capabilities. Staff may rely on cloud-based communication tools, while event managers may depend on online dashboards for sales and attendance information.
These systems do not all behave in the same way when the connection disappears.
Before the event, identify the critical systems and ask: What stops working if the internet disappears for ten minutes? What about one hour?
That simple exercise often reveals vulnerabilities that are otherwise invisible.
Check Whether Ticket Scanning Has an Offline Mode
Ticket entry is usually the most urgent concern because a connectivity problem can immediately become a physical queue.
Some ticketing systems can download the information required to validate tickets onto scanning devices and continue checking tickets when the connection is unavailable. Other systems may depend more heavily on live connectivity.
There is no universal offline method.
Even systems that support offline scanning can have limitations. For example, when multiple scanners operate independently without synchronising, duplicate-use information may not be shared between devices until they reconnect.
That means the important question is not simply: “Does our ticket scanner work offline?”. It is: “Exactly what can it validate offline, and what happens when several devices are offline at the same time?”
Find out before the event and test it at the venue.
Load What You Need Before Doors Open
If your ticketing system supports offline operation, preparation matters.
Devices may need to download ticket or attendee information while they still have a reliable connection. If the device has never loaded the necessary data, there may be nothing useful for it to fall back on when the network disappears.
This is particularly important at venues where mobile coverage is weak, such as basements, remote sites or large structures that interfere with signal.
The practical lesson is simple: Do not wait for the network to fail before preparing the offline system.
Open and test the relevant scanning software before customers arrive, and make sure staff know whether devices need to remain open or connected in a particular way for offline operation to work.
Have a Second Way to Connect
For an event where connectivity is operationally critical, a backup connection can be valuable.
Depending on the venue, this could involve a second fixed connection, another mobile network or another appropriate connectivity service.
The exact solution depends on the site.
What matters is avoiding a single point of failure where every scanner, payment terminal and staff device depends on one router or one network connection.
But there is an important distinction: A backup connection is only useful if the critical equipment can actually use it.
Test the failover with the real devices before the event. A spare SIM card sitting in a drawer is not a tested contingency plan.
Keep Critical Information Available Without the Cloud
An outage is much easier to manage when the information staff need is still accessible.
Important operational information should not exist only inside an online system that may become unreachable.
Depending on the event, this could include venue contacts, emergency procedures, staff assignments, supplier numbers, access rules, escalation contacts and instructions for dealing with ticketing problems.
This does not mean printing every piece of data you have.
It means identifying the small amount of information that would be genuinely difficult to operate without.
And if offline copies contain personal information, protect them appropriately. UK data-protection guidance emphasises the need to maintain confidentiality, integrity and availability of personal data and to have measures that allow access to be restored after technical incidents.
A backup should be useful without becoming a new security problem.
Give Staff a Communication Backup
The event may still be running even if your normal staff communication system is not.
If teams normally use an internet-based messaging platform, decide in advance what they will use if it becomes unavailable.
For some events, mobile calls or SMS may be sufficient. Larger or more operationally complex events may use radios.
The technology matters less than the structure.
Staff should know who is coordinating the response, who can authorise changes to entry procedures and where technical problems should be reported.
When the network fails, you do not want twenty people independently trying to solve the same problem.
A contingency plan needs an owner.
Protect the Entrance From the Outage
The biggest operational mistake is allowing a technical problem to become a queue problem.
If scanning continues offline, use the approved offline procedure.
If scanning cannot continue normally, move uncertain cases away from the main flow and use the event's predefined contingency process.
Do not let one customer with a complicated ticket stop dozens of people behind them.
And do not simply abandon access controls because the system is unavailable.
A good contingency process should balance two objectives: keep legitimate customers moving while maintaining reasonable control over admission.
Reconcile Everything When the Connection Returns
Getting back online is not the end of the incident.
If scanners worked offline, confirm that their records have synchronised successfully. If multiple devices operated independently, check that the resulting attendance records are consistent.
Do the same for any transactions or operational changes that were processed during the outage.
Look for missing records, duplicate entries or transactions that require reconciliation.
This matters because offline operation can temporarily create multiple independent versions of what happened.
The system needs to return to one reliable record.
Recovery is part of the contingency plan, not an administrative task for later.
Test the Failure Before It Happens
The best time to discover that your backup plan does not work is during a controlled test.
Simulate a connectivity failure before the event.
Disconnect a scanner. Test the backup network. Confirm what happens to ticket validation. Test the payment contingency with the provider's approved procedure. Make sure staff can still communicate. Then restore the connection and verify that data synchronises correctly.
This is particularly important because resilience is not just about having backup technology. It is about knowing that the complete process works.
The ICO recommends testing security measures and making improvements where tests reveal weaknesses.
A contingency plan becomes valuable when it has been rehearsed.
Frequently Asked Questions
Q: Can tickets still be scanned if the internet goes down?
A: Sometimes. It depends on the ticketing platform and its offline capabilities. Some systems can validate tickets using information stored on the device, while others require a live connection. Confirm the exact behaviour of your system and test it before the event.
Q: Is a backup internet connection enough?
A: Not by itself. The backup needs to work with the actual devices and systems that depend on connectivity. Test the failover at the venue before the event.
Q: Will card payments work without internet?
A: Not necessarily. Offline payment capabilities vary by provider, terminal and transaction type. Confirm the specific rules with your payment provider rather than assuming offline payments are available.
Q: What should staff do if they cannot verify a ticket?
A: Follow the event's predefined contingency procedure and move uncertain cases to the appropriate support point where possible. Staff should not invent new access rules during an outage.
Q: What should happen after the internet comes back?
A: Confirm that offline scans and other transactions have synchronised correctly, investigate missing or duplicate records and make sure critical systems have returned to their normal state.
If you need additional advice or support, the TicketCRM team is always ready to help with your questions!