Surfaces
Volunteer Applications
Volunteer application review, applicant details, decisions, and reviewer notes.
First created Last updated
Overview
Volunteer Applications is the review queue for people applying to volunteer positions. Reviewers use it to search the queue, inspect attendee-style applicant details, read labeled question responses, accept or reject applications, and record organizer notes.
Dashboard route
/ems/manage/volunteer-applications?id=:eventId
Inputs and controls
| Input or control | What it changes | Before using |
|---|---|---|
| Refresh | Reloads applications, departments, positions, and the current review state. | Use it before making decisions if another reviewer may be working the same queue. |
| Search | Narrows the visible list by applicant display name, username, department, or position. | Clear the search before reporting queue totals. |
| Status filter | Narrows the list by review status. | Use all statuses when auditing what already happened; use pending when doing first-pass review. |
| Bulk selection | Selects pending applications for bulk action where available. | Bulk decisions should be used only when the same decision is appropriate for every selected applicant. |
| Application row | Shows applicant name, position, department, submitted date, and review state. | Confirm the row belongs to the correct event and position before opening actions. |
| Details | Opens the full attendee-style detail view. | Read the applicant profile data and every labeled question response before deciding. |
| Review status | Chooses the decision in the action modal. | Accepted approves the application. Rejected declines it. Existing rejected applications open with rejected selected; other states default to accepted. |
| Organizer notes | Stores internal review context for the application. | Keep notes factual: why the person was accepted, why they were rejected, or what a later lead should know. |
| Apply status | Saves the selected accepted or rejected state and organizer notes. | Confirm the decision matches the position’s staffing need before applying. |
| Cancel or close | Leaves the action modal without saving. | Use this if the details do not support the intended decision yet. |
What reviewers see
The details view combines the applicant identity, profile photo when available, username, position, department, application status, and submitted answers. Question labels come from the position’s application form, so unclear questions should be fixed in Volunteer Positions before more applicants use the form.
Accepted applications can feed later staffing work. Rejected applications remain part of the event’s review history and can be reviewed again with updated notes when needed.
Only an accepted application or an explicit manual volunteer assignment grants attendee-side roster visibility. Pending and rejected applicants must not receive shift rows, locations, or tracking controls from either the API or regosite. Changing an accepted application to rejected removes that entitlement; keep any reviewer explanation in organizer notes rather than exposing roster details to the attendee.
Flowchart context
Active Event Workflow checks Volunteer Applications when reviewing people and program operations. Accepted applicants may later appear in Staff Roster and Live Shift Tracker.
Common mistakes
Do not accept applicants without confirming the position still needs people. Over-acceptance creates staffing confusion and subsidy risk.