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 event dates, capacity, venue, ownership and lifecycle.
OverviewOpen event capacity×
Award / Competition Mgmt · Events
New
Open event capacity
Approval conditions
| Record number | Event name | Capacity | Starts at | Venue | Organization | |
|---|---|---|---|---|---|---|
| EVN-76240 | Event 667 | 190 | 24 Oct | VNS-6358 | ORG-3521 | |
| EVN-19067 | Event 696 | 660 | 05 Oct | VNS-3704 | ORG-6722 | |
| EVN-64858 | Event 999 | 110 | 05 Oct | VNS-1983 | ORG-8373 | |
| EVN-72556 | Event 964 | 850 | 24 Oct | VNS-8913 | ORG-2136 | |
| EVN-33614 | Event 202 | 950 | 25 Oct | VNS-9063 | ORG-1493 |
6 of 6 records
Event 667Events · EVN-76240
Capacity190
Starts at24 Oct
VenueVNS-6358
OrganizationORG-3521
What you can do
Give each event a clear operating record
The event record is the starting point for the program team. Name the event, choose the hosting organization and venue, assign its owner, and enter its start time and capacity. Add an end time when the operating window is known. A competition organizer might run an opening reception and a separate public ceremony; each event needs its own capacity and admission record if the team intends to manage those separately.
The owner uses the event status to distinguish a draft from a review item, an approved plan from an open event, and a finished event from a cancelled one. A status change should reflect a real decision. The revision identifies the version being reviewed, so the team can tell whether a decision belongs to the plan currently on screen.
How the work is organized
- Schedule. The Events page places event dates on a calendar and shows admission-hour activity beside capacity.
- Ownership. Each event has a linked person, organization and venue; those references keep follow-up responsibility clear.
- Lifecycle. Draft, Review, Approved, Open, Completed and Cancelled distinguish planning from live admission and closeout.
What to agree during setup
Decide who creates an event, who independently reviews it, and what evidence must accompany a change in capacity or venue. Set the hosting organization and its time zone before entering dates. Keep venue names and contacts current so the operations team is not working from a stale location note. Agree when an approved event may open for registration and who may cancel it after registration or admission activity exists.
Check the handoff on an actual case
Take a planned ceremony with a known room limit. The Event Owner enters the ceremony name, start time, venue, and capacity. The Event Reviewer compares the room and the proposed headcount and records a decision with a reason. The owner opens registration only after the plan is approved. During the event, the Admission Lead compares arrivals with the capacity strip and admission-hour bars. At close, the owner checks the admitted history before marking the event completed. A cancellation keeps earlier decisions and admission activity available for review.
What your team sees
- Upcoming event schedule — Scan approved and open events by start and end time, venue and capacity.
- Events awaiting review — Find proposed event plans that need a named decision.
- Event lifecycle board — Follow event status, owner, venue and capacity across the planning cycle.
Follow the work through
Start with event planning and review, then use registration and admission and closeout. Set access in roles.
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.
- People
- People records for award and competition operations: a platform user's membership in the hosting organization with role title, time zone and active state.
- 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 Owner
- , Event Reviewer, Admission Lead, Admin
Set up Award / Competition Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.