Event Management Glossary

Use The Terms In Context

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Event Management Glossary narrows that work to plain definitions for Event Management words, records, routes, and workflows. Because this is a reference page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What The Terms Are For

This is a lookup page, but the definitions still belong to real operations. Read the term, then connect it to the record, screen, file, or decision where the word appears. The intended readers are All event operators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage?id=:eventId.
• Records or contracts involved: Glossary terms.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

How To Read A Definition Safely

1. Find the exact term used by the system: Begin by naming the Event Management situation, the owner, and the exact item involved in Event Management Glossary.
2. Read the surrounding workflow: Use /rego/events/manage?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the term consistently in notes: Keep Glossary terms in view so the work stays tied to the records or contracts it can affect.
4. Ask for review when two terms sound similar: Before handing off, save proof such as event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

Before You Use A Term In A Note

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Confirm the term or page. Look up unclear words before operating the dashboard, especially status, scope, payment, check-in, appeal, or record terms. This anchors the work to the correct scope before any record changes.
2. Step 2 - Check the related context. Use the exact term from the dashboard when writing notes so another operator can find the same state later. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Apply the guidance. If two terms seem similar, open the related reference or lifecycle page before deciding. This keeps the event state understandable before another setting changes.
4. Step 4 - Return to the workflow. After the term is clear, return to the workflow page and complete the documented steps. This leaves a handoff trail another operator can understand.

Core terms

Term	Meaning
Event	The main record for an event.
Rego	Short for registration.
Tier	Main attendee registration option.
Add-on	Optional extra item or service.
Inclusion	Item or benefit included with a tier or package.
Conditions of Entry	Policies attendees must accept.
Check-in	Verifying and marking attendee arrival.
Offline snapshot	Controlled export for offline check-in.
Settlement	Finance reconciliation record.
POS	Point of Sales for on-site sales.
Dealers Den	Vendor/dealer application and registration area.
Volunteer position	Role people can apply to help with.
Staff roster	Shift schedule for staff or volunteers.

Status words

Term	Meaning
Draft/hidden	Not ready for attendees.
Published/visible	Attendee-facing information may be live.
Pending	Needs review, payment, or action.
Approved	Accepted by staff or system policy.
Cancelled	No longer proceeding.
Refunded	Money return was recorded or completed.