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.
Feature · Events
Example screen with sample data
Events
Plan schedules, capacity and responsibility for each program.
OverviewOpen Events×
Live Event Streaming · Events
New
Open Events
Approval conditions
| Record number | Subject | Status | Starts at | Ends at | Capacity | |
|---|---|---|---|---|---|---|
| EVN-90599 | Open evn-490 | Open | 17 Oct | 25 Oct | 110 | |
| EVN-64730 | Open evn-256 | Open | 27 Oct | 29 Oct | 420 | |
| EVN-65681 | Open evn-162 | Open | 03 Oct | 07 Oct | 820 | |
| EVN-36106 | Open evn-965 | Open | 09 Oct | 18 Oct | 840 | |
| EVN-65856 | Open evn-649 | Open | 09 Oct | 16 Oct | 590 |
6 of 6 records
Open evn-490Events · EVN-90599
OpenStarts at17 Oct
Ends at25 Oct
Capacity110
CounterpartyVNS-7576
What you can do
Plan the event record
An Event Manager starts with the program subject, a start time, capacity and the organization responsible for the event. The owner is a Team Member and the counterparty is a Venue. That combination makes the schedule more useful than a date alone: admissions staff can identify who can answer a capacity question, and the reviewer can see which organization will run the program. The Events page shows a calendar, capacity strip and admission-hour bars, with the selected event detail below the visualization.
The event record has draft, review, approved and open states for the team to use as work progresses. Keep the revision with the decision. If the owner changes the program after review, the team needs to know which version the reviewer actually saw. A reviewer can return an event for correction and state the reason in Review Decisions. The owner then resolves the point before the event is opened.
How the work is organized
- Schedule. starts at and ends at describe the planned interval for the event.
- Capacity. Capacity sets the number the admissions team must reconcile against reserved quantities.
- Responsibility. Organization, Owner and Counterparty connect the program to the operating team and venue.
What to agree during setup
Agree who may create an event, who reviews it and who opens admission. Decide whether a returned decision sends the current draft back to the same owner. Establish the time zone for each Organization so the schedule is read consistently. Keep a named owner for every event and a usable venue record before the first rehearsal.
Check the handoff on an actual case
Suppose an organizer plans a panel with a fixed room capacity. The Event Manager enters its start and end time, selects the venue and submits the current revision for review. The Event Reviewer examines capacity and venue eligibility, then records an approve or return decision with a reason. Once approved, admissions staff can work against the open event. If the venue changes later, the team reviews the changed record rather than treating the earlier decision as approval of the new venue. At closeout, the owner checks admissions and payment evidence before marking the event completed.
What your team sees
- Upcoming Event Schedule — Dated approved and open programs, with their venue and owner.
- Events Awaiting Review — Programs whose current state calls for a reviewer.
- Open Events — Programs for which the admissions team is working.
Follow the work through
See event preparation and admissions.
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.
Who uses it
Permissions- Event Manager
- , Event Reviewer, Admissions Coordinator, Admin.
Set up Live Event Streaming your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.