Table of contents
Published October 27, 2026.
Tier the roles before choosing checks
A volunteer who sorts donated books and a volunteer who drives a van of children require different screening. Write a short matrix that maps role risk to required checks, references, training, and supervision. The matrix should be approved by leadership and reviewed when a role changes, not rebuilt for every applicant.
Make the application collect only what the check needs
Ask for legal name, contact details, role, availability, and the consents required for the selected checks. Do not collect a social security number on a general volunteer form. If a background check requires sensitive identifiers, route the applicant to the vendor's secure flow and record only the result and the date.
Hand off to the vendor with a complete packet
The screening vendor needs the applicant's consent, identity details, and the package selected for the role. Send one packet, log the send time, and record the vendor reference number. A packet that arrives incomplete restarts the clock and leaves the coordinator explaining a delay that was avoidable.
Record reference checks as evidence
A reference call should produce a dated note with the questions asked, the relationship to the applicant, and the factual answers. Avoid writing impressions as if they were facts. If a reference cannot be reached, record the attempts and route the decision to the program lead rather than marking the check complete.
Hold the first shift at a named gate
The scheduler should not be able to book a first shift until the screening record shows every required result. Put the gate in the scheduling tool, not in a coordinator's memory. If the role requires a vehicle record or a credential, that check has its own expiry date and its own gate.
Handle expired and renewed checks
Some checks expire annually or when a volunteer changes roles. Keep the expiry date in the record and run a monthly report of checks expiring in the next sixty days. Renewal is a new result, not an extension typed into the old row.
Separate screening records from volunteer communications
The volunteer newsletter, event roster, and public profile should never expose screening details. Store results in a restricted folder with access limited to the program lead and HR. Share only the status needed to schedule, such as cleared for the role on a given date.
A youth program example
A weekend tutor completes the application and references but the background check is still pending when the first session is scheduled. The gate blocks the assignment, the coordinator tells the volunteer the start date is pending, and the program lead offers a non-direct role for the first session. The record shows why the delay happened and who approved the temporary assignment.
Retention and cleanup
Keep screening records only as long as the retention schedule requires, then destroy them on a documented date. Do not keep rejected applicants' sensitive data in a shared drive indefinitely. A clean retention routine reduces both privacy risk and the chance that an old result is mistaken for a current clearance.
- Role risk tier
- Required checks and expiries
- Vendor reference
- Reference notes
- First-shift gate
- Retention date