Create 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, Create an Event narrows that work to minimum safe workflow for creating an event before public registration opens. 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 Partner admins and Event 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/events/new and /rego/events/manage?id=:eventId.
• Records or contracts involved: Events.
• 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 Create an Event.
2. Read the visible state before editing anything: Use /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. Make only the change this guide describes: Keep Events 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 /rego/events/new after the event name, dates, venue, capacity, payment owner, and policy owner are known. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Create the event with only confirmed details and keep public visibility off until review is complete. 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. Open /rego/events/manage?id=:eventId and confirm the event ID is present in the URL. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Complete details, public information, registration settings, payment instructions, Conditions of Entry, and notification basics in that order. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Ask a second operator to review public copy, prices, dates, and policies before sharing links. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Publish only when the public event page, registration path, and dashboard records all match. This leaves a handoff trail another operator can understand.

Before creating

Gather the basics:

• Event name.
• Public name and internal name, if different.
• Dates and venue.
• Registration opening and closing target.
• Expected attendee capacity.
• Payment plan.
• Staff owner.
• Policies that must be accepted.

Creation steps

1. Action 1. Open /rego/events/new. Confirm the visible event state before continuing.
2. Action 2. Create the event with the minimum correct details. Check the attendee or staff impact before moving on.
3. Action 3. Open the manage overview. Keep the event ID and public result in view.
4. Action 4. Confirm the event ID is in the URL. Confirm the visible event state before continuing.
5. Checkpoint 5. Complete Details and Public Info. Use it to confirm the work is still on the right path.
6. Action 6. Configure registration before sharing any public link. Check the attendee or staff impact before moving on.

Common mistakes

• Publishing before prices are final.
• Creating public copy before Conditions of Entry are ready.
• Forgetting who owns finance review.
• Using a test event as the production event.
• Sharing a public link before staff have checked it.

Verification

After creation:

• Direct load of /rego/events/manage?id=:eventId works.
• Event appears in /rego/events.
• Event details show the right name and dates.
• Public visibility is intentional.