Ticketing

End-user documentation

Ticketing / Event Pass

Event pass operations for venue areas, seating blocks, seats, passes, QR ticket rendering, approval, allocation, and email-blast workflows.

Purpose and What Problem This Solves

The Ticketing module gives event teams a structured place to create passes, manage venue seating, allocate tickets, send QR passes, and track approval workflows. It separates actual ticket/pass operations from broader promotional campaigns.

Who normally uses this module

What You Can Do Here

• Create venue areas, seating blocks, and seats.
• Build and manage Event Pass records.
• Allocate passes, add users, approve entries, and email QR tickets.
• Review seats and blocks for capacity planning.
• Prepare a foundation for scanner check-in and public checkout workflows.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

1. Set up venue areas, blocks, and seats before issuing passes.
2. Create the Event Pass record with event details, capacity, and rules.
3. Allocate passes or seats to the correct attendees or user groups.
4. Run approval and email-blast workflows only after reviewing recipient data.
5. Test QR rendering and sample email delivery before live distribution.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Set up venue seating

1. Create areas that match the actual venue layout.
2. Add blocks and seats using a naming convention staff can understand at the gate.
3. Check capacity totals against the venue plan.
4. Lock or review seating data before ticket allocation starts.

Issue event passes

1. Create the pass with event details, eligibility, dates, and seat or area rules.
2. Add or import users/attendees and validate emails.
3. Allocate passes or seats and run approval where required.
4. Send QR tickets after a sample email has been verified.

Handle pass corrections

1. Search by attendee, email, pass, seat, or QR reference.
2. Confirm the correction needed: name, seat, email, resend, or cancellation.
3. Apply the correction according to policy and avoid duplicate live passes.
4. Record the support note for gate or audit reference.

Industry Notes and Good Practice

• Venue data should match the real physical entry process. Confusing area/block/seat names slow down gate operations.
• Email-blast workflows should be treated like operational distribution, not marketing blasts. Accuracy matters more than volume.
• Keep pass allocation and promo campaigns separate: Ticketing issues access; Promos drives engagement.
• Test QR rendering before launch so staff know what a valid pass looks like.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

• Capacity from areas, blocks, and seats matches the approved event plan.
• Attendee emails are validated before QR distribution.
• Duplicate passes or seat conflicts are resolved before event day.
• Support corrections are logged and communicated to gate staff when needed.

Related ERPat areas

FAQ and Troubleshooting

Is this the same as Promos?

No. Ticketing manages passes and seating. Promos manages promotional campaigns such as raffles.

Why did someone not receive a QR email?

Check email address, allocation status, approval status, mail delivery logs, and whether the pass was included in the blast.

Can I change a seat after sending a ticket?

Follow event policy and make sure the old pass or seat assignment is no longer active.

What should beginners set up first?

Areas, blocks, seats, event pass rules, test attendee, and sample QR email.

ERPat Ticketing / Event Pass user guide. This static HTML page is documentation-only and does not change module routing, permissions, or runtime behavior.