Volunteer Reference Check: A Practical Coordinator Guide
Run a defensible volunteer reference check step by step. Covers consent, sample questions, red flags, documentation, and FCRA-friendly screening workflows.
On this page
It's Wednesday evening at a youth shelter, and the coordinator is halfway through a shift when a parent asks a simple question: “Were his references checked before he started?” The coordinator opens the volunteer file. The application is there. The background report is there. The two reference lines are listed, but nobody ever dialed them.
This happens because intake moves quickly, a background report feels thorough, or a missed task never triggers an alert. A volunteer reference check then becomes a checkbox instead of a conversation. That gap matters because a database can provide a record snapshot, while a reference can describe reliability, judgment, boundary behavior, and how someone handled pressure over time.
A national survey found that more than 90% of nonprofits interviewed volunteers, but only about three-fourths contacted references, and one in three said some volunteers received no screening at all. Among organizations with fewer than 10 volunteers, just 63% checked references and 57% conducted any background check (Nonprofit Quarterly's summary of the national survey). Later industry surveys described a more formal screening environment, with 92% of volunteer organizations conducting criminal record checks in a 2018 survey and 98% reporting background checks in a 2020 report (Points of Light's volunteer screening trends). The pattern is clear: organizations may adopt database screening while still leaving the human reference layer unfinished.
Table of Contents
- The Moment a Coordinator Realizes the Reference Never Got Called
- Consent, Privacy, and the Disclosure You Actually Need Before Calling
- Reference Questions That Work for Different Volunteer Roles
- Red Flags Worth Trusting and False Alarms to Ignore
- Fitting Reference Checks Into a Complete Screening Workflow
- FCRA, Adverse Action, and Periodic Re-Screening Explained
- Your One-Page Reference Check Playbook
The Moment a Coordinator Realizes the Reference Never Got Called
The uncomfortable part isn't that the coordinator made one mistake. The uncomfortable part is that the file looks complete at first glance. Every document has a place, every box appears to have been addressed, and the missing calls remain invisible until someone asks for proof.
In youth programs, shelters, and church teams, references often reveal information that a criminal record search can't. A former supervisor may remember repeated no-shows, poor judgment during conflict, or a pattern of ignoring boundaries. A database won't tell you whether a volunteer accepted correction calmly, disclosed a mistake, or became defensive when a participant needed extra care.
Practical rule: Treat the reference call as a behavioral interview conducted with someone who has already observed the applicant in another setting.
A reference isn't a guarantee of safety. It can be incomplete, overly generous, or based on a shallow relationship. Still, a structured call gives the coordinator another opportunity to test consistency between the application, interview, and screening results. A glowing general endorsement with no examples deserves a different interpretation from a detailed account of how the applicant handled an upset client or a missed deadline.
Build the decision before the applicant arrives
The defensible process starts with a role-risk matrix, not with a phone in your hand. Assign each volunteer role a risk level based on access, supervision, contact with vulnerable people, transportation, money, and the consequences of poor judgment.
A low-contact event greeter may need a lighter check than an overnight shelter host. A youth driver or volunteer handling donations needs questions that address boundaries, responsibility, and decision-making under pressure. The matrix should determine the number and type of references, the background screening required, the escalation path, and the re-screening policy.
A workable policy file contains:
- Role tier: Low, medium, or high risk, with the reasons recorded.
- Consent record: A standalone disclosure and written authorization completed before contact.
- Question set: A standard script crafted to the duties of that role.
- Call log: Date, time, contact method, independently verified contact details, questions asked, and answers recorded promptly.
- Disposition: Advance, pause for clarification, change role, or decline, with the reason tied to written criteria.
Nonprofit guidance recommends using the same standard script for applicants in the same role, asking position-related questions, avoiding leading prompts, and recording answers in writing (VolunteerHub's reference-check guidance). That consistency protects the organization from making one applicant prove more than another applicant for reasons unrelated to the role.
What reference checks catch that other layers miss
| Screening Layer | What It Confirms | What It Misses |
|---|---|---|
| Application | Experience, availability, stated qualifications, and role interest | Whether the applicant's account matches observed behavior |
| Interview | Communication, motivation, and responses to scenarios | Long-term reliability and conduct outside the interview |
| Background check | Records returned through the selected screening process | Everyday judgment, attendance, boundaries, and response to feedback |
| Reference check | Observed reliability, temperament, discretion, and work habits | Unreported or unknown conduct, weak reference relationships, and risks the reference chooses not to disclose |
| Training and supervision | Performance after placement and response to policy | Conduct before the volunteer enters the program |
A reference call often takes only a short block of coordinator time, but it has to be scheduled, documented, and reviewed. It's one of the most useful control layers precisely because organizations can't outsource the judgment entirely to a database.
The coordinator in that shelter didn't need a more complicated form. She needed a closed loop: consent, a role-specific script, a call log, an escalation rule, and a final disposition. That's how a missed reference becomes a process failure the organization can prevent rather than a surprise discovered during a parent conversation.
Consent, Privacy, and the Disclosure You Actually Need Before Calling
Call references only after the applicant has given clear permission. The safest operational approach is a standalone disclosure and authorization, separate from the general volunteer application, written in plain language and signed before anyone contacts a reference.
A practical form can say:
I authorize [organization name] to contact the references I provide to assess my suitability for the volunteer role of [role name]. I understand that the organization may ask role-related questions about my reliability, judgment, conduct, and experience. I understand that providing a reference is voluntary and that the organization will record the response for its screening and placement decision.
Adapt the language to your counsel's instructions and local requirements. The important distinction is that the applicant can see what the organization plans to do. A buried checkbox that says “I agree to screening” doesn't explain who may be contacted, why the call is being made, or how the information will be used.
Set a narrow privacy boundary
Use only the references the applicant supplied, and contact only the details listed or independently verified through a reliable source. Don't cold-call an applicant's current supervisor because you found that person online. If the applicant hasn't authorized that contact, the coordinator risks exposing the volunteer's application and damaging trust.
Ask questions tied to the role. Don't seek medical details, family information, protected characteristics, or gossip about unrelated personal matters. The reference check should assess suitability for the duties the volunteer will perform, not invite a general character investigation.
Before the first call, place these items in the same file:
- Signed disclosure and authorization
- Reference names, relationships, and contact details
- Record of any permission limits or unavailable references
- Call notes and follow-up messages
- Screening partner correspondence, if a third party is used
- Final decision and reason
That file should show what the applicant authorized, what the coordinator asked, what the reference said, and how the organization reached its decision. A refusal to provide a reference isn't automatically disqualifying, but it should be recorded rather than bypassed.
Reference Questions That Work for Different Volunteer Roles
A useful question changes with the volunteer's access and responsibility. “Was this person good?” invites polite praise. “Would you rehire this person for a role requiring dependable attendance and calm judgment?” forces the reference to connect the answer to observable behavior.
Use the same core structure for each applicant in a tier, then adjust the examples to the role. The volunteer character reference guide can help coordinators build a repeatable approach instead of improvising every call.
Low-contact roles
For food sorters, event greeters, reception helpers, and supervised activity assistants, focus on basic dependability and cooperation:
- How do you know the applicant, and in what setting did you observe their work?
- What responsibilities did the applicant handle?
- How consistently did they arrive as agreed?
- How did they respond when instructions changed?
- Can you describe a time they worked with people they didn't know?
- How did they respond to correction?
- Did they complete assigned tasks without repeated reminders?
- Were there any concerns about honesty, respect, or safe conduct?
- What kind of supervision helped the applicant perform well?
- Would you rehire or invite the applicant back for a similar role, and why?
Medium-contact roles
For mentors, shelter intake volunteers, food pantry leads, and volunteers who regularly interact with clients, ask for behavior under pressure:
- What contact did the applicant have with clients, guests, students, or service users?
- How did they handle confidential or sensitive information?
- Tell me about a time the applicant dealt with an upset person.
- How did the applicant respond when a boundary or policy limited what they could do?
- Did they recognize when an issue needed to be escalated?
- How dependable were they during demanding periods?
- How did they react to feedback from a supervisor?
- Did you ever see them make a mistake, and what did they do next?
- Were there concerns about favoritism, inappropriate familiarity, or poor discretion?
- Would you recommend the applicant for this role, and is there anything you'd want the coordinator to supervise closely?
High-contact roles
For youth drivers, overnight hosts, one-to-one mentors, and finance volunteers, the questions should test judgment, access, and accountability:
- What responsibilities did the applicant hold when they worked without close supervision?
- How did they handle one-to-one contact with a client, child, or vulnerable person?
- Can you describe a time they faced a safety, boundary, or confidentiality issue?
- Did they follow procedures when doing so was inconvenient?
- How did they handle transporting people, controlling funds, or holding keys and access credentials?
- Did they ever conceal, minimize, or delay reporting a mistake?
- How did they respond when a person challenged their authority?
- Were there any concerns about private communication, favoritism, or boundary crossing?
- What safeguards or supervision would you put around this applicant?
- Would you place the applicant in this role again, and what reservations, if any, would you have?
| Reference Question | Low-Contact Role | Medium-Contact Role | High-Contact Role |
|---|---|---|---|
| Attendance and follow-through | Essential | Essential | Essential |
| Response to correction | Useful | Essential | Essential |
| Client or participant boundaries | Basic | Essential | Critical |
| Confidentiality and discretion | Useful | Essential | Critical |
| Judgment under pressure | Useful | Essential | Critical |
| Unsupervised responsibility | Rarely needed | Sometimes needed | Essential |
| Money, driving, or access control | Not applicable | Role dependent | Essential when applicable |
| Rehire or recommend question | Essential | Essential | Essential |
The rehire question earns its place because it requires a decision, not a compliment. Follow it with, “What makes you say that?” Specific examples are more useful than a string of adjectives.
Red Flags Worth Trusting and False Alarms to Ignore
Reference responses usually fall into three buckets: hard stops, soft warnings, and false alarms. The coordinator's job isn't to punish awkward communication. It's to distinguish information that affects role safety from noise that merely reflects personality or an imperfect reference relationship.
Hard stops
An unexplained disappearance from a prior commitment matters more when the applicant described that same role as a successful long-term placement. A credible report of a boundary breach, dishonesty about dates, or concealed responsibility should pause placement while the coordinator follows the written policy.
Don't convert one concerning sentence into a final decision without checking context. Record the exact answer, ask a neutral follow-up, and compare it with the application and interview.
Soft warnings
Reluctance to recommend can mean a serious concern, a weak relationship, or a reference who doesn't feel comfortable speaking freely. Ask, “What would you want a supervisor to know before placing this person in the role?” A vague answer about judgment deserves clarification, especially for unsupervised or youth-facing work.
Use a consistent hesitation scale:
- No concern recorded: Specific, role-relevant examples and a clear recommendation.
- Clarification needed: Limited knowledge, vague answers, or uncertainty about the applicant's duties.
- Escalate: Reluctance to recommend, conflicting dates, or a concern tied directly to role duties.
- Pause or decline under policy: Credible information about dishonesty, boundary violations, or conduct that conflicts with the role's written criteria.
False alarms
A nervous reference may stumble through an answer because they're unfamiliar with screening calls. Slow communication may reflect scheduling problems rather than reluctance. A personality clash doesn't necessarily predict poor conduct with shelter guests or youth participants.
Consistent praise with no specifics can also be weak evidence. It may indicate a strong relationship, but it may just mean the reference barely observed the applicant. Record it as limited information, not as a positive finding.
A hesitation is a signal to investigate, not a verdict. The record should show what you asked, what the reference knew, and why the answer changed the next step.
Fitting Reference Checks Into a Complete Screening Workflow
A reference call works best as part of a layered funnel. It shouldn't replace the application, interview, identity review, background check, training, or supervision.
Use this sequence:
- Application: Confirm experience, availability, role interest, and supplied references.
- Consent: Obtain the standalone disclosure and written authorization.
- Reference check: Ask the role-specific questions and document the call.
- Background check: Order the screening appropriate to the role and jurisdiction.
- Training: Complete role-specific safeguarding, confidentiality, safety, and supervision requirements before placement.
A soft red flag should trigger a pause, not an automatic background-check order or automatic rejection. Ask a follow-up, obtain another reference when policy allows, compare the answer with the application, and escalate to the person responsible for screening decisions. If the issue affects a role-specific criterion, the organization should document whether it changed the role, required additional supervision, or ended the application.
When a screening credit was purchased before a material discrepancy made the applicant ineligible, check the provider's refund policy and record the reason for any refund. Don't order unnecessary searches because a reference call felt uncomfortable.
Keep one audit trail
Use a handoff form when a coordinator sends information to a screening partner:
- Applicant name and internal application identifier
- Role and assigned risk tier
- Consent completion date
- Checks requested and reason for each
- Reference outcome, summarized without unnecessary sensitive details
- Specific discrepancy requiring review
- Coordinator name and timestamp
- Required return path for the report and decision
The partner needs the context necessary to run the authorized screening, not every detail from a confidential reference conversation. Store the reference notes, screening report, decision criteria, and any disposition notices under the same applicant record with controlled access.
Organizations also benefit from treating screening as part of broader community-building volunteer practices. A safe process should support volunteers after onboarding through clear expectations, supervision, communication, and recognition, not rely on one call to carry the entire safeguarding burden.
For a reusable policy framework, coordinators can start with the volunteer background check policy generator and then adapt the output to their roles, jurisdiction, and counsel's guidance.
An explanatory walkthrough can help staff understand how the layers fit together:
FCRA, Adverse Action, and Periodic Re-Screening Explained
The Fair Credit Reporting Act can apply when a third-party screening company prepares a consumer report for a volunteer decision, particularly when the organization uses that report to decide whether someone may serve. Don't assume unpaid status removes every compliance obligation. Ask the screening provider and qualified counsel how the rules apply to your structure, role, and intended use.
The coordinator should know which documents must exist before a report is ordered and which artifacts arrive from the screening partner.
| Trigger | Coordinator Keeps on File | Screening Partner Provides |
|---|---|---|
| Third-party report will support a volunteer decision | Standalone disclosure and written authorization | Report prepared under the provider's process |
| Organization needs a permissible purpose | Role, application, and screening rationale | Confirmation or workflow record associated with the order |
| Report may lead to denial or role restriction | Review notes and consistent decision criteria | Pre-adverse-action materials or process guidance, where provided |
| Organization makes a final negative decision | Final decision, date, and notice record | Final adverse-action workflow or notice support, where provided |
| Applicant disputes information | Dispute correspondence and pause record | Reinvestigation and updated report, when applicable |
Before ordering a report, use a standalone disclosure, obtain written authorization, and ensure the organization has a permissible purpose. If information may lead to declining the applicant, provide the required pre-adverse-action notice and the applicable report and rights information, allow the required opportunity to respond, then issue a final adverse-action notice if the decision remains negative. The FCRA compliance guide for nonprofits offers a practical reference point, but it shouldn't replace legal review.
Re-screen by role, not habit
A single onboarding check doesn't prove that a volunteer's circumstances remain unchanged. Set a written cadence based on access and risk. A practical internal policy might use annual review for youth-serving and cash-handling roles, every two years for mid-tier roles, and every three years for low-risk administrative roles, with the schedule approved for your program rather than treated as a universal legal rule.
Review the policy quarterly. Update it when a role changes, a safeguarding incident exposes a gap, a provider changes its workflow, or local requirements change. Record consent and disclosure steps again when the process requires a new report.
Your One-Page Reference Check Playbook
Print this page and keep it beside the onboarding workstation. It turns a good policy into a repeatable action.
Tier the role
| Volunteer Role | References Required | Background Check Depth | Risk Level |
|---|---|---|---|
| General supervised support | 1 | None or organization-approved basic review | Low |
| Youth mentor | 2 | Basic or role-required screening | Medium |
| Finance, driving, or unsupervised youth role | 3 | Enhanced, role-appropriate screening | High |
These are policy examples, not universal legal requirements. Match them to actual access, supervision, and local rules. Nonprofit guidance recommends at least two references for many volunteer roles and considering more for higher-risk positions (volunteer reference-checking guidance).
Use the compact script
- Open: Identify yourself, the organization, the role, and the applicant's permission for the call.
- Ask: What duties did the applicant perform?
- Test: How reliable were they when plans changed?
- Probe: How did they handle correction, conflict, confidentiality, and boundaries?
- Verify: Did the applicant complete responsibilities without repeated reminders?
- Decide: Would you rehire or recommend them for this role, and why?
- Close: Is there anything you'd want supervised closely before placement?
Complete the file
- Signed disclosure and authorization
- Role tier and required screening
- Reference relationship and independently confirmed contact details
- Date, time, script version, and written answers
- Specific examples, hesitation, and follow-up questions
- Background-check order and result
- Escalation notes and final disposition
- Training completion and re-screening date
Review the policy quarterly, and revise it after a safeguarding incident, a role redesign, or a compliance workflow change. The coordinator should be able to open any file and explain not only what was checked, but why that level of checking matched the volunteer's duties.
If your organization needs a more consistent way to collect references alongside volunteer screening, VolunteerBadge offers configurable reference collection and FCRA-oriented background-screening workflows that can keep authorization, results, and follow-up records together. Visit VolunteerBadge to review how its reference and screening tools could fit your role-risk matrix and onboarding process.
