Staff and Volunteer Lifecycle

Follow The Record Over Time

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, Staff and Volunteer Lifecycle narrows that work to departments, volunteer positions, applications, roster planning, publication, live shifts, and closeout. Because this is a lifecycles 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 Changes Across The Lifecycle

This page follows a record from one state to another. Read it as a timeline so handoffs, reversals, and closeout work stay understandable. The intended readers are HR leads and Volunteer coordinators. 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/human-resources?id=:eventId, /rego/events/manage/volunteer-positions?id=:eventId, and /rego/events/manage/staff-roster?id=:eventId.
• Records or contracts involved: Departments, Volunteer applications, Staff roster, and Shifts.
• 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.

Track Each State Change

1. Find the current state: Begin by naming the Event Management situation, the owner, and the exact item involved in Staff and Volunteer Lifecycle.
2. Read what must be true before the next state: Use /rego/events/manage/human-resources?id=:eventId, /rego/events/manage/volunteer-positions?id=:eventId, and /rego/events/manage/staff-roster?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Watch for side effects when the state changes: Keep Departments, Volunteer applications, Staff roster, and Shifts in view so the work stays tied to the records or contracts it can affect.
4. Keep the history clear for the next reviewer: 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.

The Lifecycle Is Clear When

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. Define roles, requirements, supervisors, shift times, and expected workload before opening volunteer applications. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Review applications against role needs and record approval, rejection, waitlist, or follow-up decisions. 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. Build the roster from approved people and confirm every live area has coverage. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. During the event, use live shift tracking for arrivals, no-shows, swaps, breaks, and escalations. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. After the event, reconcile hours, subsidies, incidents, and unresolved volunteer notes. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Archive or retain staff records according to policy and prepare lessons for the next event. This leaves a handoff trail another operator can understand.

Lifecycle overview

Stage	Meaning	Verify
Plan departments	Event roles and locations are defined.	Coverage needs are clear.
Open positions	Volunteer roles are created.	Expectations are written.
Review applications	Staff approve or reject applicants.	Remarks and decisions are recorded.
Build roster	Shifts are assigned.	No critical coverage gaps.
Publish roster	Staff can see duties.	Published state is intentional.
Track live shifts	Event day operations monitor coverage.	Live tracker reflects roster.
Close out	Notes and attendance are reviewed.	Future event lead can learn from records.