Close Out an Event

Work Through The Task

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, Close Out an Event narrows that work to post-event workflow for reconciling money, records, inventory, staff notes, and attendee obligations. Because this is a basics 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 Task Changes

This is a practical workflow. Read it from top to bottom the first time: the early checks set scope, the middle steps make the change, and the final checks prove the result. The intended readers are Event leads, Partner admins, and Finance staff. 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/settlements?id=:eventId, /rego/events/manage/finance-analytics?id=:eventId, and /rego/events/manage/inventory-tracking?id=:eventId.
• Records or contracts involved: Payments, Refunds, Settlements, Inventory, and Staff records.
• 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.

Follow The Work In Order

1. Confirm the exact scope before opening the tool: Begin by naming the Event Management situation, the owner, and the exact item involved in Close Out an Event.
2. Read the visible state before editing anything: Use /rego/events/manage/settlements?id=:eventId, /rego/events/manage/finance-analytics?id=:eventId, and /rego/events/manage/inventory-tracking?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Make only the change this guide describes: Keep Payments, Refunds, Settlements, Inventory, and Staff records in view so the work stays tied to the records or contracts it can affect.
4. Verify the result where another operator would look: 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.

Finish With Proof

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 - Anchor the work to one event. Open the event manage page after the event ends and confirm the correct event ID. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Review registrations, check-in totals, refunds, transfers, waitlist state, payments, settlements, inventory, POS, staff shifts, and communications. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Change only the intended event setting or record. Resolve open attendee obligations such as unpaid balances, pending refunds, unclaimed inclusions, or unresolved transfers. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Export or record required reports according to policy, then store them in the approved location. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Mark closeout notes, archive operational files, and remove old offline snapshots according to retention rules. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Have finance and event leadership confirm the event can be treated as closed. This leaves a handoff trail another operator can understand.

Why closeout matters

An event is not finished when the doors close. Money, refunds, inventory, staff notes, communications, and records still need review.

Closeout checklist

1. Action 1. Confirm all check-in records are synced. Confirm the visible event state before continuing.
2. Action 2. Review unpaid, overpaid, refunded, transferred, and cancelled registrations. Check the attendee or staff impact before moving on.
3. Checkpoint 3. Reconcile settlements and payment reports. Use it to confirm the work is still on the right path.
4. Action 4. Review inventory and POS records. Keep the event ID and public result in view.
5. Action 5. Check outstanding volunteer or staff notes. Confirm the visible event state before continuing.
6. Action 6. Archive or export only what policy allows. Check the attendee or staff impact before moving on.
7. Action 7. Record any post-event corrections. Keep the event ID and public result in view.
8. Action 8. Preserve evidence for finance or safety follow-up. Confirm the visible event state before continuing.

Common mistakes

• Assuming payment provider totals match dashboard totals without checking.
• Forgetting pending refunds.
• Leaving temporary staff data active.
• Not reviewing inventory shortages.
• Losing offline check-in files without syncing.