Plan the Review of Community Event Volunteer Applications

To review volunteer applications fairly and without losing track of anyone, settle five things before the first application arrives. First, name who handles intake, who reviews and who decides exceptions. Second, have the event owner approve the selection criteria and any eligibility or screening requirements. Third, confirm what applicant information reviewers may see and how it is protected. Fourth, keep one register that records each application's evidence, status and decision reason. Fifth, send every applicant a clear decision notice. This guide covers the stage from receiving an application to notifying the applicant. Acceptance hands the volunteer to whoever allocates shifts. It does not assign a shift or complete onboarding.

Decide who owns each part of the review

• Intake owner: receives applications, gives each one a reference, checks that the requested information is present and sends clarification requests.
• Reviewer: assesses each complete application against the approved criteria, records evidence for each criterion and proposes a decision with a reason.
• Exception decision-maker: resolves eligibility or screening questions the reviewer cannot settle, and any case that falls outside the criteria.
• Event owner: approves the criteria and requirements before review starts, and confirms the privacy arrangements and who may access applicant information.
• Shift-allocation owner: takes over accepted volunteers. This role sits outside the review itself.

On a small event, one person may hold several of these roles. Even so, write each role down by name. When questions come up mid-review, everyone then knows who answers them.

Get the selection criteria approved before reviewing

Reviewers should apply criteria, not invent them as they go. Ask the event owner to approve a short written list before any application is assessed. Typical inputs are the roles you need filled, what each role requires, and the information the application form asks for. Keep two kinds of criteria apart. Some are organizer choices, such as preferring applicants available for a full day. Others come from outside the organizing team, such as a venue, a sport's governing body, an insurer or a law that applies where the event takes place. Where screening, age or similar eligibility rules may apply, the event owner should confirm with the responsible body what actually applies. Reviewers then treat those confirmed requirements as fixed rather than as judgment calls.

Steps from intake to decision

• 1. Confirm the roles, approved criteria and privacy arrangements described above.
• 2. Set up the review register and agree with the responsible owner who can access it and how long records are kept.
• 3. As each application arrives, give it a reference, record the received date and role interest, and set the status to received.
• 4. Check that the required information is complete. If anything is missing, send a clarification request and set the status to awaiting information.
• 5. When the application is complete, set it to under review. The reviewer then records evidence against each approved criterion.
• 6. Send any unresolved eligibility or screening question to the exception decision-maker. Do not decide it at reviewer level.
• 7. Record the decision (accepted, waitlisted or declined), the reason tied to the criteria, and the reviewer's name.
• 8. Send the decision notice and record the notification date.
• 9. Pass accepted applicants to the shift-allocation owner.

Build the review register

Field	What to record
Application reference	A short ID such as V014, used instead of the applicant's name in shared summaries
Received date	When the application came in
Role interest	The volunteer role or roles the applicant asked for
Required information complete?	Yes or no, plus what is missing
Criterion-by-criterion evidence	What the application shows against each approved criterion
Clarification requested	What was asked and when
Reviewer	Who assessed the application
Decision and reason	Accepted, waitlisted or declined, with the criterion-based reason
Notification date	When the applicant was told

Using references rather than names in shared summaries limits how much personal information is passed around. That matters most when several volunteers lead the review together.

Use a small set of statuses

• Received: logged, not yet checked.
• Awaiting information: a clarification request has been sent.
• Under review: complete and being assessed against the criteria.
• Accepted: approved and ready to hand to shift allocation.
• Waitlisted: suitable, but not needed yet.
• Declined: does not meet the approved criteria, or the role is full.

Each status should have one clear next action. Received leads to a completeness check. Awaiting information waits for a reply. Under review leads to a decision, or to the exception decision-maker if eligibility or screening is unresolved. The final three statuses lead to a notice. When an application sits in a status with no next action, it usually means someone forgot to follow up.

Record decisions and notify applicants

Write each decision reason against the criteria. For example, write "not available on event day, required for this role" rather than "not a good fit." Reasons like this stay consistent across reviewers and are easy to explain if an applicant asks. Every applicant should get a notice that states the decision and what happens next. For accepted volunteers, say who will contact them about shifts. For waitlisted applicants, explain that they may be contacted if a place opens. Record the date each notice was sent, so you can see at a glance that no one was left without a reply.

Illustrative example

Hypothetical: application V014 arrives without the requested availability. The intake owner records awaiting information and sends a clarification request. Once the applicant replies, the application moves to under review. The reviewer records evidence against each criterion, and the decision is approved as accepted. The notice is sent and dated, and V014 passes to the shift-allocation owner. Choosing a shift and onboarding happen from that point on, outside the review.

Check the plan for gaps and conflicts

• Every role in the review has a named owner, including exceptions.
• The event owner approved the criteria and any eligibility or screening requirements before the first review.
• Organizer preferences are kept separate from venue, governing-body, insurer or legal requirements.
• Access to the register and how long records are kept have been agreed with the responsible owner.
• No application sits in received or awaiting information without a follow-up.
• Every decision has a reason linked to a criterion and a reviewer's name.
• Every decided application has a notification date.
• Accepted volunteers have been passed to the shift-allocation owner, and no one assumes acceptance means a shift is assigned.