These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Event + Ticketing + CRM + Analytics
- Features
- Event Planning
Event Planning
Set an event's schedule, capacity, venue and accountable owner.
OverviewOpen events×
Event + Ticketing + CRM + Analytics · Event Planning
New
Open events
Approval conditions
| Record number | Subject | Capacity | Starts at | Counterparty | |
|---|---|---|---|---|---|
| EVN-66179 | Open evn-161 | 90 | 25 Oct | VNS-8213 | |
| EVN-23947 | Open evn-305 | 160 | 05 Oct | VNS-1053 | |
| EVN-24294 | Open evn-982 | 840 | 09 Oct | VNS-6852 | |
| EVN-55584 | Open evn-706 | 100 | 10 Oct | VNS-8210 | |
| EVN-50294 | Open evn-753 | 800 | 11 Oct | VNS-6993 |
6 of 6 records
Open evn-161Events · EVN-66179
Capacity90
Starts at25 Oct
CounterpartyVNS-8213
What you can do
Plan the operating window
The event owner starts with a subject, a record number, a start time and capacity. The event also belongs to an organization and names a venue and team member. These details give the admission team a specific operating scope. A calendar entry without an owner or venue is hard to act on when attendees arrive. The owner should confirm the time zone with the organization before publishing the schedule to the team.
An event can remain in Draft while its owner checks the operating plan. Review is a distinct step: the owner submits a revision, and an independent reviewer records a decision against that revision. After approval, the owner can open the event for admission. The event record then provides the parent for admission lines, scans, payment evidence, attachments and operation receipts. Those links matter when the team later explains why a ticket was admitted or why a capacity claim was held.
How the work is organized
- Preparation. Keep the subject, schedule, venue, organization and capacity together before asking for review.
- Decision. Record the reviewer and source revision so a changed draft cannot borrow an older approval.
- Execution. Open approved scope, then reconcile admissions and payment evidence before closing it.
What to agree during setup
Choose who may own events in each organization and who can review that owner’s submissions. Confirm how the venue code and eligibility note will be maintained. Agree when a session is considered complete and who decides to cancel it. The start and end time should represent the actual admission window the operations team will use. If the event spans time zones, the organization and team member time zones should be checked together during the pilot.
Set a practical capacity policy before the first open event. An operator should know whether a reserved admission line still counts when no one has checked in. Keep a correction path for a changed time or venue after review. A revision change should prompt a new decision before execution continues.
Check the handoff on an actual case
For a Saturday concert, the event owner prepares a venue, a start time and a capacity of 300. The independent reviewer checks that exact revision and records the decision. The owner opens the approved event. The admission operator then selects the event explicitly before recording a reservation or scan. If the venue changes after approval, the owner submits the revised event for another decision. At close, the reconciliation lead compares admitted quantities with verified provider captures. The completed event retains its original admission history.
What your team sees
- Event calendar — Scheduled approved and open events with their start, end and venue.
- Events awaiting review — Event revisions waiting for an independent decision.
- Event status board — Draft through completed work grouped by its current state.
Follow the work through
Follow event preparation and event closure. The data model shows the event’s linked records.
What it keeps track of
Data model- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Organizations
- Operating organizations that own events, venues and team members.
- Team members
- Staff membership linking a platform user to an organization and role.
- Venues
- Physical or virtual venues and resource providers used by events.
- Review decisions
- Independent reviewer decisions recorded against a source revision.
- Admissions
- Reserved and admitted admission lines for an event.
- Ticket scans
- Ticket scan records submitted for review and completion.
Who uses it
Permissions- Event Owner
- , Independent Reviewer, Admission Operator, Reconciliation Lead, Admin.
Set up Event + Ticketing + CRM + Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.