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.
- Community Event Platform
- Features
- Event planning
Event planning
Define each event with its owner, organization, group and capacity.
OverviewOpen event calendar×
Community Event Platform · Event planning
New
Open event calendar
Approval conditions
| Record number | Name | Event date | Ends at | Capacity | Organization | |
|---|---|---|---|---|---|---|
| CE-32991 | Event 355 | 18 Oct | 23 Oct | 910 | ORG-3003 | |
| CE-71587 | Event 530 | 27 Oct | 05 Nov | 20 | ORG-3061 | |
| CE-23449 | Event 902 | 19 Oct | 23 Oct | 780 | ORG-5417 | |
| CE-59258 | Event 516 | 07 Oct | 16 Oct | 940 | ORG-2632 | |
| CE-23866 | Event 264 | 22 Oct | 30 Oct | 350 | ORG-6387 |
6 of 6 records
Event 355Community events · CE-32991
Event date18 Oct
Ends at23 Oct
Capacity910
OrganizationORG-3003
What you can do
Keep the operating record clear
The Event Owner keeps the event name, date, capacity, organization, owner and community group together. The selected event is the parent for registrations, admission lines and evidence. Before requesting review, the owner checks that the group belongs to the organization and that the capacity matches the planned setting. The revision distinguishes the scope being reviewed from later edits.
How the work is organized
- Draft and review. The owner prepares the event and supporting evidence before an Independent Reviewer decides its current revision.
- Open admission. An approved event moves to Open only after its reviewed scope is checked.
- Keep the parent visible. The Community Events Workspace shows a calendar, capacity strip and admission-hour bars beside the selected event; actions use that explicit selection.
What to agree during setup
Choose who owns a proposed event and who reviews it independently. Agree which organization may use each community group, how capacity is set and when an event should move into review. Use one real upcoming event for the rehearsal, including its date, location context and person accountable for it.
Check the handoff on an actual case
A neighborhood workshop is entered for a Saturday with a named owner and a community group as its setting. The owner checks the date, capacity and organization before sending it for review. The reviewer reads the same event revision and records a decision. Once approved, the owner can open admission. If the event changes in the meantime, the earlier decision should not silently authorize the new scope.
The workshop example also gives staff a useful change test. After the reviewer decides the first version, change the capacity or date and try to open the event using the earlier approval. The action should require a decision on the new revision. Keep the older decision linked to the scope it actually covered. When the event is open, select it in the Community Events Workspace and compare the calendar date and capacity strip with the saved event before taking registrations. This rehearsal makes the opening handoff visible to both the owner and admission staff.
What your team sees
- Event lifecycle board — Event records grouped by status, with the owner and capacity visible before opening.
- Open event calendar — Open events placed by date so staff can select the event before admitting people.
Follow the work through
- Event approval connects the draft and reviewer decision.
- Registration to admission follows the participant request and capacity.
- Event closeout reconciles admission and provider evidence.
Check the record definitions before importing active work.
What it keeps track of
Data model- Community events
- Programs, events and sessions with capacity, lifecycle and revision.
- Organizations
- Operating organizations that own events, venues and team members.
- People
- Staff membership linking a platform user to an organization and role.
- Community groups
- Physical or virtual venues and resource providers used by events.
- Evidence documents
- Uploaded evidence files linked to an event with visibility scope.
Who uses it
Permissions- Event Owner
- Prepares the event.
- Independent Reviewer
- Decides its current scope.
- Admin
- Manages access.
- Registration Coordinator
- And Admission Steward use the approved event after opening.
Set up Community Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.