Event Management Data Records

Use This Reference Carefully

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 Data Records narrows that work to plain-language map of records created and changed by Event Management. 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 This Reference Collects

This page is for checking details. Use it to confirm names, routes, records, fields, or certification points before relying on memory. The intended readers are Support leads and Senior 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: Events, Registrations, Payments, Staff, and Inventory.
• 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 Find The Right Entry

1. Search for the exact name or route: Begin by naming the Event Management situation, the owner, and the exact item involved in Event Management Data Records.
2. Read the surrounding note, not only the matching line: 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. Compare the reference with the live screen, file, or service evidence: Keep Events, Registrations, Payments, Staff, and Inventory in view so the work stays tied to the records or contracts it can affect.
4. Save the evidence that proves the entry was checked: 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.

Confirm The Reference Still Matches Reality

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 - Choose the right path. Use this reference when you need to confirm a route, role, record, or certification expectation before acting. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Find the dashboard surface or record type involved in the current task. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Do the operating action. Compare what you see in /rego/events/manage?id=:eventId with the expected access, state, and records described here. This keeps the event state understandable before another setting changes.
4. Step 4 - Verify the result. If something does not match, stop the workflow and capture the route, event/report ID, user role, and visible error state. The next operator should be able to see why this step was taken.
5. Step 5 - Hand off remaining work. Return to the related operating guide after the reference question is answered. This leaves a handoff trail another operator can understand.

Record map

Record	Plain meaning
Event	Main event setup and public information record.
Tier	Base registration option.
Add-on	Optional item or purchase.
Inclusion	Item or entitlement included with a tier/package.
Registration	Attendee event record.
Payment	Money proof, balance, or provider-related record.
Refund	Money returned or intended to be returned.
Transfer	Registration ownership or assignment change.
Upgrade	Tier or package change.
Waitlist entry	Queue record when capacity or approval is constrained.
Dealer application	Vendor application record.
Volunteer application	Volunteer signup and review record.
Shift	Staff or volunteer schedule record.
Activity submission	Submitted activity/program entry.
Communication	Sent or previewed event message context.
Coupon	Discount or attendee-specific adjustment.
Affiliate record	Partner/source tracking entry.
Inventory item	Stock or fulfillment record.
POS sale	On-site sale record.
Offline snapshot	Export for offline check-in.
Settlement	Finance reconciliation record.
Analytics	Derived views from source records.

Support lead trace

Use this path when changing behavior:

page -> runtime module -> dashboard-data/helper/API -> database record -> audit/cleanup -> certification