Staffing and Volunteering

Use This Dashboard Area Safely

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Staffing and Volunteering narrows that work to workspace guide for local staffing and volunteering views imported from regosite workflows. Because this is a surfaces page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. 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 The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Staff leads, Volunteer leads, and Workspace 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: /workspace/:eventId/staffing and /workspace/:eventId/volunteering.
• Records or contracts involved: Imported roster assignments, Staff assignments, and Volunteer assignments.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Staffing and Volunteering.
2. Read the current state before changing it: Use /workspace/:eventId/staffing and /workspace/:eventId/volunteering to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Use the smallest action that matches the task: Keep Imported roster assignments, Staff assignments, and Volunteer assignments in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Before You Leave The Screen

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 offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook for workspace staffing or volunteering.

1. Step 1 - Open the exact screen for the event. Open the workspace staffing or volunteering surface for the correct imported event. This ensures assignments match the event.
2. Step 2 - Identify what the screen reads and writes. Confirm the user is signed in as the correct local operator and their imported assignment is visible. This prevents wrong-person assumptions.
3. Step 3 - Use one control at a time. Use the page to inspect current assignment, shift timing, role, location, and event information. This gives the operator their task context.
4. Step 4 - Check who or what was affected. Escalate missing assignment, wrong role, wrong location, or stale shift information to the roster lead. This protects coverage.
5. Step 5 - Confirm the screen and history agree. Confirm any roster correction appears in admin roster or live shift tracker if changed by a lead. This keeps staff views aligned.
6. Step 6 - Leave notes another operator can follow. Send the operator to their lane or record the unresolved issue. This finishes the staffing check.

Use this when

1. Action 1. Staff need their shift details without opening admin tools. Confirm the event ID, file, or device state before continuing.
2. Action 2. Volunteers need local assignment confirmation. Check the offline proof before moving on.
3. Action 3. Leads need to confirm whether imported roster data is visible to operators. Keep the sync history or import summary visible.