A volunteer skills inventory is a structured way to learn what people can do, what they want to learn, and how they prefer to contribute. A thoughtful inventory can help a community group match people with projects while respecting their time, privacy, and choices.
1. Decide what the inventory is for
Start with a practical purpose. For example, you might need to staff a neighborhood translation project, plan a community workshop, or find people interested in coordinating events. A clear purpose helps you ask only useful questions and explain how answers will be used.
Write a short statement before drafting the form:
We are collecting information about volunteers’ skills, interests, and availability so we can offer relevant community project opportunities. Sharing information is optional, and volunteers can update or withdraw it by contacting the project coordinator.
Adapt that statement to reflect your actual process. Do not promise confidentiality, deletion, or restricted access unless your group can reliably provide it. If responses will be shared with project leads, say so plainly.
Distinguish between three kinds of information:
- Current skills: tasks someone can do now, whether learned through employment, education, caregiving, hobbies, or community activity.
- Interests and learning goals: tasks someone would like to try, practice, or learn with support.
- Practical availability: when and how someone is able to participate, including remote, in-person, occasional, or short-term options.
These categories help avoid treating a volunteer’s past experience as an obligation to perform that work indefinitely. An inventory is a conversation starter, not a promise that someone is available for every role that fits their skills.
2. Choose a format people can use
Use the simplest format that is accessible to your volunteers and manageable for your group. A short online form can be convenient for some people; a paper form, phone conversation, or facilitated group conversation may work better for others. Offer more than one route when possible, and make sure answers from different formats are recorded consistently.
Before choosing a tool, consider:
- Can people complete it on a phone or with assistive technology?
- Can someone ask for help, dictate an answer, or respond on paper?
- Does the format work for people with limited internet access or varying literacy levels?
- Who can view responses, and can you limit access to the people who need it?
- Can a person skip questions or update an answer later?
Use plain language, short prompts, and examples. Avoid making a form depend on specialized software or requiring a long written response. If you collect answers on paper, explain who will transfer them and how originals will be stored or disposed of according to your group’s actual practices.
| Format | Useful when | Plan for |
|---|---|---|
| Online form | Volunteers can respond independently and you need consistent answers | Phone usability, screen-reader compatibility, access controls, and a non-digital option |
| Paper form | People meet in person or prefer writing by hand | Legible prompts, a private way to return it, and secure handling afterward |
| Conversation | A person prefers speaking, needs language support, or wants help identifying skills | Consent before taking notes, a neutral note-taker, and a chance to review the summary |
| Group activity | You are exploring skills together during a meeting | A way to contribute privately, since some people may not want to share in a group |
Do not assume one method fits everyone. A hybrid process usually works better than insisting that all volunteers use a single channel.
3. Write questions that surface skills fairly
People may not call their experience a “skill,” especially if they learned it outside paid work or formal training. Ask about tasks and situations rather than relying only on job titles or certificates. For instance, “Have you helped organize a family or community event?” can reveal relevant experience that a question about professional event planning might miss.
A useful inventory can include the following sections:
- Ways to contact and communicate: collect only the contact details needed to follow up, and explain who will use them.
- Skills or tasks: “What kinds of things can you help with?” Offer examples such as writing, welcoming visitors, repairing items, taking notes, interpreting, gardening, or coordinating schedules.
- Where the experience comes from: invite—but do not require—examples from work, school, family responsibilities, hobbies, or community life.
- Confidence and support: ask whether the person can work independently, prefers a partner, or wants an introduction or training.
- Interests: “What would you like to do?” and “What would you like to learn?”
- Availability and boundaries: ask about general times, preferred commitment length, location, accessibility needs relevant to participation, and tasks the person does not want to do.
- Permission to follow up: ask whether it is okay to contact them about a specific type of opportunity.
Keep questions optional where possible. Do not collect sensitive personal details just because a form has space for them. Ask about participation needs in a respectful, task-focused way—for example, “What would make this activity accessible for you?”—and explain who will see the answer. Avoid asking volunteers to disclose diagnoses, immigration status, political beliefs, or personal histories when those details are not necessary to plan the work.
Use a flexible skills list
A menu of examples makes the form easier to complete, but it can also imply that only listed skills count. Include an “Other skill or experience” option and an open response. Organize examples by activity rather than prestige:
- Communication: writing, editing, translation, interpretation, public speaking, listening.
- Organization: scheduling, welcoming, note-taking, coordinating supplies, facilitating a meeting.
- Practical work: cooking, gardening, setup, maintenance, sewing, transport coordination.
- Digital and creative work: photography, design, data entry, website updates, audio or video editing.
- Community knowledge: familiarity with local services, languages, neighborhood history, or community networks.
These examples are prompts, not a ranking. Do not assume that fluency, formal credentials, or prior nonprofit experience is required unless a particular task truly depends on it.
4. Make the process respectful and accessible
Human-rights literacy begins with recognizing that people should be able to participate without being pressured to reveal more than they choose. A person’s language, disability, age, income, or lack of formal credentials should not be used as a shortcut for deciding their worth or capability. Focus on what a task requires and what support can make participation possible.
Explain the process in a brief introduction and, if you invite people verbally, give them time to decide. Make clear that completing an inventory is voluntary and does not guarantee placement. People should be able to skip a question, describe a skill in their own words, or say that they are interested but not currently available.
Practical access steps include:
- Use readable text, clear headings, and one question at a time.
- Avoid jargon and explain terms such as “facilitation” or “outreach.”
- Provide a way to request translation or communication support where your group can offer it.
- Let people answer by phone or in person if online forms are a barrier.
- Ask about access needs for a specific activity without demanding a diagnosis.
- Offer private ways to share information that someone may not wish to discuss in a group.
If you cannot provide a requested accommodation, respond honestly and discuss alternatives with the volunteer rather than making assumptions. For example, a person who cannot attend an evening meeting might contribute asynchronously, if the project has a suitable task and the volunteer is interested.
5. Turn responses into a usable inventory
An inventory only helps if your group can find and interpret the information. For a small project, a secure spreadsheet may be enough. A larger group might use a volunteer-management system it already understands. Choose a setup that matches your capacity; a complicated database that no one maintains will quickly become unreliable.
Use consistent fields, such as:
- Volunteer name or identifier.
- Skills and experience, in the volunteer’s own terms where practical.
- Interest or learning goal.
- Support or training preference.
- Availability and preferred commitment.
- Relevant location or participation format.
- Date last confirmed and follow-up preference.
Limit access to people who need the information to coordinate volunteers. Avoid putting unnecessary personal details in notes. If you use a shared spreadsheet, review its sharing settings and avoid public links. Keep a short record of who is responsible for updates and how volunteers can correct their entry.
You can use a simple matching table to plan a project:
| Project task | Helpful skills | Support available | Volunteer preference |
|---|---|---|---|
| Welcome participants | Listening, communication, local knowledge | Pair with an experienced host | In-person, event day |
| Prepare a community handout | Writing, translation, design | Editorial review and accessible template | Short, remote task |
| Coordinate a neighborhood activity | Scheduling, organizing supplies | Shared checklist and co-coordinator | Planning plus event day |
Treat a match as a proposal. Check with the volunteer before assigning a task, and confirm the scope, time commitment, point of contact, and any training or safety arrangements relevant to the activity.
6. Match skills to community projects
Begin each project by listing its tasks, not by looking for an idealized “perfect volunteer.” Break a broad need such as “support outreach” into concrete activities: draft a flyer, distribute it at agreed locations, welcome attendees, or collect non-sensitive feedback. Clear tasks make it easier for volunteers to judge whether the work fits their skills, interests, and availability.
For each task, describe:
- What the person would do and what the task is meant to accomplish.
- Expected time and whether the work is one-time or ongoing.
- What resources, training, or partner support are available.
- Any genuine requirements, such as a language needed for a specific conversation.
- How the volunteer can decline, pause, or ask for a different task.
Use skills to broaden participation, not to confine people. Someone who has experience in bookkeeping may want to try gardening. A person with no formal title may have strong facilitation skills from organizing family or neighborhood activities. Offer options for people who want to learn, and pair them with someone who can provide appropriate guidance.
Do not treat an inventory as a substitute for project planning. A list of skills cannot establish whether a task is safe, accessible, adequately supervised, or within the group’s capacity. Plan those aspects separately with the people responsible for the project.
7. Follow up, update, and troubleshoot
After collecting responses, acknowledge them and explain what happens next. If you do not yet have a suitable project, say so rather than implying that a role is imminent. When you have an opportunity, share enough detail for the volunteer to make an informed choice and allow time for a response.
Common problems have practical fixes:
- People leave the skills question blank. Add examples, ask about everyday tasks, and allow a conversation instead of demanding a polished answer.
- The same few people get every assignment. Review how opportunities are offered. Invite interest from people whose skills are less visible, and distribute learning opportunities with consent.
- Responses become outdated. Ask volunteers periodically whether they want to update their information. Do not assume availability continues indefinitely.
- The list is too broad to use. Add project-specific task descriptions and ask about interest, support needs, and current availability rather than adding more skill labels.
- A volunteer feels pressured by a match. Reiterate that the inventory is not a standing commitment. Offer a straightforward way to decline or change direction.
- People cannot access the form. Provide an alternate method, check the form on a phone, and simplify the language and layout.
Set a review rhythm your group can sustain, such as checking entries when a new project begins or inviting people to confirm their preferences at a regular volunteer meeting. Keep only the information you still need, following your group’s stated handling practices. If someone asks to correct or remove their information, respond through the process you described.
8. A ready-to-adapt invitation
You can use this short message when inviting people to participate:
We are planning upcoming community projects and would like to learn what kinds of activities you enjoy, what experience you can share, and what you would like to learn. This optional inventory helps us suggest relevant opportunities; it does not commit you to a role. You can skip questions, answer by [available alternatives], or update your preferences later. Your responses will be seen by [who will access them] and used for [specific purpose]. Contact [project contact method] if you have a question or want to change your response.
Replace the bracketed sections with accurate details before sending. Then review the inventory from a volunteer’s perspective: Is the purpose clear? Can someone decline? Are the questions relevant to real tasks? Is there a non-digital option? Can people describe skills in their own words? If the answer to those questions is yes, your group has a practical starting point for connecting people with community work they choose to do.