Event Management Documentation

Choose Your Starting Point

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 Documentation narrows that work to a staged guide for running Furries PH partner events safely, clearly, and accountably. Because this is a start 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 Section Helps You Decide

This is the map page. Start here when you know the general area but not the exact guide. The page should help you choose the next safe reading path before opening a dashboard screen, file, or service route. The intended readers are Partner admins, Event leads, Operations staff, and Support leads. 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, /rego/events, /rego/events/new, and /rego/events/manage?id=:eventId.
• Records or contracts involved: Events, Registrations, Payments, Staff records, 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.

A Natural Way Through The Section

1. Name the situation in front of you: Begin by naming the Event Management situation, the owner, and the exact item involved in Event Management Documentation.
2. Match it to the closest guide group: Use /rego, /rego/events, /rego/events/new, and /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. Open one guide at a time: Keep Events, Registrations, Payments, Staff records, and Inventory in view so the work stays tied to the records or contracts it can affect.
4. Return here when the work changes shape: 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.

Leave This Page With A Direction

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. Start at this guide home and choose the stage that matches your job: foundations, basics, surfaces, best practices, lifecycles, or reference. This anchors the work to the correct scope before any record changes.
2. Step 2 - Confirm scope and records. Open the linked dashboard surface only after you understand the purpose and risk of that workflow. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Do the operating action. Follow the page-specific operator runbook before changing records. This keeps the event state understandable before another setting changes.
4. Step 4 - Verify the result. Use related links when a step touches another workflow, such as payments, check-in, appeals, or record maintenance. The next operator should be able to see why this step was taken.
5. Step 5 - Hand off remaining work. After finishing work, verify the dashboard state and record any follow-up for the next operator. This leaves a handoff trail another operator can understand.

What this guide is for

Event Management is the dashboard area partners use to create events, open registration, manage attendees, take payments, run check-in, coordinate staff and volunteers, handle Dealers Den, send communications, track inventory, and close out records.

This guide teaches the system in stages. It starts with beginner concepts, then moves into safe operating steps, feature guides, best practices, lifecycles, and support lead references.

Learning stages

Stage	Read when	Pages
Foundations	You need the basic ideas first.	What Is Event Management?, Event Accountability, Records and Public Pages
Safe basics	You need to run normal event work.	Create an Event, Configure Registration, Run Check-In, Close Out an Event
Dashboard surfaces	You need to understand each page.	Overview and Lists, Details and Public Info, Rego Config, Dealers Den, Check-In and Snapshots
Best practices	You need safer judgement.	Event Setup Planning, Payments and Refunds, Check-In and Privacy, Attendee Communications
Lifecycles	You need to know how records move over time.	Event Lifecycle, Registration Lifecycle, Payment and Refund Lifecycle, Post-Event Maintenance
Reference	You need exact routes, roles, records, or certification checks.	Route Map, Role Access Matrix, Data Records, Certification Checklist, Glossary

Dashboard surface groups audited

• Event entry routes: /rego, /rego/events, /rego/events/new, /rego/regos.
• Event setup: manage overview, details, rego config, Conditions of Entry, notifications, Google Wallet.
• Registration operations: regos, registrants, waitlist, upgrades, transfers, refunds, coupons.
• Dealers Den: settings, applications, registrations, packages, acknowledgements.
• Staff operations: Human Resources, volunteer positions, volunteer applications, staff roster, live shift tracker.
• Activities and submissions: activity forms, submissions review, approved submissions.
• Communications and finance: communications, affiliates, payments, settlements, analytics.
• Inventory and POS: inventory analytics, inventory tracking, inclusion claim, Point of Sales.
• Offline operation: check-in, offline snapshot, snapshot history.

Core rule

Every event change should answer four questions:

1. Question 1. What attendee or staff experience does this change? Write the answer before choosing the next action.
2. Question 2. What record or money movement does this change? Write the answer before choosing the next action.
3. Question 3. Who is responsible for checking it? Write the answer before choosing the next action.
4. Question 4. How can a future event lead verify what happened? Write the answer before choosing the next action.