At an event, money is not lost only through major failures. It can disappear through dozens of small decisions made under pressure: an unauthorised refund, an incorrect ticket upgrade, a complimentary ticket given without approval, or a payment that is never properly reconciled.
One mistake may be insignificant. Repeated across a busy event, however, small errors can become a real financial leak.
The answer is not to expect staff to be perfect. The smarter approach is to build systems that make costly mistakes harder to make, easier to spot and quicker to correct.
Give Financial Decisions a Clear Owner
Many operational problems begin with unclear responsibility.
If several employees can approve refunds, change ticket types or provide complimentary access, customers may receive different answers depending on who they speak to. Worse, nobody may be certain who has the final authority.
Before the event, define who can approve what.
Frontline staff can handle routine problems, while unusual refunds, significant upgrades, complimentary tickets or other financially sensitive exceptions can require supervisor approval.
The exact limits depend on the event, but the principle is simple: Every important financial decision should have a clear owner. This protects revenue without preventing staff from solving ordinary customer problems quickly.
Make the Correct Action Easy
A busy event is a poor environment for complicated procedures.
Staff should not need to read a long manual when a customer is standing in front of them with a ticket that will not scan.
For common problems, give employees short instructions: What should I check? What can I resolve? When should I escalate?
For example, a failed ticket scan might require staff to check the ticket status and customer details before escalating the issue. A refund request might follow a defined approval process rather than being decided spontaneously at the entrance.
Good procedures should be tested before the event. If staff cannot follow them quickly during a briefing, they will be even harder to use when queues are forming.
Train for Problems, Not Just the Perfect Scenario
Training often focuses on how the event is supposed to work.
More valuable training prepares staff for when it does not.
Brief employees on realistic situations such as duplicate bookings, invalid or already-used tickets, incorrect ticket categories, payment problems, refund requests and difficult access cases.
Just as importantly, explain when they should not improvise.
A staff member may give away an upgrade simply because it seems like the quickest way to resolve a dispute. Clear escalation rules reduce this kind of well-intentioned but costly decision-making.
The goal is not to prepare employees for every imaginable problem. It is to prepare them for the problems they are most likely to encounter.
Let Technology Handle Repetitive Decisions
The more rules employees have to remember, the greater the opportunity for human error.
A properly configured ticketing system can validate ticket types, apply defined prices, record transactions and control access according to the rules set by the organiser.
This is particularly useful for repetitive decisions that do not require human judgement.
But automation only works when the underlying setup is correct. Ticket types, prices, permissions, refund rules and other important configurations should be checked and tested before the event.
Technology should reduce unnecessary human decisions—not simply automate a bad process.
Make the Money Reconcile
Where an event handles cash, establish clear procedures for receiving, recording, securing and reconciling it. Responsibilities should be appropriately separated where practical, particularly for higher-risk processes.
Digital payments reduce some risks associated with physical cash, but they do not eliminate the need for reconciliation.
After the event, compare relevant ticketing, payment, refund, discount and complimentary-ticket records.
If the numbers do not match, investigate while the event is still fresh.
The objective is not to assume someone is responsible for the discrepancy. It is to make sure every significant financial movement can be explained.
Treat Repeated Mistakes as a Process Problem
One employee making an error may simply be human error. Five employees making the same error is different.
Perhaps the ticket categories are confusing. Perhaps the instructions are unclear. Perhaps the software makes the wrong action easier than the right one. Perhaps staff are dealing with an unrealistic workload.
That is why a useful post-event review asks more than: Who made the mistake? It asks: Why was the mistake possible in the first place?
Fixing the underlying process can prevent the same problem from appearing at every future event.
Frequently Asked Questions
Q: Which staff mistakes can cost an event organiser money?
A: Common examples include incorrect ticket handling, unauthorised refunds or discounts, complimentary tickets issued without approval, payment discrepancies and errors in financial reconciliation.
Q: Should every staff member be allowed to issue refunds?
A: Not necessarily. Refund authority should follow the organiser's policies and risk controls. Routine cases can have a defined process, while unusual or higher-value refunds may require additional approval.
Q: How can staff avoid making expensive decisions under pressure?
A: Give them clear limits on what they can approve and a simple escalation route for anything outside those limits. The safer decision should also be the easiest one to follow.
Q: Can ticketing software reduce staff mistakes?
A: Yes. Properly configured systems can validate ticket types, apply pricing rules, control permissions and record transactions, reducing repetitive manual decisions. The configuration itself should be tested before the event.
Q: What should organisers do when the same staff mistake happens repeatedly?
A: Investigate the process rather than blaming individuals. Repeated errors can indicate unclear instructions, poor system design, insufficient training or an unrealistic workflow.
Q: How can organisers protect revenue without making staff procedures complicated?
A: Keep everyday procedures simple and place stronger controls around financially sensitive actions such as refunds, discounts, upgrades and complimentary tickets.
If you need additional advice or support, the TicketCRM team is always ready to help with your questions!