Volunteer Program Agreements & Documentation for Nonprofits: WhatExecutive Directors and Boards Need to Get Right
Volunteers are essential to nonprofit work. They staff events, serve clients, support programs, help with fundraising, and often become some of an organization’s most committed ambassadors. But when volunteer programs run informally, they also create legal and governance risk.
A poorly documented volunteer relationship can create wage-and-hour exposure, anti-discrimination issues, negligent screening claims, background check compliance problems, confidentiality concerns, insurance gaps, data security issues, and audit questions. The line between volunteer service and compensable work depends on how the relationship actually operates, not what the organization calls it. The same substance-over-label principle can affect discrimination risk when a volunteer role comes with meaningful benefits, serves as a path to paid work, or looks too much like a staff position. This article focuses on the next step: the documentation system nonprofits need once they understand those risks.
The right question is not “Do we have a volunteer form?” The better question is: “Do we have a volunteer documentation system that accurately reflects how our program works?”
1. A Volunteer Agreement Is Not the Same Thing as a Volunteer Policy
Many nonprofits use the terms “volunteer policy,” “volunteer handbook,” “volunteer waiver,” and “volunteer agreement” interchangeably. They should not.
A policy explains rules. A handbook gives operational guidance. A waiver may address specific liability issues. A signed agreement documents the relationship between the organization and the volunteer. Those documents may overlap, but they do not do the same job.
A well-drafted volunteer agreement creates a record that the individual is serving voluntarily, without expectation of compensation, and within a defined role. It should also address confidentiality, intellectual property, use of name or image, safety expectations, anti-discrimination and anti-harassment expectations, and any required releases or acknowledgments. That record matters if there is a wage claim, discrimination complaint, injury, data incident, funder review, insurance issue, or dispute over what the volunteer was authorized to do.
But a volunteer agreement is not a magic shield. If the organization treats a volunteer like an unpaid employee, uses volunteers to perform staff work, makes volunteer service a hiring pipeline, or gives the role employment-like benefits, the agreement will not cure the problem. The document has to match the program.
Volunteer-immunity statutes may protect individual volunteers, but they generally do not eliminate the nonprofit’s own exposure for negligent supervision, negligent hiring, inadequate training, poor policy design, or discrimination-related claims. Under the federal Volunteer Protection Act, individual protection generally depends on whether the volunteer acted within assigned responsibilities, was properly licensed or certified where required, and avoided willful or criminal misconduct, gross negligence, reckless misconduct, or conscious disregard for safety. Documentation helps establish those boundaries.
Waivers and releases can help, especially for higher-risk activities, but they have limits. A release may address ordinary negligence if properly drafted and signed before service begins. It generally will not protect the organization from gross negligence, recklessness, willful misconduct, or statutory claims.
2. Documentation Should Reinforce, Not Re-Argue, Volunteer Classification
Volunteer classification turns on the economic reality of the relationship, not the label the organization uses. In discrimination cases, courts may also look past the volunteer label where the role provides meaningful remuneration, credentials, benefits, or a pathway to paid work. The agreement should document the facts that support the organization’s treatment of the role, not merely recite a conclusion.
For documentation purposes, the agreement should confirm that the person is serving freely, without expectation of compensation, and for charitable, civic, religious, or humanitarian reasons. It should also make clear that the role does not replace paid staff work, promise employment, or create a hiring preference unless the organization has intentionally created and documented that pathway.
This is where many templates fall short. A form that says “I am a volunteer” may be less useful than a role description and agreement that show why the role is voluntary, limited, and distinct from compensable work.
The point is not to re-litigate classification in the agreement. The point is to create contemporaneous records that support the organization’s classification decision if it is later questioned.
3. The Core Documents Most Volunteer Programs Need
Most established volunteer programs need more than one form. The basic documentation suite usually includes—
volunteer application;
volunteer role description;
volunteer services agreement;
volunteer policy or handbook;
background check authorization, where screening is required;
confidentiality and data protection acknowledgment;
photo, video, and media release, where applicable;
training, orientation, and safety acknowledgments;
incident reporting and recordkeeping protocol; and
health, safety, reimbursement, conduct, and dismissal procedures.
Each document has a job. The application collects baseline information. The role description defines scope. The services agreement documents the relationship. The policy and handbook communicate recruitment, supervision, reimbursement, conduct, safety, and dismissal rules. The background check authorization supports screening compliance. The confidentiality acknowledgment protects sensitive information. Training acknowledgments show the organization communicated the rules. The recordkeeping protocol makes the file usable when it matters.
The role description deserves special attention. It is one of the organization’s best tools for showing that a volunteer role is distinct from paid staff work. It also matters for liability because federal volunteer-immunity protection generally depends, in part, on whether the volunteer acted within assigned responsibilities. A clear role description shows what was authorized — and what was not. If it sounds like an unpaid job description, that is a warning sign. If it mirrors an employee’s duties, that is a bigger one.
4. Background Checks Require Their Own Compliance Process
Background checks are often treated as a volunteer management best practice. For many organizations, they are also a legal compliance issue.
When a nonprofit uses a third-party screening company, the Fair Credit Reporting Act may apply. Organizations using consumer reports for personnel decisions must provide proper disclosure, obtain written authorization, and follow the required adverse-action process before rejecting an applicant based on the report. For volunteer programs, the safest approach is to treat third-party background checks with the same procedural care used for employment screening.
The authorization should not be buried inside the volunteer agreement. Bundling it into a general form can create consent problems where the law requires a clear, standalone disclosure. The organization should also document why a particular level of screening is required for the role.
The role should inform the level of screening. Volunteers working with children, elderly persons, individuals with disabilities, patients, clients in crisis, money, vehicles, or confidential records generally require more rigorous screening than low-risk, supervised volunteers. Depending on the role, that may include an application, interview, reference checks, criminal record review where permitted, driving record review, credential verification, periodic renewal, or medical clearance.
State and local laws may add limits on when an organization may ask about criminal history and how it evaluates screening results. Multi-state nonprofits should not assume that unpaid status removes those rules from the analysis.
5. Jurisdiction Matters for Documentation
As always, Federal law sets the floor. State and local law often determine what the documentation needs to address.
In Massachusetts, volunteer documentation is part of broader governance and risk management. Massachusetts law provides targeted immunity for uncompensated officers, directors, and trustees of charitable organizations, and separate protections for certain uncompensated volunteers in nonprofit sports programs. Those protections have limits, including exclusions for intentional harm, gross negligence, automobile-related claims, and certain primarily commercial activities. Programs involving youth, health information, donor information, financial systems, or other personal information should also account for Massachusetts data security requirements.
In New York, nonprofits generally rely on the federal Volunteer Protection Act for general volunteer immunity because New York does not have a broad state volunteer protection statute comparable to Connecticut’s. New York has targeted protections in narrower settings, including volunteer firefighters and certain recreational-use contexts. Classification remains fact-specific: a signed volunteer agreement or letter of understanding is not dispositive of employment, unemployment insurance, or workers’ compensation status. Compensation, direction, control, and the actual structure of the relationship matter.
In DC, volunteer agreements should account for federal wage-and-hour principles and should not suggest that volunteers fall outside ordinary nondiscrimination, harassment, confidentiality, or safety expectations because they are unpaid. DC’s volunteer-immunity framework also depends on insurance, including statutory coverage thresholds and any applicable exception. The DC Human Rights Act is broad, and the volunteer question is not always cleanly resolved where the relationship looks more like work than service.
In Connecticut, the federal Volunteer Protection Act applies, and Connecticut also provides separate statutory immunity for uncompensated directors, officers, and trustees of certain tax-exempt nonprofits when they act in good faith and within policy or decision-making responsibilities. That protection does not extend to reckless, willful, or wanton misconduct. Connecticut also has targeted protections for volunteer firefighters, ambulance members, and trained volunteers rendering emergency assistance. The applicable framework depends on the person’s role, the conduct at issue, and whether the claim is against the individual volunteer or the organization.
The practical point is simple: state law does not change the need for documentation, but it can change what the documentation needs to prove. A national template may be a useful starting point. It is rarely the finish line for a multi-state nonprofit.
6. Confidentiality, Intellectual Property, and Data Protection
Volunteer programs increasingly involve access to sensitive information, including donor lists, client records, student information, health-related information, employee information, financial data, internal strategy, and program materials.
A confidentiality clause should match the role. A greeter at a public event does not need the same data access terms as a volunteer working with client files or donor records. If volunteers use personal devices, access cloud systems, communicate with clients, or handle personal information, the organization should address access limits, password practices, document storage, return or deletion of records, and reporting obligations for suspected data incidents.
Intellectual property also deserves attention. Volunteers may create training materials, photographs, curriculum, social media content, research, templates, or program tools. Without clear ownership language, the organization may not have the rights it assumes it has, especially where volunteer-created materials become part of a program model, grant deliverable, publication, or website.
Healthcare, youth-serving, shelter, and congregate-care programs may also need role-specific privacy training, medical clearance records, or other onboarding documentation before service begins.
These provisions should be in an operative agreement signed before service begins. A later acknowledgment may help, but it is weaker than front-end documentation that clearly states the volunteer’s obligations and the organization’s rights.
7. Employees, Board Members, and Other Dual Roles Need Separate Paper Trails
Employees, board members, interns, former staff, and other dual-role participants create risk when their volunteer service overlaps with another relationship to the organization.
The documentation rule is straightforward: do not blend roles. If someone is both an employee and a volunteer, keep separate records for each relationship. If a board member also performs operational work, document when the person is acting as a director and when the person is serving in a separate operational capacity. If volunteer service is used as a hiring pipeline, document that process intentionally and apply it consistently.
The same principle applies to interns, fellows, and former staff. The file should make the capacity clear, identify the applicable rules, and avoid using a volunteer agreement to paper over a relationship that needs a different legal framework.
A clean paper trail will not fix a misclassified relationship, but it helps show that the organization recognized the distinction and managed each role intentionally.
8. Recordkeeping and Audit Readiness
Documentation only helps if the organization can locate it, rely on it, and explain it.
A volunteer file should generally include the application, role description, signed agreement, required authorizations, background check documentation, training records, confidentiality or data acknowledgments, incident reports, and separation records where applicable. Those records should be stored consistently, with access limited to personnel who need them.
Retention should be intentional. A practical baseline is to retain executed releases and related program records for five to seven years after service ends, unless a grant, contract, insurance requirement, statute, or pending claim requires more. Some records should be kept long enough to defend against employment, tort, insurance, or regulatory claims. Others, especially background check reports and sensitive personal information, should not be kept indefinitely. A “save everything forever” approach creates its own risk.
Electronic signatures are generally appropriate, but the organization should preserve the audit trail: who signed, what they signed, when they signed it, and whether the signed version matches the current program documents. That matters during funder due diligence, insurance review, accreditation, litigation, and regulatory inquiries.
Insurance review should be part of the documentation process. Confirm whether general liability, D&O, accident medical reimbursement, abuse and molestation, auto, cyber, and workers’ compensation policies apply to volunteers. This is especially important in DC, where volunteer-immunity rules are tied to liability insurance, and in New York and Connecticut, where volunteers may fall outside default workers’ compensation coverage unless the organization has arranged alternative protection.
9. When a Template Is Enough, and When It Is Not
Templates can be useful. For a small, single-state nonprofit using a few volunteers for low-risk, supervised activities, a well-designed template may be a reasonable starting point.
Templates are usually not enough where the organization has employees who also volunteer, operates in multiple states, serves children or vulnerable adults, runs background checks, gives volunteers access to donor or client data, uses volunteer-created content, provides stipends or reimbursements, offers meaningful benefits, uses volunteer roles as a hiring pipeline, or relies on volunteers for core program delivery.
In those situations, the question is not whether the form looks complete. The question is whether the documentation system matches the organization’s legal risk profile.
Practical Next Step: Audit the Program Before It Expands
Before expanding a volunteer program, nonprofit leaders should audit the current documentation suite. At minimum, confirm whether the organization has:
a written volunteer policy or handbook covering recruitment, supervision, reimbursement, conduct, safety, and dismissal;
written role descriptions that distinguish volunteer work from paid staff work and avoid unintentionally creating staff-like roles;
a signed volunteer services agreement confirming the unpaid and voluntary nature of the relationship;
a clear statement of any stipend, reimbursement, benefit, credential, or hiring-pipeline feature associated with the role;
separate background check authorization and adverse-action procedures, where screening is used;
role-stratified screening procedures, including applications, interviews, reference checks, credential checks, driving record review, medical clearance where appropriate, and periodic renewal for higher-risk roles;
confidentiality, data protection, IP, and media provisions tailored to the role;
training, orientation, safety, and policy acknowledgments signed before service begins;
a process for employees, board members, interns, and former staff who also serve as volunteers;
jurisdiction-specific review for each state or locality where volunteers serve;
an insurance review confirming how the organization’s policies apply to volunteers, including workers’ compensation gaps and accident medical reimbursement coverage; and
a retention and disposal policy for volunteer records, including a five-to-seven-year baseline for executed releases and related records unless a longer period applies.
Volunteer documentation is a system, not a form. The organizations that get this right are not just protecting themselves from legal claims. They are showing staff, volunteers, funders, insurers, and board members that the program is being managed with the same care as the rest of the organization.
This article is for general informational purposes only and does not constitute legal advice. Reading this article does not create an attorney-client relationship. For advice specific to your organization's situation, contact Commonlight Legal LLP.
Alex Booker is the Managing Partner of Commonlight Legal LLP, a boutique law firm serving nonprofits in Massachusetts, DC, New York, and Connecticut. He advises executive directors and boards on employment law, governance, and general nonprofit counsel.
Before founding Commonlight, Alex adjudicated federal employment cases at the U.S. Merit Systems Protection Board, where he researched and advised on novel issues in federal personnel law, and he litigated whistleblower, wage and hour, and civil rights cases on behalf of employees at a DC employment firm. He is admitted to practice in Massachusetts and Washington, DC.