HR Roster and Shifts

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, HR Roster and Shifts narrows that work to eMS LAN guide for roster entries, live shift tracking, and HR state affected by offline operations. 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 HR leads and Volunteer 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/manage/human-resources?id=:eventId, /rego/events/manage/staff-roster?id=:eventId, and /rego/events/manage/live-shift-tracker?id=:eventId.
• Records or contracts involved: HR settings, Roster entries, and Shift tracking records.
• 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 HR Roster and Shifts.
2. Read the current state before changing it: Use /rego/events/manage/human-resources?id=:eventId, /rego/events/manage/staff-roster?id=:eventId, and /rego/events/manage/live-shift-tracker?id=:eventId 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 HR settings, Roster entries, and Shift tracking records 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 when staff operations run through EMS LAN.

1. Step 1 - Open the exact screen for the event. Confirm roster and shift devices use the correct event snapshot. This prevents staff activity from being logged under the wrong event.
2. Step 2 - Identify what the screen reads and writes. Check departments, roster entries, published roster state, shift times, and supervisors. This sets the staffing baseline.
3. Step 3 - Use one control at a time. Record arrivals, no-shows, swaps, breaks, and shift completion as they happen. This changes LAN-local shift state.
4. Step 4 - Check who or what was affected. Escalate uncovered areas, unknown staff, or role mismatches immediately. This protects onsite coverage.
5. Step 5 - Confirm the screen and history agree. Compare live shift state with supervisor notes during handoff. This catches missing staff records.
6. Step 6 - Leave notes another operator can follow. Give final staff notes to the reconciliation owner after import. This preserves staff accountability.

Common mistakes

• Treating roster changes as private notes instead of records.
• Forgetting no-shows and swaps.
• Not telling reconciliation staff which shifts were manually corrected onsite.